linux-kernel - Re: Oops on i915 on 8086:a011 pine trail 2.6.32-rc6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Nov 2009 09:33:05 -0500
From:	Woody Suwalski <woodys@...dros.com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
cc:	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: Oops on i915 on 8086:a011 pine trail 2.6.32-rc6

Luis R. Rodriguez wrote:
> On Tue, Nov 10, 2009 at 3:27 PM, Luis R. Rodriguez <mcgrof@...il.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.
>
>   
I had similar problem on Pineview ( I think you have meant Pineview - 
not Pinetrail?)  - had to boot with "nomodeset" option.
However it has been rectified in a first git after -rc6.
Works for me now...

Woody

--
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/