[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090302213412.GB25076@elte.hu>
Date: Mon, 2 Mar 2009 22:34:12 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
Cc: Sitsofe Wheeler <sitsofe@...oo.com>,
"dri-devel@...ts.sourceforge.net" <dri-devel@...ts.sourceforge.net>,
LKML <linux-kernel@...r.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [TIP,regression,i915] /dev/dri/card0 is no longer present
* Pallipadi, Venkatesh <venkatesh.pallipadi@...el.com> wrote:
> On Sun, 2009-03-01 at 05:48 -0800, Sitsofe Wheeler wrote:
> > On Sun, Mar 01, 2009 at 12:39:48PM +0100, Ingo Molnar wrote:
> > >
> > > Thanks, i've reverted the commit for now. Could you please send
> > > a 'dmesg' from the bootup with the failed driver? By all
> > > likelyhood an ioremap failure causes a driver failure.
> > >
> >
> > See below (drm says it initalized though...):
> >
> > [ 0.000000] Linux version 2.6.29-rc6-00006-g17581ad (@verona) (gcc version 4.2.4) #87 Sun Mar 1 13:42:28 GMT 2009
> > [ 0.000000] KERNEL supported cpus:
> > [ 0.000000] Intel GenuineIntel
> > [ 0.000000] PAT WC disabled due to known CPU erratum.
>
> Looks like PAT is getting disabled on this platform. Can you
> send the output of /proc/cpuinfo please.
Does this mean we failed an ioremap()? We still should not fail
a device ioremap _ever_. We should just fall back to UC and be
done with it. We may emit a warning if we consider it
troublesome, but we should never ever break working drivers
really.
Ingo
--
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