From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 11 12:58:25 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E911C16A417; Mon, 11 Feb 2008 12:58:25 +0000 (UTC) (envelope-from ben@altesco.nl) Received: from altus-escon.com (altesco.xs4all.nl [82.95.106.39]) by mx1.freebsd.org (Postfix) with ESMTP id 6FEB513C45D; Mon, 11 Feb 2008 12:58:25 +0000 (UTC) (envelope-from ben@altesco.nl) Received: from benjoam.altus-escon.com (benjoam.altus-escon.com [193.78.231.14]) by altus-escon.com (8.13.6/8.13.1) with ESMTP id m1BCwJAH084206; Mon, 11 Feb 2008 13:58:24 +0100 (CET) (envelope-from ben@altesco.nl) Message-Id: <2B3CDACE-9D13-4A2C-900B-12EB421238B2@altesco.nl> From: Ben Stuyts To: obrien@freebsd.org In-Reply-To: <20080209002356.GB30493@dragon.NUXI.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Mon, 11 Feb 2008 13:58:18 +0100 References: <3E1A8014-3F18-492B-8288-46706F420123@altesco.nl> <9892EE5A-068E-4BFA-8D31-9FF7184C3181@altesco.nl> <20080209002356.GB30493@dragon.NUXI.org> X-Mailer: Apple Mail (2.915) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (altus-escon.com [193.78.231.42]); Mon, 11 Feb 2008 13:58:24 +0100 (CET) X-Virus-Scanned: ClamAV 0.92/5769/Mon Feb 11 11:56:45 2008 on earth.altus-escon.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Panic when connecting USB drive to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2008 12:58:26 -0000 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