Bug 995296 - Bug after kernel upgrade
Summary: Bug after kernel upgrade
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-09 02:10 UTC by chule
Modified: 2013-10-08 16:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-08 16:28:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description chule 2013-08-09 02:10:07 UTC
Description of problem:
Not urgent since Fedora19 still works but still thought I should submit.
After running and update and upgrading to the latest kernel kernel-3.10.4-300.fc19.x86_64
I started getting this messages:
 $ journalctl -b | grep -n -E "hw|failed"
483:Aug 08 20:14:12 fb0x kernel: mei_me 0000:00:16.0: version message writet failed
485:Aug 08 20:14:12 fb0x kernel: mei_me 0000:00:16.0: wait hw ready failed. status = 0x0
486:Aug 08 20:14:12 fb0x kernel: mei_me 0000:00:16.0: version message writet failed
488:Aug 08 20:14:12 fb0x kernel: mei_me 0000:00:16.0: wait hw ready failed. status = 0x0

So I ran:
$ lspci -v | grep 16.0
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)

My guess is the latest kernel might have an issue with my chipset.

I went back to kernel 3.9.9-302.fc19.x86_64 and no longer have the issue.

P.S.: First time I submit a bug so let me know if there's something missing. 
Thank you.

Comment 1 Josh Boyer 2013-09-18 20:37:13 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 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Josh Boyer 2013-10-08 16:28:15 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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