Re: Deadlock: Linux-2.2.18, sym53c8xx, Compaq ProLiant, HP Ultrium

[Andreas Haumer]

Hi Gérard,

thanks for your reply!

Gérard Roudier wrote:
> 
> On Wed, 19 Dec 2001, Andreas Haumer wrote:
> 
[...]
> 
> > Dec 10 15:00:01 server kernel: st0: Error with sense data: Info
> > fld=0x8000, Current st09:00: sense key Hardware Error
> > Dec 10 15:00:01 server kernel: Additional sense indicates Internal
> > target failure
> 
> This one is the result of a REQUEST SENSE performed due probably to a
> CHECK condition SCSI status reported by the device. It is not a SCSI
> transport problem. The device just reports an error to the application
> client. This is not a normal situation but happens very often.
> 
Ok.

> > [...]
> >
> >    After that, the amanda process hangs in state "D" and
> >    cannot be killed anymore. The machine itself is still
> >    working.
> >    This _seems_ to be the indication of an error of the
> >    HP Ultrium itself, though the drive works quite fine
> >    otherwise...
> 
> The 'D' states indicates that the process is waiting for something without
> being interruptible. This may be due to it not having been waken up on the

I knew that...

> IO error. The sym53c8xx driver did its work by performing the REQUEST
> SENSE, but something in upper layer seem not to complete the IO.
> 
That's what I wasn't sure about...

[...]
> 
> > b) Does the st0 error message indicate it should be replaced?
> 
> Probably not. But it is very poor an information about the real issue.
> 
I know, but I have the problem to decide how to proceed in this
situation...

> > c) Is there a bug in the sym53c8xx driver which makes the
> >    amanda process hang uninterruptable when this error occurs?
> 
> Not known. But possible, even if in my opinion, the driver is not at
> fault.
> 
Ok.

[...]
> 
> There are probably still bugs in the driver, but none are intentionnal,
> beleive me.
> 
I honestly do believe you! :-)

> > The Ultrium hardware error is not reproducable at will. It
> > just happens every now and then.
> > Next thing I will try is to use a different SCSI controller
> > (Adaptec 29160 or the like) to see if the hanging process
> > occurs with a different SCSI driver, too.
> 
> This is indeed something to try.
> I am very interested in the result.
> 
The controller change is scheduled on December 28th.
We'll then see how it works in the next weeks/months.
I'll keep you (and LKML) informend...

Thank you.

- andreas

-- 
Andreas Haumer                     | mailto:[e-mail]
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: [phone]
A-1100 Vienna, Austria             | Fax: [phone]