From: Bart Trojanowski <bart@jukie.net>
To: Prakash Punnoor <prakash@punnoor.de>, linux-kernel@vger.kernel.org
Subject: Re: nforce chipset + dualcore x86-64: Oops, NMI, Null pointer deref, etc
Date: Sat, 2 Dec 2006 14:37:16 -0500 [thread overview]
Message-ID: <20061202193716.GE20337@jukie.net> (raw)
In-Reply-To: <200612021840.48073.prakash@punnoor.de>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
* Prakash Punnoor <prakash@punnoor.de> [061202 13:32]:
> Am Samstag 02 Dezember 2006 18:22 schrieb Bart Trojanowski:
> > In summary, I have an Opteron 170 in a Shuttle SN25P (nforce4 chipset).
> > I've tested the ram overnight and swapped out every component in the
> > system except for the HDDs. I see these problems only with the
> > dual-core, and even on an older Asus nforce4 based motherboard.
> > noticed the following events (the complete dmesg is included below).
>
> > [ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
> > [ 0.000000] If you got timer trouble try acpi_use_timer_override
>
> Have you tried this?
I saw the suggestions, but I didn't understand what that was asking. I
will checkout that code.
Cheers,
-Bart
--
WebSig: http://www.jukie.net/~bart/sig/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-02 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 17:22 nforce chipset + dualcore x86-64: Oops, NMI, Null pointer deref, etc Bart Trojanowski
2006-12-02 17:40 ` Prakash Punnoor
2006-12-02 19:37 ` Bart Trojanowski [this message]
2006-12-02 19:41 ` Prakash Punnoor
[not found] <fa.EzYK0cTOJOhsylgT7NpDZwIOqx8@ifi.uio.no>
2006-12-02 17:46 ` Robert Hancock
2006-12-02 19:36 ` Bart Trojanowski
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=20061202193716.GE20337@jukie.net \
--to=bart@jukie.net \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash@punnoor.de \
/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