1002:714a Kernel 3.5 is not booting

This change was made by a bot.

Fibonacci, thank you for reporting this and helping make Ubuntu better. Could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc5-raring/ ?

Still happens.

Fibonacci, the next step is to commit bisect this from Quantal to the last release this worked for you. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

I couldn't find the bug without installing the linux-image-extra packages. However, my desktop is barely usable without said packages, so I had to installed them anyway.
I've found through bisection that the bug is not present in 3.4.0-5.11, though it is on 3.5.0-1.1.

I tried to do a commit bisect between those two versions, but I could find no kernel older than 3.5 on git://kernel.ubuntu.com/ubuntu/ubuntu-quantal.git, and no kernel newer than 3.2 on git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git.
Perhaps I'm doing something wrong. How can I then perform the bisect?

Fibonacci, as per http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git;a=tags one may further narrow the kernel versions down by testing:
v3.5-rc3 -> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc3-quantal/
v3.5-rc2 -> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc2-quantal/

The bug is still present on v3.5-rc2.
I could still not proceed with the commit bisect: after running git bisect start v3.5-rc2 Ubuntu-3.4.0-5.11 there is no debian.master/ or debian/ directory, so I cannot build a new kernel for testing.

Fibonacci, please see https://wiki.ubuntu.com/Kernel/KernelBisection#Why_did_the_folders_debian_and_debian.master_disappear.3F .

This is the result of the bisect. Unfortunately I had to skip some kernels because they wouldn't compile.

2099810f903caa1920f3ef6014fb7f36e4786490 is the first bad commit
commit 2099810f903caa1920f3ef6014fb7f36e4786490
Author: Dave Airlie <email address hidden>
Date: Tue Apr 3 11:53:05 2012 +0100

    drm/radeon: enable pci bus mastering after card is initialised (v2)

    This closes a race seen with kexec where we enable PCI bus mastering
    but the card has been reinitialised fully yet.

    This was previously fixed by a patch from Jerome, but this should
    close the race completely.

    v2: add SI support as suggested by Alex.

    Reported-and-tested-by: Markus Trippelsdorf <email address hidden>
    Signed-off-by: Dave Airlie <email address hidden>

:040000 040000 543c4ab332c9e62bf964d005f42e918160508777 73177e660b0ebca43b6a449bc208d7c8b00ab8c8 M drivers

The bug is also affecting my configuration:
Laptop Compaq 6910p with radeon X2300 video.

- output of: "lspci | grep VGA"
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M64-S [Mobility Radeon X2300]

- output of: "uname -a" (my current configuration, working perfectly)
Linux Compaq-6910p 3.2.0-44-generic #69-Ubuntu SMP Thu May 16 17:35:01 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Basically trying to boot all Linux distro with Kernel > 3.4 will result in a black screen with unresponsive keyboard. Booting with nomodeset=1 always works but brings a 1024x768 resolution instead of native 1280x800.

As user "Fibonacci" found out the offending kernel patch, what can be done to undo it in future kernel versions? I understand that we are a relatively small number of users affected, with a relatively outdated hardware. Any hope?

Thanks for your work and time.

GPratique, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Fibonacci, could you please test the latest upstream kernel available (v3.10-rc2) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Still there.

Fibonacci, thank you for testing the newest mainline kernel. The issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

Christopher, Fibonacci,

It seems to me that this bug is related to one already reported on Kernel.org:

https://bugzilla.kernel.org/show_bug.cgi?id=54191
"Unable to boot without disabling KMS: ATI Mobility Radeon X1300"

Thanks for your work.

GPratique, thank you for the link. Unfortunately, the public bugzilla is not the preferred venue of reporting new bugs, or validating previously reported ones for upstream maintainers or developers. Hence, Fibonnacci would want to follow the instructions noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1108457/comments/15 in maximize the speed of this issue being addressed.

@penalvch: understood. Although it seems to me that this bug has already been reported in different ways multiple times across multiple distributions. For example bug #1070773 here at launchpad looks pretty much a duplicate to me.

Is there a way to contact the dev who did the commit discovered by Fibonacci, i.e. Dave Airlie? He seems pretty high up in the food chain, and would probably be of great help.

GPratique, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1108457/comments/18 :
>"Although it seems to me that this bug has already been reported in different ways multiple times across multiple distributions. For example bug #1070773 here at launchpad looks pretty much a duplicate to me."

linux (Ubuntu) bug reports are treated as separate reports based on the preference of the Ubuntu Kernel team:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

and the Ubuntu Bug Control team and Ubuntu Bug Squad:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

unless a developer notes otherwise.

>"Is there a way to contact the dev who did the commit discovered by Fibonacci, i.e. Dave Airlie? He seems pretty high up in the food chain, and would probably be of great help."

Unfortunately, one does not contact people simply based on a the maintainership hierarchy, as this is considered spam. If we did, all issues would then just go to Linus, who has better things to do, then entertain every "I have a bug in the linux kernel" e-mail sent to him.

Despite this, Fibonacci not performing the actions previously requested of him are counterproductive to getting this issue resolved, for the reasons stated previously. If you have further questions, please do not comment further in this report, but instead you may contact me directly, place them in the appropriate forum, and perform the actions previously requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1108457/comments/12 .

Thank you for your understanding.

This issue and it's numerous siblings may have been solved upstream in kernel 3.9.6 by:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=e335ccae2ae4caef26a1e81711c44aec1cc83bd2

Regards,

Fibonacci,

could you please update to the latest kernel in quantal-updates (3.5.0-37.58) and see if it fixes this bug?
Thanks.

FWIW the related bug #1070773 is fixed by the kernel 3.8.0-28.41 from raring-proposed - it also containts the necessary patch "radeon: Fix system hang issue when using KMS with older cards".