From: Martin Wilck <Martin.Wilck@Fujitsu-Siemens.com>
To: ROBIN "Jean-Marie (EURIWARE)" <jmrobin@euriware.fr>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andre Hedrick <andre@linux-ide.org>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: OSB4 in impossible state
Date: 04 Sep 2002 12:23:49 +0200 [thread overview]
Message-ID: <1031135030.3314.64.camel@biker.pdb.fsc.net> (raw)
In-Reply-To: <6005F8DAD235D611BDF80008C7EB75D01B008D@excsrvequ1.euriware>
Am Mit, 2002-09-04 um 11.30 schrieb ROBIN Jean-Marie (EURIWARE):
> i have installed a redhat 7.3 on a COmpaq DL360 G2, i had a kernel panic
> with the message "ServerWorks OSB4 in impossible state" when i mount a
> cdrom...
> On newsgroups archives, i look at your patch and created a new kernel.
> Now i have no more crash but cdrom is still not accessible with the
> following error:
> hda: timeout waiting DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hda: status error: status 0x48 { DriveReady DataRequest }
> hda: drive not ready
> have you any news about this problem? No more infos on web.
Hmm - seems that DMA really doesn't work as it should. In this case my
patch really only prevents the crash. For the moment, I can only advise
you to start the kernel with the hda=nodma option.
I am forwarding this to Andre and Alan, who know much more about this
than I do. It would be helpful if you could tell us your Chipset
revision.
Martin
--
Martin Wilck Phone: +49 5251 8 15113
Fujitsu Siemens Computers Fax: +49 5251 8 20409
Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com
D-33106 Paderborn http://www.fujitsu-siemens.com/primergy
next parent reply other threads:[~2002-09-04 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6005F8DAD235D611BDF80008C7EB75D01B008D@excsrvequ1.euriware>
2002-09-04 10:23 ` Martin Wilck [this message]
2002-09-04 10:49 ` Alan Cox
2002-09-04 18:14 ` Andre Hedrick
2002-09-05 7:02 ` Martin Wilck
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=1031135030.3314.64.camel@biker.pdb.fsc.net \
--to=martin.wilck@fujitsu-siemens.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=jmrobin@euriware.fr \
--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
all inboxes | Powered by JetHome®