From: Daniel Drake <dan@reactivated.net>
To: Herve Fache <herve.fache@europemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux hangs on nVidia nForce2 400 Ultra
Date: Sun, 04 Jan 2004 18:03:54 +0000 [thread overview]
Message-ID: <3FF8558A.2080308@reactivated.net> (raw)
In-Reply-To: <20040104173624.19046.qmail@iname.com>
Hi,
Theres been some work done on this issue lately. Originally, my system only
hung when I had IO-APIC and local APIC support compiled into the kernel. But I
think other people had hanging problems even without this.
You could first try using a 2.6-mm series kernel, as these include some
patches which fix nforce2 problems for most people (but not me).
The other option is to try Ross Dickinson's patches:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107199838022614&w=2
If you use Ross's patches, as well as the -mm fixes, you should revert out the
nforce-disconnect-quirk patch to avoid your CPU getting needlessly hot.
Personally, I have stability running 2.6.1-rc1-mm1 with the disconnect-quirk
reverted out, Ross's patches, booting with parameter apic_tack=2. I have
APIC/IOAPIC compiled in and working.
Daniel.
Herve Fache wrote:
> Hi chaps!
>
> My system hangs (no oops, nothing) on disk access using either 2.4.23 or 2.6.0. A rather reliable way for me to
> crash it is to, for example, copy the sources of the Linux kernel.
>
> It hanged once on CD-ROM access, which could lead to a more IDE-level problem. Also, the only time it did it in
> another operating system (humm...) was after it crashed in Linux and I pressed reset (no shut down), which
> makes me think it could the IDE controller [driver]'s fault...
>
> It seems I'm the only one on Earth to have this problem (according to Google), but if there was a way to track it
> down I'd be happy to try.
>
> I have attached my 2.6.0 kernel config for info.
>
> Thanks!
> Hervé.
next prev parent reply other threads:[~2004-01-04 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 17:36 Herve Fache
2004-01-04 18:00 ` Andreas Unterkircher
2004-01-04 18:03 ` Daniel Drake [this message]
2004-01-06 6:12 ` Bob
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=3FF8558A.2080308@reactivated.net \
--to=dan@reactivated.net \
--cc=herve.fache@europemail.com \
--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
Powered by JetHome