public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Kvasnica <samuel.kvasnica@tuwien.ac.at>
To: linux-kernel@vger.kernel.org
Cc: Vitez Gabor <gabor@swszl.szkp.uni-miskolc.hu>,
	ivtv-devel@lists.sourceforge.net
Subject: Re: nforce2 random lockups - still no solution ?
Date: Thu, 23 Oct 2003 12:17:47 +0200	[thread overview]
Message-ID: <3F97AACB.2020609@tuwien.ac.at> (raw)
In-Reply-To: <20031022133327.GA25283@swszl.szkp.uni-miskolc.hu>

Dear Gabor,

thantks a lot, indeed you are right ! I've been confused by some nforce 
FAQs where 'nolapic' option was recommended. In fact I did never check 
whether this option
really exists. Now, after recompiling the kernel the framegrabber works 
with uncompressed stream for almost 24h and it is rock-solid.

So, a workaround recommendation for all using ivtv driver on nforce2 
chipsets and kernels up to 2.4.22:

*** RECOMPILE YOUR KERNEL WITH LOCAL APIC DISABLED ***,

otherwise you'll experience very rare random lockups while watching the 
compressed stream and lockups within 10 minutes when watching the 
uncompressed
yuv stream.

What I'd like to know is whether this bug is AMD processor or chipset 
related. Is there a patch available ? I tried 2.6.0-test8 and it wasn't 
stable. I'd prefer to use APIC instead of XT-PIC because some drivers 
e.g. kernel DRM don't support shared interrupts and I can't get own 
interrupt for the video card.

Sam


Vitez Gabor wrote:

>Hi,
>
>On Wed, Oct 22, 2003 at 03:22:04PM +0200, Samuel Kvasnica wrote:
>  
>
>>I'm booting the kernel with acpi=off, noapic and nolapic options and 
>>    
>>
>
>nolapic? That's not a valid kernel command line parameter I'm afraid. 
>
>fgrep -ri nolapic $KERNEL_SOURCE_DIR
>
>gives nothing. ???
>
>
>	Gabor
>  
>


  parent reply	other threads:[~2003-10-23 10:17 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 [this message]
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=3F97AACB.2020609@tuwien.ac.at \
    --to=samuel.kvasnica@tuwien.ac.at \
    --cc=gabor@swszl.szkp.uni-miskolc.hu \
    --cc=ivtv-devel@lists.sourceforge.net \
    --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