I suspect it is *NOT* hardware. We had the same log messages. But under RH it works perfectly :-( Unfortunately. Regards Harry
-----Original Message----- From: Jim Bonnet [SMTP:jimbo@caldera.com] Sent: Thursday, October 24, 2002 3:45 PM To: SLE Subject: Re: [SLE] "aic7xxx_abort returns 0x2002"...
Jim Bonnet wrote:
Bruce Marshall wrote:
On Wednesday 23 October 2002 10:16 am, Jim Bonnet wrote:
I have this same error.. I have yet to resolve the problem, I am running suse kernel 2.4.16... Which kernel are you running? Further- when you get this error does your machine hard lock?
What I find is that I can write to the tape device hanging on this card(2940UW) for several hundred megabytes and then for no apparent reason I get this error.
Regards- Jim
Are you sure you are running the aic7xxx_old module?? I've never had any problems with that module (and I think the new one is a piece of crap) on 2940UW's or the newer xx160 controllers.
I'm trying it now. I read that this helped the issue. I just got the new
2.4.19 kernel from SuSE and am running tests.. Stay tuned ;)
Jim
No joy- Now Im running this kernel: k_deflt-2.4.19-117 which I think is the latest offered.. Im now no longer getting machine hangs but instead a process that is bound to /dev/st0 waiting on a write that can not or will not complete.. In the logs I see this kernel debugging output:
Oct 24 02:50:43 ns1 kernel: scsi2:0:5:0: Attempting to queue an ABORT message Oct 24 02:50:43 ns1 kernel: scsi2: Dumping Card State while idle, at SEQADDR 0x7 Oct 24 02:50:43 ns1 kernel: ACCUM = 0xf9, SINDEX = 0x57, DINDEX = 0x26, ARG_2 = Oct 24 02:50:43 ns1 kernel: HCNT = 0x0 SCBPTR = 0x0 Oct 24 02:50:43 ns1 kernel: SCSISEQ = 0x12, SBLKCTL = 0x2 Oct 24 02:50:43 ns1 kernel: DFCNTRL = 0x0, DFSTATUS = 0x2d Oct 24 02:50:43 ns1 kernel: LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80 Oct 24 02:50:43 ns1 kernel: SSTAT0 = 0x5, SSTAT1 = 0xa Oct 24 02:50:43 ns1 kernel: STACK == 0x3, 0x190, 0x160, 0x0 Oct 24 02:50:43 ns1 kernel: SCB count = 4 Oct 24 02:50:43 ns1 kernel: Kernel NEXTQSCB = 2 Oct 24 02:50:43 ns1 kernel: Card NEXTQSCB = 2 Oct 24 02:50:43 ns1 kernel: QINFIFO entries: Oct 24 02:50:43 ns1 kernel: Waiting Queue entries: Oct 24 02:50:43 ns1 kernel: Disconnected Queue entries: 0:3 Oct 24 02:50:43 ns1 kernel: QOUTFIFO entries: Oct 24 02:50:43 ns1 kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 Oct 24 02:50:43 ns1 kernel: Sequencer SCB Info: 0(c 0x4c, s 0x57, l 0, t 0x3) 1( Oct 24 02:50:43 ns1 kernel: Pending list: 3(c 0x48, s 0x57, l 0) Oct 24 02:50:43 ns1 kernel: Kernel Free SCB list: 1 0 Oct 24 02:50:43 ns1 kernel: Untagged Q(5): 3 Oct 24 02:50:43 ns1 kernel: DevQ(0:5:0): 0 waiting Oct 24 02:50:43 ns1 kernel: (scsi2:A:5:0): Queuing a recovery SCB Oct 24 02:50:43 ns1 kernel: scsi2:0:5:0: Device is disconnected, re-queuing SCB Oct 24 02:50:43 ns1 kernel: Recovery code sleeping Oct 24 02:50:44 ns1 kernel: Recovery SCB completes Oct 24 02:50:44 ns1 kernel: Recovery code awake Oct 24 02:50:44 ns1 kernel: aic7xxx_abort returns 0x2002 Oct 24 02:50:44 ns1 kernel: scsi2:0:5:0: Attempting to queue a TARGET RESET mess Oct 24 02:50:44 ns1 kernel: scsi2:0:5:0: Command not found Oct 24 02:50:44 ns1 kernel: aic7xxx_dev_reset returns 0x2002 Oct 24 02:50:49 ns1 kernel: scsi: device set offline - not ready or command retr Oct 24 02:50:50 ns1 kernel: st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host Oct 24 02:50:50 ns1 kernel: st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host
I get similar results with both the drivers.. (_old and the new one) I have also toggled off acpi, apic, apm, and smp to really try and simplify my setup..
I'm starting to suspect hardware in my case but will keep messing with it..This tape drive was working recently. but hardware does fail..Its an HP T20e drive
I get the symptoms when writing say a 20gb directory to the tape. It works just fine on smallish dir's but the big ones are problematic.
Regards- Jim
--
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com