Re: Adaptec 29320LPE errors on boot

Rodrigo Severo
2008-03-05T16:26:20Z

On 3/5/08, James Bottomley <James.Bottomley@hansenpartnership.com> wrote:
> On Wed, 2008-03-05 at 12:42 -0300, Rodrigo Severo wrote:
> > I have this Adaptec 29320LPE SCSI board (used the aic79xx driver)
> > which give several errors during boot time, just after it recognizes
> > the HDs connected to it.
> >
> > If I remove the SCSI HD there are no SCSI errors.
> >
> > The very first error messages have scrolled up and I don't know how to
> > get to them (is there a way?)
>
>
> If you can get it to boot (say to a ramdisk with a shell) then dmesg
> gives them ... otherwise you need a serial console.

I managed to get the first error messages:

Attempting to Queue an Abort message: CDB 0x3c 0xa 0x0 0x0 0x0 0x0 0x0 0xfc 0x0
scsi0: hwerrint, Discard Timer has timed out
scsi0: hwerrint, Illegal Opcode in sequencer program

then it gets to the messages I included in my previous message.

> > but here is the transcript of what I can
> > see:
> >
> > scsi0: hwerrint, Sequencer Parity Error
> > scsi0: hwerrint, Data-path Parity Error
> > scsi0: hwerrint, Scratch or SCB Memory Parity Error
> > scsi0: hwerrint, CIOBUS Parity Error
>
>
> That's a pretty comprehensive sequence of parity errors. Assuming
> they're the root cause rather than something caused by the first error:
> best case, you just need a better cable or termination;

I don't think so (please see my answer to Mark Salyzyn's message).

> worst case, your
> card is actually hosed in its internal data path.

I also don't think so because I get this same exact error if I try
this SCSI board on three different motherboard models BUT there is one
fourth model where I don't get these errors. Some info on the "working
motherboard":

# lspci
00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2)
00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1)
00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2)
00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2)
00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6100
nForce 430 (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Miscellaneous Control
01:06.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)
01:06.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m (rev 01)
01:07.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
04:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit
Ethernet Adapter (rev b0)

In face of this info on the varying behaviour on different
motherboards and of the info on my asnwer to Mark Salyzyn's message do
you still think this can be a cable/driver/terminator/adapter issue?

I ask because it seems unlikely to me but I don't have that much
experience on SCSI issues.

Regards,