public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Kvasnica <samuel.kvasnica@tuwien.ac.at>
To: Vitez Gabor <gabor@swszl.szkp.uni-miskolc.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nforce2 random lockups - still no solution ?
Date: Wed, 22 Oct 2003 15:27:26 +0200	[thread overview]
Message-ID: <3F9685BE.3000406@tuwien.ac.at> (raw)
In-Reply-To: <20031022085449.GA21393@swszl.szkp.uni-miskolc.hu>

Gabor,

I'm booting the kernel with acpi=off, noapic and nolapic options and 
according to syslog it is really disabled. Lockups are very rare (they 
come either during
30mins after boot or never) but I cat get them very quickly when using 
the framegrabber with ivtv driver. The ivtv driver itself works rock 
solid on older PIII system
(btw, that PIII runs SMP kernel !). So I think there are definitely DMA 
problems with nforce2 boards under linux.

Sam

Vitez Gabor wrote:

>If turning off APIC doesn't solve the problem, try a kernel with 
>LOCAL APIC support turned off. 
>
>
>	Gabor
>  
>


  reply	other threads:[~2003-10-22 13:27 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 [this message]
     [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=3F9685BE.3000406@tuwien.ac.at \
    --to=samuel.kvasnica@tuwien.ac.at \
    --cc=gabor@swszl.szkp.uni-miskolc.hu \
    --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