[Kernel-packages] [Bug 1250909] Re: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8, 2

2013-12-17 Thread Christopher M. Penalver
Rohan Garg, the next step is to fully commit bisect from 3.11 to 3.12.0-2 in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? ** Tags added: needs-bisect regression-release ** Summary changed: - Trusty linux kernel 3.12.0

[Kernel-packages] [Bug 1250909] Re: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8, 2

2013-12-11 Thread Rohan Garg
The kernel from your link does not bring up the display. The last message I think I saw was : fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You recei

[Kernel-packages] [Bug 1250909] Re: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8, 2

2013-12-10 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix t

[Kernel-packages] [Bug 1250909] Re: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8, 2

2013-11-13 Thread Rohan Garg
Hi I'm attaching a image since it's impossible to capture a log file. ** Attachment added: "IMG_20131113_192608.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+attachment/3908214/+files/IMG_20131113_192608.jpg -- You received this bug notification because you are a member

[Kernel-packages] [Bug 1250909] Re: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8, 2

2013-11-13 Thread Joseph Salisbury
Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot: https://wiki.ubuntu.com/DebuggingKernelBoot As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture