This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Does your machine come back from hibernation successfully if you use
these commands?
echo shutdown > /sys/power/disk
echo disk > /sys/power/state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/79
I have run the 'hibernate hang' (aka situation 1) quite a lot of times
now, but only one time I managed to catch something with locatehang:
Looking for function that matches hash from the Magic Number from the kernel
log.
Magic: 2:752:371 maps to hash: 5a7cf2
Hash
What I mean is in #45 is that the date/time flips from July 29th to March 11th,
my guess is that that value comes from the RTC...
Attached is the System.map
** Attachment added: "System.map"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/797922/+attachment/2241517/+files/System.map
--
Situation 1:
rtl8192, the wifi driver, is on the last log line. Re-run the 's4test -h' test
but unloaded the r8192se_pci module first. There is not mucht difference. The
last line before the reboot in kern.log is now:
PM: Syncing filesystems ... called -> sys_sync()
--
You received this bug no
I don't understand what you mean in comment #45. If there's something in
the log that indicates a value was written to the RTC, I'm overlooking
it.
Note that the timestamps in the kernel log always start from 0 after
boot and represent how many seconds the machine has been running.
--
You receiv
Unfortunately I'm not able to tell much from that crash dump. I might be
able to tell a little more if you will attach /boot/System.map-$(uname
-r) to the bug report so I can look up what some of the addresses I see
correspond to.
Did you run locatehang after the hang on resume with nomodeset? If
In the kern.log I found some logging from situation 1. From the
timestamps in the logging after reboot you can see that the RTC was used
to store a value.
** Attachment added: "s4test-hibernate-kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/797922/+attachment/2241460/+files/s4t
** Attachment added: "105_4990.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/797922/+attachment/2241442/+files/105_4990.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
** Attachment added: "105_4988.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/797922/+attachment/2241440/+files/105_4988.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
** Attachment added: "105_4989.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/797922/+attachment/2241441/+files/105_4989.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
Mixed results so far. I have tested 2 situations:
1) without 'nomodeset' , i.e. nouveau loaded and module use counter=2. (in
this situation is hangs on hibernate)
s4test -h : prints on the screen that it hibernates, switches off the screen
and machine is unresponsive, no disk activitity. (I did
It is an internal wiki page (probably because it's still fairly error-
prone); I didn't notice that earlier. Here are the instructions.
1. Download the pmdebug utilities. These are currently available in a
git repository, so you need to have git installed (sudo apt-get install
git). Then run 'git
The link you sent replies: "You are not allowed to view this page". If
I click on login, it does authenticate me, however the message "You are
not to view this page" is persistent :-(
Is it page for Canonical internal use only, perhaps?
--
You received this bug notification because you are a me
Test with nouveau loaded and nomodeset (i.e. nouveau use count=0), suspends
correct. On resume print a one line message:
[ 90.708043] ata1.01: failed to resume link (SControl 0)
I see this message right before suspend as well (also without nouveau loaded
and resume working fine) so I think thi
You might check that with nomodeset whether resume really hung or the
display just didn't come on. I.e. ping the device on the network, or
install an ssh server and try to log in.
Here's the link I forgot to include earlier for the systemtap debugging.
Since it doesn't look like you have any other
Blacklisting nouveau does not prevent it from loading, even the boot
parameter 'rdblacklist=nouveau' does not work. It is loaded and in use,
i.e. no way to get it removed. According to
http://kubuntuforums.net/forums/index.php?topic=3110471.10;wap2 the
'nomodeset' parameter prevents nouveau from
If you suspect nouveau you could try blacklisting it and rebooting. To
blacklist it you just need to add a line that reads 'blacklist nouveau'
to /etc/modprobe.d/blacklist.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Full install: 2 harddisks are in raid0 with lvm and LUKS on top of it, kubuntu
applications are installed, root password is set to enable root-login on the
console.
The minimal install used earlier uses sda directly with lvm (no raid and no
LUKS) and has a minimal set of applications (no X), i.e
The firewire driver is the problem!
Which is odd because as said I did do tests with driver unloading until all of
them were unloaded. But there are differences between this and previous tests,
one of them is a kernel change: was 2.6.38-8, is now 2.6.38-10.
With 'nomodeset' on, resume from hibe
That's something. There's probably a lot of scrollback that we can't see
that would be really helpful there though.
What I can see is in firewire. You said you tried unloading modules
before, but would you try unloading firewire_ohci and firewire_core
before hibernating and see what you get on the
** Attachment added: "105_4977.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/797922/+attachment/2236670/+files/105_4977.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
Repeated the test in #29 but added the 'nomodeset' parameter.
Now I get the crash on the screen. I have tried to set the consolefont smaller
but it switches back to standard VGA right before the crash.
Attached are some pictures, I managed to take.
** Attachment added: "105_4976.JPG"
https:
Sorry, this laptop does not have a serial port.
pm-hibernate in recovery mode + no_console_suspend + alt-sysreq-9 gives
the same result as #25.
I have just installed systemtap but never used it yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
So you have. And based on that it looks like a problem suspending
devices.
Our debugging options start getting more difficult at this point. If you
have a serial port (and another machine with a serial port) we can print
out the console on it. If this is possible I can provide instructions to
set
Done that, see #21
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
kernel hangs in pm-hibernate on saving to disk
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Please try the steps under "Per sub-system hibernate testing" on the
page below and report back your results.
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
kernel hangs in pm-hibernate on saving to disk
To manage notificatio
The boot parameter no_console_suspend is already there from earlier tests (I
check in the grub-menu that is is actually passed at boot)
Done alt-sysrq-9, I see the loglevel message.
After pm-hibernate it writes 3 lines to the screen, clears the screen, then the
following lines:
Looking for spla
Okay, they are probably different problems then.
Let's try this next. Boot with no_console_suspend, then switch to a
virtual terminal 1 (i.e. press Ctrl-Alt-1). Then press Alt-Sysrq-9, and
you should see a message that says "Loglevel set to 9". Now run 'sudo
pm-hibernate' and report back what appe
I do not know whether the behaviour is related.
With hibernation it hangs with black screen during hibernation
With suspend it hangs on resume.
The hibernation problem occurs in kernels 2.6.38-8 and 3.0-0, it does NOT in
occur in 2.6.35-28.
The suspend problem occurs in kernels 2.6.38-8 and 3.0
Can you clarify your hibernation problem? Does the machine hang when
hibernating, or does it hibernate okay and then hang when resuming from
hibernation? If the hang is during resume then it looks likely from what
you've described that the problem might be the same as the one you have
resuming from
I started off with suspend and switched to hibernate as it seemed to work
little better.
Anyway I have tried suspend using the info from the wiki. It looks like the
machine suspends correctly: it switches off the fans and in the end the screen
too (although I have set the boot parameter 'no_co
Please try the steps under the "Debugging Hibernate" section of the
following link and report back you findings.
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume
Also, have you tested to see if suspend to RAM works? We generally
recommend using suspend instead of hibernate, as it t
At the moment of running the apport-collect I had Maverick installed with the
kernels of Maverick, Natty and Oneiric.
I tried to run apport-collect with the Oneiric kernel but it is recognized as a
vanilla kernel, therefore I reran the process with the Natty kernel. The
results are posted above.
apport information
** Description changed:
Machine hangs with black screen during hibernation. Only hard powerdown / up
helps, but no hibernation image is found on boot.
Problem occurs in kernels 2.6.38-8 and 3.0-0, it does NOT in occur in
2.6.35-28.
I have tried maverick and natty with
** Tags added: apport-collected
** Description changed:
Machine hangs with black screen during hibernation. Only hard powerdown / up
helps, but no hibernation image is found on boot.
Problem occurs in kernels 2.6.38-8 and 3.0-0, it does NOT in occur in
2.6.35-28.
I have tried maverick an
Please run 'apport-collect 797922' from a terminal on the affected
machine to attach the relevant information to this bug report. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797922
Title:
kernel hangs in pm-hibernate on saving to disk
To manage notifications about th
39 matches
Mail list logo
