← Back to team overview

kernel-packages team mailing list archive

  1. kernel-packages team
  2. Mailing list archive
  3. Message #07615

[Bug 879158] Re: REISUB fails to reboot the computer.

  Thread Previous • Date Previous • • Thread Next 
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.

** Tags added: needs-kernel-logs

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Attachment removed: "This is the output of the lshw command on the Ubuntu computer this bug was tested on."
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879158/+attachment/2563690/+files/hardware2.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/879158

Title:
  REISUB fails to reboot the computer.

Status in “linux” package in Ubuntu:
  Incomplete

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 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879158/+subscriptions
  Thread Previous • Date Previous • • Thread Next