Messages in this thread | | | From | "Perez-Gonzalez, Inaky" <> | Subject | AIC7(censored) card gone wild? | Date | Fri, 20 Jun 2003 21:10:55 -0700 |
| |
Hi Justin, list ...
I have a 2xPIII 797 Mhz with an AIC-7899P U160/m; I have been running it under 2.5.66 since it was released, always using the AIC7XXXX driver (new one).
However, suddenly something weird happened; since one week ago, I get panics (in the serial console) like the one attached (milikk.panic.txt) always caused or having an rsync process as current (rsync is used for backup).
I also noticed that at about the same time I started to get got those panics, I get the following when booting the kernel:
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.28 <Adaptec aic7899 Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit) Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DA40 Type: Direct-Access ANSI SCSI revision: 03 scsi0:A:0:0: Tagged Queuing enabled. Depth 8 (scsi0:A:6): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit) Vendor: QUANTUM Model: ATLAS10K2-TY367L Rev: DDD6 Type: Direct-Access ANSI SCSI revision: 03 scsi0:A:6:0: Tagged Queuing enabled. Depth 8 scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.28 <Adaptec aic7899 Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
scsi1: Unexpected busfree while idle SEQADDR == 0x31 scsi1:0:4:0: Attempting to queue an ABORT message >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< scsi1: Dumping Card State while idle, at SEQADDR 0x9 Card was paused ACCUM = 0x2, SINDEX = 0x48, DINDEX = 0xe4, ARG_2 = 0x0 HCNT = 0x0 SCBPTR = 0x0 SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x1] SCSISEQ[0x12] SBLKCTL[0x6] SCSIRATE[0x0] SEQCTL[0x10] SEQ_FLAGS[0xc0] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x8] SIMODE1[0xa4] ..... <SNIPPED- full version @ attached milikk.dump> ...
So I wonder, what does that error mean? SCSI1 has attached a CDRW (Sony Yamaha CDRW 8/4/24) but now it doesn't show up anymore (and so, I cannot get the model). .
Could it mean by SCSI Adapter is hosed? or my CDRW drive? or something else? I see this same behavior with 2.5.72, although it gets stuck in "scsi1: Unexpected busfree while idle\nSEQADDR == 0x31", repeats it, goes up to 0x32, back to 0x31 again, repeats 0x31 ...
Removing the CDRW helps (no more message) so I tend to assume the CDRW is dead; but I am still waiting to see a panic again.
Thanks,
Iñaky Pérez-González -- Not speaking for Intel -- all opinions are my own (and my fault)
<<milikk.dump>> kernel BUG at kernel/timer.c:376!60/serio0 invalid operand: 0000 [#1]plorer Mouse on isa0060/serio1 CPU: 0---[ cut here ]------------ EIP: 0060:[<c012dd08>] Not tainted EFLAGS: 00010007 eax: f0ebdf68 ebx: f0ebdf68 ecx: 00eb9f00 edx: c1a135dc esi: c1a13da4 edi: c1a134a0 ebp: 0000001f esp: d89f3704 ds: 007b es: 007b ss: 0068 Process rsync (pid: 9968, threadinfo=d89f2000 task=f5be0040) Stack: c1a134a0 f71cded4 c1a134a0 015c0060 fffffffd d89f2000 c012e301 c1a134a0 c1a13cac 0000001f d89f2000 00000000 00000001 00000001 c042e228 fffffffd 00000000 c0129be5 c042e228 00000046 c0453088 00000000 c0453084 d89f3780 Call Trace: [<c012e301>] [<c0129be5>] [<c011a317>] [<c010bf3a>] [<c0205f4d> Code: 0f 0b 78 01 1f c2 38 c0 eb d5 8d b4 26 00 00 00 00 8d bc 27 <0>Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing [unhandled content-type:application/octet-stream]
| |