Bug 1014639 - message flood in /var/log/messages
Summary: message flood in /var/log/messages
Keywords:
Status: CLOSED DUPLICATE of bug 917081
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-10-02 13:03 UTC by Miroslav Lisik
Modified: 2013-10-02 13:07 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-02 13:07:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Extract from /var/log/messages. (9.92 KB, text/plain)
2013-10-02 13:03 UTC, Miroslav Lisik
no flags Details

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 ***


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