Date: Mon, 11 Feb 2008 13:58:18 +0100 From: Ben Stuyts <ben@altesco.nl> To: obrien@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Panic when connecting USB drive to amd64 Message-ID: <2B3CDACE-9D13-4A2C-900B-12EB421238B2@altesco.nl> In-Reply-To: <20080209002356.GB30493@dragon.NUXI.org> References: <3E1A8014-3F18-492B-8288-46706F420123@altesco.nl> <9892EE5A-068E-4BFA-8D31-9FF7184C3181@altesco.nl> <20080209002356.GB30493@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 Feb 2008, at 01:23, David O'Brien wrote: > On Fri, Feb 08, 2008 at 07:02:46PM +0100, Ben Stuyts wrote: >>> >> I have connected the same drive to a different system, running a >> somewhat >> older version of i386 7.0, and it does not panic. So maybe it is >> amd64 >> specific. Here are the drive's details that came up: >> >> FreeBSD jirad.altus-escon.com 7.0-BETA4 FreeBSD 7.0-BETA4 #3: Tue >> Dec 4 >> 17:03:57 CET 2007 root@jirad.altus-escon.com:/usr/obj/usr/src/sys/ >> GENERIC i386 > > The kernel you paniced with is from Feb 2008. It would be helpful > if you > could try either a BETA4 kernel on your AMD64 machine, or a Feb 2008 > kernel on your i386. Ok, I tested with an updated kernel on the i386, and it works fine. So at least it is not a regression problem. > Also note, if these two machines are different, they can easily have > different hardware and thus trigger/not-trigger the problem just due > to > the HW differences. Yes, very different. In any case, the problem still exists on the amd64 machine, so I'd appreciate any help in getting this problem resolved. Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2B3CDACE-9D13-4A2C-900B-12EB421238B2>