I'm a novice at ubuntu. When one clicks on a crash report in the top panel,
one is told that it would be helpful to file a report and when you click on
yes, the computer does everything. This may be why you are still getting
emails, but I am making a wild guess. Another problem has emerged on my
computer and this may be what was causing my problem. I am also receiving
emails. My last 2 lines in my emails have an unsubscribe link, don't yours?
Or did it not work for you? Good luck.
Jim
-----Original Message-----
From: Green72 <email address hidden>
To: <email address hidden>
Date: Thu, 13 Jan 2011 13:11:01 -0000
Subject: Re: [Bug 464552] Re: suspend_test_finish warning triggers too
easily, increase timeout to match mainline times
I have no Idea why I am still getting emails on the matter. This was
fixed ages ago.
If someone could direct me to the method of unsubscription it would be
appreciated.
Cheers,
Stephen.
On 10/01/2011 8:46 AM, Charlie Kravetz wrote:
> As stated in the description above, please file a new bug for your
> issue. This original issue was fixed-released a year ago, and many
> things have changed since that time. You can file a new bug by opening a
> terminal and typing "ubuntu-bug linux" without the quotes. Thank you for
> helping improve Ubuntu.
>
Title:
suspend_test_finish warning triggers too easily, increase timeout to
match mainline times
Status in OEM Priority Project:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Karmic:
Fix Released
Bug description:
Many of these messages are basically cosmetic noise, the average time
to resume is actually 8.2s when older hardware is taken into account.
SATA reconnect alone is allowed to take up to 5s therefore a 5s
timeout is wholy too low for this message. Upstream has upped this
limit to 10s. Using this instance to track the integration of this
upstream change into the lucid and karmic kernels.
If your resume is taking a very long time then please file a new bug.
=== ORIGINAL DESCRIPTION ===
Received message about kernel crash after logging in.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: yossi 2394 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 28
Simple ctrls : 20
Date: Thu Oct 29 23:34:16 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=3210adf9-ff09-4dbb-9d3b-dc431a419062
MachineType: TOSHIBA PORTEGE M200
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic
root=UUID=9ba59e59-1134-4205-baef-87a673f95ab3 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-14-generic N/A
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at
/build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52
suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 10/24/2005
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.80
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias:
dmi:bvnTOSHIBA:bvrVersion1.80:bd10/24/2005:svnTOSHIBA:pnPORTEGEM200:pvrPPM20E-0053C-EN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE M200
dmi.product.version: PPM20E-0053C-EN
dmi.sys.vendor: TOSHIBA
I'm a novice at ubuntu. When one clicks on a crash report in the top panel,
one is told that it would be helpful to file a report and when you click on
yes, the computer does everything. This may be why you are still getting
emails, but I am making a wild guess. Another problem has emerged on my
computer and this may be what was causing my problem. I am also receiving
emails. My last 2 lines in my emails have an unsubscribe link, don't yours?
Or did it not work for you? Good luck.
Jim
-----Original Message-----
From: Green72 <email address hidden>
To: <email address hidden>
Date: Thu, 13 Jan 2011 13:11:01 -0000
Subject: Re: [Bug 464552] Re: suspend_test_finish warning triggers too
easily, increase timeout to match mainline times
I have no Idea why I am still getting emails on the matter. This was
fixed ages ago.
If someone could direct me to the method of unsubscription it would be
appreciated.
Cheers,
Stephen.
On 10/01/2011 8:46 AM, Charlie Kravetz wrote:
> As stated in the description above, please file a new bug for your
> issue. This original issue was fixed-released a year ago, and many
> things have changed since that time. You can file a new bug by opening a
> terminal and typing "ubuntu-bug linux" without the quotes. Thank you for
> helping improve Ubuntu.
>
-- /bugs.launchpad .net/bugs/ 464552
You received this bug notification because you are a direct subscriber
of a duplicate bug (525589).
https:/
Title: test_finish warning triggers too easily, increase timeout to
suspend_
match mainline times
Status in OEM Priority Project:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Karmic:
Fix Released
Bug description:
Many of these messages are basically cosmetic noise, the average time
to resume is actually 8.2s when older hardware is taken into account.
SATA reconnect alone is allowed to take up to 5s therefore a 5s
timeout is wholy too low for this message. Upstream has upped this
limit to 10s. Using this instance to track the integration of this
upstream change into the lucid and karmic kernels.
If your resume is taking a very long time then please file a new bug.
=== ORIGINAL DESCRIPTION ===
Received message about kernel crash after logging in.
ProblemType: KernelOops nUse: snd/controlC0: yossi 2394 F.... pulseaudio Amixer. info: /'Intel 82801DB-ICH4 with AD1981B at irq 11' vice: RESUME= UUID=3210adf9- ff09-4dbb- 9d3b-dc431a4190 62 Modules: nvidia 2.6.31- 14-generic 2.6.31-14.48 /boot/vmlinuz- 2.6.31- 14-generic 9ba59e59- 1134-4205- baef-87a673f95a b3 ro quiet splash gnature: Ubuntu 2.6.31- 14.48-generic eVersions: backports- modules- 2.6.31- 14-generic N/A buildd/ linux-2. 6.31/kernel/ power/suspend_ test.c: 52 test_finish+ 0x80/0x90( ) version: Version A0 asset.tag: 0000000000 vendor: TOSHIBA version: Version 1.0 bvrVersion1. 80:bd10/ 24/2005: svnTOSHIBA: pnPORTEGEM200: pvrPPM20E- 0053C-EN: rvnTOSHIBA: rnPortablePC: rvrVersionA0: cvnTOSHIBA: ct10:cvrVersion 1.0: version: PPM20E-0053C-EN
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: i386
AudioDevicesI
USER PID ACCESS COMMAND
/dev/
CRDA: Error: [Errno 2] No such file or directory
Card0.
Card hw:0 'I82801DBICH4'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 28
Simple ctrls : 20
Date: Thu Oct 29 23:34:16 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDe
MachineType: TOSHIBA PORTEGE M200
NonfreeKernel
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
root=UUID=
ProcVersionSi
RelatedPackag
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at
/build/
suspend_
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 10/24/2005
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.80
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.
dmi.chassis.
dmi.modalias:
dmi:bvnTOSHIBA:
dmi.product.name: PORTEGE M200
dmi.product.
dmi.sys.vendor: TOSHIBA
To unsubscribe from this bug, go to: /bugs.launchpad .net/oem- priority/ +bug/464552/ +subscribe
https:/