netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Tom Prince <tom.prince@ualberta.net>
Cc: netdev@vger.kernel.org, Edward Hsu <edward_hsu@realtek.com.tw>
Subject: Re: Fried r8169.
Date: Thu, 25 Oct 2007 23:36:45 +0200	[thread overview]
Message-ID: <20071025213645.GA2226@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20071025154438.GA2673@hermes.priv>

Tom Prince <tom.prince@ualberta.net> :
> While testing Linux v2.6.24-rc1, I noticed that my onboard r8169 had
> disappeared, and the it remained gone when I rebooted to v2.6.23 and v2.6.22,
> where it had previously worked.

[...]
> I am running x86_64 ASUS Z92T laptop (an OEM version of the A6T).
> 
> I have posted dmesg/lspci/config from v2.6.23 (and soon v2.6.24) at 
>  www.math.uwo.ca/~rprince5/r8169/
> 
> Also these appear to be the relevant log messages from when the device was
> working. Unfortunately, I didn't have the foresight to save dmesg/lspci from
> before the device disappeared.

Can you try an older/vendor kernel and power-off the host before restarting ?

I have experienced something similar. My 8168b returns but the magic spell
is still not clear.

[...]
> kernel: r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
> kernel: ACPI: PCI Interrupt Link [LNEA] enabled at IRQ 16
> kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNEA] -> GSI 16 (level, low) -> IRQ 16
> kernel: PCI: Setting latency timer of device 0000:01:00.0 to 64
> kernel: eth1: RTL8168b/8111b at 0xffffc200020e2000, 00:18:f3:87:0b:bb, XID 38000000 IRQ 16

8168b as well. Okay...

-- 
Ueimor

  reply	other threads:[~2007-10-25 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 15:44 Fried r8169 Tom Prince
2007-10-25 21:36 ` Francois Romieu [this message]
2007-10-26  0:29   ` Tom Prince

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=20071025213645.GA2226@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=edward_hsu@realtek.com.tw \
    --cc=netdev@vger.kernel.org \
    --cc=tom.prince@ualberta.net \
    /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).