Messages in this thread | | | Date | Mon, 20 Jul 1998 16:53:54 -0700 (PDT) | From | "Aaron J. Grier" <> | Subject | Re: 2.0.35 and aic7xxx |
| |
On Fri, 17 Jul 1998, Aaron D. Turner wrote:
> 2.0.34 is also broken. This time I compiled in verbose scsi error > reporting... here's the scoop: > > Bad scbptr 16 during SELTO > Referenced SCB 255 not vaild during SELTO > SCSI SEQ = 0x5 SEQADDR= 0x5 SSTATO = 0x10 SSTAT1 = 0x8 > Bad scbptr 16 during SELTO > Referenced SCB 255 not vaild during SELTO > SCSI SEQ = 0x5 SEQADDR= 0x8 SSTATO = 0x10 SSTAT1 = 0x8
I see similar messages on the bootup of my 2.1.109 box, but it proceeds to work just fine.
(scsi1:0:-1:-1) Scanning channel for devices. (scsi0:-1:-1:-1) Bad scbptr 255 during SELTO. (scsi0:-1:-1:-1) Referenced SCB 255 not valid during SELTO. SCSISEQ = 0x12 SEQADDR = 0x9 SSTAT0 = 0x10 SSTAT1 = 0x8a
I've found that messing around with the BIOS settings dealing with resetting the card at boot time can change this. Perhaps the card is being initialized to a configuration by BIOS that the driver doesn't completely clear, hence the scbptr error? 255 certainly seems like an initialization value...
---- Aaron J. Grier | agrier@cse.ogi.edu "I generally find that a goat isn't really necessary, but bloodying one's fingers while installing the system and SCSI chain does seem to correlate with more reliable operation." -- Leonard N. Zubkoff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
| |