Opened 10 years ago

Closed 10 years ago

Last modified 3 years ago

#3761 closed bug (invalid)

KDL upon unplugging a USB stick

Reported by: TheNerd Owned by: axeld
Priority: normal Milestone: R1
Component: - General Version: R1/pre-alpha1
Keywords: Cc: dennis.dentremont@…
Blocked By: Blocking: #7820
Has a Patch: no Platform: x86


I am running Haiku rev 30140 on an Acer TravelMate 800 laptop. When I plug in my Patriot Memory Razzo 16GB memory stick it recognizes it and displays an icon on the desktop but as soon as I unplug it Haiku crashes and goes into KDL.

Below is what I get from the initial KDL Screen:

PANIC: could not write back block 1 (device not ready)

Welcome to Kernel Debugging Land... Thread 32 "usb explore" running on CPU 0 kdebug>

I am not sure how to get set up to use the serial port or whatever to get more info but I can give it a try if someone wants to tell me how.

I did a search and I think it may be a similar issue to ticket 2364.

Change History (7)

comment:1 Changed 10 years ago by mmlr

But you do unmount the volume before unplugging, do you? Otherwise this is invalid because it's expected that you can't write to an unplugged device.

comment:2 Changed 10 years ago by TheNerd

To produce this crash I did not unmount it. As far as I'm concerned the OS shouldn't crash from improperly unplugging a device. Correct me if I'm wrong, but other OSs don't crash when you unplug without unmounting a device.

Maybe it shouldn't be a bug but at least a feature request...

comment:3 Changed 10 years ago by mmlr

Resolution: invalid
Status: newclosed

It doesn't actually crash. It panics to indicate a dataloss that's all. Panics like this will be changed to other means of reporting like syslog.

comment:4 Changed 10 years ago by TheNerd

yes that is correct. Urias gracefully pointed out the continue command to me. I still think Haiku (at some point) should maybe handle that a bit better.


comment:5 Changed 10 years ago by mmlr

Yes this is exactly what I mean. For releases, panics like this will just be disabled or changed to other means of reporting, most likely the syslog.

comment:6 Changed 10 years ago by TheNerd

understood :) thanks!

comment:7 Changed 3 years ago by waddlesplash

Blocking: 7820 added
Note: See TracTickets for help on using tickets.