Bug 878058 - "Could not configure common clock" during boot
Summary: "Could not configure common clock" during boot
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-11-19 15:16 UTC by yury.skanavy
Modified: 2015-02-25 00:36 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-01 15:57:29 UTC
Type: Bug

Attachments (Terms of Use)

Description yury.skanavy 2012-11-19 15:16:17 UTC
Description of problem:

I am getting this message on boot:
"Could not configure common clock"

This is on Lenovo W530 notebook with a fresh Fedora 17.

Please note that I am not sure if I am reporting against the correct component. If that's the case please let me know how to properly re-file this bug. 

Version-Release number of selected component (if applicable):
Fedora 17

How reproducible:

Steps to Reproduce:
1. Install Fedora.
2. Boot.
Actual results:
"Could not configure common clock" is shown during boot. Seems to cause no further issues.

Expected results:
No message.

Additional info:

Comment 1 Josh Boyer 2013-01-07 21:07:19 UTC
Are you still seeing this with the 3.6.10 or newer kernel updates?  If so, please attach the output of dmesg after a fresh boot.

Comment 2 Justin M. Forbes 2013-02-01 15:57:29 UTC
This bug is being closed because it has been set needinfo for more than 2 weeks without a response. If this is still an issue, please reopen and reply with the requested information.

Comment 3 Nathan G. Grennan 2013-02-21 02:19:19 UTC
In case anyone runs across this bug report later, the fix is likely to disable VT-D. Setting the UEFI mode in the bios to Legacy only may also help.

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