lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Fri, 18 Apr 2014 00:31:57 +0200
From:	Alessandro Suardi <alessandro.suardi@...il.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 3.15-rc1: Endless "Disabling PPGTT because VT-d is on" messages in /var/log/messages

[hoping I persuaded gmail to get my old text-only email settings back, grrr]


Noticed that my root fs was filling up, and found out that /var/log/messages was
 approaching 2GB of space, most of which were as per $subject. To give an idea
 of the magnitude, here's a snippet from a saved sample of /var/log/messages:

[root@...x log]# grep  "Disabling PP" messages.save.head |head -1
Apr 15 03:44:10 xbox kernel: [    3.115126] [drm] Disabling PPGTT
because VT-d is on
[root@...x log]# grep  "Disabling PP" messages.save.head |tail -1
Apr 15 03:45:50 xbox kernel: [  130.165219] [drm] Disabling PPGTT
because VT-d is on
[root@...x log]# grep -c "Disabling PP" messages.save.head
610

Or from the dmesg ring:

[root@...x log]# dmesg|head
[22446.690572] [drm] Disabling PPGTT because VT-d is on
[22446.690616] [drm] Disabling PPGTT because VT-d is on
[22446.704560] [drm] Disabling PPGTT because VT-d is on
[22446.706747] [drm] Disabling PPGTT because VT-d is on
[22446.720202] [drm] Disabling PPGTT because VT-d is on
[22446.722447] [drm] Disabling PPGTT because VT-d is on
[22446.724850] [drm] Disabling PPGTT because VT-d is on
[22446.727268] [drm] Disabling PPGTT because VT-d is on
[22446.733052] [drm] Disabling PPGTT because VT-d is on
[22446.735319] [drm] Disabling PPGTT because VT-d is on



Are there patches for this issue, or is a workaround available to prevent a
 filesystem full condition on my root fs?


This is on a Dell Latitude E6420 laptop, Fedora 19 x86_64, onboard
 Intel video card... yes, I have an old A08 BIOS, but I've never seen
 this issue while regularly updating my mainline kernel weekly or so...


Available for more details if needed, thanks in advance,

--alessandro

"don't underestimate the things that I will do"

 (Adele, "Rolling In The Deep")
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ