Messages in this thread | | | Date | Sun, 22 Mar 1998 15:30:25 -0600 | From | Doug Ledford <> | Subject | Re: SCSI deadlock |
| |
Roland Hautz wrote:
> logs, again reading "kernel: (scsi0:0:0) Target busy". The nmi-oops ^^^^^^^^^^^^^^^^^^^^^^
Didn't you say this drive is a Barracuda? If so, that message is troublesome. I never see Barracuda drives cause that message unless they have a sector that is so badly damaged that it hoses the Barracuda's drive firmware. You may end up having to low level format. In any case, I would change the tar command to tar -cvf - . so that it prints the file names as it processes them and then see if it always hangs on the same file. FWIW, this may not be a case of a hard lock, it may be an interrupt flood from repeated BUSY target status messages. There is suppossed to be a wait machanism in the aic7xxx 5.0.x driver to combat this situation but I haven't verified it under 2.1.x so I don't know if the timer routines are working properly. When I get the 5.1.x aic7xxx patches out the door, they will be geared specifically for 2.1.x kernels, but that's still going to be a few weeks at least anyway as I need to finish up a few things in the 5.0.x series.
--
Doug Ledford <dledford@dialnet.net> Opinions expressed are my own, but they should be everybody's.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |