Date: Tue, 19 May 2009 09:57:39 -0700 From: Chris H <chris#@1command.com> To: freebsd-stable@freebsd.org Subject: Re: failed to set mtrr: invalid argument Message-ID: <20090519095739.5o53vu0gcg4owkww@webmail.1command.com> In-Reply-To: <4A126DBA.9080701@andric.com> References: <20090518222644.k2pez2x9q88o4k8g@webmail.1command.com> <20090518224246.0qrzye1z40w4ws8g@webmail.1command.com> <20090518232019.36g94wxl7zeo088g@webmail.1command.com> <3a142e750905182328m60439dfcgadd4c28ba037400e@mail.gmail.com> <20090518234011.k55bmqq3488kko8c@webmail.1command.com> <4A126DBA.9080701@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Dimitry Andric <dimitry@andric.com>: > On 2009-05-19 08:40, Chris H wrote: >> I see. Well I'm specifically using the nv driver. Here's another >> attempt to provide the relevant info: > > I could not find the error message from $subject in these logs. Where > is it? :) If I had found it, I would have better known what direction to travel to overcome it. :) Aparently Xorg wants to keep it a secret - I saw no "argument". The closest possible answer I can come up with, involves "write combining" and provinding some information in /proc/mtrr But I only have /proc and nothing in it. Thought about echo(1)ing the information to mtrr. But don't understand the whole thing well enough to /dare/ do it. I only know it involves something in this area: 0xfd000000/16777216, 0xf0000000/134217728, 0xfa580000/524288 out of the Xorg log. I'm also not sure if GENERIC knows how to handle mtrr (Memory Type Range Registers) ideally. I hadn't built world/kernel yet because there are also some issues on the ATA ports that need to be resolved. I started a theread on this earlier. Thank you for taking the time to respond. --Chris H >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090519095739.5o53vu0gcg4owkww>