Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jan 2006 20:52:58 +0100
From:      Juergen Lock <nox@jelal.kn-bremen.de>
To:        Ian Dowse <iedowse@iedowse.com>
Cc:        freebsd-usb@freebsd.org
Subject:   Re: cvs commit: src/sys/dev/usb ehci.c ehci_pci.c ehcivar.h
Message-ID:  <20060130195258.GA7172@saturn.kn-bremen.de>
In-Reply-To: <200601300051.aa09730@nowhere.iedowse.com>
References:  <20060129235559.GA29869@saturn.kn-bremen.de> <200601300051.aa09730@nowhere.iedowse.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 30, 2006 at 12:51:25AM +0000, Ian Dowse wrote:
> In message <20060129235559.GA29869@saturn.kn-bremen.de>, Juergen Lock writes:
> >Hmm.  Now I just got the following panic with it, pipe->queue.stqh_first
> >shouldn't be NULL right?  (Maybe it already got a new command for the
> >same umass device while there still is an ehci_intrlist_timeout pending
> >for the last command and so the new one interferes?)
> 
> Is that with umass devices only, or were there other USB devices
> in use?

Yes only the umass device was in use, even the mouse on that box
is on ps2.

>  The trace looks familiour so it might be something that has
> been fixed in -current.

 Well ehci_intrlist_timeout belongs to the ehci patch in the Subject
so its pretty new...  (I don't know the code enough to know if it
matters, but shouldnt the timer only be scheduled if the interrupt
did appear too early, i.e. the transfer indeed wasnt complete yet?
Not all transfers hung before i applied the patch, so it only
happens `sometimes'...)

>  Could you see if there were any related
> console messages just before the crash with
> 
> 	dmesg -a -M vmcore_file -N kernel_file
> 
 Ok, appended below.

> and if possible recompile your kernel to contain the drivers for
> any USB devices you use rather than loading modules? Using modules
> causes the stack trace to miss out information from module frames.

 I alread had usb in the kernel, so no usb related klds were in use.

-----snip--------
(sa0:umass-sim0:0:0:0): Retrying Command
(sa0:umass-sim0:0:0:0): error 28
(sa0:umass-sim0:0:0:0): Unretryable Error


Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x4c
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc0584f7d
stack pointer	        = 0x10:0xd420cc3c
frame pointer	        = 0x10:0xd420cc58
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 27 (swi5: clock sio)
trap number		= 12
panic: page fault
KDB: stack backtrace:
kdb_backtrace(100,c1987180,10,d420cbfc,c) at kdb_backtrace+0x29
panic(c07b08f4,c07ee5b5,0,fffff,c198e59b) at panic+0xa8
trap_fatal(d420cbfc,4c,c1987180,0,c) at trap_fatal+0x27c
trap_pfault(d420cbfc,0,4c) at trap_pfault+0x1ef
trap(18,10,10,0,c29a6b80) at trap+0x315
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0xc0584f7d, esp = 0xd420cc3c, ebp = 0xd420cc58 ---
usb_transfer_complete(c1aaf300,1f,c29a6b80,c1aaf300,c1a3f800) at usb_transfer_complete+0xcd
ehci_idone(c1aaf300,c2881680,c1aaf36c,c1aaf354,0) at ehci_idone+0x120
ehci_check_intr(c1a3f800,c1aaf300) at ehci_check_intr+0x73
ehci_softintr(c1a3f800,d420ccc8,c056f833,c1a3f800,d420ccf4) at ehci_softintr+0x25
usb_schedsoftintr(c1a3f800) at usb_schedsoftintr+0xd
ehci_intrlist_timeout(c1a3f800) at ehci_intrlist_timeout+0xb
softclock(0) at softclock+0x25e
ithread_loop(c197d500,d420cd48) at ithread_loop+0x151
fork_exit(c05ce974,c197d500,d420cd48) at fork_exit+0x74
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd420cd7c, ebp = 0 ---
Uptime: 10h2m19s
Dumping 511 MB
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060130195258.GA7172>