2008-10-22 09:38:34 |
Philipp Dreimann |
bug |
|
|
added bug |
2008-10-23 17:08:56 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
2008-10-23 17:08:56 |
Leann Ogasawara |
linux: statusexplanation |
|
Thanks Philipp,
Just so I can gather some additional information about your system, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
It would be best if you could capture the dmesg output after you resume from suspend. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback. |
|
2008-11-07 17:52:27 |
Thomas Novin |
bug |
|
|
added attachment 'syslog.txt' (syslog.txt) |
2008-11-07 17:56:33 |
Thomas Novin |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
2008-11-07 17:56:58 |
Thomas Novin |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
2008-11-07 17:57:16 |
Thomas Novin |
bug |
|
|
added attachment 'version.log' (version.log) |
2008-11-08 10:08:40 |
Thomas Novin |
linux: status |
Incomplete |
New |
|
2008-11-08 10:08:40 |
Thomas Novin |
linux: statusexplanation |
Thanks Philipp,
Just so I can gather some additional information about your system, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
It would be best if you could capture the dmesg output after you resume from suspend. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback. |
|
|
2008-11-11 01:02:43 |
Leann Ogasawara |
linux: status |
New |
Incomplete |
|
2008-11-11 01:02:43 |
Leann Ogasawara |
linux: statusexplanation |
|
Hi Thomas,
I think you actually have a different bug than Philipp and should open a new report. The reason I say this is the warning you see is just that, a warning. It's indicating that it took longer to resume the devices than anticipated. Philipp mentioned he sees no other ill effects whereas you mention your system freezes so I suspect even though you may be seeing the same warning you likely have separate issues. I'd assume when Philipp posts the above requested information that it will show he has different hardware than you (via the lspci output). So for now if you can open a separate bug report that would be great. We can always mark bugs as duplicates later on if necessary. Thanks. |
|
2008-11-11 19:57:14 |
Mark Grandi |
bug |
|
|
added attachment 'kernel warning.txt' (the warning from kernel.log) |
2008-11-11 19:58:27 |
Mark Grandi |
bug |
|
|
added attachment 'dmesg.log' (dmesg output from polygon) |
2008-11-11 19:58:55 |
Mark Grandi |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci output from polygon) |
2008-11-11 19:59:42 |
Mark Grandi |
bug |
|
|
added attachment 'version.log' (version.log from polygon) |
2008-11-22 12:55:15 |
moose |
bug |
|
|
added attachment 'dmesg_lspci_version.zip' (logs from moose) |
2009-02-21 17:40:21 |
TJ |
linux: assignee |
|
intuitivenipple |
|
2009-02-21 17:40:21 |
TJ |
linux: statusexplanation |
Hi Thomas,
I think you actually have a different bug than Philipp and should open a new report. The reason I say this is the warning you see is just that, a warning. It's indicating that it took longer to resume the devices than anticipated. Philipp mentioned he sees no other ill effects whereas you mention your system freezes so I suspect even though you may be seeing the same warning you likely have separate issues. I'd assume when Philipp posts the above requested information that it will show he has different hardware than you (via the lspci output). So for now if you can open a separate bug report that would be great. We can always mark bugs as duplicates later on if necessary. Thanks. |
This appears to be caused by bug #331415 "request_firmware() fails on resume from suspend" but I need to know what device drivers might be requesting firmware.
Please attach /var/log/kern.log that contains the Oops message - it should also contain clues as to which driver was delayed.
If the logs confirm it I'll mark this as a duplicate of that bug. |
|
2009-02-27 00:13:40 |
Jacob Torrey |
bug |
|
|
added attachment 'kern.log' (kern.log) |
2009-02-27 00:15:46 |
Jacob Torrey |
bug |
|
|
added attachment 'cpuinfo.txt' (cpuinfo.txt) |
2009-02-27 00:16:08 |
Jacob Torrey |
bug |
|
|
added attachment 'lspci.txt' (lspci.txt) |
2009-03-20 19:20:40 |
TJ |
tags |
intrepid linux-2.6.27 regression |
intrepid linux-2.6.27 regression test-suspend-seconds |
|
2009-03-20 19:22:48 |
TJ |
linux (Ubuntu): importance |
Undecided |
Low |
|
2009-03-20 19:22:48 |
TJ |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
2009-04-19 18:18:27 |
Andres Mujica |
summary |
kernel warning while suspending |
kernel false positive warning while suspending (took more than 5secs) |
|
2009-04-19 18:23:02 |
Andres Mujica |
tags |
intrepid linux-2.6.27 regression test-suspend-seconds |
intrepid linux-2.6.27 metabug regression test-suspend-seconds |
|
2009-10-30 17:38:26 |
Andy Whitcroft |
marked as duplicate |
|
464552 |
|
2009-11-05 00:43:19 |
Mark Grandi |
removed subscriber Mark Grandi |
|
|
|