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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 17 Mar 2012 07:36:39 +0100
From:	Michael Reinelt <>
To:	lkml <>
Subject: MTRR cleanup does not kick in

Hi there,

I am (again) suffering from:
kernel: mtrr: no more MTRRs available
kernel: [drm] MTRR allocation failed.  Graphics performance may suffer.

kernel is vanilla 3.2.11

I know that this *used* to work, but I had to specify mtrr_gran_size=16M mtrr_chunk_size=128M on the kernel command line.

Now, with the current kernel, I could not find *any* MTRR cleanup debug messages at all.

I debugged a bit, and probably found the cause:


/* Check if we only had WB and UC */
     num_var_ranges - num[MTRR_NUM_TYPES])
	return 0;

This one kicks in, and disables the MTRR cleanup, resulting in all 10 MTRR registers in use, and no more MTRRs available 
for DRM.

I disabled this check, and now the MTRR cleaner works fine, even finding a optimal value for my system with only 9 
registers, leaving one available for DRM.

maybe the mtrr_need_cleanup() function should take nr_mtrr_spare_reg into account?

regards, Michael

PS please keep me on CC as I'm not subscribed. thanks!

Michael Reinelt <>
GPG-Key 0xDF13BA50
ICQ #288386781
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists