Ubuntu
linux package

regression: suspend2ram/resume broken since 2.6.24-17

Bug #236456 reported by pittipatti on 2008-06-01

This bug report is a duplicate of: Bug #226279: Kernel 2.6.24-17 - broken resume from suspend to RAM. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

After the upgrade from 2.6.24-16 to 2.6.24-17 the system doesn't wake up from suspend2ram.

With 2.6.24-16 there was no problem.

I get following output after running echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force:

[ 12.407168] Magic number: 0:968:196
[ 12.407171] hash matches /build/buildd/linux-2.6.24/drivers/base/power/main.c:112
[ 12.407192] hash matches device ttys8
[ 12.407199] hash matches device ttypb

Tags:

Revision history for this message

pittipatti (pittipatti) wrote on 2008-06-01: Re: [Bug 236456] [NEW] suspend2ram/resume broken since 2.6.24-17

dmesg.log Edit (34.5 KiB, text/plain; name="dmesg.log")
lspci-vvnn.log Edit (19.5 KiB, text/plain; name="lspci-vvnn.log")
uname-a.log Edit (80 bytes, text/plain; name="uname-a.log")
version.log Edit (27 bytes, text/plain; name="version.log")

Changed in linux:
assignee:	nobody → ubuntu-kernel-team

Revision history for this message

pittipatti (pittipatti) wrote on 2008-06-04:

Still the same behavior with today's kernel-update to 2.6.24-18

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2008-06-11:

Hi pittipatti,

This looks like a duplicate of bug 226279 so I'm marking it as such. I believe the upcoming -19 kernel in hardy-proposed should resolve this for you. If you could test and provide feedback in that report, it would be great.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-12-23: Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.