Red Hat Bugzilla – Bug 162269
Kernel hang during boot before init starts (ACPI/PCI/IRQ related, happens at IDE probing time)
Last modified: 2015-01-04 17:20:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
The kernel hangs during boot on my Compaq AMD Athlon XP laptop (Presario 920EA).
The hang occurs during IDE probing:
-- kernel output start --
ACPI: PCI Interrupt 0000:00:10.0[A]: no GSI - using IRQ 0
ALI15X3: chipset revision 196
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x8080-0x8087, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x8088-0x808f, BIOS settings: hdc:pio, hdd:pio
-- !! KERNEL HANGS HERE !!, kernel output end --
ALI IDE controller regressions ? kernel-2.6.12-1.1385_FC4 boots just fine on the very same laptop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to boot kernel on my laptop.
Actual Results: The kernel hung.
Expected Results: I expected it to boot, this laptop has never previously had problems with Fedora kernels.
Specs will be attached.
Created attachment 116261 [details]
Specs of machine where kernel hangs
Need more ? Please ask, and I shall post it.
Exact same issue here with kernel 2.6.12-1.1387_FC4 on an HP Athlon XP laptop
(Pavillion ze4560us). Same boot messages with ALI15X3 chipset before hang as well.
I seem to be having the same problem on my desktop. Kernel 2.6.12-1.1387_FC4, no
problems with 2.6.11-1.1369_FC4
[<c0100274>] init +0x0/0xfc
[<c0103c03>] common_interrupt +0x1a/0x20
[<c010101a>] default_idle +0x0/0x29
[<c0101040>] default_idle +0x26/0x29
[<c042170a>] cpu_idle +0x34/0x4c
[<c042170a>] start_kernel +0x15d/0x1b7
[<c04212f7>] unknown_bootoption +0x0/0x1b6
This is what my screen says when it gets stuck.
Created attachment 116293 [details]
Discription of my computer
just the output of lspci
I just tested 184.108.40.206 vanilla, and it has the exact same problem. Thus the
problem has probably been introduced with this version. 220.127.116.11 is the only
change from 1.1385_FC4 to 1.1387_FC4, according to RPM changelog.
Will try with vanilla 2.6.13-rc1.
(In reply to comment #5)
> I just tested 18.104.22.168 vanilla, and it has the exact same problem. Thus the
> problem has probably been introduced with this version. 22.214.171.124 is the only
> change from 1.1385_FC4 to 1.1387_FC4, according to RPM changelog.
> Will try with vanilla 2.6.13-rc1.
Doesn't work either, same problem 8(.
> (In reply to comment #5)
> > I just tested 126.96.36.199 vanilla, and it has the exact same problem. Thus the
> > problem has probably been introduced with this version. 188.8.131.52 is the only
> > change from 1.1385_FC4 to 1.1387_FC4, according to RPM changelog.
> > Will try with vanilla 2.6.13-rc1.
> Doesn't work either, same problem 8(.
OK, I got i working with 2.6.13-rc1. Seems this patch was needed:
(ACPI/IRQ stuff, one line fix)
I applied it to 2.6.13-rc1, and it now boots.
I will now try this patch isolated on 2.6.12-1.1387_FC4, and see if it works,
since 2.6.13-rc1 had other problems with FC4 that I'm not willing to deal with,
(In reply to comment #7)
> I will now try this patch isolated on 2.6.12-1.1387_FC4, and see if it works,
> since 2.6.13-rc1 had other problems with FC4 that I'm not willing to deal with,
> right now.
OK, confirmed, 2.6.12-1.1387_FC4 boots on my laptop after applying the above
patch I mentioned in comment #7. I'll settle for this right now, and leave it up
the bugzilla/kernel maintainers to change bug status, when it's officially fixed
(the patch comes from linux-2.6.13-rc1-git5 upstream).
For those who want to recompile the 1.1387_FC4 kernel, I'm going to add the
patch as an attachment.
Created attachment 116312 [details]
Patch that fixes problem (on my laptop, at least).
pci=noacpi works on my laptop that has the problem with not booting
2.6.12-1.1387_FC4, where as 2.6.11-1.1369_FC4 worked without it.
(In reply to comment #10)
> pci=noacpi works on my laptop that has the problem with not booting
> 2.6.12-1.1387_FC4, where as 2.6.11-1.1369_FC4 worked without it.
Yep, seems like this is the easiest work-around, without having to disable ACPI
entirely (or recompiling w/patch).
*** Bug 162321 has been marked as a duplicate of this bug. ***
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
(In reply to comment #13)
2.6.12-1.1398_FC4 boots just fine.
The problem disappeared after the update to 2.6.12-1.1390_FC4. As far as I'm
concerned, this bug is fixed.
2.6.12-1.1390_FC4 is working fine for me.