From: kernel@street-vision.com
To: kas@informatics.muni.cz (Jan Kasprzak)
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD 760MPX DMA lockup
Date: Thu, 12 Sep 2002 15:07:38 +0000 (GMT) [thread overview]
Message-ID: <200209121507.g8CF7cY07728@tench.street-vision.com> (raw)
In-Reply-To: <20020912161258.A9056@fi.muni.cz> from "Jan Kasprzak" at Sep 12, 2002 04:12:58 PM
>
> Hello, kernel hackers,
>
> my dual athlon box is unstable in some situations. I can consistently
> lock it up by running the following code:
>
> fd = open("/dev/hda3", O_RDWR);
> for (i=0; i<1024*1024; i++) {
> read(fd, buffer, 8192);
> lseek(fd, -8192, SEEK_CUR);
> write(fd, buffer, 8192);
> }
>
> It locks up in a minute or so (solid lock up, it does not react even
> to a NumLock key or console switching). It can surely be a HW problem
> (this is a new box), but how to tell whether this is the case?
>
> The mainboard is MSI K7D Master, AMD 760MPX chipset, 460W power supply,
> 1GB RAM.
>
> The box survived whole night of memtest86 and the whole night of three kernel
> compiles running in parallel in an infinite loop.
>
> This problem is on many recent kernels (tried 2.4.18-11 from RedHat "null",
> 2.4.20-pre5-ac1, 2.4.20-pre5-ac5, 2.4.20-pre6). It does not matter whether
> I compile the kernel SMP or UP, with or without CONFIG_HIGHMEM.
Well I have run this several times on my MPX, and it is fine.
This is 2.4.20-pre1, dual AMD 2000MP, only difference is it is the Tyan
version of the MPX, not the MSI.
Justin
next prev parent reply other threads:[~2002-09-12 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 14:12 Jan Kasprzak
2002-09-12 15:07 ` kernel [this message]
2002-09-12 16:22 ` Petr Konecny
2002-09-12 23:10 ` Denis Vlasenko
2002-09-12 19:14 ` AMD 760MPX DMA lockup (partly solved) Jan Kasprzak
2002-09-12 20:43 ` Alan Cox
2002-09-13 9:41 ` Jan Kasprzak
2002-09-13 9:46 ` Vojtech Pavlik
2002-09-12 21:34 ` Vojtech Pavlik
2002-09-13 11:58 ` Denis Vlasenko
2002-09-13 11:44 ` kernel
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=200209121507.g8CF7cY07728@tench.street-vision.com \
--to=kernel@street-vision.com \
--cc=kas@informatics.muni.cz \
--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®