Re: kernel panic on 6.1-PRERELEASE with Lexar Jumpdrive2
On Tue, 2006-Feb-14 20:01:54 -0800, Joseph Olatt wrote: >Using Peter Jeremy's suggestion, I was able to get a backtrace. Since I >couldn't figure out an easier way to capture the backtrace, I >transcribed by hand from the console. A serial console would be much easier if you've got another system with a serial port. Whilst the backtrace is a start, you've left out the actual panic message and associated register dump. Is it a 'panic' or some sort of trap? I don't quickly see call to panic() in probedone(). Whilst you're at it, if you have a debug kernel, can you try running kgdb on it and "list *0x" where is the eip value listed in the kernel trap message (if any) [not the 'trap 0x1' in the backtrace]. >I still wish I could get the system to dump and save the core. I still >haven't figured out why the system freezes in the middle of a core dump. Are you dumping to an ATA or SCSI disk? If the latter, it's possible that the panic has upset the CAM subsystem (though this isn't supposed to happen). -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic on 6.1-PRERELEASE with Lexar Jumpdrive2
On Tue, Feb 14, 2006 at 08:07:48PM +1100, Peter Jeremy wrote: > On Mon, 2006-Feb-13 19:44:07 -0800, Joseph Olatt wrote: > >I've been having kernel panics when I use one particular USB flash drive > >(LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2) with FreeBSD > >6.1-PRERELEASE (See [1] below). All I have to do to get the kernel to > >panic is to insert and remove the drive from the USB port 2 or 3 times > > You left out details of the panic and backtrace. > > >This problem happens only if the "ehci" device is enabled in the kernel > > Note that echi(4) states: > BUGS > The driver is not finished and is quite buggy. > > >So I suspect that it is a problem with the "ehci" driver. Unfortunately > >I'm not being able to get a crash dump as the system starts dumping and > >then freezes. > > Try adding the following options so you can get backtraces without dumps: > options KDB > options KDB_TRACE > options DDB > Using Peter Jeremy's suggestion, I was able to get a backtrace. Since I couldn't figure out an easier way to capture the backtrace, I transcribed by hand from the console. Here is the output: ### Begin Backtrace ### dt> bt Tracing pid 39 tid 100030 td 0x32bcc00 probedone(c3a56800, c3606000) at probedone+0x4b2 camisr(c0926a78) at camisr+0x27d ithread_loop(c33c3400, d44aad38) at ithread_loop+0x159 fork_exit(c0631330, c33c3400, d44aad38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd44aadbc, ebp = 0 --- ### End Backtrace ### I still wish I could get the system to dump and save the core. I still haven't figured out why the system freezes in the middle of a core dump. It looks like the the function "probedone" is defined in: /usr/src/sys/cam/cam_xpt.c I'm not familiar with DDB. If anyone would like more information, I'll be glad to get the system to panic again and follow your instructions. regards, joseph ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic on 6.1-PRERELEASE with Lexar Jumpdrive2
On Mon, 2006-Feb-13 19:44:07 -0800, Joseph Olatt wrote: >I've been having kernel panics when I use one particular USB flash drive >(LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2) with FreeBSD >6.1-PRERELEASE (See [1] below). All I have to do to get the kernel to >panic is to insert and remove the drive from the USB port 2 or 3 times You left out details of the panic and backtrace. >This problem happens only if the "ehci" device is enabled in the kernel Note that echi(4) states: BUGS The driver is not finished and is quite buggy. >So I suspect that it is a problem with the "ehci" driver. Unfortunately >I'm not being able to get a crash dump as the system starts dumping and >then freezes. Try adding the following options so you can get backtraces without dumps: options KDB options KDB_TRACE options DDB >I have 2 other newer flash drives and they seem to work fine. Which suggests it needs a quirk of some sort. >umass0: at uhub0 port 5 (addr 2) disconnected >(da0:umass-sim0:0:0:0): lost device >(da0:umass-sim0:0:0:0): removing device entry >umass0: detached >umass0: LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2 >umass0: BBB reset failed, IOERROR >umass0: BBB bulk-in clear stall failed, IOERROR >umass0: BBB bulk-out clear stall failed, IOERROR >umass0: BBB reset failed, IOERROR I've seen similar behaviour on ulpt as well. The USB subsystem does not appear to recover from errors on the hardware side. In my case, that USB port wedges and cannot be used until the system is reset (though other ports are OK). -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kernel panic on 6.1-PRERELEASE with Lexar Jumpdrive2
Hello, I've been having kernel panics when I use one particular USB flash drive (LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2) with FreeBSD 6.1-PRERELEASE (See [1] below). All I have to do to get the kernel to panic is to insert and remove the drive from the USB port 2 or 3 times (without mounting the drive. Entries in /dev do not get created. See [2] for error I get when I insert the drive and [3] for the error I get when I remove the drive.) This problem happens only if the "ehci" device is enabled in the kernel (GENERIC has it enabled by default). If I comment out the "ehci" device and use only the "uhci" device, then I get a device entry in /dev and I'm able to mount the flash drive just fine and, insert and remove as many times as I like without any problems. So I suspect that it is a problem with the "ehci" driver. Unfortunately I'm not being able to get a crash dump as the system starts dumping and then freezes. I wanted to see if there is anybody on the list who has experienced anything similar. I have 2 other newer flash drives and they seem to work fine. The system seems to panic only when I use this particular flash drive. The flash drive is empty and I'm able to mount it fine if I use only the "uhci" driver. regards, joseph [1]: FreeBSD 6.1-PRERELEASE #0: Sun Feb 12 21:39:40 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC [2]: umass1: LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2 da4 at umass-sim1 bus 1 target 0 lun 0 da4: Removable Direct Access SCSI-0 device da4: 40.000MB/s transfers da4: 125MB (256000 512 byte sectors: 64H 32S/T 125C) (da4:umass-sim1:1:0:0): Synchronize cache failed, status == 0x10, scsi status == 0x0 umass1: Invalid CSW: sig 0x53555355 should be 0x53425355 [3]: umass0: at uhub0 port 5 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: LEXAR MEDIA JUMPDRIVE2, rev 2.00/1.25, addr 2 umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR (da0:umass-sim0:0:0:0): removing device entry Opened disk da0 -> 5 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
