Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

usb/145513: New USB stack: no new devices after forced usb flash detach

1 view
Skip to first unread message

Krutov Mikle

unread,
Apr 8, 2010, 6:55:44 AM4/8/10
to freebsd-gn...@freebsd.org

>Number: 145513
>Category: usb
>Synopsis: New USB stack: no new devices after forced usb flash detach
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 08 11:00:15 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Krutov Mikle
>Release: 8.0-STABLE
>Organization:
>Environment:
FreeBSD takino.homeftp.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Mon Mar 8 06:25:34 MSK 2010 ro...@takino.homeftp.org:/usr/obj/usr/src/sys/TAKINO amd64

>Description:
After detaching the mounted usb-flash device, no new usb-devices are detected.
USB controller is "device = 'SB700 USB OHCI1 Controller"
>How-To-Repeat:
1) attach (vfat-formated, did not test with other fs) flash device, mount it
2) detach without umounting
3) try to attach another usb-device
4) see no new devices, no dmesg messages, nothing
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:

Hans Petter Selasky

unread,
Apr 8, 2010, 7:52:50 AM4/8/10
to freeb...@freebsd.org, freebsd-gn...@freebsd.org

Hi,

That's because the UMASS detach is hanging, most likely.

Try to break into the kernel and get a backtrace.

--HPS

Hans Petter Selasky

unread,
Apr 8, 2010, 8:00:19 AM4/8/10
to freeb...@freebsd.org
The following reply was made to PR usb/145513; it has been noted by GNATS.

Mikle Krutov

unread,
Apr 8, 2010, 1:50:03 PM4/8/10
to freeb...@freebsd.org
The following reply was made to PR usb/145513; it has been noted by GNATS.

From: Mikle Krutov <nekoex...@gmail.com>
To: Hans Petter Selasky <hsel...@c2i.net>
Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/145513: New USB stack: no new devices after forced usb
flash detach

Date: Thu, 8 Apr 2010 21:14:03 +0400

On Thu, Apr 08, 2010 at 01:52:50PM +0200, Hans Petter Selasky wrote:
> Hi,
>
> That's because the UMASS detach is hanging, most likely.
>
> Try to break into the kernel and get a backtrace.
>
> --HPS

Hi,
I unfortunately could not find any info about how do i do this. Could
you provide me some link?

--
Wbr,
Krutov Mikle

Hans Petter Selasky

unread,
Apr 8, 2010, 1:40:03 PM4/8/10
to freeb...@freebsd.org
The following reply was made to PR usb/145513; it has been noted by GNATS.

From: Hans Petter Selasky <hsel...@c2i.net>
To: Mikle Krutov <nekoex...@gmail.com>
Cc: freeb...@freebsd.org,
freebsd-gn...@freebsd.org
Subject: Re: usb/145513: New USB stack: no new devices after forced usb flash detach

Date: Thu, 8 Apr 2010 19:29:43 +0200

On Thursday 08 April 2010 19:14:03 Mikle Krutov wrote:
> On Thu, Apr 08, 2010 at 01:52:50PM +0200, Hans Petter Selasky wrote:
> > Hi,
> >
> > That's because the UMASS detach is hanging, most likely.
> >
> > Try to break into the kernel and get a backtrace.
> >
> > --HPS
>
> Hi,
> I unfortunately could not find any info about how do i do this. Could
> you provide me some link?
>

Add:

options KDB # Enable kernel debugger support.
options DDB # Support DDB.
options GDB # Support remote GDB.

When it hangs, enter this from the console:

sysctl debug.kdb.panic=1

Type

alltrace

bt

bt all

or something similar.

Type "continue" when you are finished.

You can also use CTRL+ALT+ESC key combination.

--HPS

Hans Petter Selasky

unread,
Apr 8, 2010, 1:29:43 PM4/8/10
to Mikle Krutov, freebsd-gn...@freebsd.org, freeb...@freebsd.org
On Thursday 08 April 2010 19:14:03 Mikle Krutov wrote:
> On Thu, Apr 08, 2010 at 01:52:50PM +0200, Hans Petter Selasky wrote:
> > Hi,
> >
> > That's because the UMASS detach is hanging, most likely.
> >
> > Try to break into the kernel and get a backtrace.
> >
> > --HPS
>

Mikle Krutov

unread,
Apr 8, 2010, 1:14:03 PM4/8/10
to Hans Petter Selasky, freebsd-gn...@freebsd.org, freeb...@freebsd.org
On Thu, Apr 08, 2010 at 01:52:50PM +0200, Hans Petter Selasky wrote:
> Hi,
>
> That's because the UMASS detach is hanging, most likely.
>
> Try to break into the kernel and get a backtrace.
>
> --HPS
Hi,
I unfortunately could not find any info about how do i do this. Could
you provide me some link?

--
Wbr,
Krutov Mikle

Mikle Krutov

unread,
Apr 10, 2010, 7:03:09 PM4/10/10
to Hans Petter Selasky, freebsd-gn...@freebsd.org, freeb...@freebsd.org
Sorry for no-response for such a long time, that was because after the
kernel-update (i've fetched the latest sources before rebuilding with
debug support) i could not reproduce that bug. Before kernel-update it
has happened not every time, so i wanted to see what happends for a
couple of days.

--
Wbr,
Krutov Mikle

Mikle Krutov

unread,
Apr 10, 2010, 7:10:03 PM4/10/10
to freeb...@freebsd.org
The following reply was made to PR usb/145513; it has been noted by GNATS.

From: Mikle Krutov <nekoex...@gmail.com>


To: Hans Petter Selasky <hsel...@c2i.net>

Cc: freeb...@freebsd.org, freebsd-gn...@freebsd.org
Subject: Re: usb/145513: New USB stack: no new devices after forced usb
flash detach

Hans Petter Selasky

unread,
Apr 11, 2010, 2:45:55 AM4/11/10
to freeb...@freebsd.org, Mikle Krutov

Will you close this PR then if you cannot reproduce during the coming week?

--HPS

0 new messages