public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Buckingham <peter@pantasys.com>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: linux-kernel@vger.kernel.org, kevin.mullins@asusts.com,
	JASON_RILEY@asusts.com, karim@opersys.com,
	Andreas Koch <koch@esa.informatik.tu-darmstadt.de>,
	Linus Torvalds <torvalds@osdl.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	dave.jones@redhat.com
Subject: Re: ASUS K8N-DL Beta BIOS AKA PROBLEM: Devices behind PCI	Express-to-PCI bridge not mapped
Date: Wed, 29 Jun 2005 10:01:49 -0700	[thread overview]
Message-ID: <42C2D3FD.2080306@pantasys.com> (raw)
In-Reply-To: <1120018942.6936.20.camel@home-lap>

Hi Sean,

I'm glad things are a little further on for you!

Looking at your dmesg the asus bios is still buggy (but i'm not sure 
it's specifically affecting what you're seeing).

Sean Bruno wrote:
> Aperture from northbridge cpu 0 too small (32 MB)
> No AGP bridge found
> Your BIOS doesn't leave a aperture memory hole
> Please enable the IOMMU option in the BIOS setup
> This costs you 64 MB of RAM

this isn't a big deal, but linux expects an apperture of >= 64MB, you 
may want to change this setting in your bios.

> init IO_APIC IRQs
>  IO-APIC (apicid-pin) 4-0, 4-16, 4-17, 4-18, 4-19, 4-20, 4-21, 4-22, 4-23 not connected.
> ..TIMER: vector=0x31 pin1=2 pin2=-1
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> ...trying to set up timer (IRQ0) through the 8259A ...  failed.
> timer doesn't work through the IO-APIC - disabling NMI Watchdog!
> ...trying to set up timer as Virtual Wire IRQ...Uhhuh. NMI received for unknown reason 3d.
> Dazed and confused, but trying to continue
> Do you have a strange power saving mode enabled?
>  failed.

I seem to remember that this may be related to the bios doing the wrong 
workaround for the timer. on the nvidia chipsets this shouldn't be required.

> ...trying to set up timer as ExtINT IRQ... works.
> CPU 1: synchronized TSC with CPU 0 (last diff 17 cycles, maxerr 519 cycles)

you might want to try enabling ACPI 2.0 or something similar in your 
bios and use the HPET timer instead.

> ACPI: Subsystem revision 20050309
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND
> search_node ffff810142857280 start_node ffff810142857280 return_node 0000000000000000
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace, AE_NOT_FOUND
> search_node ffff810142857180 start_node ffff810142857180 return_node 0000000000000000

there are problems with the ACPI tables supplied by the bios. Linux is 
expecting to find these items and does not.

> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace, AE_NOT_FOUND
> search_node ffff810142857180 start_node ffff810142857180 return_node 0000000000000000
>     ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0._PRT] (Node ffff810142857140), AE_NOT_FOUND

same as above, the acpi tables are missing information.

> ACPI: PCI Interrupt 0000:02:00.0[A]: no GSI - using IRQ 5
> PCI: Setting latency timer of device 0000:02:00.0 to 64

this may be nothing, but it does look a little disturbing (especially 
since it's the USB controller).

> PCI: cache line size of 64 is not supported by device 0000:00:02.1
> ehci_hcd 0000:00:02.1: park 0
> ehci_hcd 0000:00:02.1: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004

this is also disconcerting...

i'm not sure that i've provided a lot of enlightenment...

peter

  parent reply	other threads:[~2005-06-29 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 22:05 ASUS K8N-DL Beta BIOS Sean Bruno
2005-06-29  1:46 ` Karim Yaghmour
2005-06-29  4:22   ` ASUS K8N-DL Beta BIOS AKA PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped Sean Bruno
2005-06-29  4:35     ` Sean Bruno
2005-06-29 17:01     ` Peter Buckingham [this message]
2005-06-29 17:09       ` Sean Bruno
2005-06-29 17:17         ` Peter Buckingham

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=42C2D3FD.2080306@pantasys.com \
    --to=peter@pantasys.com \
    --cc=JASON_RILEY@asusts.com \
    --cc=dave.jones@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=karim@opersys.com \
    --cc=kevin.mullins@asusts.com \
    --cc=koch@esa.informatik.tu-darmstadt.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sean.bruno@dsl-only.net \
    --cc=torvalds@osdl.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