Bug 253532
Summary: | pm-utils should check if kernel has upgraded before suspending | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Traxtopel <traxtopel> |
Component: | pm-utils | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED CANTFIX | QA Contact: | desktop-bugs <desktop-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.1 | CC: | rvokal, syeghiay |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-20 16:26:09 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
Traxtopel
2007-08-20 13:29:13 UTC
This will need a bit of work as no current fix is there, but should be doable. As we are currently already very late for RHEL-5.1.0 it's not sure if we can include this fix in RHEL-5.1.0, but certainly as soon as possible. Additionally with our normal and supported update procedure the last 3 kernels as well as the installed one will always remain on your system, and manually upgrading and removing the currently running kernel without a reboot can cause other problems as well (e.g. USB devices and other hotplug related hardware). Requesting this as a RHEL-5.2 Fastrack bug then. Read ya, Phil PS: Maybe we should mark manual upgrades of kernels in the releasenotes appropriately and mention that a reboot of the system afterwards is highly recommended? This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Unfortunately due to capacity constraints of higher prioritized issues we currently can't commit to fix this issue in time for the next Red Hat Enterprise Linux update release. We will of course still try to address this issue if time and resources are available before the end of the Development phase or at a future Red Hat Enterprise Linux update release. Read ya, Phil This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Engineering for inclusion in a Red Hat Enterprise Linux maintenance release. Red Hat does not currently plan to provide this change in a Red Hat Enterprise Linux update release for currently deployed products. The problem we identified was that this would need to be fixed overall for the system instead of for single applications as it affects a large number of applications and services that require unloading and loading modules. Also the standard and recommended way for updates always will leave the currently running kernel installed on the system, which will completely avoid this problem. With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating enhancements for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects. However, Red Hat will further review this request for potential inclusion in future major releases of Red Hat Enterprise Linux. |