From: Mehmet Giritli <mehmet@giritli.eu>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Faulty MTRR setups in Toshiba laptops crash video drivers
Date: Tue, 03 Nov 2009 15:08:33 +0200 [thread overview]
Message-ID: <1257253713.6277.7.camel@frodo.giritli.eu> (raw)
In-Reply-To: <4AEF7402.1010901@gmail.com>
On Mon, 2009-11-02 at 18:06 -0600, Robert Hancock wrote:
> On 11/02/2009 10:28 AM, Mehmet Giritli wrote:
> > Hello all,
> >
> > On some laptops using ATI 3650HD radeon chipsets and 4GB ram (and may be
> > others as well), it is impossible to start any xserver due to (faulty?)
> > mtrr setups on the machine. The computer locks up or just gives an
> > unresponsive black screen. There are various drivers for radeon cards
> > and the crash occurs in all of these drivers in the very same way!
> >
> > This bug seems to occur mostly on Toshiba laptops with ATI graphic
> > cards. For some people, CONFIG_MTRR_SANITIZER seemed to cure the issue
> > but made no difference for many others like me.
> >
> > RadeonHD people seem to have problems in understanding the nature of
> > this bug. Please have a look at the threads:
> >
> > http://lists.opensuse.org/radeonhd/2009-05/msg00040.html
> >
> > and,
> >
> > http://bugs.freedesktop.org/show_bug.cgi?id=20645
> >
> > for problem reports and dev responses. RadeonHD devs suggest that some
> > laptops have weird mtrr setups and this must be fixed in the kernel code
> > and not the driver code.
>
> Unfortunately I don't see enough details to be able to tell what lead
> them to this conclusion. Can you post the output of:
>
> lspci -vv
> cat /proc/mtrr
lspci -vv
http://bugzilla.kernel.org/attachment.cgi?id=23634
/proc/mtrr when 4GB installed
http://bugzilla.kernel.org/attachment.cgi?id=23632
/proc/mtrr when 2GB installed
http://bugzilla.kernel.org/attachment.cgi?id=23633
There is also a bug report that I opened a while back here:
http://bugzilla.kernel.org/show_bug.cgi?id=14054
>
> >
> > Currently, the only way that could make the driver work is to reduce the
> > 4GB ram to 2GB.
> >
> > dmesg from my affected machine when it has 4GB ram installed can be
> > found here:
> >
> > http://bugzilla.kernel.org/attachment.cgi?id=22856
> >
> > Also, look at the report here:
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/341681
> >
> > in order to see how many people are being affected by this bug!
> >
> > Kind Regards,
> > M. Giritli
> >
> >
>
next prev parent reply other threads:[~2009-11-03 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 16:28 Mehmet Giritli
2009-11-03 0:06 ` Robert Hancock
2009-11-03 13:08 ` Mehmet Giritli [this message]
2009-11-04 23:48 ` Robert Hancock
2009-11-05 11:02 ` Mehmet Giritli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1257253713.6277.7.camel@frodo.giritli.eu \
--to=mehmet@giritli.eu \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®