Bug 36419
| Summary: | Hangs on bootup after system installs | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Greg LaPolla <greg> |
| Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Aaron Brown <abrown> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | bero |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-06-06 00:23:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Greg LaPolla
2001-04-18 05:49:49 UTC
This is almost certainly a problem with your BIOS ("current" and "working" can
be two quite different things), since it works everywhere else.
It's definitely not an apmd problem, all apmd does is taking care of executing
scripts when the apm status changes (e.g. when you pull the plug or put the
machine into suspend).
Reassigning to kernel, because that's (1) where the problem might be if it
isn't a BIOS bug after all, and (2) it's where workarounds for the problem
could go (Mike: what do you think about disabling apm on some blacklist
BIOSes?)
Bios-specific APM blacklist is planned and currently under development by the linux APM maintainer as an extra workaround: rpm -e apmd :) Well, it worked fine under redhat 6.2. So I dont see how this can be a bios issue. It could be something that was interduced in the 2.4 kernel apm routines. Since it did work on redhat 6.2, I dont how this could be a blacklisted bios. I will try to dig into it more this weekend. And see if I can get some more info as to what is locking up when apmd loads. Is there a resolution to this yet ? you could try booting with "apm=off" on the commandline. The difference between older kernels (eg 2.2 kernels as in 6.2 and 7.0) is that the kernel currently trusts the APM bios to comply to the standard a bit more to get extra information and powersaving (eg when the system is idle). It doesnt do this on debian or Mandrake with newer kernels however redhat 7.2 beta is a litle better, at least it boots, it will lock anytime the apm command is used. It onoly appears to be specific to redhat. My question is it going to be fixed ? We don't have ANY patches against the APM code. So the only question is which config options are different. I'll check the latest Mandrake kernel; the only thing I can think of is that they have the ALLOW_IRQ option different; that can be overriden at boottime by adding a apm=allowints (7.1) apm=allow_ints (7.2) to the kernel commandline. Using apm=allow_ints on redhat 7.2 doesn't help issuing apm at the shell prompt causes the system to lock up. apm should return back the battery status or at least thats what it used to return. Well, I have found the fix sorta. After hacking around with the 2.4.7 source all weekend I downloaded 2.4.9 kernel. I only applied the ext3 patches. And built the kernel using the same options that are used to build the i386 verion except I used the k6 arch instead and omitted the options that are added by the patches. All is good now. So eaither there is a bug in the 2.4.7 kernel or you are creating a bug with patches you apply to the kernel. Also on another note the kernel pcmcia based drivers choke on my laptop when a cardbus card is inserted, works fine with 16 bit cards. So I recompiled with out pcmcia and installed the latest pcmcia-cs drivers from David Hines and all works good. I think I am working at 100%. I am still testing things. |