The timeout for this warning was increased for Lucid and later. Closing
off the development task.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2866
On Tue, 2009-04-21 at 18:16 +, Tormod Volden wrote:
> TJ, I added the test-suspend-seconds tag to a bunch of reports which I
> think are duplicates. Should I dup them, or would you like run your
> launchpad mining on them first?
Thanks Tormod that's really helpful. I'll run a modified script a
TJ, I added the test-suspend-seconds tag to a bunch of reports which I
think are duplicates. Should I dup them, or would you like run your
launchpad mining on them first?
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/
Proposing to increase TEST_SUSPEND_SECONDS to 12 to avoid false
positives based on analysis of all bug reports that have log attachments
with non-failure resume times over 5 seconds. Bugs with such logs are
tagged "test-suspend-seconds":
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=test-suspe
** Tags added: test-suspend-seconds
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Progress Update:
Currently analysing log-files collected on Launchpad to determine a
suitable value for TEST_SUSPEND_SECONDS.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notificati
** Tags added: resume
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Sat, 2009-02-28 at 08:45 +, Fridtjof Busse wrote:
> I agree that this is not a critical error, but nonethelesse a kernel
> oops is not exactly a "nice to have".
That was my point in mentioning TEST_SUSPEND_SECONDS. We are discussing
increasing the current 5-second limit to avoid these fals
2.6.27-11-generic #1 SMP Fri Feb 27 19:03:38 UTC 2009
I agree that this is not a critical error, but nonethelesse a kernel oops is
not exactly a "nice to have".
** Attachment added: "dmesg on OptiPlex 745"
http://launchpadlibrarian.net/23215692/dmesg.txt
--
WARNING: at /build/buildd/linux-2.
I'm won't have access to that machine again for at least a month, so it'll
be a bit...
Josh
On Feb 27, 2009 9:30 AM, "TJ" wrote:
The only thing of note in the disk reports is that both disks are on the
first PCI SATA controller and, probably more significant, both devices
are Western Digital. A
Sorry, my fault. I was so concentrated on the error path that I forgot
the success path. While being at that I added additional WARN statements
to cause stack traces when entering the function to wait for the link
ready. Hopefully this gives a better understanding from where this is
called. The new
Fridtjof, thank-you.
As already mentioned there is no real problem here.
[ 110.100086] sd 0:0:0:0: [sda] Starting disk
[ 114.984030] ata1: link is slow to respond, please be patient (ready=0)
[ 116.216086] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 116.232336] ata1.00: configure
2.6.27-11-generic #1 SMP Thu Feb 26 18:51:37 UTC 2009 i686 GNU/Linux
** Attachment added: "dmesg on OptiPlex 745"
http://launchpadlibrarian.net/23190714/dmesg.txt
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bug
The only thing of note in the disk reports is that both disks are on the
first PCI SATA controller and, probably more significant, both devices
are Western Digital. Anecdotal reports suggest some WD drives in
particular have this characteristic slow reset.
Please try the Intrepid kernel Stefan has
Attached is report.txt.
Josh
On Wed, Feb 25, 2009 at 4:27 AM, TJ wrote:
> Could both of you attach the details of the disk drive that is slow to
> respond? There are several potential scenarios I'm exploring:
>
> 1. Specific issues with some disk drives. Some drives take a *long* time to
> clear
I have uploaded the kernels to http://people.ubuntu.com/~smb/bug286672/
If the problem was with 2.6.28 as well this likely does not change much
at this point, but it would show whether increasing the other timeout
would help. If you try this kernel, could you please post the resulting
dmesg again?
Both kernels (intrepid and jaunty) show the same behavior, I tested to
2.6.28 on my intrepid box to check if this problem still existed in the
upcoming version.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/28667
Fridtjof, we're looking at this issue in more detail and thinking about
back-porting the Jaunty patch from bug #318978 to test kernels for
Intrepid. However we noticed that in one of your dmesg reports in
comment #16
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/286672/comments/16
It
Forgot to mention my primary concern here!
Although the change in the arbitrary time-out will remove the 'link is
slow to respond' message it won't of itself remove the kernel oops.
The ideal solution would be parallel processing for multiple devices
maybe combined with some intelligence in the k
This looks to be related to a known issue with some combinations of
controller and disk. The warning "link is slow to respond, please be
patient" is issued in drivers/ata/libata-core.c::ata_wait_ready().
It waits for the link status to change from 0xff (no device) for up to
ATA_TMOUT_FF_WAIT. Curr
** Attachment added: "Report from OptiPlex 745"
http://launchpadlibrarian.net/23120798/report.txt
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a memb
Could both of you attach the details of the disk drive that is slow to
respond? There are several potential scenarios I'm exploring:
1. Specific issues with some disk drives. Some drives take a *long* time to
clear the status register after a reset.
2. Issues with the particular chipset/controlle
Output of
sudo lspci -vvnn
attached.
Cheers.
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/23093320/lspci.txt
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug n
** Attachment added: "lspci on a Dell OptiPlex 745"
http://launchpadlibrarian.net/23077255/lspci.txt
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a m
Fridtjof, thank-you. It looks like the same cause as zippidy_josh
reported.
[10692.148085] sd 0:0:0:0: [sda] Starting disk
[10697.032030] ata1: link is slow to respond, please be patient (ready=0)
[10698.992081] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Fridtjof, zippyidy_josh, could
Sure, attached.
** Attachment added: "kern.log after waking up from S3"
http://launchpadlibrarian.net/23059884/kern.log
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification
Fridtjof, could you attach /var/log/kern.log that includes the problem.
I want to see what was going on before and after the warning message.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this
Same thing happens with the current jaunty kernel on my system after
suspend:
[ 412.802413] WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177
suspend_test_finish+0x80/0x90()
[ 412.802415] Component: resume devices
[ 412.802416] Modules linked in: radeon drm binfmt_misc bridge stp
As mentioned above, I no longer experince this issue, but I can say that I
never loaded any firmware that I'm aware of - unless you count ndiswrapper.
Previous models of MacBookPro required firmware for the webcam, but that has
never been needed on the 4,1 I have. So, from my point of view, fir
On Sat, 2009-02-21 at 17:44 +, zippidy_josh wrote:
> Attached a kern.log. I'm running:
> Linux redstone-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC
> 2009 i686 GNU/Linux
I don't *think* your issue is caused by firmware. The tell-tail is
kernel time-stamps that delay for 60 sec
Attached a kern.log. I'm running:
Linux redstone-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009
i686 GNU/Linux
The log doesn't have a 'oops' message, but has:
Feb 20 08:55:53 redstone-desktop kernel: [388341.469605] [ cut here
]
Feb 20 08:55:53 redstone-
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.
** Changed
I've merged a couple more dupes in with this; it was suggested (by
someone else!) that perhaps #331415 is a dupe of this and many of these
all relate to firmware loading - do all of those who have this problem
have stuff that loads firmware?
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power
** Tags added: metabug
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The same warning with 2.6.27-11-generic from intrepid-proposed.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I got it with 2.6.27-7-generic, but since I upgraded to
2.6.27-10-generic it seems to have disappeared.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a me
I get this warning on Intrepid resuming from suspend-to-RAM reproducibly
with the vanilla kernel 2.6.27.8 as well.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because y
Hi Pascal,
The message you are seeing is usually related to suspend/resume.
Primarily that it took longer than expected to bring up your devices.
I'll go ahead an reassign to the kernel team to look at.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) =
also see Bug #298541
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
There is also bug #287453 with the same error but not related to the
package kerneloops.
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Maby MOTU can upload new version of kerneloops 0.12 package to
repository of Ubuntu 8.10 to fix this issue?
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are
I have same problem, after kerneloops install in Ubuntu 8.10
kernel: 2.6.27-7-generic
sudo dpkg -p kerneloops:
Package: kerneloops
Priority: optional
Section: utils
Installed-Size: 164
Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]>
Architecture: i386
Version: 0.10-2ubuntu1
Depends: libc6
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/18747914/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/18747915/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18747916/Dependencies.txt
** A
44 matches
Mail list logo
