netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Bennee <kernel-hacker@bennee.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: lkml <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: r8169 ethernet hangs after a pm-suspend (and resume)
Date: Thu, 8 Oct 2009 10:27:10 +0100	[thread overview]
Message-ID: <b2cdc9f30910080227s17effd97vf13d7e91b153ad17@mail.gmail.com> (raw)
In-Reply-To: <20090909092822.GA18355@electric-eye.fr.zoreil.com>

2009/9/9 Francois Romieu <romieu@fr.zoreil.com>:
> Alex Bennee <kernel-hacker@bennee.com> :
> [...]
>> I've just recently gotten suspend working on my system. Unfortunately
>> after the resume event I loose access to the network.
>> As far as the system is concerned the network is configured properly
>> but every attempt to ping local nodes fails with "Host not reachable".
>
> Can the problem be described as "gigabit link setting does not survive
> suspend/resume" ?

Even further experimentation shows that ethernet functionality can
survive the resume for a few minutes before reseting. Once it gets
into this state even rmmod/modprobing the r8169 driver won't unwedge
the driver.

The symptoms are either the driver detecting an unknown MAC or setting
the physical address to 0xfffffffff which is obviously broken. I
suspect the hardware has gotten itself wedged somehow.

Is there any way to hard reset the chipset (without power cycling the
system)?

-- 
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk

      parent reply	other threads:[~2009-10-08  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  7:13 r8169 ethernet hangs after a pm-suspend (and resume) Alex Bennee
2009-09-09  9:28 ` Francois Romieu
2009-09-09  9:37   ` Alex Bennee
2009-09-10  6:49   ` Alex Bennee
2009-10-08  9:27   ` Alex Bennee [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=b2cdc9f30910080227s17effd97vf13d7e91b153ad17@mail.gmail.com \
    --to=kernel-hacker@bennee.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).