Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Jul 1996 19:35:06 -0400 (EDT)
From:      "Amir Y. Rosenblatt" <amir@neuron.net>
To:        freebsd-current@freebsd.org
Subject:   SCSI errors and repeated panics
Message-ID:  <199607212335.TAA00588@prozac.neuron.net>

next in thread | raw e-mail | index | archive | help
A short while ago I started getting massive numbers of SCSI erros (to be 
shown below) followed by kernel panics.  It's happenbed 3 times in the 
last hour.  Only once did it drop me to ddb (output included below).

First off my hardware and software configuration is as follows:
Intel P120 on an ASUS motherboard
64 meg RAM
Adaptec 2940UW hooked up to the following:
	- On the 68-pin cable, a pair of ST32550W 2.1 gig 'cudas (sd0 and 
	  sd1, with SCSI ID's 0 and 1 in that order).
	- On the 50-pin cable, an an HP C1533A DAT drive and an NEC 
	  MultiSpin 4V CD-ROM drive (SCSI IDs 3 and 2 in that order).
	The chain is terminated on one end by the second 'cudah and on 
	the other with the CD-ROM drive.
A 3Com 3c509-TP 
An ATI Mach64 video card.

It's running 2.2-061296-SNAP system binaries with a kernel compiled from 
-current as of June 10th.

The following is from /var/log/messages -- these messages were all 
repeated several dozen times with each crash -- this is just to give a 
sampling.

---------------[Begin Included Text]-------------------

Jul 21 18:17:56 prozac /kernel: sd0(ahc0:0:0): timed out in dataout phase, 
SCSIS IGI == 0x0
Jul 21 18:17:56 prozac /kernel: sd0(ahc0:0:0): timed out in dataout phase, 
SCSIS IGI == 0x0
Jul 21 18:17:57 prozac /kernel: ahc0: Issued Channel A Bus Reset #2. 2 SCBs 
aborted
Jul 21 18:17:57 prozac /kernel: ahc0: Issued Channel A Bus Reset #2. 2 SCBs 
aborted
Jul 21 18:17:57 prozac /kernel: :2
Jul 21 18:17:57 prozac /kernel: :2
Jul 21 18:17:57 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1
Jul 21 18:17:57 prozac /kernel: sd0(ahc0:0:0):  Logical unit is in process 
of becoming ready field replaceable unit: 2
Jul 21 18:17:57 prozac /kernel: sd0(ahc0:0:0):  Logical unit is in process 
of becoming ready field replaceable unit: 2
Jul 21 18:17:57 prozac /kernel: , retries:1
Jul 21 18:17:57 prozac /kernel: , retries:1
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0):  Logical unit is in process 
of becoming ready field replaceable unit: 2
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0):  Logical unit is in process 
of becoming ready field replaceable unit: 2
Jul 21 18:17:58 prozac /kernel: , FAILURE
Jul 21 18:17:58 prozac /kernel: , FAILURE
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0): NOT READY asc:4,1
Jul 21 18:17:58 prozac /kernel: sd0(ahc0:0:0):  Logical unit is in process 
of becoming ready field replaceable unit: 2

[etc...]

Jul 21 18:18:00 prozac /kernel: , retries:1
Jul 21 18:18:00 prozac /kernel: , retries:1
Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0
Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0
Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0):  Power on, reset, or bus 
device reset occurred field replaceable unit: 1
Jul 21 18:18:16 prozac /kernel: sd1(ahc0:1:0):  Power on, reset, or bus 
device reset occurred field replaceable unit: 1
Jul 21 18:18:16 prozac /kernel: , retries:4
Jul 21 18:18:16 prozac /kernel: , retries:4
Jul 21 18:24:35 prozac /kernel: mode = 0100600, inum = 23192, fs = /var
Jul 21 18:24:35 prozac /kernel: mode = 0100600, inum = 23192, fs = /var
Jul 21 18:24:36 prozac /kernel: panic: ffs_valloc: dup alloc
Jul 21 18:24:36 prozac /kernel: panic: ffs_valloc: dup alloc
Jul 21 18:24:36 prozac /kernel: 
Jul 21 18:24:36 prozac /kernel: 
Jul 21 18:24:36 prozac /kernel: syncing disks... 11 11 6 FreeBSD 
2.2-CURRENT #0: Mon Jul 15 22:23:14 EDT 1996
Jul 21 18:24:36 prozac /kernel: syncing disks... 11 11 6 FreeBSD 
2.2-CURRENT #0: Mon Jul 15 22:23:14 EDT 1996

[then during bootup]

Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): CD-ROM 
Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): CD-ROM 
Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): NOT READY asc:4,0
Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0): NOT READY asc:4,0
Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0):  Logical unit not ready, 
cause not reportable
Jul 21 18:24:39 prozac /kernel: cd0(ahc0:2:0):  Logical unit not ready, 
cause not reportable
Jul 21 18:24:39 prozac /kernel: can't get the size
Jul 21 18:24:39 prozac /kernel: can't get the size

----------------[End Included Text]--------------------

The third time it hosed itself it dropped into the debugger.  Here's what 
it aaid:

spec_getpages: I/O read error
vm_fault: pager input (probably hardware) error, PID 243 failure

Fatatl trap 12: page fault while in kernel mode
fault virtual address		= 0x80accd0
fault code			= supervisor read, page not present
instruction pointer		= 0x8:0xf0108877
stack pointer			= 0x10:0xefbffde0
frame pointer			= 0x10:0xefbffe0c
code segment			= base 0x0, limit 0xfffff, type 0x1b
				= DPL 0, pres 1, def32 1, gran 1
processor eflags		= interrupt enabled, resume, IOPL=0
current process			= 243 (tcsh)
interrupt mask			= 
kernel: type 12 trap, code=0
Stopped at exec_aout_imgact + 0x17: movl 0(%esi), %edx

Incidentally, I had a vm panic last week that I posted about to the list 
as well.  Don't know if there's a connection.  

As it moved toward the 4th panic (I was watching the SCSI error messages 
pop up on screen, I waited till the disk activity paused, then shut it 
down, removed the cover and cranked up the air conditioner in the room 
all the way.  Let it sit for 15 minutes, closed it back up and brought it 
back online.  It's been bahaving fine so far since then.  I got these 
errors once before, last week, when I installed the CD-ROM drive and 
forgot to adjust the termination appropriately on the SCSI chain.  Fixing 
the termination setup, however put an end to those problems.  I suppose 
it might just be an issue of internal cooling -- it's a full-height tower 
case with a fan in the lower froint sucking air in and one in the upper 
rear pushing it out.  There's no airflow directly over the disks, but I 
did seperate each of them from everything else (including each other) by 
an ampty half-height bay worth of space.  

Any suggestions would be greatly appreciated.  Thank you.

	-Amir





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607212335.TAA00588>