usb/145513: New USB stack: no new devices after forced usb
flash detach
Mikle Krutov
nekoexmachina at gmail.com
Sat Apr 17 21:30:05 UTC 2010
On Sun, Apr 11, 2010 at 08:45:55AM +0200, Hans Petter Selasky wrote:
> On Sunday 11 April 2010 01:10:03 Mikle Krutov wrote:
> > The following reply was made to PR usb/145513; it has been noted by GNATS.
> >
> > From: Mikle Krutov <nekoexmachina at gmail.com>
> > To: Hans Petter Selasky <hselasky at c2i.net>
> > Cc: freebsd-usb at freebsd.org, freebsd-gnats-submit at freebsd.org
> > Subject: Re: usb/145513: New USB stack: no new devices after forced usb
> > flash detach
> > Date: Sun, 11 Apr 2010 03:03:09 +0400
> >
> > On Thu, Apr 08, 2010 at 07:29:43PM +0200, Hans Petter Selasky wrote:
> > > 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
> >
> > 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.
> >
>
> Will you close this PR then if you cannot reproduce during the coming week?
>
> --HPS
So, this can be marked as 'closed'. I've tried it a couple of times with
different load, uptime, usb devices count, etc, no changes - it was
fixed.
As i understand, i can not close the bug, only the dev of fbsd can.
Sorry for wasting your time.
--
Wbr,
Krutov Mikle
More information about the freebsd-usb
mailing list