[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/566834
** This bug is no longer a duplicate of bug 1073749
WARNING: at /build/buildd/linux-3.5.0/kernel/power/suspend_test.c:53
suspend_test_finish+0x86/0x90()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
James Deibele, thank you for reporting this and helping make Ubuntu better.
Lucid reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If
so, as per
*** This bug is a duplicate of bug 523824 ***
https://bugs.launchpad.net/bugs/523824
** This bug has been marked a duplicate of bug 523824
WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
--
You received this bug notification because
*** This bug is a duplicate of bug 1073749 ***
https://bugs.launchpad.net/bugs/1073749
** This bug is no longer a duplicate of bug 523824
WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
** This bug has been marked a duplicate of bug
** Tags added: suspend-test-finish
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi James,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 17.420 seconds. I'm setting this
to
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi,
The warning reported here typically indicates that it took longer for your
system to resume from suspend than expected. I believe there is a 5 sec barrier
which your system likely exceeded. Typically
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi,
Looking at your Dmesg log, we can find several errors like this:
...
[6.551462] end_request: I/O error, dev sr0, sector 0
[6.551502] Buffer I/O error on device sr0, logical block 0
...
Some
On 06.05.2010 18:08, ^_Pepe_^ wrote:
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi,
Looking at your Dmesg log, we can find several errors like this:
...
[6.551462] end_request: I/O error, dev sr0, sector 0
[6.551502] Buffer I/O error
So, it's not a IDE problem
** This bug is no longer a duplicate of bug 464552
suspend_test_finish warning triggers too easily, increase timeout to match
mainline times
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
WARNING: at
Hi again,
Your dmesg (original reporter) also includes a warning regarding HDD
warning: maximal mount count reached, running e2fsck is recommended
Please, consider to run
sudo e2fsck -pcfv /dev/ where is the / partition with a LiveCD
version.
Thanks
--
WARNING: at
** Tags added: kernel-suspend
** Tags added: kj-triage
--
WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
https://bugs.launchpad.net/bugs/566834
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Summary changed:
- 195980.117021 - cut here -
+ WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
--
WARNING: at /build/buildd/linux-2.6.32/kernel/power/suspend_test.c:53
suspend_test_finish+0x88/0x90()
14 matches
Mail list logo
