From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sitsofe Wheeler <sitsofe@yahoo.com>,
"dri-devel@lists.sourceforge.net"
<dri-devel@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [TIP,regression,i915] /dev/dri/card0 is no longer present
Date: Mon, 02 Mar 2009 13:43:55 -0800 [thread overview]
Message-ID: <1236030235.4586.79.camel@localhost.localdomain> (raw)
In-Reply-To: <20090302213412.GB25076@elte.hu>
On Mon, 2009-03-02 at 13:34 -0800, Ingo Molnar wrote:
> * Pallipadi, Venkatesh <venkatesh.pallipadi@intel.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.
>
No. We don't break ioremap. We try to fallback on UC_MINUS here. But,
there is something wrong happening in that path, that is resulting in
this issue. I am looking at that right now.
I have found another problem with this particular patch, on one of test
systems. So, let us keep the revert until I fix what looks like two
different problems here.
Thanks,
Venki
next prev parent reply other threads:[~2009-03-02 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090301110455.GA18547@silver.sucs.org>
2009-03-01 11:39 ` [TIP,regression,i915] /dev/dri/card0 is no longer present Ingo Molnar
2009-03-01 13:48 ` Sitsofe Wheeler
2009-03-02 19:05 ` Pallipadi, Venkatesh
2009-03-02 21:34 ` Ingo Molnar
2009-03-02 21:43 ` Pallipadi, Venkatesh [this message]
2009-03-02 22:11 ` Ingo Molnar
2009-03-03 18:24 ` Eric Anholt
2009-03-03 14:50 ` Sitsofe Wheeler
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=1236030235.4586.79.camel@localhost.localdomain \
--to=venkatesh.pallipadi@intel.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sitsofe@yahoo.com \
--cc=suresh.b.siddha@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.