Repeatable kernel panic on -CURRENT using ZFS over SATA

Steven Schlansker stevenschlansker at berkeley.edu
Tue Oct 2 01:32:23 PDT 2007


Hello everyone,
I recently set up a 6 drive SATA raidz2.  Whenever I try to use the 
array, the dmesg fills up with warnings that WRITE_DMA must be retried 
(repeatedly)

As soon as I remove the load, everything runs fine.

FreeBSD scotch.CSUA.Berkeley.EDU 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue 
Sep 25 21:37:14 PDT 2007 
root at scotch.CSUA.Berkeley.EDU:/usr/obj/usr/src/sys/GENERIC  i386

00:00.0 Host bridge: Intel Corporation 82840 840 (Carmel) Chipset Host 
Bridge (Hub A) (rev 01)
00:01.0 PCI bridge: Intel Corporation 82840 840 (Carmel) Chipset AGP 
Bridge (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02)
00:1f.2 USB Controller: Intel Corporation 82801AA USB (rev 02)
00:1f.3 SMBus: Intel Corporation 82801AA SMBus (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA 
TNT2/TNT2 Pro] (rev 11)
02:04.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] 
(rev 78)
02:06.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 
[CrystalClear SoundFusion Audio Accelerator] (rev 01)
02:0e.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
03:05.0 RAID bus controller: Silicon Image, Inc. SiI 3114 
[SATALink/SATARaid] Serial ATA Controller (rev 02)
03:06.0 RAID bus controller: Silicon Image, Inc. SiI 3512 
[SATALink/SATARaid] Serial ATA Controller (rev 01)
03:0a.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
03:0a.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)



Dmesg with errors here:
http://soda.csua.berkeley.edu/~steven/dmesg.txt

The eventual end result:
http://soda.csua.berkeley.edu/~steven/Image053.jpg


The only references I can find to similar problems were either not 
resolved, or seemed to be related to a chipset which I am not using.

Is this a known issue?  How can I make this machine stable?  Is there 
any more information I can provide to aid debugging?  Thanks so very much,
Steven Schlansker


More information about the freebsd-current mailing list