[Toshiba Satellite C650-16R] Touchpad not working after restart

[florin]

I have installed Oneric recently and it's the second time I get this bug. I cannot see any action that could cause it, but just after restart the touchpad (padding + buttons) does not work at all. I am using only the keyboard to submit this bug report.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: florin 1499 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6400000 irq 42'
   Mixer name : 'Conexant CX20585'
   Components : 'HDA:14f15069,1179fde2,00100302'
   Controls : 8
   Simple ctrls : 5
Date: Tue Oct 18 02:53:24 2011
HibernationDevice: RESUME=UUID=2077879b-4c01-4c71-b8d0-3d278020eb32
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 003: ID 10f1:1a2a Importek
MachineType: TOSHIBA Satellite C650
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=35a99d92-7566-4c55-88d1-a4fcf7717737 ro quiet splash pcie_aspm=force vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.90
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.90:bd03/16/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC14E-00400MG5:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite C650
dmi.product.version: PSC14E-00400MG5
dmi.sys.vendor: TOSHIBA

[florin (florin-arjocu)]

After I've logged out, it worked again.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. 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.

[florin (florin-arjocu)]

Sorry for late reply, I'm also traveling. Please reply to each question, to make things clear.

As I'm not very used to this language, I have to clarify your requests:
1. daily means one like this (different date depending on the day)?
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2011-10-21-oneiric/

2. The current RC is this one?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc10-oneiric/

3. Now I have pcie_aspm=force in grub config and
in /etc/rc.local there is this line
echo powersave > /sys/module/pcie_aspm/parameters/policy
Should I keep these settings for testing?

Thanks!

[florin (florin-arjocu)]

I've been using the last RC I found there and the problem with the touchpad did not appear again. I would get to the conclusion that the problem was in the default kernel shipped with Oneric Ocelot.

florin@florin-Satellite-C650:~$ uname -a
Linux florin-Satellite-C650 3.1.0-030100rc10-generic #201110200610 SMP Thu Oct 20 10:11:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

[florin (florin-arjocu)]

I've been using 3.1rc10 in the last few days and the bug occured. I'll also use the daily build for a while to see the differences.

[florin (florin-arjocu)]

I reinstalled the system due to some hardware (hdd) issues and I will install the latest daily kernel and see if the bug is still there as 3.1rc10 still "carried" the touchpad bug.

[penalvch (penalvch)]

florin, 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 (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-v3.13-rc1

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.

[florin (florin-arjocu)]

I have tested the latest upstream kernel 2-3 weeks ago for a different bug, and this bug was still present. Yesterday I uninstalled the kernel as it was worse than the standard one in Ubuntu 13.10 (with all updates), so I cannot tell which version exactly was, it was 3.12.*

[penalvch (penalvch)]

florin, an update is available for your BIOS (2.00). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[florin (florin-arjocu)]

I can confirm that in my case it is no longer a problem, I found the real culprit: an imperfect hardware contact.

[penalvch (penalvch)]

florin, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/876976/comments/11 regarding this being due to a hardware problem. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.