Alt+SysRq+K (SAK) on VT1 causes kernel panic (Attempted to kill init)

[Max Bowsher]

Pressing Alt+SysRq+K (SAK, kill processes on this VT) on VT1 attempts to kill init, thereby panicing the kernel.

init should probably be excluded from SAK killing, as should any core system daemons (udev, etc.) which may or may not retain some association with vt1 (I can't tell, since the kernel panics :-))

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: linux-image-2.6.28-7-generic 2.6.28-7.20
ProcCmdLine: root=UUID=57eb71e0-dd7f-48b8-86a1-1cf6593fd188 ro
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-7.20-generic
SourcePackage: linux

[Max Bowsher (maxb)]

This is rather odd... this happens reproducably on my ThinkPad Z61p, but not on my Aspire One.

[Jeremy Foshee (jeremyfoshee)]

Hi Max,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 329576

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Max Bowsher (maxb)]

I am no longer able to reproduce this, let's assume it's fixed.