From: Tom Dickson <tdickson@inostor.com>
To: linux-kernel@vger.kernel.org
Subject: Does 2.4.25 fix spurious "Serverworks OSB4 in impossible state"
Date: Tue, 13 Apr 2004 15:48:41 -0700 [thread overview]
Message-ID: <407C6E49.8040000@inostor.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm running 2.4.20, and every once in a while I get the "Serverworks
Chipset in impossible state."
But I have the following:
ServerWorks CSB5: IDE controller on PCI bus 00 dev 79
ServerWorks CSB5: chipset revision 147
ServerWorks CSB5: not 100% native mode: will probe irqs later
which shouldn't trigger that warning, right?
Will I have to upgrade to 2.4.25 fix this, or is there a simple patch I
can apply to 2.4.20 to prevent this lockup from occuring?
ide=nodma is way too slow for my purposes, though it seems to work.
- -Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAfG5I2dxAfYNwANIRAlywAKCjX+0lEbXwTpO8rv6Fs+WY0v7pgACfT7Ro
1msiavEyuvMp4/0KzS+ngpA=
=O8wO
-----END PGP SIGNATURE-----
reply other threads:[~2004-04-13 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=407C6E49.8040000@inostor.com \
--to=tdickson@inostor.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