Ronny Egner wrote:
ffffff008bfe0480 unix:die+dd () ffffff008bfe0590 unix:trap+177b () ffffff008bfe05a0 unix:cmntrap+e6 () ffffff008bfe0690 0 () ffffff008bfe06b0 unix:debug_enter+38 () ffffff008bfe06d0 unix:abort_sequence_enter+35 () ffffff008bfe0720 kbtrans:kbtrans_streams_key+102 () ffffff008bfe0750 conskbd:conskbdlrput+e7 () ffffff008bfe07c0 unix:putnext+21e () ffffff008bfe0800 kbtrans:kbtrans_queueevent+7c () ffffff008bfe0830 kbtrans:kbtrans_queuepress+7c () ffffff008bfe0870 kbtrans:kbtrans_untrans_keypressed_raw+46 () ffffff008bfe08a0 kbtrans:kbtrans_processkey+32 () ffffff008bfe08f0 kbtrans:kbtrans_streams_key+175 () ffffff008bfe0920 usbkbm:usbkbm_wrap_kbtrans+20 () ffffff008bfe0960 usbkbm:usbkbm_streams_callback+3c () ffffff008bfe09e0 usbkbm:usbkbm_unpack_usb_packet+2f6 () ffffff008bfe0a10 usbkbm:usbkbm_rput+84 () ffffff008bfe0a80 unix:putnext+21e () ffffff008bfe0ac0 hid:hid_interrupt_pipe_callback+7c () ffffff008bfe0b00 usba:usba_req_normal_cb+155 () ffffff008bfe0b60 usba:hcdi_do_cb+133 () ffffff008bfe0ba0 usba:hcdi_cb_thread+b2 () ffffff008bfe0c40 genunix:taskq_thread+248 () ffffff008bfe0c50 unix:thread_start+8 () syncing file systems... done dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: all
<snip>
So just judgint from the stack trace ($C macro) the problem seems to be related to some kind of USB device? Can anyone help me?
Your stack trace above is the direct result of dropping to the debugger, from handling the USB interrupt at the bottom of the trace, all the way up through the usbkbm and kbtrans drivers, up to dropping out of Solaris via the debug_enter() call. The remainder of the stack is the result of forcing the panic - a jmpl to a zero address triggers an instant bad trap, and the system panics through the normal mechanism. The USB device here is merely the messenger of the Alt-F1 sequence to drop to the debugger. This particular stack is not a problem in itself.
For your issue, you will need to see what other threads are doing in the system at the time you halted it.
[ Might be worth ruling out http://defect.opensolaris.org/bz/show_bug.cgi?id=12528 - I don't think it's the right bug, but it reared its head recently. I don't know whether this only affects the graphics card or the entire system... ]
You may need to be looking at what the IO layer was doing with the two internal disks at the time - IIRC, threads blocked in biowait() are a good starting point.
Regards, Brian -- Brian Ruthven Solaris Revenue Product Engineering Sun Microsystems UK Sparc House, Guillemont Park, Camberley, GU17 9QG _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
