public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Conklin <steve.conklin@canonical.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	UBUNTU kernel-team <kernel-team@lists.ubuntu.com>
Subject: Re: Oops on i915 on 8086:a011 pine trail 2.6.32-rc6
Date: Thu, 19 Nov 2009 09:29:22 -0600	[thread overview]
Message-ID: <4B056452.40108@canonical.com> (raw)
In-Reply-To: <43e72e890911111426h3cd1e5bfya3fa6da810ce633e@mail.gmail.com>

On 11/11/2009 04:26 PM, Luis R. Rodriguez wrote:
> On Tue, Nov 10, 2009 at 3:27 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> Getting an oops with a pine trail netbook I'm doing testing on on
>> 2.6.32-rc6 with a fresh new distro kernel for the next Ubuntu 10.04
>> release:
>>
>> https://launchpad.net/ubuntu/+source/linux/2.6.32-3.3/+build/1339939/+files/linux-image-2.6.32-3-386_2.6.32-3.3_i386.deb
>>
>> The machine boots fine with 2.6.31.
>>
>> The oops happens early on the boot process, I'll next rebuild my own
>> with early boot delay (CONFIG_BOOT_PRINTK_DELAY) as that seems to be
>> the only way I'm going to get this full trace out. Good thing is its
>> 100% reproducible so I should be able to bisect. The only thing
>> visible so far is the end of the oops:
>>
>> http://bombadil.infradead.org/~mcgrof/oops-img/2009/11/2.6.32-rc6-i915-8086-a011-oops-01.jpg
> 
> I compiled my own 2.6.32-rc6 based Linus' tip from today actually and
> I didn't run into issues.
> 
>   Luis

Luis (and everyone else),

I'm taking the lead for graphics on the Ubuntu kernel team. I'm happy to have bugs filed
on launchpad for these, and you can contact me directly or send email to the canonical
kernel team list, which I'm including in this distribution.

I'm tracking issues with a couple of platforms using the i915 driver as delivered
both in the karmic release, and in the 10.04 kernel. I hope to have them resolved soon.
Testing on the non-pinetrail platform this morning, the issues were resolved with the
patches queued for Linus's next merge. Knowing that Linus' tip solves your pine trail
issue is good information. Thanks for your testing work!

Steve Conklin

      parent reply	other threads:[~2009-11-19 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 23:27 Oops on i915 on 8086:a011 pine trail 2.6.32-rc6 Luis R. Rodriguez
2009-11-11 22:26 ` Luis R. Rodriguez
2009-11-16 14:33   ` Woody Suwalski
2009-11-19 15:29   ` Steve Conklin [this message]

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=4B056452.40108@canonical.com \
    --to=steve.conklin@canonical.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@gmail.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