On Sat, 4 Oct 2003, Matthias Urlichs wrote:
> Hi,
>
> Alan Stern wrote:
> > For comparison, here is the corresponding log I got when I unplugged a USB
> > CD-RW device, minus several lengthy and uninformative stack dumps
> > following the "Badness" lines -- did you enable debugging in
> > lib/kob
Hi,
Alan Stern wrote:
> For comparison, here is the corresponding log I got when I unplugged a USB
> CD-RW device, minus several lengthy and uninformative stack dumps
> following the "Badness" lines -- did you enable debugging in
> lib/kobject.c?
Yes, I did.
I'll try to find that problem; thanks
On Sat, 4 Oct 2003, Smurf wrote:
> The relevant part of the log is:
>
> Oct 4 11:16:44 linux kernel: usb-storage: -- dissociate_dev
> Oct 4 11:16:44 linux kernel: CLASS: Unregistering class device. ID = '0:0:0:0'
> Oct 4 11:16:44 linux kernel: kset_hotplug
> Oct 4 11:16:44 linux kernel: fill_
Hi,
Alan Stern:
> In turn, scsi_remove_host() calls class_device_unregister() and
> device_del(), and those calls should appear in the debugging log once you
> make the changes listed above. Somewhere in there is where the problem
> lies, and it may take a little work to track it down exactly.
On Fri, Oct 03, 2003 at 02:11:21PM -0400, Alan Stern wrote:
>
> The important part of the control flow is where storage_disconnect() in
> drivers/usb/storage/usb.c calls scsi_remove_host() in
> drivers/scsi/hosts.c. That call occurs between the "dissociate_dev" and
> the "sending exit command" lo
On Fri, 3 Oct 2003, Matthias Urlichs wrote:
> OK, here's the debug output when I remove the keychain:
>
> Oct 3 17:41:32 linux kernel: hub 1-1:1.0: port 1, status 100, change 1, 12 Mb/s
> Oct 3 17:41:32 linux kernel: usb 1-1.1: USB disconnect, address 4
> Oct 3 17:41:32 linux kernel: usb 1-1.1
Hi,
Alan Stern wrote:
> I tried doing much the same thing just now using 2.6.0-test5-bk10 (with a
> real disk drive, not a keychain, but that shouldn't matter). It worked as
> it should, reusing the sda device number.
Hmmm.
One possibly relevant snippt of information: This is a PowerBook G4. I
Hi,
Randy.Dunlap wrote:
> On Fri, 3 Oct 2003 13:58:48 +0200 Matthias Urlichs <[EMAIL PROTECTED]>
wrote:
> | I get that too, with my USB keychain. It seems that removing it
> | doesn't unregister the SD driver for some reason.
>
> Is this 2.4.x and not 2.6.0x?
Sorry. This is 2.6, current Bitkeepe
Hi,
Alan Stern wrote:
> with USB debugging and usb-storage debugging both configured on? Also, be
> sure to capture the debugging messages -- either configure your syslog
> daemon or use dmesg.
>
OK, here's the debug output when I remove the keychain:
Oct 3 17:41:32 linux kernel: hub 1-1:1.0: p
Hi,
Alan Stern wrote:
> Assuming you did unmount it first
... which I did (even if not, a subsequent 'umount -f' on it should release
the reference) ...
> could you try doing this again, but
> with USB debugging and usb-storage debugging both configured on? Also, be
> sure to capture the debug
On Fri, 3 Oct 2003, Matthias Urlichs wrote:
> I get that too, with my USB keychain. It seems that removing it
> doesn't unregister the SD driver for some reason.
Matthias:
I tried doing much the same thing just now using 2.6.0-test5-bk10 (with a
real disk drive, not a keychain, but that shouldn'
On Fri, 3 Oct 2003 13:58:48 +0200 Matthias Urlichs <[EMAIL PROTECTED]> wrote:
| I get that too, with my USB keychain. It seems that removing it
| doesn't unregister the SD driver for some reason.
Is this 2.4.x and not 2.6.0x?
After unmounting the device, does it help to do
eject /dev/sdx
That
I get that too, with my USB keychain. It seems that removing it
doesn't unregister the SD driver for some reason.
The kernel says:
Oct 3 12:34:00 linux kernel: hub 1-1:1.0: new USB device on port 1, assigned address 4
Oct 3 12:34:00 linux kernel: bus usb: add device 1-1.1
Oct 3 12:34:00 linux k
13 matches
Mail list logo
