From: "Daniela Engert" <dani@ngrt.de>
To: "Martin Wilck" <Martin.Wilck@Fujitsu-Siemens.com>
Cc: "Linux Kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: Serverworks OSB4 in impossible state
Date: Tue, 11 Jun 2002 09:45:20 +0200 (CDT) [thread overview]
Message-ID: <20020611064201.9F55DEDBE@mail.medav.de> (raw)
In-Reply-To: <1023780145.23733.352.camel@biker.pdb.fsc.net>
On 11 Jun 2002 09:22:24 +0200, Martin Wilck wrote:
>Am Mon, 2002-06-10 um 18.41 schrieb Daniela Engert:
>> The intersting bits of the DMA status register are bits 0 though 2. A
>> value of 5 indicates the condition "interrupt from unit, DMA state
>> machine active". This is a valid status! It basically means the unit
>> issued an interrupt before the PRD table is exhausted. This makes sense
>> because the CD-ROM units fails to transfer the amount of data described
>> by the PRD table because of the non-recoverable read error.
>
>Shouldn't the error bit be set too? (But that wouldn't make any
>difference with the current driver ...)
No it shouldn't. The error is happening on the unit side and not on the
host side of the bus. Thus it is correct that the host is *not*
reporting an error (which is true) but only the CD-ROM unit.
>> What you makes sense (the next DMA transfer is scheduled but never
>> carried out by the CD-ROM unit) except for the panic, ofcoz. The
>> correct driver action in this case were stopping the DMA engine and
>> issuing a reset of the state machines involved (both on the host and
>> the unit side).
>
>The message, the comments in the code, and what Alan wrote here:
>http://groups.google.com/groups?hl=de&lr=&threadm=linux.kernel.Pine.LNX.4.31.0206031234370.12103-100000%40boxer.fnal.gov&rnum=2&prev=/groups%3Fq%3Dosb4-bug%2540ide.cabal.tm%26hl%3Dde%26lr%3D%26selm%3Dlinux.kernel.Pine.LNX.4.31.0206031234370.12103-100000%2540boxer.fnal.gov%26rnum%3D2
>suggest that trying to recover from this condition is extremely
>dangerous (note that the kernel doesn't even panic(), because
>a sync() may kill a disk, the comments say).
I'm aware of all of that. By pure chance I have a machine with an OSB4
sitting on my desk for a couple of days. May be I can find a defect
CD-ROM to test it with my driver and see if it manages to recover from
errors like these. Hopefully, the PCI tracer gives some more insight.
Ciao,
Dani
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniela Engert, systems engineer at MEDAV GmbH
Gräfenberger Str. 34, 91080 Uttenreuth, Germany
Phone ++49-9131-583-348, Fax ++49-9131-583-11
next prev parent reply other threads:[~2002-06-11 7:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 15:52 Serverworks OSB4 in impossible state Martin Wilck
2002-06-10 16:41 ` Daniela Engert
2002-06-11 7:22 ` Martin Wilck
2002-06-11 7:45 ` Daniela Engert [this message]
2002-06-11 8:37 ` Martin Wilck
2002-06-11 11:25 ` Martin Wilck
2002-06-11 21:27 ` Chris Wedgwood
2002-06-12 7:24 ` Martin Wilck
2002-06-13 11:50 ` Daniela Engert
2002-06-13 11:59 ` Martin Wilck
2002-06-13 12:04 ` Daniela Engert
2002-06-13 18:27 ` rico-linux-kernel
2002-06-13 23:48 ` Re[2]: " Nerijus Baliunas
2002-06-12 8:58 ` Alan Cox
2002-06-12 8:47 ` Martin Wilck
2002-06-12 9:14 ` Alan Cox
2002-06-12 10:30 ` OSB4 PATCH (was: Re: Serverworks OSB4 in impossible state) Martin Wilck
2002-06-12 20:35 ` Christian Zoffoli
[not found] <1030002761.32380.27.camel@pluto.unixpac.com.au>
2002-08-22 8:35 ` ServerWorks OSB4 in impossible state Martin Wilck
2002-08-22 8:51 ` Andre Hedrick
2002-08-22 12:02 ` Martin Wilck
2002-08-22 16:45 ` Tomas Szepe
2002-08-22 17:48 ` Andre Hedrick
2002-08-22 17:59 ` Alan Cox
2002-08-22 18:14 ` Tomas Szepe
2002-08-22 17:58 ` Alan Cox
2002-08-22 18:58 ` Martin Wilck
[not found] <20020613112932.C2B8C10A1B@mail.medav.de>
2002-06-13 12:52 ` Serverworks " Martin Wilck
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 17:40 Steven Timm
2002-06-04 0:29 ` Alan Cox
2002-06-03 18:11 ` kwijibo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020611064201.9F55DEDBE@mail.medav.de \
--to=dani@ngrt.de \
--cc=Martin.Wilck@Fujitsu-Siemens.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox