From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: magallon@posta.unizar.es,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Status of ServerWorks UDMA
Date: Tue, 16 Oct 2001 00:49:15 +0200 [thread overview]
Message-ID: <20011016004915.A28798@werewolf.able.es> (raw)
In-Reply-To: <20011016003812.A28638@werewolf.able.es> <E15tGWg-0003fP-00@the-village.bc.nu>
In-Reply-To: <E15tGWg-0003fP-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Oct 16, 2001 at 00:48:02 +0200
On 20011016 Alan Cox wrote:
>> I have just installed a system with kernel 2.4.20, and it stops booting
>> with a message like:
>>
He, he, I meant 2.4.10....
>> Controller is in an impossible state. Disable UDMA.
>
>That is triggered when we see a case that can cause disk corruption.
>
>> Board is a SuperMicro 370DLE (SW LE chipset). I have tried disabling
>> ide channels on the bios, but kernel still sees them. I have tried to
>
>At some point I'll sort this properly if Andre doesnt do it first.
>
>> boot with ide0=nodma (is this options real, or I just have invented it ??)
>> No solution.
>
>ide=nodma
>
TNX!!
>Please send me details on the system. lspci -v output too.
>
As I said, it is a SUPER P3TDLE, with 2 UDMA/33 channels, and a cdrom
in hda and a zip in hdc (nothing in any slave).
I will send you details tomorrow from work.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.12-ac2-beo #1 SMP Mon Oct 15 00:23:19 CEST 2001 i686
next prev parent reply other threads:[~2001-10-15 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 22:38 Status of ServerWorks UDMA J . A . Magallon
2001-10-15 22:48 ` Alan Cox
2001-10-15 22:49 ` J . A . Magallon [this message]
2001-10-16 14:13 ` J . A . Magallon
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=20011016004915.A28798@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=magallon@posta.unizar.es \
/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