Date: Tue, 31 Jan 2006 01:12:35 +0000 From: Ian Dowse <iedowse@iedowse.com> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: freebsd-usb@freebsd.org Subject: Re: cvs commit: src/sys/dev/usb ehci.c ehci_pci.c ehcivar.h Message-ID: <200601310112.aa34663@nowhere.iedowse.com> In-Reply-To: Your message of "Mon, 30 Jan 2006 23:34:13 %2B0100." <20060130223413.GA11711@saturn.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20060130223413.GA11711@saturn.kn-bremen.de>, Juergen Lock writes: > Alright, here comes that: > intr_context = 3, Interesting - this actually suggests that two threads might be in the the interrupt service routine at the same time, which should not be possible unless there is a bug causing a callback to sleep. Could you see if you can find the EHCI interrupt thread in the output of: ps -axl -M vmcore -N kernel | grep irq It might show up like "[irq3: ehci" but if there are other interrupts shared with it you might need to look through dmesg output to find the IRQ number used by ehci and then look for that thread instead. Then from gdb, use 'info threads' to find the gdb thread ID for it (look for the PID=XX then read the first column). Finally, "thread TID" followed by "bt" should show what that thread is doing. e.g. if you see 7 Thread 100002 (PID=14: irq3: ehci0) 0xc050bb23 in ... then use "thread 7" and "bt". Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200601310112.aa34663>