Bug 125450 - [panic] Removing USB flash card while being accessed causes kernel panic, even without device mounted
Summary: [panic] Removing USB flash card while being accessed causes kernel panic, eve...
Status: Closed Feedback Timeout
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 7.0-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-09 21:50 UTC by Simson L. Garfinkel
Modified: 2015-12-25 05:14 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simson L. Garfinkel 2008-07-09 21:50:00 UTC
 1. insert a USB flash drive on /dev/da0
 2. dd if=/dev/da0 of=/dev/null
 3. WHile the dd is going, pull the flash drive
 
 FreeBSD panics

Fix: 

You guys have to do this.
How-To-Repeat:  
 Just do it again.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-07-10 10:28:03 UTC
State Changed
From-To: open->closed

See http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/46176 and subsequent 
(e.g. http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html). 


Comment 2 Mark Linimon freebsd_committer freebsd_triage 2008-07-10 10:28:03 UTC
Responsible Changed
From-To: gnats-admin->freebsd-usb
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2008-07-10 19:28:01 UTC
State Changed
From-To: closed->open

re-open.
Comment 4 Mark Linimon 2008-07-10 19:29:02 UTC
we're going to need a stack trace, as well.

mcl
Comment 5 Simson L. Garfinkel 2008-07-10 20:19:00 UTC
I'm happy to get you a stack trace; it's easy to make this happen. How  
do I get a stack trace from a kernel panic?

On Jul 10, 2008, at 11:29 AM, Mark Linimon wrote:

> we're going to need a stack trace, as well.
>
> mcl
>
Comment 6 Eitan Adler freebsd_committer freebsd_triage 2011-09-29 16:38:14 UTC
State Changed
From-To: open->feedback

run kgdb on the core file and type 'bt' Keep in mind that you need the 
same kernel as the one the dump was generated on