REISUB fails to reboot the computer.

[Little Girl]

My son uses Ubuntu 10.04 and I use Kubuntu 10.04. Both computers are desktop machines, and are not identical. On each of our systems, Alt+SysRq+REISUB fails to reboot our computers.

STEPS TO REPRODUCE:

1) Close all open programs so that you're just on your Desktop.

2) Hold down the Alt and SysRq keys.

3) Slowly type REISUB.

4) Release the Alt and SysRq keys.

EXPECTED RESULTS:

Visual feedback when typing each letter of REISUB followed by the computer rebooting. (Note that I'm not sure whether there should be some sort of visual feedback when the letter R is pressed.)

ACTUAL RESULTS:

R does nothing.
E says "Disconnected from Plymouth" and leaves the blinking cursor at a computer log-in in TTY 1.
I kills a bunch of processes, disconnects the system BUS, and leaves me with a blinking cursor at a log-in prompt in TTY 1.
S performs an emergency system sync and leaves me with a blinking cursor that is not at a log-in prompt in TTY 1.
U Disconnects her from USB, does an emergency remount, and leaves me with a blinking cursor that is not at a log-in prompt in TTY 1.
B does nothing.

ADDITIONAL INFORMATION:

Maco (one of your devs) tried it on an Ubuntu 10.04 machine and it successfully rebooted the computer.

POSSIBLY RELATED INFORMATION:

If, instead, we do Alt+SysRQ+REISUO to shut the machine down rather than reboot it, it successfully shuts the machine down:

R does nothing.
E says "Disconnected from Plymouth" and leaves the blinking cursor at a computer log-in in TTY 1.
I kills a bunch of processes, disconnects the system BUS, and leaves me with a blinking cursor at a log-in prompt in TTY 1.
S performs an emergency system sync and leaves me with a blinking cursor that is not at a log-in prompt in TTY 1.
U Disconnects her from USB, does an emergency remount, and leaves me with a blinking cursor that is not at a log-in prompt in TTY 1.
O stops all devices and shuts down the computer.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2)
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18
Regression: Yes
Reproducible: Yes
Tags: lucid audio regression-potential needs-upstream-testing
Uname: Linux 2.6.32-33-generic i686
UserGroups: audio cdrom dialout floppy lpadmin plugdev video

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 879158

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Little Girl (littlergirl)]

I'm sorry, but I'm confused. Since the bug is that the computer fails to reboot when the specified keys are pressed, do you wish us to use the apport command once we have manually rebooted the computer?

[Joseph Salisbury (jsalisbury)]

Yes, it would be good if you could run that apport command once the system is booted.

Are you waiting a few seconds after each magic key. This gives the corresponding command time to actually do its job.

Another thing you could try is by performing the same task logged in with an ssh session. This is done by sending characters to the file /proc/sysrq-trigger :

$ echo r | sudo tee /proc/sysrq-trigger
$ echo e | sudo tee /proc/sysrq-trigger
$ echo i | sudo tee /proc/sysrq-trigger
$ echo s | sudo tee /proc/sysrq-trigger
$ echo u | sudo tee /proc/sysrq-trigger
$ echo b | sudo tee /proc/sysrq-trigger

[Joseph Salisbury (jsalisbury)]

Also, 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 . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

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

Thanks in advance.

[Little Girl (littlergirl)]

I created a new user on the Kubuntu machine, repeated the steps that cause the bug, manually rebooted the computer, and ran the apport-collect 879158 command.

Yes, we always wait a few seconds after pressing each of the REISUB keys.

We don't use SSH on our machines, and we don't own a test machine, so we can't do your SSH commands. We can't do the upstream kernel testing for the same reason. Hopefully you have test machines that demonstrate this bug.

Please let me know if there's anything else we can do.

[Mackenzie Morgan (maco.m)]

You can use one broken computer to ssh to the other and run the commands,
then switch.
On Oct 23, 2011 6:50 PM, "Little Girl" <email address hidden> wrote:

> I created a new user on the Kubuntu machine, repeated the steps that
> cause the bug, manually rebooted the computer, and ran the apport-
> collect 879158 command.
>
> Yes, we always wait a few seconds after pressing each of the REISUB
> keys.
>
> We don't use SSH on our machines, and we don't own a test machine, so we
> can't do your SSH commands. We can't do the upstream kernel testing for
> the same reason. Hopefully you have test machines that demonstrate this
> bug.
>
> Please let me know if there's anything else we can do.
>
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/879158
>
> Title:
> REISUB fails to reboot the computer.
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> My son uses Ubuntu 10.04 and I use Kubuntu 10.04. Both computers are
> desktop machines, and are not identical. On each of our systems,
> Alt+SysRq+REISUB fails to reboot our computers.
>
> STEPS TO REPRODUCE:
>
> 1) Close all open programs so that you're just on your Desktop.
>
> 2) Hold down the Alt and SysRq keys.
>
> 3) Slowly type REISUB.
>
> 4) Release the Alt and SysRq keys.
>
> EXPECTED RESULTS:
>
> Visual feedback when typing each letter of REISUB followed by the
> computer rebooting. (Note that I'm not sure whether there should be
> some sort of visual feedback when the letter R is pressed.)
>
> ACTUAL RESULTS:
>
> R does nothing.
> E says "Disconnected from Plymouth" and leaves the blinking cursor at a
> computer log-in in TTY 1.
> I kills a bunch of processes, disconnects the system BUS, and leaves me
> with a blinking cursor at a log-in prompt in TTY 1.
> S performs an emergency system sync and leaves me with a blinking cursor
> that is not at a log-in prompt in TTY 1.
> U Disconnects her from USB, does an emergency remount, and leaves me with
> a blinking cursor that is not at a log-in prompt in TTY 1.
> B does nothing.
>
> ADDITIONAL INFORMATION:
>
> Maco (one of your devs) tried it on an Ubuntu 10.04 machine and it
> successfully rebooted the computer.
>
> POSSIBLY RELATED INFORMATION:
>
> If, instead, we do Alt+SysRQ+REISUO to shut the machine down rather
> than reboot it, it successfully shuts the machine down:
>
> R does nothing.
> E says "Disconnected from Plymouth" and leaves the blinking cursor at a
> computer log-in in TTY 1.
> I kills a bunch of processes, disconnects the system BUS, and leaves me
> with a blinking cursor at a log-in prompt in TTY 1.
> S performs an emergency system sync and leaves me with a blinking cursor
> that is not at a log-in prompt in TTY 1.
> U Disconnects her from USB, does an emergency remount, and leaves me with
> a blinking cursor that is not at a log-in prompt in TTY 1.
> O stops all devices and shuts down the computer.
> ---
> Architecture: i386
> DistroRelease: Ubuntu 10.04
> InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i38...

[penalvch (penalvch)]

Little Girl, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Little Girl (littlergirl)]

I'm sorry for abandoning this bug report. It never got fixed in Kubuntu 10.04. We are currently using Kubuntu 12.04 with the 3.2.0-51-generic-pae #77-Ubuntu SMP kernel and REISUB works just fine. I didn't do all the testing with mainline builds because this is a production machine. My kernel version looks nothing like your example, so you might want to do the kernel-fixed-upstream tag. Feel free to close out the bug since it's working fine now, and let me know if there's anything else I should do before that happens.

[penalvch (penalvch)]

Little Girl, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879158/comments/10 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.