From owner-freebsd-hackers Fri Nov 16 10:30:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2A24737B418 for ; Fri, 16 Nov 2001 10:30:05 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fAGIWFo01305; Fri, 16 Nov 2001 10:32:16 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200111161832.fAGIWFo01305@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: sandeepj@research.bell-labs.com (Sandeep Joshi) Cc: hackers@freebsd.org Subject: Re: Tracking down "BTX halted" In-reply-to: Your message of "Fri, 16 Nov 2001 11:03:30 EST." <200111161603.LAA09239@aura.research.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 16 Nov 2001 10:32:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I changed the disklabels on a few SCSI disks and now > I keep getting these "BTX halted" messages every time > I reboot. The most likely cause of this is that you're messing up the disks to the point that your BIOS (probably your SCSI controller BIOS) is crashing when it tries to read them. > They dont occur if I disconnect those disks. They occur > even after I rewrite those labels. Its not dedicated mode > or whatever now.. You must have missed something. 8) > I am willing to post the entire system configuration > but it would be really nice if instead someone could > tell me _HOW_ to determine the problem. If the above guess is correct, you're looking at a BIOS bug. You might try updating your SCSI controller/motherboard BIOS, but there's no guarantee that'll fix the problem. The only real solution is to hot-plug the disks, camcontrol rescan, then dd zeroes over the heads of the disks and then re-lable them safely. > A colleague tells me its possible to track the problem > from the registers(cs,es,..) in the message dump. That would tell you where, exactly, the crash is occuring, and would make it possible to absolutely finger the culprit. What's the value of the cs register? If it's above 0xa000, then the BIOS is at fault. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message