[Panasonic CF-29PTQGZBM] suspend/resume failure

[Wzrd1]

Error popped up when logging in.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-18-generic 3.13.0-18.38
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lightdm 5899 F.... pulseaudio
                      steve 28949 F.... pulseaudio
Date: Fri Mar 21 15:54:47 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=4dd663f1-7dc5-4baf-90f8-22368f79c0f4
InstallationDate: Installed on 2014-03-12 (9 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140121.1)
InterpreterPath: /usr/bin/python3.4
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-29PTQGZBM
PccardctlStatus:
 Socket 0:
   5.0V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "serial_cs"
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=4f2c4fa6-3528-4bbe-b3a4-b9f8f185696d ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-18-generic N/A
 linux-backports-modules-3.13.0-18-generic N/A
 linux-firmware 1.126
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [Matsushita Electric Industrial Co.,Ltd. hostname] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/03/2006
dmi.bios.vendor: Phoenix Technologies K.K.
dmi.bios.version: V5.00L14
dmi.board.name: CF29-5
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: UNDEFINED\n
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: dmi:bvnPhoenixTechnologiesK.K.:bvrV5.00L14:bd08/03/2006:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-29PTQGZBM:pvr005:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF29-5:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-29PTQGZBM
dmi.product.version: 005
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Wzrd1 (stephen-p-villano)]

Panasonic CF-29PTQGZBM.
It's an old Panasonic Toughbook.

It currently is running / on an SSD, /home and /tmp on a HD. Was going
to put /var there, to cut down on writes, but had issues and discarded
the notion for a while.
Haven't had to do any tuning with the SSD, it's running nicely "out of
the box".
The only non-vanilla I have on the box is I'm using fingerprint for
authentication.

On 4/26/14, 10:29 AM, Christopher M. Penalver wrote:
> Wzrd1, could you please provide the full computer model as noted on the
> sticker?
>

[penalvch (penalvch)]

Wzrd1, did you happen to log in after suspending the computer and it ran out of battery, or pulling the power when the battery was out?

[Wzrd1 (stephen-p-villano)]

On 4/26/14, 5:33 PM, Christopher M. Penalver wrote:
> Wzrd1, did you happen to log in after suspending the computer and it ran
> out of battery, or pulling the power when the battery was out?
>
> ** Summary changed:
>
> - [Matsushita Electric Industrial Co.,Ltd. hostname] suspend/resume failure
> + [Panasonic CF-29PTQGZBM] suspend/resume failure
>
> ** Tags added: latest-bios-v5.00l14
>
Jeeze, It's been a while. Can't recall. I can try to reproduce the
problem if you want.
From what I recall, it had errored going into suspend mode. I think I
had to do a hard restart, but it has been a while.

From a bit OT side, what do you think it would take to get hibernate to
work? As I recall, this model wasn't supported for hibernation.

[penalvch (penalvch)]

Wzrd1, regarding hibernate, this is a different problem, necessitating a separate report. Please feel free to enable and test hibernation following https://help.ubuntu.com/community/PowerManagement/Hibernate#Hibernate_Disabled_by_Default. If found to not work, please feel free to file a new report via a terminal:
ubuntu-bug linux

Regarding this report, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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-3.15-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.

[Wzrd1 (stephen-p-villano)]

On 4/26/14, 6:44 PM, Christopher M. Penalver wrote:
> Wzrd1, regarding hibernate, this is a different problem, necessitating a separate report. Please feel free to enable and test hibernation following https://help.ubuntu.com/community/PowerManagement/Hibernate#Hibernate_Disabled_by_Default. If found to not work, please feel free to file a new report via a terminal:
> ubuntu-bug linux
>
> Regarding this report, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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-3.15-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.
>
Sorry for the delay, RL got in the way.
Any recommendation on upstream version? Stay with the 3.13.x tree or go
with the 3.14.x tree for initial testing or even with the 3.15.x tree?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]