newer kernels (3.10+) don't boot on MacBook Air 6.1

[Miek Gieben]

The current raring kernel boots (with nosmp and libata.force=noncq), newer kernels don't boot at all. They hang with ramdisk loading and nothing seems to happen. This is difficult to debug, as it happens so early in the boot.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-27-generic 3.8.0-27.40
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
Uname: Linux 3.8.0-27-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: miek 1872 F.... pulseaudio
Date: Sun Aug 18 22:49:05 2013
HibernationDevice: RESUME=UUID=f4250ce4-23bc-413f-9a97-205cd9ca67e5
InstallationDate: Installed on 2013-08-19 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424)
Lsusb:
 Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
 Bus 001 Device 003: ID 05ac:0290 Apple, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 05ac:828f Apple, Inc.
MachineType: Apple Inc. MacBookAir6,1
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=003d813a-5ee5-40bc-a81f-dbed66aaf939 ro nosmp libata.force=noncq quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-27-generic N/A
 linux-backports-modules-3.8.0-27-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0099.B00.1305241529
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-35C1E88140C3E6CF
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-35C1E88140C3E6CF
dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
dmi.product.name: MacBookAir6,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 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 this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc6-saucy/

[Joseph Salisbury (jsalisbury)]

We can perform a kernel bisect if the v3.11-rc6 kernel does not boot as well.

[Miek Gieben (miek)]

I tested v3.11-rc5 yesterday, that one didnt boot. I'll try the rc6 shortly.

[Miek Gieben (miek)]

rc6 does not boot, kernel crash with 'nosmp', kernel hang with 'smp'

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy
v3.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/
v3.10-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc4-saucy/
v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

[Miek Gieben (miek)]

Both kernels tested with 'nosmp' etc.

v3.9-saucy: boots
v3.10-rc1: crashes

Both won't boot with 'smp'

[Joseph Salisbury (jsalisbury)]

Can you capture a digital image or screen capture of the failure your seeing and post it to the bug.

It sounds like we are seeing two bugs here. First is the system won't boot without smp. The second is that a regression was introduced in v3.10-rc1 that prevents the system from booting even with smp.

Let's focus on the second bug first and possible open a new bug for the first.

[Miek Gieben (miek)]

Ack.

To add some references, the first bug is: https://bugzilla.kernel.org/show_bug.cgi?id=60635 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197451.

[Miek Gieben (miek)]

Image of failed boot of v3.10-rc1

[Joseph Salisbury (jsalisbury)]

I started a kernel bisect between v3.9 final and v3.10-rc1. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
73287a43cc79ca06629a88d1a199cd283f42456a

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1213795

Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results.

Thanks in advance

[Miek Gieben (miek)]

[ Quoting <joseph.salisbury@canonica> in "[Bug 1213795] Re: newer kernels (3...." ]
> I started a kernel bisect between v3.9 final and v3.10-rc1. The kernel
> bisect will require testing of about 7-10 test kernels.
>
> I built the first test kernel, up to the following commit:
> 73287a43cc79ca06629a88d1a199cd283f42456a
>
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1213795
>
> Can you test that kernel and report back if it has the bug or not. I
> will build the next test kernel based on your test results.

with nosmp,libata.force=noncq -> crash
with smp -> hang in Booting Node 0, Processor #1

So fail for this bisect.

grtz Miek

[Miek Gieben (miek)]

https://bugs.launchpad.net/ubuntu/precise/+source/linux/+bug/1197451/comments/25

Booting 3.11-rc6 with this method works for me too, but still need: nosmp

[Joseph Salisbury (jsalisbury)]

Thanks for testing. It sounds like there are two bugs. It sounds like the crash with nosmp,libata.force=noncq no longer happens with v3.11-rc6? You are now only having an issue booting without the nosmp option?

[Miek Gieben (miek)]

Yes, that is correct. A successful boot with 3.11-rc6 requires nosmp. (note I compiled this kernel myself, this is not the ppa-mainline kernel)

[Joseph Salisbury (jsalisbury)]

Can you also see if the latest Raring kernel also requires both nosmp,libata.force=noncq, or just nosmp. It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13.7-raring/

We may want to re-focus this bug on the 3.11-rc6 kernel not being able to boot without nosmp and open a new bug for Raring if it still requires nosmp and libata.force=noncq

[Miek Gieben (miek)]

3.8.13.7-raring (only installed the linux-image .deb) hangs with 'smp', but boots with 'nosmp'

[Joseph Salisbury (jsalisbury)]

Do you happen to know if there was an earlier kernel version that did not require the nosmp option?

[Miek Gieben (miek)]

See: https://bugzilla.kernel.org/show_bug.cgi?id=60635#c7
Pasted here:

I did some additional testing:

Kernels from: http://kernel.ubuntu.com/~kernel-ppa/mainline/

  Version smp nosmp
  --------- ------ -------
  3.8.13 hang ?
  3.7.10 hang ?
  3.6.11 hang ?

I stopped there, the all hang with the symptom describe in this bug report.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel and it still requires the nosmp option. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue as well, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Miek Gieben (miek)]

Thanks, but this is already happened and this bug already links to it: https://bugzilla.kernel.org/show_bug.cgi?id=60635

[Miek Gieben (miek)]

Converting Ubuntu to EFI boot fixes the problem! I can boot now. All CPUs are detected and the forceata stuff is also not needed. Note the function keys and touchpad still don't work (even with 3.11-rc6), but that is a seperate bug

[Joseph Salisbury (jsalisbury)]

@Miek Gieben, What steps did you take to convert Ubuntu to EFI? Did you just enable it in the BIOS or something else?

[Miek Gieben (miek)]

I followed the steps listed on a Ubuntu page where you can convert your
grub install to an efi boot. I didn't change anything in the BIOS. Sorry,
don't have the URL at hand atm.
On 26 Aug 2013 13:55, "Joseph Salisbury" <email address hidden>
wrote:

> @Miek Gieben, What steps did you take to convert Ubuntu to EFI? Did
> you just enable it in the BIOS or something else?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1213795
>
> Title:
> newer kernels (3.10+) don't boot on MacBook Air 6.1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1213795/+subscriptions
>

[Miek Gieben (miek)]

this guide: https://help.ubuntu.com/community/UEFI#Converting_Ubuntu_into_EFI_or_Legacy_mode