|
Bugzilla – Full Text Bug Listing |
| Summary: | machine freezes unless noapic is given | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Rihards Olups <richlv> |
| Component: | Kernel | Assignee: | Andreas Kleen <ak> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | acpi |
| Version: | Alpha 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | hwinfo output with and without noapic | ||
|
Description
Rihards Olups
2006-01-02 23:13:50 UTC
Could you please supply the output of hwinfo with and without noapic? Created attachment 61954 [details]
hwinfo output with and without noapic
Hm, the boot message log shows <7>APIC error on CPU0: 04(40) (exactly once) <7>APIC error on CPU0: 40(40) (many many times) 04 is Send accept error 40 is Received illegal vector Andi, any clue what might cause this? Could this have to do that the whole ACPI subsystem could not be loaded and some IO/apic configuration might be missing(#141375)?:
ACPI-0311: *** Error: ns_search_and_enter: Bad character in ACPI Name: 43035350
ACPI-0292: *** Error: Looking up [0x43035350] (NON-ASCII)
in namespace, AE_BAD_CHARACTER
ACPI-0115: *** Error: acpi_load_tables: Could not load namespace: AE_BAD_CHARACTER
ACPI-0123: *** Error: acpi_load_tables: Could not load tables: AE_BAD_CHARACTER
ACPI: Unable to load the System Description Tables
Yes, many modern systems don't work in APIC mode without ACPI since the mptables are untested. Did ACPI work with earlier kernels on the system? suse 10.0 refused to install (did not find any ide or sata blockdevices), so 10.1a4 is the first operating system on this machine. temporalily upgrading to rc6-git<something> did not help. Should probably figure out why the ACPI stack can't parse your ACPI tables. Can you please attach acpidmp output? it was already found out at bug 141375 - seems that two bytes are swapped in bios. in any case, acpidmp is also attached there. i informed asrock the next day, but have received no answer so far. maybe somebody else with more influential email address can bug them ;) Ok BIOS bug -> INVALID. |