From: Thomas Molina <tmolina@home.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rachel Greenham <rachel@linuxgrrls.org>, <linux-kernel@vger.kernel.org>
Subject: Re: VIA KT133A crash *post* 2.4.3-ac6
Date: Fri, 15 Jun 2001 19:03:05 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0106151858540.12619-100000@localhost.localdomain> (raw)
In-Reply-To: <E159qX2-0001WC-00@the-village.bc.nu>
On Tue, 12 Jun 2001, Alan Cox wrote:
> > With DMA (UDMA Mode 5) enabled, my machine crashes on kernel versions
> > from 2.4.3-ac7 onwards up to 2.4.5 right up to 2.4.5-ac13. 2.4.3 vanilla
> > and 2.4.3-ac6 are completely stable. -ac7 of course is when a load of
> > VIA fixes were done. :-}
>
> Unfortunately there isnt a great deal I can do but say 'talk to VIA'.
>
> > With DMA (any setting, but UDMA mode 5 preferred of course) enabled, on
> > kernels 2.4.3-ac7 and onwards, random lockup on disk access within first
> > few minutes of use - sometimes very quickly after boot, sometimes as
> > much as ten minutes later given use. Running bonnie -s 1024 once or
>
> Yep. Lots of people see these. I even have people reporting it and not reporting
> it on the same board.
>
> Only known cure its to not use DMA.
So is there no correlation from particular hardware to problems reported?
I'm running the A7V133 with a Western Digital WD300BB UDMA 5 drive on
kernel 2.4.5 with no trouble.
next prev parent reply other threads:[~2001-06-16 0:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 12:10 VIA KT133A crash *post* 2.4.3-ac6 Rachel Greenham
2001-06-12 12:42 ` Christian Bornträger
2001-06-12 13:19 ` Rachel Greenham
2001-06-12 15:58 ` Alan Cox
2001-06-12 15:56 ` Alan Cox
2001-06-16 0:03 ` Thomas Molina [this message]
2001-06-16 10:15 ` Rachel Greenham
2001-06-16 13:42 ` Thomas Molina
2001-06-16 14:13 ` Christian Bornträger
2001-06-16 18:27 ` Rachel Greenham
2001-06-16 15:24 ` Rachel Greenham
2001-06-16 16:57 ` Justin Guyett
2001-06-16 17:25 ` Rachel Greenham
2001-06-17 11:56 Jason T. Collins
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=Pine.LNX.4.33.0106151858540.12619-100000@localhost.localdomain \
--to=tmolina@home.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rachel@linuxgrrls.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;
as well as URLs for NNTP newsgroup(s).