Ticket #7812 (new defect)

Opened 6 years ago

Last modified 6 years ago

Rebooting XO running joyride-2230 and 8.2-759 results in "hard stop"

Reported by: joe Owned by: dgilmore
Priority: blocker Milestone: 8.2.0 (was Update.2)
Component: initscripts Version: Development build as of this date
Keywords: polish:8.2.0 Cc: charlie, kimquirk, mstone, mikus@…
Action Needed: reproduce Verified: no
Deployments affected: Blocked By:


Some of the XOs (at least 2) running joyride-2230 demonstrated this behavior. When rebooting a machine, the XO stops (in the process of shutting down) with a message: "waiting for X server to shut down...", then: "<init: unexpected signal 15.".

Change History

Changed 6 years ago by mikus

  • cc mikus@… added

The bypass is to press alt-ctl-F2, to get the "don't do this" screen to show. Then the XO will complete shutdown normally.

Changed 6 years ago by mstone

  • owner changed from dilinger to dgilmore
  • component changed from kernel to initscripts

Changed 6 years ago by kimquirk

  • keywords polish:8.2.0 added

Not a blocker because you can shutdown with power button... but needs high priority investigation.

Changed 6 years ago by dsaxena

From http://lists.laptop.org/pipermail/devel/2008-August/018243.html:

I rebooted from the XO menu in Home view. The last message on screen was in a console error, something like "error 15 from xinit". But 10 minutes later that was still on screen. I pressed a few keys and the screen changed to the safety graphic and the machine restarted.

The pressing a few keys to continue the reboot process is new. Looks like a process is hanging and waiting for input before it continues?

Changed 6 years ago by frances

i had the same reboot issue today (9/8/08) in a g1g1 XO that i upgraded to 8.2-759. Just thought I should mention it.

Changed 6 years ago by joe

  • priority changed from high to blocker
  • summary changed from Rebooting XO running joyride-2230 results in "hard stop" to Rebooting XO running joyride-2230 and 8.2-759 results in "hard stop"

Observed this in a bunch of machines that have been updated with 8.2-759 and then rebooted. Needed to power down machines manually (using a power button) before rebooting again.

Changed 6 years ago by thomaswamm

  • next_action changed from never set to reproduce
  • version changed from not specified to Development build as of this date

I have seen this bug (hang when shutting down) several times with build 8.2-767. The bug seems to occur when shutting down (or restarting) after some prior activity crash, maybe from oom-killer or X BadAlloc. Or does it happen when shutting down with a background activity still in memory? Need to find a reliable way to reproduce this bug so it can be diagnosed.

The mikus fix (press ctrl-alt-group) works for me.

Changed 6 years ago by thomaswamm

This is probably a dup of #7531.

Changed 6 years ago by mikus

Note: the messages cited in the original #7812 description are normal - I see them even if shutdown does not "stop". The problem is when shutdown does not continue after those messages.

Note: See TracTickets for help on using tickets.