[HP 625 Notebook PC] MagicSysRq -K doesn't respond

[Sam_]

REISUB works fine but Alt-SysRq-K or Alt+Print+K doesn't respond, iirc it did in Oneiric cycle and not sure which one of latest kernel made it vanish.

kern.log says:
Jan 6 00:23:08 kernel: [ 194.775093] SysRq : Changing Loglevel
Jan 6 00:23:08 kernel: [ 194.775106] Loglevel set to 2
Jan 6 00:23:16 kernel: [ 202.589864] SysRq : Changing Loglevel
Jan 6 00:23:16 kernel: [ 202.589877] Loglevel set to 2

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-7-generic 3.2.0-7.13
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: zootie 1657 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xd4400000 irq 16'
   Mixer name : 'IDT 92HD88B1'
   Components : 'HDA:111d7667,103c1475,00100105'
   Controls : 14
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd4310000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Jan 6 00:38:23 2012
HibernationDevice: RESUME=UUID=b7df2b2e-608b-4290-b3b2-3b4ced196417
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
MachineType: Hewlett-Packard HP 625
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-7-generic root=UUID=bab9ac13-843a-4289-a0f2-b254b2dda7d3 ro
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-7-generic N/A
 linux-backports-modules-3.2.0-7-generic N/A
 linux-firmware 1.67
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DVA Ver. F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1475
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 72.0E
dmi.chassis.asset.tag: CNU1080QP1
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68DVAVer.F.06:bd12/07/2010:svnHewlett-Packard:pnHP625:pvr:rvnHewlett-Packard:rn1475:rvrKBCVersion72.0E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP 625
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Sam_ (and-sam)]

Still exists, attach kern.log

[Sam_ (and-sam)]

When killing X by alt+print+K current Oneiric kernel 3.0.0.-14 on desktop-pc says:
Jan 9 00:15:33 kernel: [128562.830869] SysRq : SAK
Jan 9 00:15:33 kernel: [128562.830907] SAK: killed process 1067 (Xorg): task_session(p)==tty->session
Jan 9 00:15:33 kernel: [128562.830986] SAK: killed process 1067 (Xorg): task_session(p)==tty->session
Jan 9 00:15:33 kernel: [128562.831001] SAK: killed process 1244 (console-kit-dae): fd#10 opened to the tty
--- multiple lines follow of processes killed.

[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 . If possible, please test the latest v3.2 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

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'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[Sam_ (and-sam)]

Tested v3.2-rc7-precise from there and hope that was the right one.
http://kernel.ubuntu.com/~kernel-ppa/mainline/

It boots into text mode only, it displayed dmesg lines 924 to 953, (attached complete dmesg).
Then I did:
~$ sudo restart lightdm

which let me login, although obviously in failsafe mode. I had gnome-system-log open to view dmesg, copied it's content to gedit, on attempt to save the file completely UI freeze. Alt+print -K did nothing, but REISUB worked.

On second boot attempt I've wanted to proceed again via lightdm as above, although mouse and graphic was stuck but it recognized key inputs, after login it only displayed a background, no desktop widgets displayed. Again Alt+print -K did nothing. I've switched to tty in order to copy dmesg, and tried to reboot with 'sudo reboot' which did nothing, so again entered REISUB and booted into standard kernel 3.2.0-8 again.

[Sam_ (and-sam)]

Before the bot asks, just updated to 3.2.0-8.15 and kern.log still says:
Jan 11 22:05:50 kernel: [ 124.814913] SysRq : Changing Loglevel
Jan 11 22:05:50 kernel: [ 124.814925] Loglevel set to 2

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Sam_ (and-sam)]

FWIW I've installed daily current. The boot was a little choppy into failsafe ui, but Sysrq -K still didn't respond.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Sam_ (and-sam)]

Tested mainline v3.3-rc1-precise, it still sets the loglevel 2.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Sam_ (and-sam)]

Please note, I'm aware how to set up MagicSysRq to be available on all keys, but I didn't change anything manually and -K is available with Oneiric kernel(s). If -K was dropped for a certain reason I couldn't find a hint for it in changelog. Maybe there was a decision made to leave it up to userland to make -K manually available again, if yes, let me know. Thanks.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Sam_ (and-sam)]

3.2.0-13.22 didn't land yet, awaiting 3.2.0-14.23.

[Sam_ (and-sam)]

Still sets loglevel 2.
3.2.0-14-generic #23-Ubuntu SMP Fri Feb 3 23:17:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Sam_ (and-sam)]

Lets hold on for a sec. I've installed Precise on my desktop-pc where -K worked and it still works with 3.2.0-14.23.
The report was made with the laptop, there it still sets loglevel 2, any idea or is it up to userland to set SysRq to allow all keys on laptop?

[Sam_ (and-sam)]

On both, pc and laptop terminal output is the same.
cat /proc/sys/kernel/syrq
1

Again, REISUB works but -K doesn't as expected on laptop.
Both pc and laptop run the same kernel.

[Sam_ (and-sam)]

No luck with 3.2.0-15. When sysrq sets loglevel 2 on laptop which uses fn-keys, then why is REISUB working and -K not?

[chris (ccpp)]

I have the same problem and my guess is: The problem is the "Fn" Key which enables "Num Lock" which turns "k" into "2".
So it's a hardware issue. I think there is no fix, unless there is an option in BIOS.
Important note: if this is the case, you never executed REISUB but RE5S4B (!)

[chris (ccpp)]

I just found a workaround which works for me!
Enable NumLock (for me that's Fn+ScrollLock) before the SysRq. The Fn key will disable NumLock then during SysRq then!

Most probably it's impossible to fix this in software...is it?

[Sam_ (and-sam)]

chris, thanks for your input.
Please note my first description where it mentions that -K worked with Oneiric (on same hardware of course; used the laptop for testing Oneiric and Precise - fresh installations).
Please note that REISUB worked, otherwise I couldn't follow the output from sreen and reboot.
Please read the log file of #3 which indicates REISUB:
Jan 5 17:02:00 kernel: [ 1427.826332] Loglevel set to 5
Jan 5 17:02:01 kernel: [ 1429.050898] SysRq : Emergency Sync
Jan 5 17:02:01 kernel: [ 1429.057291] Emergency Sync complete

I'll attach kern.log from current Precise which indicates a bit different with Alt+FN+Print+K (which still doesn't work) and afterwards magic REISUB (which still works):
....
Aug 11 18:17:50 kernel: [ 1457.223918] SysRq : Changing Loglevel
Aug 11 18:17:50 kernel: [ 1457.223924] Loglevel set to 2
Aug 11 18:18:31 kernel: [ 1498.154235] SysRq : Keyboard mode set to system default
Aug 11 18:18:33 kernel: [ 1500.003923] SysRq : Terminate All Tasks
....
Aug 11 18:18:37 kernel: [ 1503.999278] SysRq : Changing Loglevel
Aug 11 18:18:37 kernel: [ 1503.999291] Loglevel set to 5

[Sam_ (and-sam)]

I've noticed that #26 has a typo (missing 's'), the output is still the same though.
cat /proc/sys/kernel/sysrq
1

[penalvch (penalvch)]

Sam_, could you please provide the full computer model as noted on the sticker?

[Sam_ (and-sam)]

Christopher, it says on the first sticker HP Regulatory Model, lots of chinese and this number: 6060B 1204101 I5
The second sticker tells about containing broadcom.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Sam_, as per http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=4173278&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4059%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken#BIOS an update to your BIOS is available (F.20). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, 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.

[Sam_ (and-sam)]

Thanks Christopher!

Followed instructions:

:~$ cd Downloads
:~/Downloads$ ls
sp54676.exe
:~/Downloads$ cabextract sp54676.exe --filter ISO/rom.iso
Extracting cabinet: sp54676.exe

All done, no errors.

## Looked all over the filesystem, there is no such directory ISO or rom.iso.

:~/Downloads$ cabextract sp54676.exe
Extracting cabinet: sp54676.exe
  extracting FirmwareUpdate.exe
  extracting FreeDOS/KERNEL.SYS
  extracting FreeDOS/kernels.zip
  extracting hpqFlash.exe
  extracting HPUSBFW.exe
  extracting KERNELS.ZIP
  extracting ROM.CAB
  extracting Rompaq/68DVA.BIN
  extracting Rompaq/config.sys
  extracting Rompaq/EROMPAQ.EXE
  extracting Rompaq/EROMPAQ.zip
  extracting Rompaq/gpl2.txt
  extracting Rompaq/KERNEL.SYS
  extracting WSSP54676.rtf

All done, no errors.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Sam_, if your BIOS isn't actually updated you wouldn't be all done. If it is, please provide:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

[Sam_ (and-sam)]

Christopher, I know, I've intended to tell you, there is no ISO directory and no rom.iso, hence I don't know how to proceed without as per instructions from the help page.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Sam_, please see http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=4173278&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D2%257CswItem%253Dob_98395_1%257CswEnvOID%253D4059%257CitemLocale%253D%257CswLang%253D%257Cmode%253D4%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken .

[Sam_ (and-sam)]

Christopher, thanks for the link.
As mentioned the 'linux-way' doesn't work. And I'm not familiar with 'HPQFlash' or what they mean with 'disk on key', double-click on an .exe file is useless on Ubuntu.

However, the notebook is doing fine without MagicSysRq -K, the bug reporter isn't able to update the BIOS and doesn't want to waste everybodies precious time any further.

[Launchpad Janitor (janitor)]

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