From: Samuel Kvasnica <samuel.kvasnica@tuwien.ac.at>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 random lockups - still no solution ?
Date: Thu, 06 Nov 2003 11:45:39 +0100 [thread overview]
Message-ID: <3FAA2653.9020002@tuwien.ac.at> (raw)
In-Reply-To: <200311060111.06729.vda@port.imtp.ilyichevsk.odessa.ua>
>>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.
>>
>>
>
>It can be a too-aggressive chipset configuration triggering chipset big.
>
>Maybe do lspci -vvvxxx and it's WinXP equivalent (I think such tool
>for Win ought to exist somewhere, although I had no need for it yet)
>and compare the result.
>--
>vda
>
It was local APIC ! After recompiling 2.4.22 without local apic
everything works smoothly since several weeks. I wonder when there'll
be a kernel
patch that really solves these nforce2/amd issues.
Sam
next prev parent reply other threads:[~2003-11-06 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 18:01 nforce2 random lockups - still no solution ? Samuel Kvasnica
2003-10-21 18:13 ` 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 [this message]
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=3FAA2653.9020002@tuwien.ac.at \
--to=samuel.kvasnica@tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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