[Samsung NP700Z5C-S03CA] Power button not working using non-default kernel parameters, when booted in CSM mode; works fine in EFI mode

[Val]

When my Samsung NP700Z5C is booted in the CSM (BIOS compatibility) mode, pressing the power button has no effect. There is no scancode per "/lib/udev/keymap". The problem is quite annoying because if the laptop is accidentally sent to sleep or hibernate mode, there is no return back from sleep/hibernate. Pressing the power button has no effect. The laptop can be turned off by long-pressing the power button, with the collateral loss of all unsaved data.

WORKAROUND: Remove non-default kernel parameters (ex. acpi=noirq).

WORKAROUND: Boot in UEFI mode.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-23-generic 3.5.0-23.35
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: val 2259 F.... pulseaudio
Date: Sun Feb 3 22:56:12 2013
HibernationDevice: RESUME=UUID=96bef07a-40d3-4067-8c9a-211548fc7184
InstallationDate: Installed on 2013-01-17 (17 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3C/700Z5C
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=ef3ff468-e0b5-43db-ac4c-447c73805778 ro quiet splash acpi=noirq vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-23-generic N/A
 linux-backports-modules-3.5.0-23-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P04ABJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP700Z5C-S03CA
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04ABJ:bd09/19/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3C/700Z5C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP700Z5C-S03CA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 700Z3C/700Z5C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[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.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.8-rc6-raring/

[Val (vk1266)]

Joseph, it looks like as of today I can only test on mainline kernel v3.5.7.4-quantal. Versions v.3.6 and higher likely do not contain the bugfix for LP: #1040557, which is known to brick Samsung laptops like mine.

I received a tip that a new Quantal kernel will be coming to -proposed next week. I will keep checking and I can test the bug on that new Quantal kernel when it comes out. In the interim, is there anything I can do to test this bug further without the risk of tickling the bug in #1040557?

[Joseph Salisbury (jsalisbury)]

@Val,

I read your chat on IRC. I agree, it's best to hold off on testing any kernels until the official patch that fixes bug 1040557 lands in all the stable releases.

[Val (vk1266)]

Allright, the 3.8 mainline kernels for Quantal are probably not going to appear in the Mainline Builds ppa any time soon. I took some time today to try and install Raring AMD64 from daily builds on my Samsung NP700Z5C and see if the problem with the power button is still there.

It is important to mention that all of the following concerns booting into the CSM mode (the BIOS compatibility mode).

The results are quite surprising to me. Once I booted into the Raring LiveCD (13.04 kernel version 3.8.0-10-generic), I noticed that the power button worked just fine. I proceeded with the installation that completed without a hitch and booted into the newly installed 13.04. Again, no problem with the power button.

Then I booted into the Quantal Live CD (12.10 kernel version 3.5.0-17-generic). The power button worked just fine! But when I rebooted into the Quantal installation (12.10 kernel version 3.5.0-25-generic), the power button stopped working. According to /lib/udev/keymap, it sends no scancodes.

Bottom line:
Quantal LiveCD: power button works
Quantal installation: power button does not work
Raring LiveCD: power button works
Raring installation: power button works

Why can this be happening? What configs should I compare between LiveCD and the installation? What should I look for in dmesg?

[Joseph Salisbury (jsalisbury)]

It would be helpful if you could gather the following from both environments(Installed system and LiveCD):

1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log

[Joseph Salisbury (jsalisbury)]

And actually, you will want to name the .log output files something different for each of the environments.

[Joseph Salisbury (jsalisbury)]

It would also help to get the following from both environments:
cat /proc/cmdline

[Val (vk1266)]

Joseph, I have just posted a tgz with the requested output.

It looks like I should try booting the installed version without acpi=noirq. Right?

[Val (vk1266)]

Allright. Once acpi=noirq is removed from the command line, power button starting working just fine.

@Joseph: do you want me to post log files with "acpi=noirq" removed?

The still unexplained phenomenon is: in the UEFI mode, power button works fine regardless of whether acpi=noirq is present or not. In the CSM mode, power button does not work when acpi=noirq is specified.

[Val (vk1266)]

Christopher: my Samsung notebook model is NP700Z5C-S03CA.

[penalvch (penalvch)]

Val, thank you for providing the requested information. Would you please comment to why you were using the kernel parameter acpi=noirq?

[Val (vk1266)]

Christopher,

I did not change any kernel parameters during Ubuntu 12.10 installation. My installation process is described in detail in comment #114 to LP: #1040557. For convenience, here is a direct link:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557/comments/114

I thought that "acpi=noirq" *was* the default parameter. At the very least, I did not need to change it during installation and I do not recall changing it at any point until I have come across this bug.