From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Florian Fainelli <florian@openwrt.org>,
netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: v2.6.30-rc4: b44: eth0: BUG! Timeout waiting for bit 00000002 of register 42c to clear.
Date: Fri, 15 May 2009 23:50:26 +0200 [thread overview]
Message-ID: <200905152350.27270.rjw@sisk.pl> (raw)
In-Reply-To: <38b2ab8a0905031012m5d50b68es22e3c80cfa72fd60@mail.gmail.com>
On Sunday 03 May 2009, Francis Moreau wrote:
> Hello Florian,
>
> On Sun, May 3, 2009 at 6:28 PM, Florian Fainelli <florian@openwrt.org> wrote:
> >> I got this since I updated my kernel from 2.6.29 to 2.6.30-rc4.
> >>
> >> Let me know if you need more information.
> >
> > Is this seen on a Broadcom 47xx/53xx platform or on a computer with a PCI b44
> > card ?
> >
>
> $ lspci -vv
>
> 06:01.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
> Subsystem: Acer Incorporated [ALI] Device 0090
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- 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 21
> Region 0: Memory at d2000000 (32-bit, non-prefetchable) [size=8K]
> Capabilities: <access denied>
> Kernel driver in use: b44
>
>
> Let me know if you need more details.
Can anyone please tell me what the status of this report is?
Rafael
next prev parent reply other threads:[~2009-05-15 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 16:22 Francis Moreau
2009-05-03 16:28 ` Florian Fainelli
2009-05-03 17:12 ` Francis Moreau
2009-05-15 21:50 ` Rafael J. Wysocki [this message]
2009-05-16 9:42 ` Maciej Rutecki
2009-05-16 12:28 ` Francis Moreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905152350.27270.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=florian@openwrt.org \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®