public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gerd v. Egidy" <lists@egidy.de>
To: Andi Kleen <ak@suse.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
	Bill Davidsen <davidsen@tmr.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: lspci output needed was Re: Frustrated with Linux, Asus, and nVidia, and AMD
Date: Wed, 1 Nov 2006 23:17:13 +0100	[thread overview]
Message-ID: <200611012317.13963.lists@egidy.de> (raw)
In-Reply-To: <200610311528.20013.ak@suse.de>

Hi,

> Can people who use a Nvidia based AM2/SocketF board (especially when they
> have timer troubles but otherwise would be useful too) please report their
> lspcis in private mail to me?

I'll send the lspci in private as requested in a minute.

I have a ASUS M2N-SLI Deluxe (nForce 570) with a Athlon64 X2 4600+ (AM2) and 
Bios version 0307 or 0402 beta. The problem with this board seems to be a 
little different than the problem the others posting here are experiencing. 
Maybe it's a different bug but it seems to be timer-related too.

Booting 2.6.18.1 (or some other 2.6er I tried) stops with

[...]
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=0 apci2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
....trying to set up timer (IRQ0) through the 8259A ...  failed.
....trying to set up timer as Virtual Wire IRQ... failed.
....trying to set up timer as ExtINT IRQ... failed :(.
Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug
and send a report.  Then try booting with the 'noapic' option

All kernels were SMP and i386 (not x86_64).

I tried to use the acpi_skip_timer_override=0 patch that helped the other 
posters but it did not help - same error. Of course I patched the 
corresponding code for i386 in arch/i386/kernel/acpi/earlyquirk.c. Booting 
with the no_timer_check boot parameter as some people suggested does not help 
too.

Booting with apic=debug does not reveal any additional info. Only booting with 
noapic makes the machine boot.

Kind regards,

Gerd

      parent reply	other threads:[~2006-11-01 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.nWSYbiDM13Z4b2OlxoSzmqud/lI@ifi.uio.no>
     [not found] ` <fa.NxAEaSXPSQSEviWvGDBmTZn07UE@ifi.uio.no>
     [not found]   ` <fa.i/oIAoig46I/apLGccQ0BesB0W8@ifi.uio.no>
2006-10-29  4:49     ` Frustrated with Linux, Asus, and nVidia, and AMD Robert Hancock
2006-10-30  2:10       ` Bill Davidsen
2006-10-31 14:28       ` lspci output needed was " Andi Kleen
2006-10-31 16:11         ` Bill Davidsen
2006-11-01 22:17         ` Gerd v. Egidy [this message]

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=200611012317.13963.lists@egidy.de \
    --to=lists@egidy.de \
    --cc=ak@suse.de \
    --cc=davidsen@tmr.com \
    --cc=hancockr@shaw.ca \
    --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