From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: dri-devel@lists.sourceforge.net, jbarnes@virtuousgeek.org,
linux-kernel@vger.kernel.org
Subject: Re: Regression in i915 on 2.6.34-rc1
Date: Mon, 15 Mar 2010 10:51:01 -0700 [thread overview]
Message-ID: <201003151151.01891.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1268535744.28444.16.camel@dc7800.home>
On Saturday 13 March 2010 08:02:24 pm Bjorn Helgaas wrote:
> On Sat, 2010-03-13 at 13:46 -0700, Pete Zaitcev wrote:
> > On Fri, 12 Mar 2010 22:37:56 -0700
> > Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> >
> > > Thanks for the report. Would you mind posting the entire dmesg
> > > log, /proc/iomem contents, and "lspci -vv" output somewhere (maybe in
> > > bugzilla)?
> >
> > Done, new bug:
> > http://bugzilla.kernel.org/show_bug.cgi?id=15533
>
> Thanks! Sorry, I should have asked for the "pci=nocrs" (working) dmesg,
> too. Do you have that handy? What kind of machine is this? I don't
> suppose you have Windows on it; I'd really like to know what the Device
> Manager says about the PCI host bridge and graphics controller
> resources.
I added two patches to the bugzilla:
http://bugzilla.kernel.org/attachment.cgi?id=25522 (possible fix)
http://bugzilla.kernel.org/attachment.cgi?id=25523 (additional debug)
If the first patch fixes it, we're all set. If it doesn't, I'd like
the additional debug info from the second patch.
Thanks!
Bjorn
next prev parent reply other threads:[~2010-03-15 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100311003358.58194366@redhat.com>
2010-03-13 1:25 ` Pete Zaitcev
2010-03-13 5:37 ` Bjorn Helgaas
2010-03-13 6:04 ` Bjorn Helgaas
2010-03-13 6:40 ` Pete Zaitcev
2010-03-13 14:49 ` Bjorn Helgaas
2010-03-13 20:46 ` Pete Zaitcev
2010-03-14 3:02 ` Bjorn Helgaas
2010-03-15 17:51 ` Bjorn Helgaas [this message]
2010-03-17 15:26 ` Bjorn Helgaas
2010-03-22 0:19 ` Pete Zaitcev
2010-03-25 4:04 ` Bjorn Helgaas
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=201003151151.01891.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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 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®