From: Tom Prince <tom.prince@ualberta.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, Edward Hsu <edward_hsu@realtek.com.tw>
Subject: Re: Fried r8169.
Date: Thu, 25 Oct 2007 20:29:26 -0400 [thread overview]
Message-ID: <20071026002926.GA2650@hermes.priv> (raw)
In-Reply-To: <20071025213645.GA2226@electric-eye.fr.zoreil.com>
On Thu, Oct 25, 2007 at 11:36:45PM +0200, Francois Romieu wrote:
> 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.
Thanks.
Well, after power cyclic a few times, and reverting to v2.6.23, the card works
again. Unfortunately, I don't have the exact config where the card disappeared
any more, and it now shows up but doesn't work under v2.6.23. I'll spend some
time this weekend, and see if I can track down what causes it to disappear.
One data point: I have a kernel v2.6.23 + patch-2.6.23-rc9-hrt1 and a custom
acpi DSDT that seems to cause the device to disappear.
I have now uploaded dmesg/lspci/config from v2.6.23 from a succesful boot to
www.math.uwo.ca/~rprince5/r8169/
Tom
prev parent reply other threads:[~2007-10-26 0:26 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
2007-10-26 0:29 ` Tom Prince [this message]
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=20071026002926.GA2650@hermes.priv \
--to=tom.prince@ualberta.net \
--cc=edward_hsu@realtek.com.tw \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).