linux-kernel - Re: MTRR allocation failure

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1109092327210.1672@parag-X220>
Date:	Fri, 9 Sep 2011 23:31:29 -0400 (EDT)
From:	Parag Warudkar <parag.lkml@...il.com>
To:	Yinghai Lu <yinghai.lu@...cle.com>
cc:	Parag Warudkar <parag.lkml@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: MTRR allocation failure



On Fri, 9 Sep 2011, Yinghai Lu wrote:
> 
> your BIOS create one new WP entry. so mtrr sanitizer is not triggered...
> 
> Maybe you can just delete first entry before you load drm?

Thank you! That fixes the issue for me.

If anyone else has extra/write-protect entry in /proc/mtrr that can be 
deleted - here is what you can drop in /etc/modprobe.d/drm.conf -

# Free up a mtrr entry for drm
install drm /sbin/fix-mtrr-local.sh && { /sbin/modprobe --ignore-install $CMDLINE_OPTS drm ; }

/sbin/fix-mtrr-local.sh

#modify the grep arg and disable= to your needs
#!/bin/sh

grep write-protect /proc/mtrr

if [ $? -eq 0 ]; then
echo "disable=0" > /proc/mtrr
fi
exit 0
--
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/