Bug 648837 - System freeze during boot until a key or power button is pressed on AMD Gigabyte motherboard (AMD C1E)
Summary: System freeze during boot until a key or power button is pressed on AMD Gigab...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-02 09:37 UTC by Yann Droneaud
Modified: 2013-08-01 18:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 18:28:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages (143.54 KB, text/plain)
2011-10-29 20:57 UTC, Yann Droneaud
no flags Details
Kernel 3.6.2 boot message (without acpi_skip_timer_override) (72.20 KB, text/plain)
2012-10-24 09:35 UTC, Yann Droneaud
no flags Details
Kernel 3.6.2 boot message (without acpi_skip_timer_override) [again] (72.10 KB, text/plain)
2012-10-24 09:37 UTC, Yann Droneaud
no flags Details
Kernel 3.6.2 boot message (with acpi_skip_timer_override) (72.63 KB, text/plain)
2012-10-24 09:38 UTC, Yann Droneaud
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Linux Kernel 15289 0 None None None Never
Novell 666793 0 None None None Never

Description Yann Droneaud 2010-11-02 09:37:09 UTC
With Fedora 14 Beta, I have to press the power button in order to resume the boot process.

This is probably related to a bug with AMD Phenom II with Gigabyte MA790 motherboards.

At least there are workarounds: disabling AMD C1E support in BIOS or adding options such as acpi_skip_timer_override on kernel command line.

This should be noted in release notes.


See also

- https://bugzilla.kernel.org/show_bug.cgi?id=15289

- bug 614479

Comment 1 Jirka Daněk 2011-05-08 18:02:21 UTC
I disagree with the assigned severity as Low. This bug still persists in Fedora Rawhide (see bug #700800) and can be a no-go for new fedora users who have AMD C1E support enabled and do not spot the connection.

Comment 2 Dave Jones 2011-10-11 19:44:23 UTC
is this still a problem in f16-beta ?

Comment 3 Yann Droneaud 2011-10-11 20:17:19 UTC
I have tried yesterday Fedora 16 Beta x86_64 Live LXDE on the same hardware configuration, and the problem is still here.

I didn't have time to test kernel option "acpi_skip_timer_override" which I have add to Fedora 14 kernel command line.

Comment 4 Yann Droneaud 2011-10-29 20:57:41 UTC
Created attachment 530803 [details]
/var/log/messages

I have tried today Fedora 16 RC1 x86_64 Live Desktop
and the kernel was unable to brought up 3 of the 4 CPU cores while I was pushing hard on the power button just to see the kernel log scrolling ...

Oct 29 14:12:08 localhost kernel: [    0.022998] Booting Node   0, Processors  #1
Oct 29 14:12:08 localhost kernel: [    5.584158] CPU1: Not responding.
Oct 29 14:12:08 localhost kernel: [    5.584352]  #2
Oct 29 14:12:08 localhost kernel: [   11.300685] CPU2: Not responding.
Oct 29 14:12:08 localhost kernel: [   11.301319]  #3 Ok.
Oct 29 14:12:08 localhost kernel: [   16.801351] CPU3: Not responding.
Oct 29 14:12:08 localhost kernel: [   16.801421] Brought up 1 CPUs
Oct 29 14:12:08 localhost kernel: [   16.801423] Total of 1 processors activated (6429.26 BogoMIPS).

Comment 5 Dave Jones 2012-03-22 16:41:18 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 6 Dave Jones 2012-03-22 16:46:05 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 7 Dave Jones 2012-03-22 16:55:17 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 8 Yann Droneaud 2012-10-18 12:45:32 UTC
The problem is still there in Fedora 17.

Preupgrade doesn't use my default kernel options, so its grub2 entry didn't have the "acpi_skip_timer_override" option. In order to make the upgrade between F16 and F17 I need to press the power button once in a while.

Comment 9 Yann Droneaud 2012-10-18 13:06:07 UTC
See also this thread "Fedora 17 cannot boot on my pc...  " (July 2012, August 2012) on users@ list

http://lists.fedoraproject.org/pipermail/users/2012-July/thread.html#422701
http://lists.fedoraproject.org/pipermail/users/2012-August/thread.html#422750

Comment 10 Dave Jones 2012-10-23 15:30:01 UTC
# 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
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 11 Yann Droneaud 2012-10-24 09:29:12 UTC
Hi,

I've just done some test with kernel-3.6.2-4.fc17.x86_64 on my system eg.
AMD Phenom II X4 955 / Gigabyte MA790 (GA-MA790X-UD4) with chipset AMD 790X / AMD SB750

Without "acpi_skip_timer_override", I have to press the power button one time to unblock the system. With the option, the system boot without any annoyance.

Comment 12 Yann Droneaud 2012-10-24 09:35:33 UTC
Created attachment 632667 [details]
Kernel 3.6.2 boot message (without acpi_skip_timer_override)

See the log message without acpi_skip_timer_override, the system hang about 16 seconds before I press the power button.

Comment 13 Yann Droneaud 2012-10-24 09:37:07 UTC
Created attachment 632668 [details]
Kernel 3.6.2 boot message (without acpi_skip_timer_override) [again]

Another boot without the option. I waited about 16 seconds before pressing the power button.

Comment 14 Yann Droneaud 2012-10-24 09:38:22 UTC
Created attachment 632669 [details]
Kernel 3.6.2 boot message (with acpi_skip_timer_override)

The boot messages with option acpi_skip_timer_override. No need to press the power button.

Comment 15 Fedora End Of Life 2013-07-04 06:49:26 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2013-08-01 18:28:23 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.