From: Charles Duffy <charlesduffy-doANK8/0m3qakBO8gow8eQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: 2.6.5: Hitachi HA8000/70 panic, missing devices
Date: Mon, 05 Apr 2004 12:56:06 -0500 [thread overview]
Message-ID: <1081187765.2966.51.camel@duffbox> (raw)
Howdy. I'm presently working with a Hitachi HA8000/70. This system has a
Gigabyte motherboard primarily using ServerWorks chipsets.
With ACPI fully enabled, the system boots but fails to recognize some
PCI devices. Booting with pci=noacpi, or with ACPI deselected but
ACPI_BOOT selected, the system panics. This happens in SMP or UP as long
as ACPI_BOOT is enabled.
I'm able to convince the system to boot correctly (and show all devices)
in uniprocessor mode with PCI_GODIRECT and ACPI (as well as ACPI_BOOT)
disabled. The system was able to boot correctly running SMP in 2.4.
I've included links to a wide array of potentially relevant information
below. If there's anything I've left out, or some test I could run,
please let me know. If you're really interested in this one and in the
Austin area, it may be possible to loan the hardware or get together in
person -- I'll buy lunch.
---
A hand-typed boot log (no null-modem cable available) showing the panic
with pci=noacpi is at:
http://quackerhead.com/~duff/HA8000_70/noacpi_panic.txt
dmidecode output is at:
http://quackerhead.com/~duff/HA8000_70/dmidecode.txt
The original ACPI DSDT is at:
http://quackerhead.com/~duff/HA8000_70/dsdt.orig
My modified ACPI DSDT (same issue; less dead code and IASL-friendly):
http://quackerhead.com/~duff/HA8000_70/dsdt.new
Extra-verbose lspci output with a uniprocessor, non-ACPI_BOOT kernel:
http://quackerhead.com/~duff/HA8000_70/lspci_direct_pci_config.txt
the above shows all devices in the system.
Extra-verbose lspci output with a fully ACPI kernel:
http://quackerhead.com/~duff/HA8000_70/lspci_full_acpi_config.txt
the above is missing the GigE and SCSI controllers.
/proc/interrupts with the SMP ACPI kernel (and missing devices):
http://quackerhead.com/~duff/HA8000_70/interrupts_full_acpi_config.txt
this one uses IO-APIC-{edge,level} almost everywhere
/proc/interrupts with the UP non-ACPI kernel:
http://quackerhead.com/~duff/HA8000_70/interrupts_direct_pci_config.txt
this one uses XT-PIC everywhere
dmesg output with the SMP ACPI kernel (including ACPI debug info):
http://quackerhead.com/~duff/HA8000_70/dmesg_full_acpi_config.txt
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-05 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 17:56 Charles Duffy [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 5:54 2.6.5: Hitachi HA8000/70 panic, missing devices Li, Shaohua
[not found] ` <571ACEFD467F7749BC50E0A98C17CDD803B1208C-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-04-06 13:02 ` Charles Duffy
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=1081187765.2966.51.camel@duffbox \
--to=charlesduffy-doank8/0m3qakbo8gow8eq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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