Bug 4546
Summary: | A fix for APM on Acer Extensa 501T and possibly others. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael McConachie <michael> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | claudiol |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-02-04 03:10:46 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
Michael McConachie
1999-08-16 16:09:24 UTC
Doug, could you please evaluate this? Kernel problem, not apmd. Doesn't apply to current kernel - guess we can close this? This is a kernel problem - it's fixed in 2.3.x (CONFIG_APM_BAD_ENTRY_OFFSET), but it's still present in kernel 2.2.14. The patch mentioned above doesn't apply to current 2.2 kernels; the line in question is line 1353 in arch/i386/kernel/apm.c 2.2.14-1.2.0. I don't see a problem with this patch - IMO it can get in. Its already handled differently in current 2.2 |