mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI issues on HP DL585 G2
Date: Sun, 28 Jun 2009 18:49:34 -0700	[thread overview]
Message-ID: <86802c440906281849m51ab3c82u84d76a1aaceba2ef@mail.gmail.com> (raw)
In-Reply-To: <20090628223132.GO20436@tamriel.snowman.net>

On Sun, Jun 28, 2009 at 3:31 PM, Stephen Frost<sfrost@snowman.net> wrote:
> Yinghai,
>
> * Yinghai Lu (yhlu.kernel@gmail.com) wrote:
>> try 2.6.30
>
> dmesg from 2.6.30 (w/ pci=noapic noapic) attached.  Box didn't boot
> again, but we did get a "hung process" message from the kernel after a
> while.  I don't have more info than that about the boot w/o pci=noapic
> noapic, sorry.  I can try and get that info at another time if this
> isn't enough.
>

your BIOS doesn't assign resource for some devices
[    0.688930] pci 0000:01:03.0: reg 30 32bit mmio: [0x000000-0x01ffff]
[    0.689183] pci 0000:01:04.2: reg 30 32bit mmio: [0x000000-0x00ffff]
[    0.696343] pci 0000:41:01.0: reg 30 32bit mmio: [0x000000-0x01ffff]
[    0.696525] pci 0000:41:02.0: reg 30 32bit mmio: [0x000000-0x01ffff]
[    0.696740] pci 0000:42:02.0: reg 30 32bit mmio: [0x000000-0x03ffff]

and acpi ioapic
ACPI: IOAPIC (id[0x08] address[0xf7cf0000] gsi_base[0])
IOAPIC[0]: apic_id 8, address 0xf7cf0000, GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xf7fd0000] gsi_base[24])
IOAPIC[1]: apic_id 9, address 0xf7fd0000, GSI 24-30
ACPI: IOAPIC (id[0x0a] address[0xf7fe0000] gsi_base[31])
IOAPIC[2]: apic_id 10, address 0xf7fe0000, GSI 31-37
ACPI: IOAPIC (id[0x0b] address[0xf7ff0000] gsi_base[38])
IOAPIC[3]: apic_id 11, address 0xf7ff0000, GSI 38-61

mptable report
[    0.000000] Intel MultiProcessor Specification v1.4
[    0.000000] MPTABLE: OEM ID: HP
[    0.000000] MPTABLE: Product ID: PROLIANT
[    0.000000] MPTABLE: APIC at: 0xFEE00000
[    0.000000] I/O APIC #8 Version 32 at 0xD9CF0000.
[    0.000000] I/O APIC #9 Version 32 at 0xD9FD0000.
[    0.000000] I/O APIC #10 Version 32 at 0xD9FE0000.

are you sure these two come from same BIOS ?

YH

  reply	other threads:[~2009-06-29  1:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28  3:40 Stephen Frost
2009-06-28  4:26 ` Yinghai Lu
2009-06-28 14:17   ` Stephen Frost
2009-06-28 22:31   ` Stephen Frost
2009-06-29  1:49     ` Yinghai Lu [this message]
2009-06-29  1:57       ` Stephen Frost
2009-06-29  3:47         ` Yinghai Lu
2009-06-29 13:23           ` Stephen Frost
2009-06-28 17:20 ` Alex Chiang
2009-06-28 17:35   ` Stephen Frost
2009-06-28 22:32   ` Stephen Frost
2009-06-30  1:15     ` dann frazier
2009-06-30  1:17       ` Stephen Frost
2009-06-30  1:47         ` Yinghai Lu
2009-06-30  1:51           ` Stephen Frost
2009-06-30  1:53             ` dann frazier
2009-06-30  2:06               ` Stephen Frost
2009-06-30 16:08                 ` dann frazier
2009-06-30 19:30                 ` dann frazier
2009-07-01  1:35                   ` Stephen Frost
2009-07-03 22:54                     ` dann frazier
2009-06-30  2:10               ` Stephen Frost
2009-06-30  2:15                 ` dann frazier
2009-06-30  2:21                   ` Stephen Frost
2009-06-30  5:57                     ` Yinghai Lu
2009-06-30  1:18       ` Stephen Frost

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=86802c440906281849m51ab3c82u84d76a1aaceba2ef@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrost@snowman.net \
    /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®