From: Wojtek Zabolotny <W.Zabolotny@elka.pw.edu.pl>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.6.33.7 (the highest version with RT patch) does not work with b44 ethernet controller
Date: Thu, 04 Nov 2010 15:06:31 +0100 [thread overview]
Message-ID: <4CD2BDE7.2070307@elka.pw.edu.pl> (raw)
I have updated my RT-kernel to version 2.6.33.7-rt29 (the newest RT
version),
and I've found that I've lost Ethernet connectivity.
In the logs I could see messages like this:
Nov 2 09:30:28 wzlaphp kernel: b44: eth0: powering down PHY
Nov 2 09:30:28 wzlaphp kernel: b44: eth0: BUG! Timeout waiting for bit
00000002 of register 42c to clear.
Nov 2 09:30:32 wzlaphp kernel: b44: eth0: BUG! Timeout waiting for bit
80000000 of register 428 to clear.
I was not sure whether the probem is related to the 2.6.33.7 kernel
itself or with the RT patch, so I've compiled also the unpatched version
of 2.6.33.7
It is also not able to communicate with my Ethernet controller, but now
the error messages are different:
b44 0000:02:0e.0: PCI INT A disabled
b44 0000:02:0e.0: BAR 0: set to [mem 0xf4108000-0xf4109fff] (PCI address
[0xf4108000-0xf4109fff]
b44 0000:02:0e.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
ssb: Sonics Silicon Backplane found on PCI device 0000:02:0e.0
b44.c:v2.0
b44: Invalid MAC address found in EEPROM
b44 ssb1:0: Problem fetching invariants of chip, aborting.
b44: probe of ssb1:0 failed with error -22
Now I'm using the old 2.6.33.5-rt23 kernel, and everything works perfectly.
--
Wojciech M Zabolotny
wzab@ise.pw.edu.pl
next reply other threads:[~2010-11-04 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 14:06 Wojtek Zabolotny [this message]
2010-11-04 14:19 ` Thomas Backlund
2010-11-04 18:10 ` Thomas Backlund
2010-11-04 14:20 ` Eric Dumazet
2010-11-04 17:58 ` Wojciech Zabołotny
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=4CD2BDE7.2070307@elka.pw.edu.pl \
--to=w.zabolotny@elka.pw.edu.pl \
--cc=linux-kernel@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®