From owner-freebsd-hackers Mon Mar 17 18:50:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA25695 for hackers-outgoing; Mon, 17 Mar 1997 18:50:44 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA25681 for ; Mon, 17 Mar 1997 18:50:39 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA03582; Mon, 17 Mar 1997 21:50:04 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 17 Mar 1997 21:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id VAA01497 for ; Mon, 17 Mar 1997 21:32:00 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id VAA00497 for freebsd-hackers@freefall.cdrom.com; Mon, 17 Mar 1997 21:37:20 -0500 (EST) Date: Mon, 17 Mar 1997 21:37:20 -0500 (EST) From: Thomas David Rivers Message-Id: <199703180237.VAA00497@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Another problems with aha2940 in 2.1-STABLE (post 2.1.7) - process stuck. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well - thanks to Charles, I'm actually running this morning's 2.1-STABLE release (thanks again.) However, I just ran my aha2940 "killer" test; which is a tar to /dev/rst0 of some significant quantity. In 2.1.6.1; this would cause the machine to lock up - as I reported earlier - the SCSI bus would simply go wild when the last tape write had completed and the tape was in the process of rewinding. Further SCSI I/O was hosed; causing an eventual panic/reboot. This has improved somewhat, as the machine doesn't go crazy. But, the process doing the write is "stuck." The output of /bin/ps -gaxl shows the process is stuck in scsicm: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 402 397 5 -5 5 552 400 scsicm DN+ p0 0:19.90 tar cvf /dev/rst0 Cnews POP X sc shape1.4pl6 I am unable to kill the process (a reboot is likely in order.) Also, the following messages appeared on the console: sd0(ahc0:0:0): SCB 0x4 - timed out in command phase, SCSISIGI == 0x84 SEQADDR == 0x61 st0(ahc0:2:0): abort message in message buffer sd0(ahc0:0:0): SCB 0x2 timedout while recovery in progress st0(ahc0:2:0): SCB 0x3 - timed out in command phase, SCSISIGI == 0x94 SEQADDR == 0x60 st0(ahc0:2:0): no longer in timeout ahc0: Issued Channel A Bus Reset. 3 SCBs aborted Clearing bus reset sd0(ahc0:0:0): UNIT ATTENTION info?:4020040 asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred , retries:3 sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:3 sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:2 Clearing 'in-reset' flag sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:2 sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:1 sd0(ahc0:0:0): NOT READY info?:4020040 asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , retries:1 sd0(ahc0:0:0): NOT READY asc:4,1 sd0(ahc0:0:0): Logical unit is in process of becoming ready , FAILURE For completeness; here's the devices found during the probe: ahc0 rev 0 int a irq 15 on pci0:17 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "HP C3323-300 4242" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1003MB (2056008 512 byte sectors) (ahc0:1:0): "MICROP 1548-15MZ1077802 HZ2P" type 0 fixed SCSI 1 sd1(ahc0:1:0): Direct-Access 1635MB (3349512 512 byte sectors) (ahc0:2:0): "WANGTEK 5150ES SCSI FA23 08" type 1 removable SCSI 1 st0(ahc0:2:0): Sequential-Access drive offline (ahc0:3:0): "NEC CD-ROM DRIVE:400 1.0" type 5 removable SCSI 2 cd0(ahc0:3:0): CD-ROM cd0(ahc0:3:0): NOT READY asc:3a,0 Medium not present can't get the size Hope this helps debug this a little... - Dave Rivers -