From: Mike Rapoport <mike@compulab.co.il>
To: Steve Glendinning <steve.glendinning@smsc.com>
Cc: netdev@vger.kernel.org, LAKML <linux-arm-kernel@lists.infradead.org>
Subject: smsc911x suspend/resume
Date: Mon, 08 Feb 2010 11:42:27 +0200 [thread overview]
Message-ID: <4B6FDC83.9090205@compulab.co.il> (raw)
Hi all,
I'm trying to make suspend/resume work on OMAP3-based system and I'm
encountering issues with resume of SMSC 9220 chip.
After resume the interface is unusable unless I do 'ifconfig eth0 down'
and 'ifconfig eth0 up'.
I would expect that 'ping <some host>' would work right after resume
without need to bring the interface down and up, but probably I miss
something.
Any help would be appreciated.
--
Sincerely yours,
Mike.
WARNING: multiple messages have this Message-ID (diff)
From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: smsc911x suspend/resume
Date: Mon, 08 Feb 2010 11:42:27 +0200 [thread overview]
Message-ID: <4B6FDC83.9090205@compulab.co.il> (raw)
Hi all,
I'm trying to make suspend/resume work on OMAP3-based system and I'm
encountering issues with resume of SMSC 9220 chip.
After resume the interface is unusable unless I do 'ifconfig eth0 down'
and 'ifconfig eth0 up'.
I would expect that 'ping <some host>' would work right after resume
without need to bring the interface down and up, but probably I miss
something.
Any help would be appreciated.
--
Sincerely yours,
Mike.
next reply other threads:[~2010-02-08 9:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 9:42 Mike Rapoport [this message]
2010-02-08 9:42 ` smsc911x suspend/resume Mike Rapoport
2010-02-08 10:11 ` Daniel Mack
2010-02-08 10:11 ` Daniel Mack
2010-02-08 11:30 ` Mike Rapoport
2010-02-08 11:30 ` Mike Rapoport
2010-02-08 11:46 ` Daniel Mack
2010-02-08 11:46 ` Daniel Mack
2010-02-08 14:42 ` Mike Rapoport
2010-02-08 14:42 ` Mike Rapoport
2010-02-08 14:49 ` Daniel Mack
2010-02-08 14:49 ` Daniel Mack
2010-02-08 15:10 ` Mike Rapoport
2010-02-08 15:10 ` Mike Rapoport
2010-02-11 18:26 ` Steve.Glendinning
2010-02-11 18:26 ` Steve.Glendinning at smsc.com
2010-02-14 9:01 ` mike
2010-02-14 9:01 ` mike at compulab.co.il
2010-02-08 11:46 ` Steve.Glendinning
2010-02-08 11:46 ` Steve.Glendinning at smsc.com
2010-02-08 11:53 ` Daniel Mack
2010-02-08 11:53 ` Daniel Mack
2010-02-08 12:27 ` Steve.Glendinning
2010-02-08 12:27 ` Steve.Glendinning at smsc.com
2010-02-08 13:55 ` Mike Rapoport
2010-02-08 13:55 ` Mike Rapoport
2015-03-06 9:16 Ran Shalit
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=4B6FDC83.9090205@compulab.co.il \
--to=mike@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@smsc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.