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]
Message-ID: <20100301131101.GA8644@gherkin.frus.com>
Date:	Mon, 1 Mar 2010 07:11:01 -0600
From:	Bob Tracy <rct@...rkin.frus.com>
To:	linux-kernel@...r.kernel.org
Subject: K6-III/450 MTRR support

Anyone got a quick way to determine whether MTRR support is working
correctly on this old CPU?  "cat /proc/mtrr" doesn't show anything
configured in cases where I used to see a few entries.  Using the "nv"
driver (Xorg 1.6.3 dated 2009-07-31: latest version for Slackware 13)
produces two error messages...  This one appears in syslog:

kernel: mtrr: no MTRR for d0000000,4000000 found

and this one appears as the last line of output to the virtual console
after shutting down the X server:

waiting for X server to shut down error setting MTRR (base = 0xd0000000, \
size = 0x04000000, type = 1) Invalid argument (22)

Here are the applicable kernel config lines: if the config doesn't make
sense, I'm sure someone will let me know.  The last time I *know* MTRRs
worked properly was before the PAT and SANITIZER options showed up:
yeah, that far back...

CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y

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