From: Frank van Maarseveen <frankvm@frankvm.com>
To: netdev@vger.kernel.org
Subject: b44 (Broadcom BCM4401 100Base-T) + NETCONSOLE + link up == lockup
Date: Tue, 22 Aug 2006 11:20:24 +0200 [thread overview]
Message-ID: <20060822092024.GA1089@janus> (raw)
Noticed this on 2.6.17.8 and it is easily reproduced. When disconnecting
and connecting the network cable from a BCM4401 100Base-T NIC the usual
"link is down" and "link is up" messages show up unless netconsole
logging is enabled upon boot using (e.g.):
netconsole=@172.17.1.65/,514@172.17.1.64/00:12:3f:85:17:52
In that case the "link is up" message no longer makes it to the virtual
console/remote machine and the machine seems to lock up. alt-sysrq-p
doesn't show anything on the VC (caps- and numlock are dead too) but
alt-sysrq-b works provided it is not preceded by too many unprinted kernel
messages (so it seems). The link does go up according to the link state
LED and there is some activity (incoming packets only I suppose).
unplugging and plugging again doesn't help.
During boot the kernel says:
kernel: netconsole: device eth0 not up yet, forcing it
kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
kernel: b44: eth0: Flow control is off for TX and off for RX.
kernel: netconsole: network logging started
--
Frank
next reply other threads:[~2006-08-22 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 9:20 Frank van Maarseveen [this message]
2006-08-22 9:36 ` b44 (Broadcom BCM4401 100Base-T) + NETCONSOLE + link up == lockup Michael Buesch
2006-08-22 9:42 ` Frank van Maarseveen
2006-08-22 12:04 ` John W. Linville
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=20060822092024.GA1089@janus \
--to=frankvm@frankvm.com \
--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;
as well as URLs for NNTP newsgroup(s).