[TOSHIBA Satellite L300] suspend/resume failure

Bug #417534 reported by Kev77droid
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

When i suspend my toshiba l300 it will resume ok the first time, but when i suspend again after use i get a blank screen! Wierd.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kev 3104 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x94200000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,1179ff64,00100003 HDA:11c11040,11790001,00100200'
   Controls : 13
   Simple ctrls : 10
Date: Sun Aug 23 01:13:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=e451efa1-1bb3-4394-af76-855515536258
InterpreterPath: /usr/bin/python2.6
MachineType: TOSHIBA Satellite L300
Package: linux-image-2.6.31-6-generic 2.6.31-6.26
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: root=UUID=500c5f28-403a-4660-9267-677ed7911571 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-6.26-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-6-generic N/A
 linux-firmware 1.16
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: resume suspend
Title: [TOSHIBA Satellite L300] suspend/resume failure
Uname: Linux 2.6.31-6-generic i686
UserGroups:

dmi.bios.date: 05/28/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.40:bd05/28/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-02D00SEN:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Satellite L300
dmi.product.version: PSLB0E-02D00SEN
dmi.sys.vendor: TOSHIBA

Revision history for this message
Kev77droid (kev77) wrote :
Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

Hi all,
Please can you try with last kernel version, which is located on http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/
Thanks in advance.

tags: added: karmic
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Yuri (oxygenych) wrote :

Have the same problem with Ubuntu 10.04 beta 2, with 2.6.32 krenel

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: lucid
Revision history for this message
Kev77droid (kev77) wrote :

Yes sorry about the delay, tried kernel version located at http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/
 bug still exists, i no longer have toshiba l300 so can not confirm if bug is still present in lucid.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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