Re: USB disk causes panic in 7.0-PRERELEASE
James wrote: > On Mon, 2007-10-22 at 12:33 +0200, Svein Halvor Halvorsen wrote: >> xptioctl: pass driver is not in the kernel >> xptioctl: put "device pass0" in your kernel config file > > > Have you tried putting "device pass0" into your kernel config file and > seeing if that solves it? Yes, I see that this is the obvious solution if I wanted to just get my drive working. But I think that this should not cause a panic, and that I might help track this down. The panic is repeatable. Also, the drive works if it's plugged in while booting. I find this strange. Svein Halvor PS: I added questions@ back to the recipient list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB disk causes panic in 7.0-PRERELEASE
Hello, list! Jeg just bought a LaCie external USD hdd to store my pictures. When I plug it in, it causes my laptop to panic after ~15-20 seconds. After a reboot (with the disc still plugged in) it functions properly. These are the messages I get when I plug it in: umass0: on uhub3 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) GEOM_LABEL: Label for provider da0s1 is msdosfs/LaCie. umass0: at uhub3 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry GEOM_LABEL: Label msdosfs/LaCie removed. umass0: detached umass0: on uhub3 xptioctl: pass driver is not in the kernel xptioctl: put "device pass0" in your kernel config file On the next subsequent boot (with the device plugged in), I get: da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) GEOM_LABEL: Label for provider da0s1 is msdosfs/LaCie. And I am able to mount it. If I disconnect, and reconnect it again, the computer panics again. How can I diagnose this? The computer saves a vmcore file. Can I use this to harvest some more information? FreeBSD weld.ej2.thelosingend.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Sun Oct 14 15:04:21 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
