public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: Bart Trojanowski <bart@jukie.net>
Subject: Re: nforce chipset + dualcore x86-64: Oops, NMI, Null pointer deref, etc
Date: Sat, 02 Dec 2006 11:46:38 -0600	[thread overview]
Message-ID: <4571BBFE.9000707@shaw.ca> (raw)
In-Reply-To: <fa.EzYK0cTOJOhsylgT7NpDZwIOqx8@ifi.uio.no>

Bart Trojanowski wrote:
> Hi,
> 
> to see my history please see this thread...
> 
> http://lkml.org/lkml/2006/11/29/156
> 
> It might be sata related, but I cannot tell for sure.
> 
> 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.  
> 
> I've had a hell of a time getting 2.6.18 to stay up longer then a day.
> 2.6.19 is better but I am still seeing strangeness.  This morning I
> noticed the following events (the complete dmesg is included below).
> 
> [36514.296462] Unable to handle kernel paging request at 00000000ff757c4f RIP: 
> ..
> [36514.515894]  NMI Watchdog detected LOCKUP on CPU 0
> ..
> [36519.958059] Unable to handle kernel NULL pointer dereference at 0000000000000038 RIP: 
> 
> Now the system is quite non-responsive.  I start programs, but they
> don't run for a few minutes.  Existing programs seem to work ok.
> 
> Any suggestions would be appreciated... I am going to boot with noapic
> for now.  From what I can tell things work better with APIC disabled.

...

> [   27.337641] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> [   27.344035] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> [   27.352191] Probing IDE interface ide0...
> [   28.145997] hda: PLEXTOR DVDR PX-716AL, ATAPI CD/DVD-ROM drive
> [   28.457643] Probing IDE interface ide1...
> [   28.970267] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

Hmm. Something seems missing here. Chipset-specific driver not enabled? 
I don't see any references to DMA mode or the controller type. It seems 
like in this case something in drivers/ide is blowing up later on (which 
shouldn't happen in any case but that code is not the greatest).

Myself, I would try disabling CONFIG_IDE entirely and enabling the 
corresponding new libata PATA driver for this chipset's PATA ports (for 
nForce4 it will be pata_amd). Even if it still doesn't work it may allow 
the real problem to be diagnosed more easily.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-12-02 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.EzYK0cTOJOhsylgT7NpDZwIOqx8@ifi.uio.no>
2006-12-02 17:46 ` Robert Hancock [this message]
2006-12-02 19:36   ` nforce chipset + dualcore x86-64: Oops, NMI, Null pointer deref, etc Bart Trojanowski
2006-12-02 17:22 Bart Trojanowski
2006-12-02 17:40 ` Prakash Punnoor
2006-12-02 19:37   ` Bart Trojanowski
2006-12-02 19:41     ` Prakash Punnoor

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=4571BBFE.9000707@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=bart@jukie.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