From: Robert Raschke <rrplan9@tombob.com>
To: cinap_lenrek@gmx.de, 9fans@cse.psu.edu
Subject: Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work
Date: Fri, 8 Feb 2008 15:27:40 +0000 [thread overview]
Message-ID: <a09d2fd2df85d078326c2515fd11db14@tombob.com> (raw)
In-Reply-To: <3c4563dd29c6c682db04571f0be1d040@tombob.com>
I wrote a bit hastily:
> At the risk of repeating myself, there are several VIA boards that
> have issues with DMA (not necessarily isolated to HDD). Your best bet
> is to have a trawl through the VIA forums (www.viaarena.com) and look
> for DMA related crashes being reported. Maybe you've got one of those
> troublesome models.
Sorry, wrote this before I spotted your other emails about working
around the issue using retries. I should try again to get my VIAs to
work with a similar workaround.
Robby
next prev parent reply other threads:[~2008-02-08 15:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54b639a7eb08c31e4ef2a6d9fd7b6a62@quanstro.net>
2008-02-08 9:35 ` Kernel Panic
2008-02-08 14:55 ` erik quanstrom
2008-02-08 15:34 ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work (VIA Rhine II) Kernel Panic
2008-02-08 14:56 ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work Robert Raschke
2008-02-08 15:27 ` Robert Raschke [this message]
2008-02-06 17:58 [9fans] usb ohci support arrives -- another caution Sape Mullender
2008-02-06 19:23 ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work cinap_lenrek
2008-02-06 20:04 ` erik quanstrom
2008-02-06 22:29 ` cinap_lenrek
2008-02-06 22:40 ` erik quanstrom
2008-02-06 23:26 ` cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 22:13 cinap_lenrek
2008-02-06 8:41 ` Kernel Panic
2008-02-06 9:45 ` erik quanstrom
2008-02-06 10:43 ` Kernel Panic
2008-02-06 11:03 ` erik quanstrom
2008-02-05 8:18 Kernel Panic
2008-02-05 8:54 ` Lorenzo Fernando Bivens de la Fuente
2008-02-05 13:20 ` erik quanstrom
2008-02-05 19:48 ` Robert Raschke
2008-02-06 2:01 ` arisawa
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=a09d2fd2df85d078326c2515fd11db14@tombob.com \
--to=rrplan9@tombob.com \
--cc=9fans@cse.psu.edu \
--cc=cinap_lenrek@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).