Bug 125986 - bug in pmdisk of kernel-sourcecode
Summary: bug in pmdisk of kernel-sourcecode
Status: CLOSED DUPLICATE of bug 125882
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 2
Hardware: noarch
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
: 126079 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-06-14 20:32 UTC by Joe Winegarden
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:04:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Joe Winegarden 2004-06-14 20:32:20 UTC
Description of problem:
There is a 'typo' on line 24 of arch/i386/power/pmdisk.S in the
newly-release kernel-sourcecode-2.6.6-1.435:
movl $swsusp_pg_dir-...
$swsusp_pg_dir is an unknown object, disallowing me to compile my own
kernel with PM_DISK included.
I changed this to match the same line in kerne-source-2.6.5-1.358:
This allows make bzImage to complete successfully with PM_DISK
included. Suspend/Resume via pmdisk seems to work correctly with this
fix once new kernel is loaded.

Version-Release number of selected component (if applicable):

How reproducible:
Always, until modified as described.

Steps to Reproduce:
1. Modify kernel config to include software suspend (PM_DISK)
2. Attempt to make bzImage
3. Compilation fails with unknown object 'swsusp_pg_dir' error
Actual results:

Expected results:

Additional info:

Comment 1 Joe Winegarden 2004-06-15 20:35:48 UTC
*** Bug 126079 has been marked as a duplicate of this bug. ***

Comment 2 Dave Jones 2004-06-15 21:43:48 UTC

*** This bug has been marked as a duplicate of 125882 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:04:05 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.