Debian Bug report logs - #773713
broadcom-sta: Please support kernel 3.18

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Eduard Bloch" <bloch@unix-ag.uni-kl.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: broadcom-sta: Please support kernel 3.18

Date: Mon, 22 Dec 2014 15:48:02 +0100

[Message part 1 (text/plain, inline)]

Source: broadcom-sta
Version: 6.30.223.248-3
Severity: wishlist
Tags: patch

Hello Cyril,

I added the Gentoo patch for kernel 3.18 and fixed m-a support. I also
added versions to Breaks/Replaces because that didn't make sense IMHO,
the current versions can coexist. See attachment.

Regards,
Eduard.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.1+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

[kernel_3.18.support.diff (text/x-diff, attachment)]

Message #10 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Bruno Bierbaumer <list@bierbaumer.net>

To: Debian Bug Tracking System <773713@bugs.debian.org>

Subject: Re: broadcom-sta: Please support kernel 3.18

Date: Sun, 01 Feb 2015 17:19:53 +0100

Source: broadcom-sta
Followup-For: Bug #773713

Hello Cyril, Hello Eduard
I am also interested in Kernel 3.18+ support for broadcom-sta, but there seems
to be panic/lockup issue with newer Kernel versions.
There are freezes when going to suspend while downloading something or when
disconnecting the WiFi during a a file transfer.

The Gentoo bug tracker (https://bugs.gentoo.org/show_bug.cgi?id=523326#c24)
offers a fix for these freezes which is working for me. See attachment.

Regards,
Bruno

Message #15 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Bruno Bierbaumer <list@bierbaumer.net>

To: Debian Bug Tracking System <773713@bugs.debian.org>

Subject: Re: broadcom-sta: Please support kernel 3.18

Date: Sun, 01 Feb 2015 17:28:44 +0100

[Message part 1 (text/plain, inline)]

Source: broadcom-sta
Followup-For: Bug #773713

Attach the mentioned patch.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-rc6 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[linux-3.18-null-pointer-crash.patch (text/x-diff, attachment)]

Message #24 received at 773713@bugs.debian.org (full text, mbox, reply):

From: "Eduard Bloch" <bloch@unix-ag.uni-kl.de>

To: 773713@bugs.debian.org

Subject: Add kernel 4.0rc compatibility

Date: Tue, 24 Mar 2015 07:27:06 +0100

Hello,

please add the patch from
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676

Btw, I would NMU if nothing happens by the time when Linux 4 is
released.

Regards,
Eduard.

Message #29 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Tony Houghton <h@realh.co.uk>

To: Debian Bug Tracking System <773713@bugs.debian.org>

Subject: Re: broadcom-sta: Please support kernel 3.18

Date: Wed, 15 Apr 2015 15:14:08 +0100

Package: broadcom-sta-dkms
Version: 6.30.223.248-4
Followup-For: Bug #773713

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Tony Houghton <h@realh.co.uk>
To: Debian Bug Tracking System <773713@bugs.debian.org>
Subject: Re: broadcom-sta: Please support kernel 3.18
Bcc: Tony Houghton <h@realh.co.uk>
Message-ID: <20150415141153.1889.39110.reportbug@jeanette.centauri>
X-Mailer: reportbug 6.6.3
Date: Wed, 15 Apr 2015 15:11:53 +0100

Package: broadcom-sta-dkms
Version: 6.30.223.248-3
Followup-For: Bug #773713

This package seems to work fine with 3.19-trunk from experimental when
pacthed appropriately. I used patches from Ubuntu and Arch:

<https://github.com/longsleep/bcmwl-ubuntu/blob/master/debian/patches/0015-add-support-for-Linux-3.18.patch>
<https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch>

I had to change the paths to add amd64/ before src/, I guess you'll have
to make copies to do the same for i386 in the official package.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages broadcom-sta-dkms depends on:
ii  dkms  2.2.0.3-2

Versions of packages broadcom-sta-dkms recommends:
ii  wireless-tools  30~pre9-8

broadcom-sta-dkms suggests no packages.

-- no debconf information

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages broadcom-sta-dkms depends on:
ii  dkms  2.2.0.3-2

Versions of packages broadcom-sta-dkms recommends:
ii  wireless-tools  30~pre9-8

broadcom-sta-dkms suggests no packages.

-- no debconf information

Message #34 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: 773713@bugs.debian.org

Subject: NMU interdiff

Date: Wed, 29 Apr 2015 12:54:41 +0200

[Message part 1 (text/plain, inline)]

Dear Maintainer,

after a long period of inactivity, I decided to NMU this package with
the mentioned fixes and also kernel 4.0 support.

The NMU is not effective yet, the package is in the 10-day DELAYED queue
so you have lots of times to abort this action by uploading an official
version.

Interdiff is attached.

Best Regards,
Eduard.

[broadcom-sta-6.30.223.248_3-to-3.1.interdiff (text/plain, attachment)]

Message #39 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Bruno Bierbaumer <list@bierbaumer.net>

To: Eduard Bloch <edi@gmx.de>, 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 29 Apr 2015 13:14:36 +0200

Hallo Eduard,
Thank you for working on this bug!

Did you forgot this patch:
https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch
in the NMU?

Greetings,
Bruno

On 2015-04-29 12:54, Eduard Bloch wrote:
> Dear Maintainer,
> 
> after a long period of inactivity, I decided to NMU this package with
> the mentioned fixes and also kernel 4.0 support.
> 
> The NMU is not effective yet, the package is in the 10-day DELAYED queue
> so you have lots of times to abort this action by uploading an official
> version.
> 
> Interdiff is attached.
> 
> Best Regards,
> Eduard.
> 

Message #44 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Bruno Bierbaumer <list@bierbaumer.net>

Cc: 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 29 Apr 2015 14:08:41 +0200

Hallo,
* Bruno Bierbaumer [Wed, Apr 29 2015, 01:14:36PM]:
> Hallo Eduard,
> Thank you for working on this bug!
> 
> Did you forgot this patch:
> https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch
> in the NMU?

Well, kind of. I have put it back in the stack because I wanted to
understand what it does, and forgot it then :-).

But seriously, do you have an original issue report of any kind?

This issue is out of scope for this bug report and I also cannot
reproduce any crash with kernel 4.0, and if the patch is kernel 3.18
specific...  then, who cares?

Regards,
Eduard.

Message #49 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Bruno Bierbaumer <list@bierbaumer.net>

To: Eduard Bloch <edi@gmx.de>

Cc: 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 29 Apr 2015 14:49:23 +0200

Yes, there are many reports about this lockup.
Original one is here:
https://bugs.gentoo.org/show_bug.cgi?id=523326#c24

I don't think it 3.18 specific and Gentoo and Arch are definitely also
applying the patch to broadcom-sta for all kernel versions.

See:
-
https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-wireless/broadcom-sta/files/broadcom-sta-6.30.223.248-r3-linux-3.15-3.18.patch?view=markup
- https://aur.archlinux.org/packages/broadcom-wl-dkms/ (in
linux-recent.patch)

I could reproduce this bug all the time when I didn't had the patch applied.
At the moment I am running 3.19 with the patch applied and I don't see
any side effects :).

For me I could always reproduce the lock up by:
 - Starting a heavy download
 - Disconnecting the WiFi through NetworkManager or going to suspend

Message #54 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Bruno Bierbaumer <list@bierbaumer.net>

Cc: 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 29 Apr 2015 16:36:33 +0200

Hallo,
* Bruno Bierbaumer [Wed, Apr 29 2015, 02:49:23PM]:
> Yes, there are many reports about this lockup.

Maybe, but as said, it was not strictly in the scope of this bugreport.
It deserves a new bug report with important severity, IMHO.

> Original one is here:
> https://bugs.gentoo.org/show_bug.cgi?id=523326#c24
> 
> I don't think it 3.18 specific and Gentoo and Arch are definitely also
> applying the patch to broadcom-sta for all kernel versions.

Ok, sounds plausible. I would wait a couple of days, maybe $maintainer
will react and do something about it. Please remind me next weekend if
nothing happened in the meantime.

> For me I could always reproduce the lock up by:
>  - Starting a heavy download
>  - Disconnecting the WiFi through NetworkManager or going to suspend

Interesting... maybe my laptop is just too slow and this issue is
triggered by concurency problems?

Anyhow, the report above sounds convincing enough.

Regards,
Eduard.

Message #59 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Bruno Bierbaumer <list@bierbaumer.net>

To: Eduard Bloch <edi@gmx.de>

Cc: 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 29 Apr 2015 16:44:14 +0200

Hello!
I would say it fits in here, because the problem first appears with
Linux 3.18 and the bug is about supporting Linux 3.18+.
Fixing a bug that we know of as we go also sounds like a good idea.
Also just my opinion.

Sounds like a good plan to wait for any reaction by the maintainer.

Greetings,
Bruno


On 2015-04-29 16:36, Eduard Bloch wrote:
> Hallo,
> * Bruno Bierbaumer [Wed, Apr 29 2015, 02:49:23PM]:
>> Yes, there are many reports about this lockup.
> 
> Maybe, but as said, it was not strictly in the scope of this bugreport.
> It deserves a new bug report with important severity, IMHO.
> 
>> Original one is here:
>> https://bugs.gentoo.org/show_bug.cgi?id=523326#c24
>>
>> I don't think it 3.18 specific and Gentoo and Arch are definitely also
>> applying the patch to broadcom-sta for all kernel versions.
> 
> Ok, sounds plausible. I would wait a couple of days, maybe $maintainer
> will react and do something about it. Please remind me next weekend if
> nothing happened in the meantime.
> 
>> For me I could always reproduce the lock up by:
>>  - Starting a heavy download
>>  - Disconnecting the WiFi through NetworkManager or going to suspend
> 
> Interesting... maybe my laptop is just too slow and this issue is
> triggered by concurency problems?
> 
> Anyhow, the report above sounds convincing enough.
> 
> Regards,
> Eduard.
> 

Message #64 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Anders Hedlund <anders.j.hedlund@gmail.com>

To: 773713@bugs.debian.org

Cc: Eduard Bloch <edi@gmx.de>

Subject: Re: Bug#773713: NMU interdiff

Date: Sat, 2 May 2015 20:51:58 +0200

[Message part 1 (text/plain, inline)]

Hi,
I'm trying out the interdiff by Eduard but get the below error when trying
to install the new package. Do you guys know what's wrong?

DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64)
Sat May  2 20:28:51 CEST 2015
/bin/sh: line 0: [: : integer expression expected
/bin/sh: line 0: [: : integer expression expected
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
KBUILD_NOPEDANTIC=1 make -C /lib/modules/4.1.0-rc1/build M=`pwd`
make[1]: Entering directory '/home/anders/git/linux'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
Kernel architecture is X86_64
  LD      /var/lib/dkms/broadcom-sta/6.30.223.248/build/built-in.o
  CC [M]  /var/lib/dkms/broadcom-sta/
6.30.223.248/build/src/shared/linux_osl.o
  CC [M]  /var/lib/dkms/broadcom-sta/
6.30.223.248/build/src/wl/sys/wl_linux.o
  CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_iw.o
  CC [M]  /var/lib/dkms/broadcom-sta/
6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.o
  LD [M]  /var/lib/dkms/broadcom-sta/6.30.223.248/build/wl.o
  Building modules, stage 2.
CFG80211 API is prefered for this kernel version
Using CFG80211 API
Kernel architecture is X86_64
  MODPOST 1 modules
FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol 'cpu_tss'
scripts/Makefile.modpost:90: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 1
Makefile:1386: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/home/anders/git/linux'
Makefile:158: recipe for target 'all' failed
make: *** [all] Error 2

Br,
Anders


2015-04-29 16:44 GMT+02:00 Bruno Bierbaumer <list@bierbaumer.net>:

> Hello!
> I would say it fits in here, because the problem first appears with
> Linux 3.18 and the bug is about supporting Linux 3.18+.
> Fixing a bug that we know of as we go also sounds like a good idea.
> Also just my opinion.
>
> Sounds like a good plan to wait for any reaction by the maintainer.
>
> Greetings,
> Bruno
>
>
> On 2015-04-29 16:36, Eduard Bloch wrote:
> > Hallo,
> > * Bruno Bierbaumer [Wed, Apr 29 2015, 02:49:23PM]:
> >> Yes, there are many reports about this lockup.
> >
> > Maybe, but as said, it was not strictly in the scope of this bugreport.
> > It deserves a new bug report with important severity, IMHO.
> >
> >> Original one is here:
> >> https://bugs.gentoo.org/show_bug.cgi?id=523326#c24
> >>
> >> I don't think it 3.18 specific and Gentoo and Arch are definitely also
> >> applying the patch to broadcom-sta for all kernel versions.
> >
> > Ok, sounds plausible. I would wait a couple of days, maybe $maintainer
> > will react and do something about it. Please remind me next weekend if
> > nothing happened in the meantime.
> >
> >> For me I could always reproduce the lock up by:
> >>  - Starting a heavy download
> >>  - Disconnecting the WiFi through NetworkManager or going to suspend
> >
> > Interesting... maybe my laptop is just too slow and this issue is
> > triggered by concurency problems?
> >
> > Anyhow, the report above sounds convincing enough.
> >
> > Regards,
> > Eduard.
> >
>
> --
> To unsubscribe, send mail to 773713-unsubscribe@bugs.debian.org.
>

[Message part 2 (text/html, inline)]

Message #69 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: Anders Hedlund <anders.j.hedlund@gmail.com>

Cc: 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 6 May 2015 21:12:18 +0200

Hallo,
* Anders Hedlund [Sat, May 02 2015, 08:51:58PM]:
> Hi,
> I'm trying out the interdiff by Eduard but get the below error when trying
> to install the new package. Do you guys know what's wrong?

Partially...

> DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64)
> Sat May  2 20:28:51 CEST 2015
> /bin/sh: line 0: [: : integer expression expected
> /bin/sh: line 0: [: : integer expression expected

I cannot reproduce this with 4.1.0-rc2 and dkms. Might be a locale
issues. If you still get it with 4.1.0-rc2, consider reporting that as
dkms bug, IMHO.

> Kernel architecture is X86_64
>   MODPOST 1 modules
> FATAL: modpost: GPL-incompatible module wl.ko uses GPL-only symbol 'cpu_tss'

This one is reproducible. Here is the patch you are looking for:
http://marc.info/?l=linux-kernel&m=143076342107848

Both IMHO not this module's issues and fixable, not a showstopper.

Regards,
Eduard.

Message #74 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Eduard Bloch <edi@gmx.de>

To: 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 6 May 2015 21:38:35 +0200

[Message part 1 (text/plain, inline)]

On Wed, 29 Apr 2015 16:44:14 +0200 Bruno Bierbaumer <list@bierbaumer.net> wrote:
> Hello!
> I would say it fits in here, because the problem first appears with
> Linux 3.18 and the bug is about supporting Linux 3.18+.
> Fixing a bug that we know of as we go also sounds like a good idea.
> Also just my opinion.

Ok, as announced, I added the missing patch. Updated diff file attached,
just uploaded to 2-day DELAYED queue.

Regards,
Eduard.

[broadcom-sta-6.30.223.248_3-to-3.2.diff (text/x-diff, attachment)]

Message #79 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Bruno Bierbaumer <list@bierbaumer.net>

To: Eduard Bloch <edi@gmx.de>, 773713@bugs.debian.org

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 06 May 2015 21:41:10 +0200

Hi!
Thank you very much for adding this patch!

Greetings,
Bruno

On 2015-05-06 21:38, Eduard Bloch wrote:
> On Wed, 29 Apr 2015 16:44:14 +0200 Bruno Bierbaumer <list@bierbaumer.net> wrote:
>> Hello!
>> I would say it fits in here, because the problem first appears with
>> Linux 3.18 and the bug is about supporting Linux 3.18+.
>> Fixing a bug that we know of as we go also sounds like a good idea.
>> Also just my opinion.
> 
> Ok, as announced, I added the missing patch. Updated diff file attached,
> just uploaded to 2-day DELAYED queue.
> 
> Regards,
> Eduard.
> 

Message #84 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Jeremy Lainé <jeremy.laine@m4x.org>

To: 773713@bugs.debian.org, Eduard Bloch <edi@gmx.de>

Subject: Re: Bug#773713: NMU interdiff

Date: Wed, 06 May 2015 21:51:11 +0200

> > DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64) 
> > Sat May  2 20:28:51 CEST 2015 
> > /bin/sh: line 0: [: : integer expression expected 
> > /bin/sh: line 0: [: : integer expression expected 
>
> I cannot reproduce this with 4.1.0-rc2 and dkms. Might be a locale 
> issues. If you still get it with 4.1.0-rc2, consider reporting that as 
> dkms bug, IMHO. 
>

I got this same warning against kernel 3.19 so I don't think it is specific to a kernel version. Anyway it did not break my build.

Cheers,
Jeremy

Message #89 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Anders Hedlund <anders.j.hedlund@gmail.com>

To: 773713@bugs.debian.org

Cc: Eduard Bloch <edi@gmx.de>

Subject: Re: Bug#773713: NMU interdiff

Date: Tue, 12 May 2015 22:05:12 +0200

[Message part 1 (text/plain, inline)]

Hi
I've now upgraded to broadcom-sta-dkms 6.30.223.248-3.3 and running
kernel 4.1.0-rc3 and everything works just fine. Thanks!

Br,
Anders

[Message part 2 (text/html, inline)]

Message #94 received at 773713@bugs.debian.org (full text, mbox, reply):

From: Roger Shimizu <rosh@debian.org>

To: 773713@bugs.debian.org

Subject: Bug#773713

Date: Wed, 19 Sep 2018 22:20:15 +0900

control: close -1

This package works well with kernel in stable, testing, and sid.
There's no need to support old kernel, so I'm closing this ticket.

Thanks!
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Send a report that this bug log contains spam.