Bug 1014639

Summary: message flood in /var/log/messages
Product: [Fedora] Fedora Reporter: Miroslav Lisik <mlisik>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-02 13:07:52 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:
Attachments:
Description Flags
Extract from /var/log/messages. none

Description Miroslav Lisik 2013-10-02 13:03:42 UTC
Created attachment 806440 [details]
Extract from /var/log/messages.

Description of problem:
I can't boot system normally because there was not enough space on root partition.
This caused message flood in /var/log/messages. Size of file was 43GB after 2 hours logging.


Version-Release number of selected component (if applicable):
3.10.11-200.fc19.x86_64

How reproducible:
UNKNOWN

I worked in awesome windows manager. After I quitted it I saw terminal with message flood. I couldn't do anything, so I shutdowned laptop with the power button. I must boot in single user mode and I found problem in /var/log/messages.


Steps to Reproduce:
1.
2.
3.

Actual results:
/var/log/messages file size of 43GB after 2 hours logging.


Expected results:
Less size of log file.



Additional info:
Here is one line from log:

Oct  2 09:48:17 dhcp129-91 kernel: [ 5164.168023] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 1.

In my opinion, there shouldn't be the timestamp [ 5164.168023].
I attached extract from /var/log/messages.

Comment 1 Josh Boyer 2013-10-02 13:07:52 UTC
There is a known issue with the mei modules.  It seems fixed with 3.11 for some people, but not for others.  Blacklisting seems to be the best workaround until it's fixed.

*** This bug has been marked as a duplicate of bug 917081 ***