public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard Bloch <edi@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10: e100 network broken after swsusp/resume
Date: Sun, 2 Jan 2005 00:41:11 +0100	[thread overview]
Message-ID: <20050101234111.GA27099@zombie.inka.de> (raw)
In-Reply-To: <1104269125.21123.4.camel@localhost.localdomain>

#include <hallo.h>
* Håkan Lindqvist [Tue, Dec 28 2004, 10:25:25PM]:

> > ifplugd can see the link status change when i plug and unplug the cable,
> > but the dhclient it runs just tries and retries to get an ip without
> > success.
> 
> 
> I seem to get the same problem on my IBM Thinkpad X31.
> 
> At least e100 and snd-intel8x0 break down that way on suspend/resume.
> (http://marc.theaimsgroup.com/?l=linux-kernel&m=110419612421765&w=2)

Similar with USB on Toshiba Satellite Pro 2100. After resume, the
hardware simply does not work - the driver loads, but no USB input event
does ever reach the userspace. Reloading all USB drivers does not help.

0000:00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 42)

Regards,
Eduard.
-- 
  "After watching my newly-retired dad spend two weeks learning how to
  make a new folder, it became obvious that "intuitive" mostly means
  "what the writer or speaker of intuitive likes".
- Bruce Ediger, bediger@teal.csn.org, on X the intuitiveness of a Mac interface

  reply	other threads:[~2005-01-02 11:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 14:47 2.6.10: e100 network broken after swsusp/resume John M Flinchbaugh
2004-12-28 21:25 ` Håkan Lindqvist
2005-01-01 23:41   ` Eduard Bloch [this message]
2005-01-01 17:23 ` Pavel Machek
2005-01-01 22:17   ` John M Flinchbaugh
2005-01-01 22:52     ` Pavel Machek
2005-01-01 23:14     ` Matthew Garrett
2005-01-02  3:46       ` Barry K. Nathan
2005-01-02  5:57   ` Barry K. Nathan
2005-01-02 18:42     ` John M Flinchbaugh
2005-01-02 20:09       ` Håkan Lindqvist
2005-01-03  5:10         ` Barry K. Nathan
2005-01-03  8:31           ` Barry K. Nathan
2005-01-03  8:53             ` Pavel Machek
2005-01-03  8:47           ` Pavel Machek
2005-01-03 10:14             ` Barry K. Nathan
2005-01-03 15:05               ` [PATCH] swsusp: properly suspend and resume *all* devices Barry K. Nathan
2005-01-03 17:08                 ` Pavel Machek
2005-01-03 18:33                   ` Pavel Machek
2005-01-04  5:15                     ` Barry K. Nathan
2005-01-04  5:18                       ` Barry K. Nathan
2005-01-04  8:44                 ` Martin Lucina
2005-01-04 10:30                   ` 2.6.10 suspend/resume bustage (was Re: [PATCH] swsusp: properly suspend and resume *all* devices) Martin Lucina
2005-01-04 21:43                   ` [PATCH] swsusp: properly suspend and resume *all* devices Pavel Machek
2005-01-05 15:57                     ` Lion Vollnhals
2005-01-06 22:29                       ` Pavel Machek
2005-01-07 13:47                         ` Takashi Iwai
2005-01-07 13:54                           ` Pavel Machek
2005-01-07 14:48                             ` Dmitry Torokhov
2005-01-07 15:35                             ` Vojtech Pavlik
2005-01-07 15:59                         ` Lion Vollnhals

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=20050101234111.GA27099@zombie.inka.de \
    --to=edi@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /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