From: Samuel Kvasnica <samuel.kvasnica@tuwien.ac.at>
To: linux-kernel@vger.kernel.org
Subject: nforce2 random lockups - still no solution ?
Date: Tue, 21 Oct 2003 20:01:50 +0200 [thread overview]
Message-ID: <3F95748E.8020202@tuwien.ac.at> (raw)
Hello,
Last few weeks I spent quite much time trying to get working two nforce2
chipset based motherboards with latest linux 2.4.22 - ASUS A7N8 Deluxe
2.0 and
MSI K7N2 Delta. Althought the latest kernel version already detects
correctly all the nforce2 stuff and APIC seems to run work as well,
some random lockups still remain. At the very beginning I believed I
could get rid of lockups by setting lower udma mode on IDE (hdparm -X
udma3).
In the fact this only reduced very much the probability of lockups -
with udma5 I could freeze the system within few minutes e.g. during
kernel compilation.
with udma3 system is usually stable for several days, but sometimes it
locks. When it happens, it happens mostly during first 30 mins after boot.
I'm booting with noapic, nolapic and acpi=off, but it doesn't seem to
have really any effect on lockups.
Unfortunatelly, I can't get any debug info. I've redirected syslog to
flash-card but didn't get even a bit more of info, it seems to blow-up
the chipset completelly and immediatelly.
Now, in the system with MSI K7N2 motherboard I have a framegrabber
(Hauppauge PVR-250) installed, using ivtv driver.
I'm able to lock-up the system when streaming uncompressed video (e.g.
cat /dev/yuv0 >/dev/null) and the lockups are also hard, w/o debug info.
The ivtv driver is using DMA very heavily but seems to work on other
chipsets. So these lock-up problems might be rather DMA then APIC related.
Interesting is that I've never had such a lock-up when running WinXP on
same computer ( :-) seems impossible), even under load and with the
framegrabber.
I've run memtest on both machines for 24 hours, it shouldn't be bad
memory. On both machines I'm using just onboard hardware, except for the
AGP graphic card
(matrox and nvidia) and the framegrabber. Hard disk is on parallel IDE,
SATA controller is disabled.
So my conclusion is that the nforce2 lock-ups are still unsolved at the
moment. Any nforce experts around ?
Please, reply directly using cc:, I'm not on the list.
thanks,
Sam
next reply other threads:[~2003-10-21 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 18:01 Samuel Kvasnica [this message]
2003-10-21 18:13 ` nforce2 random lockups - still no solution ? Matt H.
2003-10-22 8:54 ` Vitez Gabor
2003-10-22 13:27 ` Samuel Kvasnica
[not found] ` <3F96847C.4000506@tuwien.ac.at>
[not found] ` <20031022133327.GA25283@swszl.szkp.uni-miskolc.hu>
2003-10-23 10:17 ` Samuel Kvasnica
2003-10-23 10:48 ` Mikael Pettersson
2003-10-23 11:04 ` Samuel Kvasnica
2003-10-23 12:51 ` James Courtier-Dutton
2003-11-05 23:11 ` Denis
2003-11-06 10:45 ` Samuel Kvasnica
2003-11-07 19:40 ` Eric Sandall
2003-11-08 7:34 ` Josh McKinney
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=3F95748E.8020202@tuwien.ac.at \
--to=samuel.kvasnica@tuwien.ac.at \
--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