From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [2.4] Nforce2 oops and occasional hang (tried the lockups patch, no difference)
Date: Thu, 11 Dec 2003 12:19:04 -0500 [thread overview]
Message-ID: <1071163143.1345.12.camel@slappy> (raw)
In-Reply-To: <20031211163825.GA1413@forming>
On Thu, 2003-12-11 at 11:38, Josh McKinney wrote:
> Do you see hard locks with APIC/IO-APIC enabled? Do you see this oops
> with APIC/IO-APIC enabled? Just curious because I can reproduce the
> hard locks eventually, but never get an oops. Also, what patches are
> you running and what kernel version?
With apic/io-apic enabled it crashes hard during boot (with oopses, as I
recall). I haven't tested apic support with the fixup patches.
The kernel is 2.4.23 plus the patches from "Fixes for nforce2 hard
lockup, apic, io-apic, udma133 covered"
(http://marc.theaimsgroup.com/?l=linux-kernel&m=107080280512734&w=2) and
athcool was running. (Its currently disabled, to see if that might have
something to do with it.) The machine hasn't been rebooted since the
oops, since it seems to be limping along. (I did find some minorly
corrupted data earlier; libbz2 had to be reinstalled. Once its
straightened out I'll run debsums against it and fix up anything that
got mangled..)
The same oops was occurring in stock 2.4.22.
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-12-11 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 16:16 [2.4] Nforce2 oops and occasional hang (tried the lockups patch, no difference) Disconnect
2003-12-11 16:38 ` Josh McKinney
2003-12-11 17:19 ` Disconnect [this message]
2003-12-11 17:22 ` Disconnect
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 2:25 Ross Dickson
2003-12-13 5:02 ` Bob
2003-12-15 16:40 ` Disconnect
2003-12-18 18:52 ` Disconnect
2003-12-19 17:24 ` Disconnect
2003-12-19 20:22 ` Craig Bradney
2003-12-19 20:32 ` Disconnect
2003-12-20 12:30 ` Voicu Liviu
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=1071163143.1345.12.camel@slappy \
--to=lkml@sigkill.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