NetBSD Problem Report #9841
Received: (qmail 1149 invoked from network); 8 Apr 2000 17:26:19 -0000
Message-Id: <200004081725.TAA26306@vader.runit.sintef.no>
Date: Sat, 8 Apr 2000 19:25:43 +0200 (MEST)
From: he@runit.no (Havard Eidnes)
Reply-To: he@runit.no (Havard Eidnes)
To: gnats-bugs@gnats.netbsd.org
Subject: Large-memory i386 (?) machines may trigger file system corruption
X-Send-Pr-Version: 3.95
>Number: 9841
>Category: kern
>Synopsis: buslogic driver corrupts data
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: thorpej
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Apr 08 17:27:00 +0000 2000
>Closed-Date: Sun Feb 10 08:55:01 +0000 2002
>Last-Modified: Sun Feb 10 08:55:01 +0000 2002
>Originator: Havard Eidnes
>Release: NetBSD-current 5 Apr 2000
>Organization:
RUNIT AS
>Environment:
NetBSD iana.sunet.se 1.4X NetBSD 1.4X (GENERIC) #0: Wed Apr 5 15:42:37 MEST 2000 he@iana.sunet.se:/local/nbsrc/src/sys/arch/i386/compile/GENERIC i386
>Description:
This machine which is a PPro200 with 1GB of RAM, can
reproducibly be crashed by running "bonnie" on one of its file
systems.
Another way is to wait for the nightly jobs to run, and those
many times also cause a crash.
However, doing a "make build" does not appear to provoke the
problem.
When this problem has been triggered by "bonnie", parts of
the data from the bonnie run has been scattered over parts
of the disk where it definitely should *not* be, causing
directory and file corruption and a mess to clean up after-
wards.
The typical panic message is triggered by internal error
detection in the ffs code with crashes of type
panic: ffs_valloc: dup alloc
or more frequently
First bad, reclen=33aa, DIRSIZ=28, namlen=19, flags=1000 entryoffsetinblock=0
/var: bad dir ino 129344 at offset 0: mangled entry
panic: bad dir
This is sometimes (but *not* always) preceded by
bha2: mbi not in round-robin order
The disk subsystem on this machine is
bha2 at pci0 dev 13 function 0: BusLogic 9xxC SCSI
bha2: interrupting at irq 11
bha2: model BT-958, firmware 5.06I
bha2: 192 H/W CCBs, sync, parity, tagged queueing
scsibus0 at bha2: 16 targets, 8 luns per target
...
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0: <SEAGATE, ST34572W, 0784> SCSI2 0/direct fixed
sd0: 4340 MB, 6300 cyl, 8 head, 176 sec, 512 bytes/sect x 8888924 sectors
sd1 at scsibus0 target 1 lun 0: <SEAGATE, ST39175LW, 0001> SCSI2 0/direct fixed
sd1: 8683 MB, 11721 cyl, 5 head, 303 sec, 512 bytes/sect x 17783240 sectors
...
This hardware has been running 1.3.3 for a *long* time without
experiencing any similar instability.
This hardware also ran 1.4.2 for a brief while in order to get
new boot code installed, but I did not see the problem with
that system either.
>How-To-Repeat:
Equip machine as above.
Run "bonnie -s 200".
Watch it crash after a minute or two.
>Fix:
Sorry, this is over my head.
Hints for how to debug this further however gratefully
accepted.
The currently running kernel has both DIAGNOSTIC and DEBUG
enabled (as can be seen from the extra info in the last of
the above two panic messages).
>Release-Note:
>Audit-Trail:
From: enami tsugutomo <enami@sm.sony.co.jp>
To: he@runit.no (Havard Eidnes)
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/9841: Large-memory i386 (?) machines may trigger file system corruption
Date: 11 Apr 2000 10:03:20 +0900
he@runit.no (Havard Eidnes) writes:
> This machine which is a PPro200 with 1GB of RAM, can
> reproducibly be crashed by running "bonnie" on one of its file
> systems.
I doubt this failre is caused by large memory. I have a machine with
128MB memory, but I have similar experiences (file system corruption
on scsi disks). The machine works with IDE drive fine.
The common characteristics with your machine are:
PentiumPro 200
Buslogic PCI scsi card
Two scsi drives.
enami.
NetBSD 1.4X (PARITY_ERROR) #338: Mon Apr 10 11:23:52 JST 2000
enami@parity-error.sm.sony.co.jp:/a/compile/PARITY_ERROR
cpu0: family 6 model 1 step 7
cpu0: Intel Pentium Pro (686-class)
total memory = 127 MB
avail memory = 85760 KB
using 4870 buffers containing 39120 KB of memory
BIOS32 rev. 0 found at 0xf7fa0
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82441FX PCI and Memory Controller (PMC) (rev. 0x02)
pcib0 at pci0 dev 1 function 0
pcib0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x01)
pciide0 at pci0 dev 1 function 1: Intel 82371SB IDE Interface (PIIX3)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
wd0 at pciide0 channel 0 drive 0: <WDC WD273BA>
wd0: drive supports 16-sector pio transfers, lba addressing
wd0: 26105 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 53464320 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
pciide0: primary channel interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
pciide0: secondary channel wired to compatibility mode
pciide0: secondary channel ignored (disabled)
fxp0 at pci0 dev 9 function 0: Intel i82557 Ethernet, rev 2
fxp0: interrupting at irq 9
fxp0: Ethernet address 00:a0:c9:9b:19:e9, 10/100 Mb/s
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
tlp0 at pci0 dev 11 function 0: DECchip 21140A Ethernet, pass 2.0
tlp_isv_srom: CRC fail
tlp_isv_srom: 0, 1
tlp0: interrupting at irq 10
tlp0: DEC DE500-AA, Ethernet address 00:00:f8:1e:17:2f
nsphy0 at tlp0 phy 5: DP83840 10/100 media interface, rev. 0
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bha0 at pci0 dev 12 function 0: BusLogic 9xxC SCSI
bha0: interrupting at irq 11
bha0: model BT-948, firmware 5.05R
bha0: 192 H/W CCBs, sync, parity, tagged queueing
scsibus0 at bha0: 8 targets, 8 luns per target
vga0 at pci0 dev 13 function 0: Matrox MGA Millennium 2064W ("Storm") (rev. 0x01)
wsdisplay0 at vga0: console (80x25, vt100 emulation)
wsdisplay0: screen 1-3 added (80x25, vt100 emulation)
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0
lpt0 at isa0 port 0x378-0x37b irq 7
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0-0xff: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
biomask e965 netmask ef65 ttymask ffe7
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <IBM, DCAS-34330, S65A> SCSI2 0/direct fixed
sd0: 4134 MB, 8205 cyl, 6 head, 171 sec, 512 bytes/sect x 8467200 sectors
sd1 at scsibus0 target 2 lun 0: <SEAGATE, ST34371N, 0280> SCSI2 0/direct fixed
sd1: 4148 MB, 5168 cyl, 10 head, 164 sec, 512 bytes/sect x 8496960 sectors
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
From: Havard.Eidnes@runit.sintef.no
To: enami@sm.sony.co.jp
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/9841: Large-memory i386 (?) machines may trigger file system corruption
Date: Tue, 11 Apr 2000 09:45:31 +0200
> > This machine which is a PPro200 with 1GB of RAM, can
> > reproducibly be crashed by running "bonnie" on one of its file
> > systems.
>
> I doubt this failre is caused by large memory. I have a
> machine with 128MB memory, but I have similar experiences (file
> system corruption on scsi disks). The machine works with IDE
> drive fine.
>
> The common characteristics with your machine are:
>
> PentiumPro 200
> Buslogic PCI scsi card
> Two scsi drives.
Ah, OK. After I submitted the PR, Jason made a comment that it
*could* be the Buslogic driver (although that was not certain).
I've already asked for another (type of) controller or an IDE
disk in this machine to see if the problem goes away.
- H=E5vard
From: Havard.Eidnes@runit.sintef.no
To: enami@sm.sony.co.jp
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/9841: Large-memory i386 (?) machines may trigger file system corruption
Date: Tue, 11 Apr 2000 12:12:51 +0200
> I doubt this failre is caused by large memory. I have a
> machine with 128MB memory, but I have similar experiences (file
> system corruption on scsi disks). The machine works with IDE
> drive fine.
>
> The common characteristics with your machine are:
>
> PentiumPro 200
> Buslogic PCI scsi card
> Two scsi drives.
Your suspicion appears to be correct, and the problem appears to
lie with the Buslogic PCI SCSI driver in -current.
I had a Tekram390U2W (53c895-based) installed in the machine, and
it now works just fine where it would earlier "crash and burn".
- H=E5vard
Responsible-Changed-From-To: port-i386-maintainer->thorpej
Responsible-Changed-By: he
Responsible-Changed-When: Thu Jun 1 15:13:29 PDT 2000
Responsible-Changed-Why:
Requested by Jason.
From: Havard Eidnes <he@netbsd.org>
To: thorpej@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-i386/9841
Date: Sat, 10 Mar 2001 19:23:22 +0100
Hi,
I suppose this PR can be closed, since
sys/dev/ic/bha.c 1.38
and associated headers have been applied and pulled up to the 1.5
release branch?
- H=E5vard
State-Changed-From-To: open->closed
State-Changed-By: thorpej
State-Changed-When: Sun Feb 10 00:54:46 PST 2002
State-Changed-Why:
The offending bha driver revisions have been backedou out.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.