Red Hat Bugzilla – Bug 810026
System reboots during startup
Last modified: 2012-11-13 10:10:34 EST
Description of problem:
The bootup process never completes. Towards the point where X would normally start, the system reboots.
Version-Release number of selected component (if applicable):
3.2.9-1.fc16.i686 and 3.2.10-3.fc16.i686
Happens every time
Steps to Reproduce:
1. switch computer on
2. watch bootup messages
3. system reboots
Bootup never completes
It's an Acer Aspire One D270 netbook. Cedarview chipset. Atom N2600. GMA 3600.
This happens with the 3.2.9-1.fc16.i686 and 3.2.10-3.fc16.i686 kernels, but not with 3.1.0-7.fc16.i686
With systemd target set to graphical, reboot happens after the following messages
Starting Open-FCoE Initiator
Started System Logging Service
(sometimes one, sometimes the other is the last message displayed).
With systemd target set to multi-user, reboot happens after
Started Console System Startup Logging
In both cases, there is a longish pause (maybe 20 seconds) after the last message is displayed, before it reboots.
F17 has CONFIG_DRM_GMA_3600=y set. If you haven't done so already, you might try upgrading to F17 and seeing if that helps.
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.