On Tuesday 21 October 2003 20:01, Samuel Kvasnica wrote:
> 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
>>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
Quoting Samuel Kvasnica <[email protected]>:
> 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
Disabling local APIC on 2.6.0-test9-mm2 also fixes this (I haven't tried on
earlier kernels).
-sandalle
--
PGP Key Fingerprint: FCFF 26A1 BE21 08F4 BB91 FAED 1D7B 7D74 A8EF DD61
http://search.keyserver.net:11371/pks/lookup?op=get&search=0xA8EFDD61
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS/E/IT$ d-- s++:+>: a-- C++(+++) BL++++VIS>$ P+(++) L+++ E-(---) W++ N+@ o?
K? w++++>-- O M-@ V-- PS+(+++) PE(-) Y++(+) PGP++(+) t+() 5++ X(+) R+(++)
tv(--)b++(+++) DI+@ D++(+++) G>+++ e>+++ h---(++) r++ y+
------END GEEK CODE BLOCK------
Eric Sandall | Source Mage GNU/Linux Developer
[email protected] | http://www.sourcemage.org/
http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
On approximately Fri, Nov 07, 2003 at 11:40:06AM -0800, Eric Sandall wrote:
> Quoting Samuel Kvasnica <[email protected]>:
> > 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
>
> Disabling local APIC on 2.6.0-test9-mm2 also fixes this (I haven't tried on
> earlier kernels).
>
> -sandalle
>
I am seeing the same thing here. Disk activity and APIC don't seem to
do well. What kind of performance hit if any are we taking by disabling
APIC?
--
Josh McKinney | Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
| They that can give up essential liberty
Linux, the choice -o) | to obtain a little temporary safety deserve
of the GNU generation /\ | neither liberty or safety.
_\_v | -Benjamin Franklin