Date: Thu, 17 Apr 2008 18:06:28 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Paul Schmehl <pauls@utdallas.edu> Cc: freebsd-scsi@freebsd.org, Steve Franks <stevefranks@ieee.org>, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: umass causes panic on 7 amd64 Message-ID: <48076774.4090602@icyb.net.ua> In-Reply-To: <767FB33508C0E8E4E3CAA61A@utd65257.utdallas.edu> References: <1207959807.00055755.1207949401@10.7.7.3> <1208046195.00056100.1208036121@10.7.7.3> <539c60b90804141549u6a138ad9u9c77bbfcbbad0ff3@mail.gmail.com> <20080415175347.GA29045@slackbox.xs4all.nl> <539c60b90804151134q7a25a141m1205a1b04d8ffc2c@mail.gmail.com> <20080415192028.GA31706@slackbox.xs4all.nl> <539c60b90804160910q3a242d7amb474b40065d6c9c6@mail.gmail.com> <1208373797.00057829.1208362805@10.7.7.3> <48071956.2090103@icyb.net.ua> <767FB33508C0E8E4E3CAA61A@utd65257.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 i386 > > 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 yet. > 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. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48076774.4090602>