umass causes panic on 7 amd64
avg at icyb.net.ua
Thu Apr 17 15:37:50 UTC 2008
on 17/04/2008 18:31 Paul Schmehl said the following:
> --On Thursday, April 17, 2008 18:06:28 +0300 Andriy Gapon <avg at icyb.net.ua>
>> on 17/04/2008 17:56 Paul Schmehl said the following:
>>> I wish I had a core file to analyze. *Every* time I reboot my machine, I
>>> have to disconnect my usb drive. Then I have to remount it after I'm back
>>> up and running. If I leave it connected during the reboot, I get the same
>>> kind of errors that were posted by Steve. After the system is up and
>>> running, umass is detected normally and I can mount and use the drive with
>>> no problems. I'm on i386, so it doesn't look like an AMD-specific problem.
>>> # uname -a
>>> FreeBSD utd65257.utdallas.edu 7.0-STABLE FreeBSD 7.0-STABLE #6: Wed Apr 16
>>> 17:14:28 CDT 2008 utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC
>>> I've rebuilt kernel and world six times in the hopes that recent src updates
>>> would fix the problem.
>>> Unfortunately, since the error occurs during boot, I know of no way to
>>> capture the error message. If I log console would that do it? I doubt the
>>> console is logging at that point. I don't think syslogd is even running
>> Eh I think I saw something like this myself.
>> Do you by a chance have that new device sg in your kernel?
>> I assume you do (GENERIC) - try to drop it.
>> I am not sure if this is some brokenness of that driver or fighting of
>> several USB drivers over the same hardware.
>> P.S. sorry for the wide broadcast, but I think that users on all 3 lists
>> might be interested.
> This is all I have in my GENERIC conf file:
> # grep -i sg /usr/src/sys/i386/conf/GENERIC
> options SYSVMSG # SYSV-style message queues
I see. Then maybe sg was a red herring in my case.
More information about the freebsd-scsi