Ubuntu
linux package

[IBM 1834RTG] suspend/resume failure

Bug #488673 reported by lelamal on 2009-11-26

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

After switching my Thinkpad R50e on this morning, it froze exactly at the login window. When I tried to move the mouse, I noticed the pointer wasn't anywhere on the screen. The half-moon-shaped led signalling sleep mode was flashing intermittently, and nothing was responding. The scenario was familiar, and after I was ultimately forced to cold-boot the system, Apport was waiting in the panel to confirm this: please see the attachment. I got the same window before reporting the following bug, a couple of days ago: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/485108. Back then, I surely suspended my laptop, but this wasn't the case today, though the freeze was interpreted as a "suspend/resume failure" (in fact, the bug was named slightly differently). Moreover, both bugs have been reported by Apport as being caused by a SERIOUS (!) Kernel problem. I don't think this leaves any doubt about the connection between this and Bug #485108.

Also, as was asked in comment #6 of Bug #485108, the freezes described seem to point to Bug #479296, here https://bugs.launchpad.net/ubuntu/+bug/479296. Can anyone confirm the three bugs have a common origin, please?

Can we please finally have an equally SERIOUS (!) answer on this malfunctions? Many thanks!

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: lelamal 1633 F.... pulseaudio
/dev/snd/pcmC0D0p: lelamal 1633 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 5'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 28
   Simple ctrls : 20
Date: Thu Nov 26 10:37:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=f9146e7a-38fe-4080-ab7d-4f0edf647170
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
MachineType: IBM 1834RTG
Package: linux-image-2.6.31-15-generic 2.6.31-15.50
PccardctlIdent:
Socket 0:
   no product info available
PccardctlStatus:
Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-15-generic root=UUID=48cb8a41-2954-41e2-baaa-990c31d64638 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-15-generic N/A
linux-firmware 1.25
RfKill:

SourcePackage: linux
Tags: resume suspend
Title: [IBM 1834RTG] suspend/resume failure
Uname: Linux 2.6.31-15-generic i686
UserGroups:

dmi.bios.date: 12/08/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1WET90WW (2.10 )
dmi.board.name: 1834RTG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1WET90WW(2.10):bd12/08/2006:svnIBM:pn1834RTG:pvrThinkPadR50e:rvnIBM:rn1834RTG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 1834RTG
dmi.product.version: ThinkPad R50e
dmi.sys.vendor: IBM

Tags:

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-11-26:

Kernel problem screenshot Edit (98.1 KiB, image/png)
AlsaDevices.txt Edit (589 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (323 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (622 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (43.3 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (4.2 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.txt Edit (664 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.regs.txt Edit (767 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (635 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (11.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (645 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (880 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (462 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (6.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (707 bytes, text/plain; charset="utf-8")
SleepLog.txt Edit (27.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (97.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (214.6 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (147.2 KiB, text/plain; charset="utf-8")

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-11-26:

Sorry, I wasn't clear enough. The attachment I mention in my report is difficult to identify among all the others. It's a screenshot, and is called: Kernel problem screenshot.

tags:

added: kernel-karmic

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2009-12-07:

Further to my previous comment, Bug #493505 is joining the list of related bugs. This is getting frustrating. Since the kernel problem reported is serious, can anyone change at least the importance of the bug to medium or higher, please?

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-04-23:

Hi lelamal,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 488673

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags:	added: kernel-suspend
tags:	added: needs-kernel-logs
tags:	added: needs-upstream-testing
tags:	added: kj-triage
Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

lelamal (lelamal-deactivatedaccount) wrote on 2010-04-27: Re: [Bug 488673] Re: [IBM 1834RTG] suspend/resume failure

Download full text (4.4 KiB)

On Saturday 24 April 2010 00:49:32 you wrote:
> Hi lelamal,
>
> This bug was reported a while ago and there hasn't been any activity in it
> recently.
Hi, this is basically because, while bugs kept adding to the original bug, the
problem was completely ignored up to the next important release, probably
hoping that would solve the issue (as it happens with many unsolved bugs,
unfortunately), although a serious kernel problem is involved. As pointed out,
however, using the machine in a working environment, I can't afford losing data
and wasting time after a broken release which contains several critical
regressions. As a result, I switched to another machine, and another flavor
(kubuntu), which finally guaranteed me unstopped, reliable work-flow. In
addition, many users must have felt the same, and resorted to the same, or
other solutions, and this, coupled with lack of serious response from
developers in a timely fashion, would finally account for the lack of activity
in this bug, recently.

> We were wondering if this is still an issue? Can you try with
> the latest development release of Ubuntu? ISO CD images are available
> from http://cdimage.ubuntu.com/releases/ .

I am sorry, but both machines are now on kubuntu (currently, lucid), so I
cannot try that now. This bug may even be set to "incomplete", but since it
was filed under karmic, I can swear it was still very active till the point I
had to switch machine and desktop manager. So, no one actively fixed it.
Besides, I do not see a clear point in testing (now!) a development release
when all I needed was back then the OS to work in a stable environment and
with a stable release. This is a rather convoluted way to fix things, and to
those who insist that ubuntu is different from Windows in that you can actually
report bugs and have them fixed before a new release comes out I would like to
point out that it's not entirely true, and I could verify that numerous times.

> If it remains an issue, could you run the following command from a Terminal
> (Applications->Accessories->Terminal). It will automatically gather and
> attach updated debug information to this report.
>
> apport-collect -p linux 488673

Sorry, I could not, for I am not running that flavor (and will not anytime
soon) and machine anymore.

> Also, if you could test the latest upstream kernel available that would be
> great. It will allow additional upstream developers to examine the issue.
> Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've
> tested the upstream kernel, please remove the 'needs-upstream-testing'
> tag. This can be done by clicking on the yellow pencil icon next to the
> tag located at the bottom of the bug description and deleting the
> 'needs-upstream-testing' text. Please let us know your results.

For the same reasons already discussed, unfortunately I cannot test my
machines with the latest upstream kernel available, because I need a stable
working environment, and all my contributions to the ubuntu project may be
limited to reporting bugs and to a few translations.

Also, note that, as explained in comment #35 at
https://bugs.launchpad.net/ubuntu/+sou...

On Saturday 24 April 2010 00:49:32 you wrote:
> Hi lelamal,
> 
> This bug was reported a while ago and there hasn't been any activity in it
> recently.
Hi, this is basically because, while bugs kept adding to the original bug, the 
problem was completely ignored up to the next important release, probably 
hoping that would solve the issue (as it happens with many unsolved bugs, 
unfortunately), although a serious kernel problem is involved. As pointed out, 
however, using the machine in a working environment, I can't afford losing data 
and wasting time after a broken release which contains several critical 
regressions. As a result, I switched to another machine, and another flavor 
(kubuntu), which finally guaranteed me unstopped, reliable work-flow. In 
addition, many users must have felt the same, and resorted to the same, or 
other solutions, and this, coupled with lack of serious response from 
developers in a timely fashion, would finally account for the lack of activity 
in this bug, recently.

> We were wondering if this is still an issue? Can you try with
> the latest development release of Ubuntu?  ISO CD images are available
> from http://cdimage.ubuntu.com/releases/ .

I am sorry, but both machines are now on kubuntu (currently, lucid), so I 
cannot try that now. This bug may even be set to "incomplete", but since it 
was filed under karmic, I can swear it was still very active till the point I 
had to switch machine and desktop manager. So, no one actively fixed it. 
Besides, I do not see a clear point in testing (now!) a development release 
when all I needed was back then the OS to work in a stable environment and 
with a stable release. This is a rather convoluted way to fix things, and to 
those who insist that ubuntu is different from Windows in that you can actually 
report bugs and have them fixed before a new release comes out I would like to 
point out that it's not entirely true, and I could verify that numerous times.

> If it remains an issue, could you run the following command from a Terminal
> (Applications->Accessories->Terminal).  It will automatically gather and
> attach updated debug information to this report.
> 
> apport-collect -p linux 488673

Sorry, I could not, for I am not running that flavor (and will not anytime 
soon) and machine anymore.
 
> Also, if you could test the latest upstream kernel available that would be
> great.  It will allow additional upstream developers to examine the issue.
>  Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .  Once you've
> tested the upstream kernel, please remove the 'needs-upstream-testing'
> tag.  This can be done by clicking on the yellow pencil icon next to the
> tag located at the bottom of the bug description and deleting the
> 'needs-upstream-testing' text.  Please let us know your results.

For the same reasons already discussed, unfortunately I cannot test my 
machines with the latest upstream kernel available, because I need a stable 
working environment, and all my contributions to the ubuntu project may be 
limited to reporting bugs and to a few translations.

Also, note that, as explained in comment #35 at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/485108, I had already 
done everything I needed to, by mentioning an upstream bug url in my comment 
and linking it to the bug. I also continued to follow the upstream bug report 
as I was told to, but there was not much activity either, I must say, so there 
was nothing you could pull into Ubuntu to take a look at it. So, I was pretty 
much waiting for developers to look into the issue, and update you on that. 
Lack of activity on both sides left the bug to stall, and me to pursue 
stability elsewhere.

Just a final, personal thought: chasing change "just for the hell of it", 
trying "to be different" at all costs at every new release, and releasing twice 
a year an unstable OS may not the best way forward, if Canonical is seriously 
considering to fix Bug 1. To me, is more important to have old bugs fixed and no 
regressions when I upgrade to new versions, rather than having a shiny new 
piece of OS half-baked twice a year just in time for its schedule just because 
it had to be released regardless. You can keep pushing dirt under the carpet, 
but sooner or later someone has to clean underneath.

Thanks in advance.
    [This is an automated message. Apologies if it has reached you 
inappropriately; please just reply to this message indicating so.]

Revision history for this message

Jeremy Foshee (jeremyfoshee) wrote on 2010-08-12:

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags:	added: kj-expired
Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

[IBM 1834RTG] suspend/resume failure

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package