LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   glitch bloats root directory by excessive writing to log files (https://www.linuxquestions.org/questions/linux-software-2/glitch-bloats-root-directory-by-excessive-writing-to-log-files-4175480325/)

wolecki 10-10-2013 02:00 PM

glitch bloats root directory by excessive writing to log files
 
Hello all,
I have successfully installed debian Jessie on my new ASUS UX32VD-DH71 zenbook laptop. There is a reoccurring error which leads to bloating the / directory partition by loop writing to log files in /var/log. Files are getting volumes of 2-4 GB, and it is specifically in kern.log, messages and syslog.
Having to deal with a full / dir is one thing, and clearly the logging system is doing it's job. I look therefor for to isolate the bug that brings to that excessive output.
Googling a little brought much about habdling the log files themselves but none had any clear relation to my problem. It was on one thread that it might be a debian bug that has to do with intel wireless cards which my system contains.

Links to kern.log and messages (last 200 or so lines):

kern.log
messages

judging these and lspci it looks the problem is with this controller:
Code:

00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
lspci:
Code:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)

kernel: 3.10-3

Thanks in advance!
Amit

wolecki 10-10-2013 02:35 PM

some more googling produced:
this guy suggests its a kernel 3.10-3 problem and that blacklisting the device stops the glitch.
then on the relevant Fedora bugzilla thread there are several reports of successfull blacklisting the module but all attempts to install newer kernel or patching were of no avail.

It seems:
a. the MEI module is useless unless one needs some Intel anti theft tech or Active Management.
b. blacklisting isn't working in kernels in which the module is built in.
c. the bug is not fixed yet up to kernel ver. 3.11.1-200

Creative ideas?

amit.


All times are GMT -5. The time now is 08:04 AM.