Bug 42795
Summary: | Unable to boot with the radeon driver | ||
---|---|---|---|
Product: | Drivers | Reporter: | Thomas (v10lator) |
Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
Status: | RESOLVED CODE_FIX | ||
Severity: | blocking | CC: | alan, alexdeucher |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Subsystem: | ||
Regression: | No | Bisected commit-id: |
Description
Thomas
2012-02-18 11:37:54 UTC
Can't attach the image as it's to big, so: http://img269.imageshack.us/img269/778/dsc01960ko.jpg Future testing showed that the error is presented since 3.3-rc1 Still presented in 3.3-r4. Can you bisect? Hi Alex, I'm not that expert, but I think bisect has something to do with git? I'll try to figure it out for myself, but it would be great if you could give me step-by-step instructions what to do. Okay, I found a description here: http://kerneltrap.org/node/11753 and hope that cloning 2.6 is right. Also, as a sidenode: The cursor (down left side of the screen) blinks for a few seconds while the system still doesn't react to anything and shows the yellow lines before the screen freezes, too. I started with git bisect good v3.2 git bisect bad v3.3-rc1 and every builded kernel had the issue (more or less, at some point near the end the screen just goes to standby instead of freezing, but every time before freezing/going to standby it showed the yellow lines) So at the end I got this: a858393b0ce5c330bda466e5ae3a658ca98588ae is the first bad commit commit a858393b0ce5c330bda466e5ae3a658ca98588ae Author: Andrei Emeltchenko <andrei.emeltchenko@intel.com> Date: Fri Sep 16 16:26:30 2011 +0300 Bluetooth: EFS: l2cap extended feature mask update Update L2CAP extended feature mask to reflect recent BT spec. Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com> Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi> :040000 040000 d7f27c8ba453168696bf5407d9ca06fd370deda4 11d22bb619481167c4133b27fd87e7be3be636af M include But how can a bluetooth change cause that? :( Okay, I tracked this down more and was able to boot a 3.3-rc4 kernel. The problem was that radeon and uvesa was compiled into the kernel. Ok, this bug can be closed then. |