Regression: Intrepid - 2.6.27 hangs on resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase-workspace (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
linux-meta (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I'm opening a new bug report as advised in Bug #272624. I have a Dell Latitude D620 which I could suspend and resume without any problems in kernel versions 2.6.27-2 and prior. But since 2.6.27-3, resume doesn't work anymore, even not with the just published 2.6.27-4. I've tried to debug this problem as shown at https:/
The debug-output shows the following.
First run:
[ 2.138531] Magic number: 8:539:138
[ 2.138536] block ram3: hash matches
[ 2.138696] rtc_cmos 00:06: setting system clock to 2008-09-22 17:06:11 UTC (1222103171)
Another run:
[ 2.130543] Magic number: 0:506:649
[ 2.130587] tty ptyde: hash matches
[ 2.130708] rtc_cmos 00:06: setting system clock to 2044-02-11 20:36:30 UTC (2338835790)
Another run:
[ 2.129585] Magic number: 0:953:872
[ 2.129588] hash matches /build/
[ 2.129659] tty ptytd: hash matches
[ 2.129754] rtc_cmos 00:06: setting system clock to 1992-06-13 06:51:46 UTC (708418306)
I'm not sure what is causing this problem now - the hardware didn't change and it even doesn't work anything detached.
Changed in linux: | |
status: | Incomplete → Confirmed |
assignee: | chrisccoulson → nobody |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
Changed in linux: | |
assignee: | chrisccoulson → nobody |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.
Please include the information as separate attachments: /wiki.ubuntu. com/DebuggingKe rnelSuspend (which you're already familiar with).
* Output of uname -a
* uname -a > uname.txt
* Output of sudo lspci -vvnn
* sudo lspci -vvnn > lspci.txt
* Output of sudo dmidecode
* sudo dmidecode > dmidecode.txt
* Try to suspend/hibernate and then restart the system and attach /var/log/kern.log.0 and /var/log/kern.log
* Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
* cp -r /proc/acpi /tmp
* tar -cvjf ~/acpi.tar.bz /tmp/acpi
* attach acpi.tar.bz from your home directory
* Please attach your /var/log/kern.log after following the debugging steps at https:/
Thanks