mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prakash Punnoor <prakash@punnoor.de>
To: Bart Trojanowski <bart@jukie.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18.3 SMP PREEMPT crashes (x86-64)
Date: Wed, 29 Nov 2006 18:12:04 +0100	[thread overview]
Message-ID: <200611291812.08408.prakash@punnoor.de> (raw)
In-Reply-To: <20061129170253.GH2418@jukie.net>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Am Mittwoch 29 November 2006 18:02 schrieb Bart Trojanowski:
> Hi all,
>
> I've been getting spurious hangs in 2.6.18 lately... first I thought it
> was hardware but tried different replacement parts and memtest. Nothing
> showed any problems.
>
> I finally hooked up a serial console to the box and I see the following.
> I include the initial dmesg output to show what's in the machine.
>
>  - Nforce4 based Shuttle XPC (PCIe, forcedeth, etc)

> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.

Does your bios have the option to enable the hpet? (Maybe after a bios 
update?)

If not:

Try booting with noapic, compile latest git kernel and buut it (w/o noapic). 
Above message should now not appear, if I am not mistaken. Otherwise you have 
to hack the kernel to not ignoge the timer override..


But I could be mistaken...
-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-11-29 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 17:02 Bart Trojanowski
2006-11-29 17:12 ` Prakash Punnoor [this message]
2006-11-29 21:07   ` Bart Trojanowski
2006-11-30 19:02     ` 2.6.19 SMP x86-64 crashes continue Bart Trojanowski
2006-11-29 17:31 ` 2.6.18.3 SMP PREEMPT crashes (x86-64) Bart Trojanowski
2006-11-29 19:08   ` 2.6.18.3 soft lockups and 2.6.19-rc6 rwlock OOPs on SMP x86-64 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=200611291812.08408.prakash@punnoor.de \
    --to=prakash@punnoor.de \
    --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

all inboxes | Powered by JetHome®