[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Stability of OpenBSD 2.8 / Advansys driver

I'm extremely happy with OpenBSD overall, but am alarmed that in a 
bit over 3 months I've experienced two crashes.  I'm used to BSD 
*never* crashing.

The first case seemed to be associated with Netatalk, and I wrote it 
off to that part of the kernel.  I didn't keep good notes as to 
exactly what happened.  Roughly:  From the Mac, my OpenBSD server 
wasn't appearing at all; when I tried to kill the daemons the kernel 
paniced and I ended up in the debugger.

Yesterday's crash is more alarming.  Symptoms again started with a 
client file sharing oddness.  I am running samba-2.0.6, and the fun 
started when Windows Explorer took forever to create a folder in a 
directory on a Samba share.  This kept happening from Windows 
explorer, but a DOS session had no problem.  A little voice told me 
to reboot the OpenBSD machine, but was immediately drowned out by a 
bigger voice that said "Are you crazy?  We don't solve problems by 
rebooting BSD.  Reboot Windows, for crying out loud."  I did.  The 
problem went away.  Usual mutters about Microsoft crap.  Still, this 
was really odd, I've never seen a Windows network *do this* before.

The little voice kept saying something is wrong here, you better do a 
backup.  Next thing I know it sounds like the driver is retensioning 
the tape.  Then I heard it again.  The next thing I know I am plopped 
into the kernel debugger.  The console has the messages

st0(adv0:5:0): timed out
adv0: exiting ccb not allocated!

It seems as though the Advansys driver has croaked on me.

This is not nice at all.  All my file systems are on a SCSI disk on 
this same controller.

So the questions:

Are there known problems with the Advansys driver?  What exactly does 
the "exiting ccb not allocated!" message mean?  Should I be running a 
different SCSI controller?

The Windows share problem and the tape driver problem may be 
completely unrelated, of course, but I wonder.

I've gotten pretty comfortable in recent months coming to think of 
OpenBSD as The Gold Standard.  I *REALLY* like it, for a lot of 
reasons.  But if I can't get more than a month and a half of uptime 
between crashes, yipes, that's not good.

Any advice appreciated, dmesg enclosed.

OpenBSD 2.8-stable (kernel) #3: Sun Jan  7 01:05:19 EST 2001
cpu0: F00F bug workaround installed
cpu0: Intel Pentium/MMX ("GenuineIntel" 586-class) 200 MHz
real mem  = 100249600 (97900K)
avail mem = 88162304 (86096K)
using 1249 buffers containing 5115904 bytes (4996K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(c5) BIOS, date 02/27/97, BIOS32 rev. 0 @ 
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82437VX" rev 0x02
pcib0 at pci0 dev 7 function 0 "Intel 82371SB (Triton II) PCI-ISA" 
rev 0x01
pciide0 at pci0 dev 7 function 1 "Intel 82371SB (Triton II) IDE" rev 
0x00: DMA, channel 0 wired to compatibility, channel 1 wired to 
atapiscsi0 at pciide0 channel 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 1 lun 0: <, TW240D, 1.10> SCSI0 5/cdrom removable
cd0: can use 32-bit, PIO mode 4, DMA mode 1
wd0 at pciide0 channel 0 drive 0: <QUANTUM BIGFOOT_CY4320A>
wd0: can use 32-bit, PIO mode 4, DMA mode 2
wd0: 16-sector PIO, LBA, 4134MB, 8960 cyl, 15 head, 63 sec, 8467200 
pciide0: channel 0 interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data 
cd0(pciide0:0:1): using PIO mode 0, DMA mode 1 (using DMA data 
adv0 at pci0 dev 17 function 0 "Advansys ABP-930/40UA" rev 0x03: irq 
scsibus1 at adv0: 7 targets
sd0 at scsibus1 targ 0 lun 0: <SEAGATE, ST318416N, 0010> SCSI3 
0/direct fixed
sd0: 17522MB, 14384 cyl, 6 head, 415 sec, 512 bytes/sec, 35885168 sec 
st0 at scsibus1 targ 5 lun 0: <HP, C1533A, 9503> SCSI2 1/sequential 
st0: density code 0x24, variable blocks, write-enabled
xl0 at pci0 dev 19 function 0 "3Com 3c905B 100Base-TX" rev 0x30: irq 
9xl0: command never completed!
 address 00:01:02:e7:e2:6c
exphy0 at xl0 phy 24: 3Com internal media interface
xl0: command never completed!
"Alliance Semiconductor AT22" rev 0x00 at pci0 dev 20 function 0 not 
isa0 at pcib0
isadma0 at isa0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
vt0 at isa0 port 0x60/16 irq 1: vga 80 col, color, 8 scr, mf2-kbd
pms0 at vt0 irq 12
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
isapnp0 at isa0 port 0x279: read port 0x203
ym0 at isapnp0 "OPL3-SAX Sound Board, YMH0021, , " port 
0x220/16,0x530/8,0x388/4,0x330/2,0x370/2 irq 5 drq 0,1
midi1 at ym0: <YM MPU-401 UART>
audio0 at ym0
joy0 at isapnp0 "OPL3-SAX Sound Board, YMH0022, PNPB02F, " port 
"OPL3-SAX Sound Board, YMH002F, , " at isapnp0 port 0x100/8 not 
wdc2 at isapnp0 "OPL3-SAX Sound Board, YMH0024, PNP0600, " port 
0x1e8/8,0x3ee/1 irq 11
pccom3 at isapnp0 "SupraExpress 336i PnP Voice Mod, SUP1381, SUP1290, 
" port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
biomask 4c40 netmask 4e40 ttymask 5ec2
pctr: 586-class performance counters and user-level cycle counter 
wd0: no disk label
dkcsum: wd0 matched BIOS disk 81
dkcsum: sd0 matched BIOS disk 80
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
WARNING: / was not properly unmounted

#include <disclaimer.h>
Jim Rosenberg
Ross Mould
259 S. College St.
Washington, PA  15301
(724) 222-7006 x 189
E-mail: jrosenberg_(_at_)_rossint_(_dot_)_net

Visit your host, monkey.org