From nobody  Sun Oct 20 07:23:51 1996
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA21462;
          Sun, 20 Oct 1996 07:23:51 -0700 (PDT)
Message-Id: <199610201423.HAA21462@freefall.freebsd.org>
Date: Sun, 20 Oct 1996 07:23:51 -0700 (PDT)
From: lutz@muc.de
To: freebsd-gnats-submit@freebsd.org
Subject: random file system corruptions with 2.1.5R and adaptec 2742
X-Send-Pr-Version: www-1.0

>Number:         1852
>Category:       kern
>Synopsis:       random file system corruptions with 2.1.5R and adaptec 2742
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    gibbs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 20 07:30:04 PDT 1996
>Closed-Date:    Sat Nov 2 12:50:06 PST 1996
>Last-Modified:  Sat Nov  2 12:51:01 PST 1996
>Originator:     Lutz Albers
>Release:        FreeBSD 2.1.5-RELEASE
>Organization:
>Environment:
FreeBSD orlando 2.1.5-RELEASE FreeBSD 2.1.5-RELEASE #0: Sat Oct 19 12:43:14 MET DST 1996     lutz@killashandra:/share/src-2.1.5R/sys/compile/orlando.sea  i386
>Description:
My file systems are getting corrupted since I updated my machine from 2.1R to 2.1.5R.
Most of the errors are 'unallocated inode' errors.  This leads to disapperaring file
(i.e. /kernel, or /etc/master.passwd :-). The problem appears only on one of
my two machines running 2.1.5. The main difference between the 2 machines
is the used SCSI-controller. Tha machine with the corruption problems is
using an Adaptec 2742 (VL-bus) controller, the other machine uses an 
Adaptec 1542CF controller.

Here's the dmesg from the 'bad' machine:
FreeBSD 2.1.5-RELEASE #0: Sat Oct 19 12:43:14 MET DST 1996
    lutz@killashandra:/share/src-2.1.5R/sys/compile/orlando.sea
CPU: i486DX (486-class CPU)
real memory  = 16777216 (16384K bytes)
avail memory = 14860288 (14512K bytes)
ahc0: <Adaptec 284X SCSI host adapter> at 0x1c00-0x1cff irq 12 on isa
ahc0: aic7770 <= Rev C, Single Channel, SCSI Id=7, 4 SCBs
ahc0 waiting for scsi devices to settle
(ahc0:0:0): "SEAGATE ST31230N 0300" type 0 fixed SCSI 2
sd0(ahc0:0:0): Direct-Access 1010MB (2069860 512 byte sectors)
(ahc0:1:0): "IBM OEM 0662S12 3 30" type 0 fixed SCSI 2
sd1(ahc0:1:0): Direct-Access 1003MB (2055035 512 byte sectors)
(ahc0:4:0): "TOSHIBA CD-ROM XM-4101TA 0064" type 5 removable SCSI 2
cd0(ahc0:4:0): CD-ROM cd present.[268501 x 2048 byte records]
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16450
sio1 at 0x2f8-0x2ff irq 10 on isa
sio1: type 16550A
sio2 at 0x3e8-0x3ef irq 11 on isa
sio2: type 16550A
lpt0 at 0x3bc-0x3c3 irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
fd1: 1.2MB 5.25in
sea0 at 0x0 irq 3 maddr 0xca000 msize 16384 on isa

sea0: type Future Domain TMC-885/TMC-950
sea0 waiting for scsi devices to settle
(sea0:5:0): "IOMEGA ZIP 100 C.18" type 0 removable SCSI 2
sd2(sea0:5:0): Direct-Access 
sd2(sea0:5:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB
sd2 could not mode sense (4). Using ficticious geometry

sd2(sea0:5:0): NOT READY asc:3a,0 Medium not present
sd2: could not get size
0MB (0 512 byte sectors)
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 15 on isa
ep0: aui/bnc[*BNC*] address 00:20:af:2f:63:8e
npx0 on motherboard
npx0: INT 16 interface
sb0 at 0x220 irq 5 drq 1 on isa
sb0: <SoundBlaster 16 4.11>
sbxvi0 at 0x0 drq 5 on isa
sbxvo0: <SoundBlaster 16 4.11>
sbmidi0 at 0x330 on isa
 <SoundBlaster MPU-401>

>How-To-Repeat:
I don't know exactly, WHEN the file systems gets corrupted ...
>Fix:
Well, I wish, I knew the solution :-(
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: gibbs 
State-Changed-When: Sun Oct 20 11:18:22 PDT 1996 
State-Changed-Why:  
These types of problems with the 2842 controller are usually related 
to cache invalidation or other DMA hardware problems with the motherboard. 
You should try disabling your external and possibly your internal cache 
and see if the problem persists. 


Responsible-Changed-From-To: freebsd-bugs->gibbs 
Responsible-Changed-By: gibbs 
Responsible-Changed-When: Sun Oct 20 11:18:22 PDT 1996 
Responsible-Changed-Why:  
My area. 
State-Changed-From-To: analyzed->closed 
State-Changed-By: gibbs 
State-Changed-When: Sat Nov 2 12:50:06 PST 1996 
State-Changed-Why:  
Originator confirms problem is fixed by using a more recent version of the 
driver. 
>Unformatted:
