[Lenovo ThinkPad S431] Boots up after shutdown

[ramgorur]

I first removed the ~/.Xauthority file it worked fine for the next two-three shutdowns, then it started again. Then I added acpi=noirq switch in the kernel parameter and seemed to be fixed for couple of weeks, then it started again. Moreover, after acpi=noirq, the bluetooth has stopped working. Moreover, I also tried to remove the module ehci_hcd by this command rmmod ehci_hcd but I failed to make this work. details can be found at:
http://www.thinkwiki.org/wiki/How_to_make_ACPI_work#Machine_reboots_after_shutting_down

WORKAROUND: Add in /etc/init.d/halt script :
set_usbs_on () {
    usbcontrolpath="/sys/bus/usb/devices/*/power/control"
    for dev in $usbcontrolpath;
    do
        echo "Setting $dev: " `cat $dev` "to on"
        echo on > $dev
        echo ""
    done
}

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: khaled 2676 F.... pulseaudio
Date: Tue Dec 17 15:03:26 2013
HibernationDevice: RESUME=UUID=febf0c2e-7d67-4ccf-b968-a069097b696a
InstallationDate: Installed on 2013-11-26 (20 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 20AXCTO1WW
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=9746bcf4-275a-4e5a-8ddd-8efec0a455f5 ro
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: HFET30WW (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrHFET30WW(1.07):bd07/10/2013:svnLENOVO:pn20AXCTO1WW:pvrThinkPadS3-S431:rvnLENOVO:rn20AXCTO1WW:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AXCTO1WW
dmi.product.version: ThinkPad S3-S431
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc4-trusty/

[penalvch (penalvch)]

ramgorur, you would want to test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/ as rc4 doesn't have all the necessary files in it.

[ramgorur (code-icted)]

penalvch and jsalisbury, http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/ solved the problem of shutdown-reboot loop.

However, I had tp-smapi-dkms installed on my system, during the installation of rc3 it was throwing an error message regarding DKMS (I do not exactly remember the error message). So, I uninstalled the tp-smapi-dkms and re-isntalled the rc3 kernel. Now the shutdown works as expected.

Moreover, I was using cpufreq-indicator app, after installing rc3 (and unistalling tp-smapi-dkms), the indicator app stopped working (does not show the current cpu-speed, instead it's showing "0.00 GHz").

Shoudl I reinstall tp-smapi-dkms? If yes, will it cause any conflict with rc3?

Should I submit a separate bug-report for this?

Please let me know.

[ramgorur (code-icted)]

penalvch, I have also found this message in dmesg --

microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x19
platform microcode: Direct firmware load failed with error -2
platform microcode: Falling back to user helper

microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x19
platform microcode: Direct firmware load failed with error -2
platform microcode: Falling back to user helper

similar messages for all cpus.

[ramgorur (code-icted)]

hi penalvch and jsalisbury, rc3 kernel did not solve the problem, the shutdown and reboot loop has started again. My machine was working normally for the next couple of shutdowns but it started again from the last night. So, I am modifying the tag as 'kernel-bug-exists-upstream' (according to jsalisbury's suggession)

I will test with http://cdimage.ubuntu.com/daily-live/current/ and let you know what I get.

[ramgorur (code-icted)]

hi, tested with http://cdimage.ubuntu.com/daily-live/current/, the shutdown-reboot loop still persists. Moreover, after the shutdown-reboot loop, keyboard does not work on the login screen, I need to do a suspend and a wakeup then the keyboard responds.

[penalvch (penalvch)]

ramgorur, thank you for performing the requested test. Did this problem not occur in a release prior to Saucy?

[CaptSaltyJack (csjubuntu)]

This bug existed as of 13.04 for sure. 12.10, not sure, but I can't install that on my laptop as it's a production laptop with work on it.

What else can we do to move towards a solution for this bug??

[ramgorur (code-icted)]

Hi, I reverted back to 12.04, according to http://www.ubuntu.com/certification/hardware/201305-13524/, it is mentioned that this version is "certified" for ThinkPad S431. But still that shutdown-reboot loop exists. What is the problem ?

[penalvch (penalvch)]

ramgorur, thank you for testing 12.04.03. For regression testing purposes, could you please test Lucid via http://old-releases.ubuntu.com/releases/lucid/ and advise to the results?

[ramgorur (code-icted)]

Hi, is there any way I can test lucid kernel wihout installing? I have only one machine and there are many personal settings I need to keep.

[penalvch (penalvch)]

ramgorur, sure. If testing the live environment of Lucid wouldn't work out, you could install a Lucid kernel in your current install via https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions and then remove it immediately after.

[ramgorur (code-icted)]

Hi, from this link http://www.pbehnke.com/main/node/11, I have managed to make a shutdown anyway --

For some reason, if the usb controls are set to 'auto', the shutdown-reboot loop starts. The solution was to make them forcefully turn 'on'. I have added a function in the /etc/init.d/halt script --

set_usbs_on () {
    usbcontrolpath="/sys/bus/usb/devices/*/power/control"
    for dev in $usbcontrolpath;
    do
        echo "Setting $dev: " `cat $dev` "to on"
        echo on > $dev
        echo ""
    done
}

and call it before the do_stop function in the 'stop' switch in "case $1". Now the machine shuts down.

[CaptSaltyJack (csjubuntu)]

Christopher:

Assuming I'm on a 64-bit laptop, is this the correct page to grab the Lucid kernel from?

https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/5297703

[Launchpad Janitor (janitor)]

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