Bug 1141592

Summary: hpet probe fails after upgrade to kernel 3.16.2-200
Product: [Fedora] Fedora Reporter: Stan King <stanley.king>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 13:11:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output exhibiting hpet probe error none

Description Stan King 2014-09-15 01:11:44 UTC 
Created attachment 937400 [details]
dmesg output exhibiting hpet probe error

Description of problem:

After upgrade to kernel 3.16.2-200.fc20.x86_64, one of my Intel-based systems shows this message in the dmesg output:

hpet: probe of PNP0103:00 failed with error -22

The processor type is Intel Core 2 Duo T8300.  
There was no similar message with kernel 3.15.10-201.fc20.x86_64.  Two other newer Intel-based systems do not exhibit this symptom with this kernel.

The following bug may have useful information, although its root cause may be different:

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

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

3.16.2-200.fc20.x86_64


How reproducible:
Every time.

Steps to Reproduce:
1. Boot system.
2.
3.

Actual results:

The above message is received.

Expected results:

No errors are expected regarding hpet.

Additional info:

Dmesg output will be attached.
Comment 1 Justin M. Forbes 2014-11-13 16:03:08 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.
Comment 2 Stan King 2014-11-23 20:42:59 UTC 
I no longer see this error with the latest kernel.  I would recommend closure.