#7628 closed bug (fixed)
Boot fails unless IO-APIC is disabled in boot menu
| Reported by: | gerald.zajac | Owned by: | mmlr |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Kernel | Version: | R1/Development |
| Keywords: | Cc: | greggd@… | |
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
When booting a computer with an MSI K7T Turbo2 motherboard, AMD Athlon XP 2000+ CPU, and 512 MB memory, the boot fails immediately after the boot screen is displayed. If IO-APIC is disabled in the boot menu, the computer boots and runs okay.
This was tested with hrev41843; however, earlier versions also had this problem.
Attachments (6)
Change History (20)
by , 13 years ago
| Attachment: | K7T_syslog added |
|---|
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
| Blocking: | 7665 added |
|---|
follow-up: 4 comment:3 by , 12 years ago
comment:4 by , 12 years ago
Replying to pulkomandy:
Does checking "disable local APIC" in the boot menu work too ?
It most certainly does, as disabling the local APIC disables all the things that depend on it (APIC timers, IO-APIC, IPIs and therefore SMP, some local interrupts for thermal / power management we don't do yet).
comment:6 by , 12 years ago
Replying to pulkomandy:
Definitely not. The system in this report does do the MP config using ACPI and the configuration is valid. The problem is much further down, where the current configuration of an interrupt link device is being read. That fails so that it's not really possible for the interrupt code to properly set up the interrupt routing. The system should continue to boot (falling back to PIC mode instead of (IO-)APIC) by simply continuing out of that panic. Possibly the link device in question isn't enabled and if not actually needed doesn't need to provide the current config. Other than that an initial configuration might be inferable by some other means, but I'll need to look into that again.
comment:7 by , 12 years ago
| Cc: | added |
|---|
comment:8 by , 12 years ago
I have the same bug but my syslog does not seem to match the reporters syslog. I'm thinking it should match at least in a general sense, because of different hardware. To get my syslog I started boot into safe mode options, made sure syslog was selected in debug options and returned to boot menu without disabling local apic. The system froze at the middle boot icon. I then did a hardware reset and boot with local apic disabled, also had the syslog disabled in debug options, for this boot. Would the syslog be generated and remembered for the boot with local apic enabled, since it is neccessary for the reset?
by , 12 years ago
| Attachment: | My hardware from lspci in Ubuntu.txt added |
|---|
My hardware from lspci in Ubuntu
follow-up: 12 comment:11 by , 12 years ago
| Milestone: | Unscheduled → R1 |
|---|
The last message from 100_0482.JPG is:
usb ohci -1: smm is in control of the host controller
comment:12 by , 12 years ago
Replying to diver:
The last message from 100_0482.JPG is:
usb ohci -1: smm is in control of the host controller
That is probably correct at least for bug #3999. As with that bug disabling C1E in the BIOS enabled Haiku to boot for me. I have not tried the other means to get around the bug as the reporter mentioned, "I hit the power button instead of the reset one. And the boot continued!!"
comment:13 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
lots and lots of core kernel + driver + usb changes since this one was opened. Please re-open if the same issue still exists on the same hardware chipset.
comment:14 by , 6 years ago
| Blocking: | 7665 removed |
|---|
I have a similar problem with a DFI AD77 motherboard and Athlon XP 2200+. (Via KT400A and VT8235 chipset) Does checking "disable local APIC" in the boot menu work too ?