Hi, sorry, but I don't use that machine anymore. Riccardo
On 29 September 2013 00:39, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Riccardo Poli, 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? If so, could you please test for this with the latest development > release of Ubuntu? ISO images are available from > http://cdimage.ubuntu.com/daily-live/current/ . > > If it remains an issue, could you please run the following command in > the development release from a Terminal > (Applications->Accessories->Terminal), as it will automatically gather > and attach updated debug information to this report: > > apport-collect -p linux <replace-with-bug-number> > > Also, could you please test the latest upstream kernel available following > https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional > upstream developers to examine the issue. Please do not test the daily > kernel folder, but the one all the way at the bottom. Once you've tested > the upstream kernel, please comment on which kernel version specifically > you tested. If this bug is fixed in the mainline kernel, please add the > following tags: > kernel-fixed-upstream > kernel-fixed-upstream-VERSION-NUMBER > > where VERSION-NUMBER is the version number of the kernel you tested. For > example: > kernel-fixed-upstream-v3.12-rc2 > > This can be done by clicking on the yellow circle with a black pencil icon > next to the word Tags located at the bottom of the bug description. As > well, please remove the tag: > needs-upstream-testing > > If the mainline kernel does not fix this bug, please add the following > tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-VERSION-NUMBER > > As well, please remove the tag: > needs-upstream-testing > > Once testing of the upstream kernel is complete, please mark this bug's > Status as Confirmed. Please let us know your results. Thank you for your > understanding. > > ** Changed in: linux (Ubuntu) > Status: Triaged => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/587136 > > Title: > 2nd Resume from Suspend results in reboot on Toshiba Satellite U400. > Fixed in 2.6.34 Mainline. > > Status in “linux” package in Ubuntu: > Incomplete > > Bug description: > 2.6.32-22: > Regardless of suspend method (lid-close, selecting "Suspend" in shutdown > menu, "pm-suspend" in a TTY), the laptop suspends correctly, resumes > correctly, suspends correctly a second time, and then once the second > resume is initiated, the system reboots. > > This issue is tested and confirmed as fixed in the 2.6.34 mainline > (2.6.34-020634-generic). > > ProblemType: Bug > DistroRelease: Ubuntu 10.04 > Package: xorg 1:7.5+5ubuntu1 > ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 > Uname: Linux 2.6.32-22-generic x86_64 > Architecture: amd64 > Date: Sat May 29 07:11:38 2010 > DkmsStatus: > vboxnetflt, 3.2.0, 2.6.32-22-generic, x86_64: installed > vboxnetadp, 3.2.0, 2.6.32-22-generic, x86_64: installed > vboxdrv, 3.2.0, 2.6.32-22-generic, x86_64: installed > MachineType: TOSHIBA Satellite U400 > ProcCmdLine: nomodeset pci=use_crs > root=UUID=4f3c9dfc-c762-423c-b1cd-81110c0b011d ro quiet splash > ProcEnviron: > PATH=(custom, user) > LANG=en_GB.utf8 > SHELL=/bin/bash > SourcePackage: xorg > Symptom: display > dmi.bios.date: 02/12/2009 > dmi.bios.vendor: TOSHIBA > dmi.bios.version: V3.30 > dmi.board.name: Satellite U400 > dmi.board.vendor: TOSHIBA > dmi.board.version: Not Applicable > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: TOSHIBA > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnTOSHIBA:bvrV3.30:bd02/12/2009:svnTOSHIBA:pnSatelliteU400:pvrPSU44E-00T017EN:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: > dmi.product.name: Satellite U400 > dmi.product.version: PSU44E-00T017EN > dmi.sys.vendor: TOSHIBA > system: > distro: Ubuntu > codename: lucid > architecture: x86_64 > kernel: 2.6.32-22-generic > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/587136/+subscriptions > -- -- ---------------------------------------------------------------------- Prof Riccardo Poli E-mail: rp...@essex.ac.uk School of Computer Science and Electronic Engineering University of Essex Telephone: (01206) 872338 Wivenhoe Park Facsimile: (01206) 872788 Colchester CO4 3SQ, UK http://csee.essex.ac.uk/staff/rpoli/ ---------------------------------------------------------------------- A Field Guide to Genetic Programming http://www.gp-field-guide.org.uk/ ---------------------------------------------------------------------- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/587136 Title: 2nd Resume from Suspend results in reboot on Toshiba Satellite U400. Fixed in 2.6.34 Mainline. Status in “linux” package in Ubuntu: Incomplete Bug description: 2.6.32-22: Regardless of suspend method (lid-close, selecting "Suspend" in shutdown menu, "pm-suspend" in a TTY), the laptop suspends correctly, resumes correctly, suspends correctly a second time, and then once the second resume is initiated, the system reboots. This issue is tested and confirmed as fixed in the 2.6.34 mainline (2.6.34-020634-generic). ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Sat May 29 07:11:38 2010 DkmsStatus: vboxnetflt, 3.2.0, 2.6.32-22-generic, x86_64: installed vboxnetadp, 3.2.0, 2.6.32-22-generic, x86_64: installed vboxdrv, 3.2.0, 2.6.32-22-generic, x86_64: installed MachineType: TOSHIBA Satellite U400 ProcCmdLine: nomodeset pci=use_crs root=UUID=4f3c9dfc-c762-423c-b1cd-81110c0b011d ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 02/12/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V3.30 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV3.30:bd02/12/2009:svnTOSHIBA:pnSatelliteU400:pvrPSU44E-00T017EN:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU44E-00T017EN dmi.sys.vendor: TOSHIBA system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/587136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp