From: Alexander Wuerstlein <arw@arw.name>
To: franois romieu <romieu@fr.zoreil.com>
Cc: Hayes <hayeswang@realtek.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: r8169 hangs machine on kernel boot (bisected)
Date: Wed, 16 Feb 2011 23:34:38 +0100 [thread overview]
Message-ID: <20110216223438.GZ15516@cip.informatik.uni-erlangen.de> (raw)
Hello,
I've just tried to boot a new computer featuring a Realtek r8168 onboard
(lspci calls it Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller [10ec:8168] (rev 04), see [1])
network chip with kernel 2.6.38-rc5 and current git. Both hang on boot
just after USB device initialization and just before the kernel usually
does DHCP. The previous 2.6.37 didn't hang on boot, but showed strange
behaviour (only 10MBit half duplex on autonegotiation, tons of errors on
the switch interface[2]) which is why I tried the newer kernel in hopes
that there would be fixes.
I bisected the hang-before-dhcp bug down to commit 'r8169: magic.'
(b646d90053f887c1bc243191e693a9b02d09f2c2, also see [1]). Since the
commit really does its description justice and looks like some weird
hardware magic, I'd like to ask the wizards on how to proceed with
fixing it.
Ciao,
Alexander Wuerstlein.
[1] Kernel .config, lspci, bisect log:
http://wwwcip.cs.fau.de/~snalwuer/kernel-r8169/
[2] the Realtek-supplied r8168 doesn't show those problems
[3] feel free to criticise my Cc:, I wasn't quite sure...
next reply other threads:[~2011-02-16 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 22:34 Alexander Wuerstlein [this message]
2011-02-18 5:44 ` hayeswang
2011-02-18 17:30 ` Alexander Wuerstlein
2011-02-21 2:05 ` hayeswang
2011-02-22 12:30 ` hayeswang
2011-02-22 14:38 ` Alexander Wuerstlein
2011-02-23 22:10 ` Alexander Wuerstlein
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=20110216223438.GZ15516@cip.informatik.uni-erlangen.de \
--to=arw@arw.name \
--cc=davem@davemloft.net \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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®