mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hayeswang <hayeswang@realtek.com>
To: "'Alexander Wuerstlein'" <arw@arw.name>
Cc: "'David S. Miller'" <davem@davemloft.net>,
	<linux-kernel@vger.kernel.org>,
	"'franois romieu'" <romieu@fr.zoreil.com>
Subject: RE: r8169 hangs machine on kernel boot (bisected)
Date: Mon, 21 Feb 2011 10:05:28 +0800	[thread overview]
Message-ID: <0F5FE6E6DCB341F592AF3F0940D99EBB@realtek.com.tw> (raw)
In-Reply-To: <20110218173013.GC15516@cip.informatik.uni-erlangen.de>

 Hello,

> From: Alexander Wuerstlein [mailto:arw@arw.name] 
> Sent: Saturday, February 19, 2011 1:30 AM
> To: Hayeswang
> Cc: 'David S. Miller'; linux-kernel@vger.kernel.org; 'franois romieu'
> Subject: Re: r8169 hangs machine on kernel boot (bisected)
> 
> Hello,
> 
> On 11-02-18 15:01, hayeswang <hayeswang@realtek.com> wrote:
> > 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.
> > 
> > I have try the 8168DP and it wouldn't hang. I think I need 
> more information.
> > Could you give the information about the motherboard and 
> the version of BIOS.
> > Besides, please use the realtek driver, and dump the MAC 
> information 
> > by using "ethtool -d eth0". These are helpful to find out 
> what happens. Thanks.
> 
> I'm sorry that it took me so long to answer, I've had some 
> problems booting the machine today since the PXE-Client 
> didn't get any DHCP requests through. I'm not sure if its 
> related, the problem cleared up after I opened up the machine 
> to get the motherboard data and stuff.
> 
> Long story short, new files 'bios', 'hardware' and 'ethtool-d' in
> http://wwwcip.cs.fau.de/~snalwuer/kernel-r8169
> Bios revision is the latest available from Fujitsu for that hardware.
> Hardware numbers and serials are accurate, but the 
> inscriptions on the chips I suspected to be PHYs were very 
> hard to read, so expect errors.
> The 'ethtool-d' is especially curious, since it consists of 
> only 'FF'-bytes. The ethtool register dump was taken on a 
> 2.6.37 with r8168 as a module.

Thanks the information you provide. I would send the information to the related
people. However, the FF value of all registers is curious. I would try to
reproduce the issue first.

> 
> fujitsu.com also has some (limited, end-user-focused) 
> hardware documentation if you enter the serial number 
> 'YL7E003277' on http://ts.fujitsu.com/support/downloads.html
> 
> If you need any further information, don't hesitate to ask.
> 

 
Best Regards,
Hayes


  reply	other threads:[~2011-02-21  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 22:34 Alexander Wuerstlein
2011-02-18  5:44 ` hayeswang
2011-02-18 17:30   ` Alexander Wuerstlein
2011-02-21  2:05     ` hayeswang [this message]
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=0F5FE6E6DCB341F592AF3F0940D99EBB@realtek.com.tw \
    --to=hayeswang@realtek.com \
    --cc=arw@arw.name \
    --cc=davem@davemloft.net \
    --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®