[402] in linux-scsi channel archive
Re: NCR53c810 lockups
daemon@ATHENA.MIT.EDU (Drew Eckhardt)
Wed Jul 19 05:25:18 1995
To: Geoffrey Bennett <geoffrey@tafe.sa.edu.au>
cc: linux-scsi@vger.rutgers.edu
In-reply-to: Your message of "Wed, 21 Jun 1995 22:14:30 +0930."
<9506211244.AA17102@bAARNie.tafe.sa.edu.au>
Date: Tue, 18 Jul 1995 22:15:18 -0600
From: Drew Eckhardt <drew@poohsticks.org>
In message <9506211244.AA17102@bAARNie.tafe.sa.edu.au>, geoffrey@tafe.sa.edu.au
writes:
>'lo all...
>
>I'm having a bit of trouble at the moment with lockups on a computer
>here with an NCR53c810 controller.
>
>If I run disk intensive stuff (e.g. cat /dev/sda > /dev/null and do
>something else) then I get messages like:
>
>Jun 21 22:04:42 Kara kernel: scsi0 : DANGER : abort_connected() called
>Jun 21 22:04:42 Kara kernel: scsi0 : DMA FIFO not empty
>Jun 21 22:04:42 Kara kernel: scsi0 : DMA FIFO not empty
>Jun 21 22:04:42 Kara kernel: scsi0 : unexpected phase unknown at dsp = 0x1d127
>0
>Jun 21 22:04:42 Kara kernel: 001d1270 : 0x0e000001 0x001d0a99
>Jun 21 22:04:42 Kara kernel: 001d1278 : 0x48000000 0x00000000
If you want any help with your problem :
1. Upgrade to rel9 of the driver, available from
ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/ncr53c810
Get the patches against 1.2.10 (sortof) and see the READMEs.
These fix huge numbers of bugs in the distribution driver.
2. Join the NCR mailing list by sending mail to
majordomo@colorado.edu
with
subscribe ncr53c810
in the text of the message
This is alpha code, there are bugs, and interim fixes and
new versions are released often; with the fixes/announcements
being on this list.
3. If the problem still persists with the new code, next
time please include the startup messages (as directed in
the SCSI-HOWTO) as well. The numbers in the kernel messages
include the NCR instruction pointer where the fault occurred, but
without the startup messages that indicate where the microcode
was relocated to, this is meaningless.
>Other stuff: it's a 486DX4/100; I've got a Pentium/66 running the same
>controller, and it has never given me these danger messages, so I'll
>try swapping the controllers to see where the problem lies, but I just
>thought I'd ask to see if anyone has seen this problem before, and
>whether they have an explanation or cure for it.
Quite likely, either the drive is doing something the NCR driver is not
expecting; or your're seeing a PCI problem due to a mainboard or other
PCI device defficiency.
