From owner-freebsd-current Sun Jun 2 21:53:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA04989 for current-outgoing; Sun, 2 Jun 1996 21:53:40 -0700 (PDT) Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04983; Sun, 2 Jun 1996 21:53:37 -0700 (PDT) Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.7.5/8.6.9) with ESMTP id VAA14272; Sun, 2 Jun 1996 21:53:34 -0700 (PDT) To: gibbs@freebsd.org Cc: current@freebsd.org Subject: more aha2940w timeouts. Date: Sun, 02 Jun 1996 21:53:32 -0700 Message-ID: <14268.833777612@pain.csrv.uidaho.edu> From: Faried Nawaz Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, With a kernel built last night around 10pm PST (after a sup), things appeared stable until 3am, when I got timeouts. I had no reboots or crashes. The boot dmesg output is ahc0 rev 0 int a irq 15 on pci0:13 mapreg[10] type=1 addr=0000fc00 size=0100. mapreg[14] type=0 addr=fefff000 size=1000. ahc0: Reading SEEPROM...done. ahc0: aic7870 Wide Channel, SCSI Id=7, 16 SCBs ahc0: Reseting Channel A ahc0: Downloading Sequencer Program...Done ahc0: Probing channel A ahc0 waiting for scsi devices to settle ahc0: target 0 synchronous at 5.0MHz, offset = 0xf (ahc0:0:0): "CONNER CFA540S 0FAE" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 510MB (1045242 512 byte sectors) sd0(ahc0:0:0): with 2800 cyls, 4 heads, and an average 93 sectors/track ahc0: target 4 using 16Bit transfers ahc0: target 4 synchronous at 10.0MHz, offset = 0x8 (ahc0:4:0): "QUANTUM XP34301 1051" type 0 fixed SCSI 2 sd1(ahc0:4:0): Direct-Access 4106MB (8410200 512 byte sectors) sd1(ahc0:4:0): with 4076 cyls, 20 heads, and an average 103 sectors/track The syslog messages are Jun 2 03:00:18 newshound /kernel: sd0(ahc0:0:0): timed out in command phase, SCSISIGI == 0x84 Jun 2 03:00:21 newshound /kernel: sd1(ahc0:4:0): asserted ATN - device reset inmessage buffer Jun 2 03:00:21 newshound /kernel: sd1(ahc0:4:0): timed out in command phase, SCSISIGI == 0x94 Jun 2 03:00:21 newshound /kernel: ahc0: Issued Channel A Bus Reset #1. 4 SCBs aborted Jun 2 03:00:22 newshound /kernel: ahc0: target 0 synchronous at 5.0MHz, offset= 0x8 Jun 2 03:00:22 newshound /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 Jun 2 03:00:22 newshound /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Jun 2 03:00:22 newshound /kernel: , retries:3 Jun 2 03:00:22 newshound /kernel: ahc0: target 4 using 16Bit transfers Jun 2 03:00:22 newshound /kernel: sd1(ahc0:4:0): UNIT ATTENTION asc:29,0 Jun 2 03:00:22 newshound /kernel: sd1(ahc0:4:0): Power on, reset, or bus device reset occurred sks:80,0 Jun 2 03:00:22 newshound /kernel: , retries:3 Jun 2 03:00:22 newshound /kernel: ahc0: target 4 synchronous at 10.0MHz, offset= 0x8 Jun 2 07:33:26 newshound /kernel: sd0(ahc0:0:0): timed out in command phase, SCSISIGI == 0x84 Jun 2 07:33:29 newshound /kernel: sd0(ahc0:0:0): BUS DEVICE RESET message queued. Jun 2 07:33:29 newshound /kernel: sd0(ahc0:0:0): timed out in command phase, SCSISIGI == 0x84 Jun 2 07:33:29 newshound /kernel: ahc0: Issued Channel A Bus Reset #1. 4 SCBs aborted Jun 2 07:33:29 newshound /kernel: ahc0: target 0 synchronous at 5.0MHz, offset= 0x8 Jun 2 07:33:29 newshound /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 Jun 2 07:33:29 newshound /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Jun 2 07:33:29 newshound /kernel: , retries:3 Jun 2 07:33:29 newshound /kernel: ahc0: target 4 using 16Bit transfers Jun 2 07:33:29 newshound /kernel: sd1(ahc0:4:0): UNIT ATTENTION asc:29,0 Jun 2 07:33:29 newshound /kernel: sd1(ahc0:4:0): Power on, reset, or bus device reset occurred sks:80,0 Jun 2 07:33:29 newshound /kernel: , retries:3 Jun 2 07:33:29 newshound /kernel: ahc0: target 4 synchronous at 10.0MHz, offset= 0x8 I don't know what triggered them at either time. I'm guessing heavy disk activity at 3am (by news.daily) caused the timeouts then. I did what you mentioned -- disable parity on the controller. On the brighter side, I've had no vm problems so far (pmap.c -- v1.97, old p90 with 48mb ram). faried.