mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Svein Ove Aas <svein.ove@aas.no>
To: Nachman Yaakov Ziskind <awacs@egps.com>, linux-kernel@vger.kernel.org
Subject: Re: DVD-RAM crashing system
Date: Sat, 19 Jul 2003 00:08:31 +0200	[thread overview]
Message-ID: <200307190008.32137.svein.ove@aas.no> (raw)
In-Reply-To: <20030718160643.A21755@egps.egps.com>

-----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-----


  reply	other threads:[~2003-07-18 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 20:06 Nachman Yaakov Ziskind
2003-07-18 22:08 ` Svein Ove Aas [this message]
2003-07-18 22:54   ` Alan Cox
2003-07-18 23:13     ` Nachman Yaakov Ziskind

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=200307190008.32137.svein.ove@aas.no \
    --to=svein.ove@aas.no \
    --cc=awacs@egps.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

all inboxes | Powered by JetHome®