-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
fredag 18. juli 2003, 22:06, skrev Nachman Yaakov Ziskind:
> Anyone out there with tips on how to resolve this? Perhaps I can
> force the kernel to think that DMA has been disabled?
No tips, I'm afraid, but don't even *think* about doing that.
As the technician said, the problem is with the chipset not accepting commands
properly; fortunately, the kernel appears to catch the situation and avoid
(potential) severe damage.
Forcing the kernel to act as if DMA is fully disabled when in fact it isn't
sounds like a very bad idea indeed; the best you could probably hope for is
to have the machine crash without losing any data.
My suggestion is this: As the hardware is obviously broken, and disabling DMA
would cause a horrendous performance drop anyway, you should get a new
chipset. Return the one you have as broken.
If that isn't an option, for whatever reason, you might try switching to a
lower-speed DMA mode using hdparm. Something like "hdparm -Xudma0 /dev/hdx"
might help, if you're lucky.
- - Svein Ove Aas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/GG/f9OlFkai3rMARApCiAKCojeoY+nfskcM6EKFco8xktnSfjQCfTq6u
rkZjj7+DtP90zv8cHuTorrA=
=lr9Y
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:36 EST