linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christian Bornträger" <linux-kernel@borntraeger.net>
To: "Rachel Greenham" <rachel@linuxgrrls.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: VIA KT133A crash *post* 2.4.3-ac6
Date: Tue, 12 Jun 2001 14:42:06 +0200	[thread overview]
Message-ID: <001901c0f33d$1a4c8170$3303a8c0@einstein> (raw)
In-Reply-To: <3B2606CF.10003@linuxgrrls.org>

> 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. :-}

I encountered the same problem after 2.4.3-ac6.

> CPU: Athlon 1.33 GHz with 266MHz FSB
> Mobo: Asus A7V133 with 266MHz FSB, UltraDMA100 (PDC20265 according to

So you put your IBM drive on the promise, right?
Removing the hard disc from the promise controller and attaching it on the
VIA-Controller solved my problems. The system is now rock solid. If you do
so, take care that your root partition moves from hde to hda. Prepare a boot
disk and pass a parameter like root=/dev/hda to the kernel. After a
successful boot, modify fstab and lilo.conf and run lilo.

> With DMA disabled, *all* kernels are completely stable.

same for me.


> 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
> twice after boot generally excites it too. :-}. Lockup is pretty severe:
> machine goes completely unresponsive, Magic SysRq doesn't work. About
> the only thing that does still work is the flashing VGA cursor. :-)
> Please read the FAQ at  http://www.tux.org/lkml/

sounds absoluty identical to my problem with ASUS A7V133 I reported some
weeks ago.


  reply	other threads:[~2001-06-12 12:44 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 [this message]
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
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='001901c0f33d$1a4c8170$3303a8c0@einstein' \
    --to=linux-kernel@borntraeger.net \
    --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).