From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Subject: Process in D state with USB and swsuspsp
Date: Sat, 26 Jun 2004 20:34:56 -0500 [thread overview]
Message-ID: <200406262031.14464.rob@landley.net> (raw)
I realise I did something stupid, but it took a while to figure it out, and
I'm not going to be the only person to do this.
My laptop has built-in wireless (orinoco_cs), but I used a USB ethernet
adapter to plug in to the wall for a bit (ohci-hcd and pegasus).
Then I the suspended the thing, unplugged the USB adapter, and packed the
laptop up. About twelve hours later, I fire the thing up, run "dhclient" to
get a wireless connection, but the first thing it tried to touch was the USB
connection that isn't there anymore. So it hung, ctrl-c wouldn't kill it,
and the process is stuck in D state.
Trying to figure out what was going on, I ran dhclient twice more and got two
more processes stuck in D state. It took a while to remember that yesterday
I was using the USB adapter, but today I'm not.
Ordinarily, I don't think the ohci-hcd module is even loaded. The kernel
currently thinks it is, but modprobe -r ohci-hcd resulted in yet another
process in D state...
As I said, I realise that unplugging even a USB adapter with the machine is
suspended is Not A Good Thing. But it's likely to be a common thing among
people who can't figure out after the fact "oh yeah, that's what's going
wrong"...
Rob
--
www.linucon.org: Linux Expo and Science Fiction Convention
October 8-10, 2004 in Austin Texas. (I'm the con chair.)
next reply other threads:[~2004-06-27 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 1:34 Rob Landley [this message]
2004-06-27 5:31 ` Process in D state with USB and swsuspsp Brad Campbell
2004-06-27 8:50 ` Rob Landley
2004-06-27 13:22 ` Oliver Neukum
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=200406262031.14464.rob@landley.net \
--to=rob@landley.net \
--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 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.