[Lenovo ThinkPad S431 20AX] boots up after shutdown, twice

[CaptSaltyJack]

Running Ubuntu 13.04 on a ThinkPad S431. When shutting down Ubuntu, the machine turns off normally, but then turns back on again by itself. I have to hit the power button to turn it off, but then it turns on once more. Hitting the power button a second time finally turns the machine off.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-30-generic 3.8.0-30.44
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: samh 1801 F.... pulseaudio
Date: Wed Sep 25 10:23:24 2013
HibernationDevice: RESUME=UUID=ce2190d2-c875-4c5d-b2e8-1b1473c7c4db
InstallationDate: Installed on 2013-09-15 (9 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO 20AXCTO1WW
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash "acpi_osi=!Windows 2012" acpi=force
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-30-generic N/A
 linux-backports-modules-3.8.0-30-generic N/A
 linux-firmware 1.106
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: Win8 STD DPK TPG
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:rvrWin8STDDPKTPG: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.12 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.12-rc2-saucy/

[CaptSaltyJack (csjubuntu)]

Replicated problem under 3.12.

[CaptSaltyJack (csjubuntu)]

Any updates on this??

[CaptSaltyJack (csjubuntu)]

Still an issue in mainline kernel 3.12.0-031200-generic #201311031935

[penalvch (penalvch)]

CaptSaltyJack, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/ and advise to the results?

[CaptSaltyJack (csjubuntu)]

Bug still exists in that kernel as well.

[penalvch (penalvch)]

CaptSaltyJack, did this problem not occur in a release prior to Raring?

[ramgorur (code-icted)]

Hi, I am also having the same problem, 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.

[CaptSaltyJack (csjubuntu)]

Christopher: not sure, I only had the laptop as of raring.

Is there anything else we can do to help test/diagnose? This is a very annoying issue and I'd love to see it resolved by 14.04.

[penalvch (penalvch)]

ramgorur, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

[penalvch (penalvch)]

CaptSaltyJack, for regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ ?

[penalvch (penalvch)]

CaptSaltyJack, thank you for your comment. Regarding it https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261886/comments/17 :
>"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 "

That would be fine for a Lucid kernel test.

Despite this, please stop commenting on bug 1261886 as you are not the original reporter of it, and at this point, it's not considered a duplicate of yours, or vice versa.

Thank you for your understanding.

[CaptSaltyJack (csjubuntu)]

How do we know these two bugs are not exactly the same? It's the same laptop and same symptoms, no?

I'll test the kernel referenced above ASAP and report back here.

[Launchpad Janitor (janitor)]

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