Bug 13328

On Friday 12 June 2009, Francis Moreau wrote:
> On Mon, Jun 8, 2009 at 9:29 AM, Francis Moreau<francis.moro@gmail.com> wrote:
> > Hello
> >
> > On Sun, Jun 7, 2009 at 11:52 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> This message has been generated automatically as a part of a report
> >> of recent regressions.
> >>
> >> The following bug entry is on the current list of known regressions
> >> from 2.6.29.  Please verify if it still should be listed and let me know
> >> (either way).
> >
> > I just pulled the 2.6.30-rc8 kernel.
> >
> > I'm giving it a test during this week and let you know if the bug
> > comes up again.
> >
> 
> It's still there on 2.6.30-rc8

On Thursday 20 August 2009, Francis Moreau wrote:
> Hello,
> 
> On Wed, Aug 19, 2009 at 10:40 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.29 and 2.6.30.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.29 and 2.6.30.  Please verify if it still should
> > be listed and let me know (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13328
> > Subject         : b44: eth0: BUG! Timeout waiting for bit 00000002 of
> register 42c to clear.
> > Submitter       : Francis Moreau <francis.moro@gmail.com>
> > Date            : 2009-05-03 16:22 (109 days old)
> > References      : http://marc.info/?l=linux-kernel&m=124136778012280&w=4
> >
> 
> It hasn't triggered on 2.6.31-rc5 after a couple of days.

On Monday 24 August 2009, Francis Moreau wrote:
> On Thu, Aug 20, 2009 at 4:52 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> > On Thursday 20 August 2009, Francis Moreau wrote:
> >> Hello,
> >>
> >> On Wed, Aug 19, 2009 at 10:40 PM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> >> > This message has been generated automatically as a part of a report
> >> > of regressions introduced between 2.6.29 and 2.6.30.
> >> >
> >> > The following bug entry is on the current list of known regressions
> >> > introduced between 2.6.29 and 2.6.30.  Please verify if it still should
> >> > be listed and let me know (either way).
> >> >
> >> >
> >> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=13328
> >> > Subject         : b44: eth0: BUG! Timeout waiting for bit 00000002 of
> register 42c to clear.
> >> > Submitter       : Francis Moreau <francis.moro@gmail.com>
> >> > Date            : 2009-05-03 16:22 (109 days old)
> >> > References      : http://marc.info/?l=linux-kernel&m=124136778012280&w=4
> >> >
> >>
> >> It hasn't triggered on 2.6.31-rc5 after a couple of days.
> >
> > Great, let's assume it's fixed, then.
> 
> Sorry but it did happen this weekend.

Hi,
I'm just looking at old regression reports...
I could not find any action on this bug besides a commit to ratelimit this message... 

Else the number of commits for the b44 driver is small. Does this issue still exist in current mainline kernels? Also I'm not clear on the implications of this issue.

I'm closing this now. If this is still an issue on current kernels, or you need more time please shout.

(In reply to comment #5)
> I'm closing this now. If this is still an issue on current kernels, or you
> need
> more time please shout.

Sorry for the late reply, but it still happens here with 2.6.35.6-48.fc14.x86_64 kernel:


[   15.449638] b44 0000:06:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[   15.449655] b44 0000:06:01.0: setting latency timer to 64
[   15.476213] b44: b44.c:v2.0
[   15.484781] b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:16:d4:54:64:8f
[   46.007862] b44 ssb0:0: eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear
[   49.706268] b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
[   49.706275] b44 ssb0:0: eth0: Flow control is off for TX and off for RX

Ok. I'm not entirely sure what the symptoms are. Do you see any negative effects besides the message in the log?

(In reply to comment #7)
> Ok. I'm not entirely sure what the symptoms are. Do you see any negative
> effects besides the message in the log?

Nope.

If this is still seen on modern kernels then please re-open/update

$ dmesg
...
[    0.000000] Linux version 3.10.38-1-lts (nobody@var-lib-archbuild-extra-i686-barthalion) (gcc version 4.8.2 20140206 (prer
elease) (GCC) ) #1 SMP Sun Apr 27 10:50:32 UTC 2014
...
[   10.430054] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00
[   10.430067] ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
[   10.430076] ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
[   10.430084] ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
...
[   10.510145] ssb: Sonics Silicon Backplane found on PCI device 0000:02:0e.0
[   10.510190] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
[   10.551779] b44 ssb0:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:14:38:10:35:01
...
[   19.457835] b44 ssb0:0 eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear
[   19.462391] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.040238] b44 ssb0:0 eth0: Link is up at 100 Mbps, full duplex
[   24.040247] b44 ssb0:0 eth0: Flow control is off for TX and off for RX

(In reply to jb from comment #10)
> $ dmesg
> ...

Additional info:
$ lspci -vv
...
02:0e.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
        Subsystem: Hewlett-Packard Company NX6110/NC6120
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
        Latency: 64
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at d000e000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: <access denied>
        Kernel driver in use: b44
        Kernel modules: b44