From owner-freebsd-hackers Wed Nov 25 21:26:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26479 for freebsd-hackers-outgoing; Wed, 25 Nov 1998 21:26:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles143.castles.com [208.214.165.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26471 for ; Wed, 25 Nov 1998 21:26:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00686; Wed, 25 Nov 1998 21:24:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811260524.VAA00686@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Shenton cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.7 on K6/2, SCSI ncr0 hangs/aborts at boot, then recovers In-reply-to: Your message of "25 Nov 1998 17:33:11 EST." <86iug3l7x4.fsf@samizdat.uucom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Nov 1998 21:24:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But when it boots, it goes through the boot loader/selector, finds the > boot code, and scans the devices, and tries to mount / from the disk. > Then it just hangs for a minute -- but finally reports and error and > completes the boot. I'm very concerned this is going to cause me mucho > trouble in the future but it does seem to work, in a sketchy way. When you say "in a sketchy way", do you mean that the system is working OK from this point on, or are there other problems? > Here's my transcript of the boot sequence from dmesg: > > [scans devices] > > changing root device to sd1s2a > > [hangs for about 60 seconds] > > ncr0: aborting job ... > ncr0:2: ERROR (90:0) (8-0-0) (0/3) @ (script 5b4:50000000). > ncr0: script cmd = 80000000 > ncr0: regdump: de 00 00 03 47 00 06 1f 35 08 80 00 90 00 0f 02. > ncr0: restart (fatal error). > sd1(ncr0:2:0): COMMAND FAILED (9 ff) @f051e000. > sd1(ncr0:2:0): 10.0 MB/s (100 ns, offset 8) > WARNING: / was not properly dismounted. > [...] > > > I don't understand how it can read the boot code from the disk with no > complaints, but then has this weird hang when mounting /. Different code talking to the device; the bootstrap uses the BIOS, while the kernel uses its own driver. It looks like the NCR part is left in a funny state that takes a restart (several?) to recover from. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message