From: Andries Brouwer <aebr@win.tue.nl>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB CF reader reboots PC
Date: Wed, 8 Jan 2003 19:49:51 +0100 [thread overview]
Message-ID: <20030108184951.GA19268@win.tue.nl> (raw)
In-Reply-To: <20030108181645.GC3127@kroah.com>
On Wed, Jan 08, 2003 at 10:16:45AM -0800, Greg KH wrote:
> > Insert CF card.
> > ls /dev shows sda and sda1
> > mount it.
> > ls /dev shows sda - no sda1
> > cd to mounted CF card
> > process hangs, sd-mod & usb-storage "busy"
> > rmmod -f usb-storage or sd-mod causes PC to stop
> > (keyboard & mouse unresponsive, wmfire frozen, net disconnects)
> So if devfs is enabled, everything works just fine?
No. I have seen this kind of thing, and muttered a little bit
on earlier occasions.
The problem is that USB storage invents a GUID, that usually
is composed of vendor and product ID of the reader, possibly
also a serial number, but does not involve the card.
When the card goes away, the partitions stay, and the device
is treated as "not present".
When a new card is inserted confusion arises.
We see that when a device goes from "not present" to "present"
it may be necessary to throw out all data we have on it.
Thus, maybe it was pointless to keep this data when it went away.
This is somewhat related to the IDs discussion of a few days ago.
People invent IDs, but nobody knows of what precisely.
Andries
next prev parent reply other threads:[~2003-01-08 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 16:51 USB CF reader reboots PC Murray J. Root
2003-01-08 17:33 ` Murray J. Root
2003-01-08 17:50 ` Eli Carter
2003-01-08 17:59 ` Murray J. Root
2003-01-08 18:16 ` Greg KH
2003-01-08 18:24 ` Murray J. Root
2003-01-08 18:49 ` Andries Brouwer [this message]
2003-01-09 16:06 ` USB CF reader reboots PC - DEVFS did it Murray J. Root
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=20030108184951.GA19268@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=greg@kroah.com \
--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