Re: usb/145513: New USB stack: no new devices after forced usb flash detach
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 > > To: Hans Petter Selasky > > Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
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 > To: Hans Petter Selasky > Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
The following reply was made to PR usb/145513; it has been noted by GNATS. From: Mikle Krutov To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@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. -- Wbr, Krutov Mikle ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
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. -- Wbr, Krutov Mikle ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
The following reply was made to PR usb/145513; it has been noted by GNATS. From: Mikle Krutov To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
The following reply was made to PR usb/145513; it has been noted by GNATS. From: Hans Petter Selasky To: Mikle Krutov Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
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 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
The following reply was made to PR usb/145513; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Krutov Mikle , freebsd-gnats-sub...@freebsd.org Subject: Re: usb/145513: New USB stack: no new devices after forced usb flash detach Date: Thu, 8 Apr 2010 13:52:50 +0200 On Thursday 08 April 2010 12:55:44 Krutov Mikle wrote: > >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 r...@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 > Hi, That's because the UMASS detach is hanging, most likely. Try to break into the kernel and get a backtrace. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/145513: New USB stack: no new devices after forced usb flash detach
On Thursday 08 April 2010 12:55:44 Krutov Mikle wrote: > >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 r...@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 > Hi, That's because the UMASS detach is hanging, most likely. Try to break into the kernel and get a backtrace. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
