Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37461 - Updating to linux/linux-header 3.11.6-1 puts system in non-bootable state.

Attached to Project: Arch Linux
Opened by Mike Mercer (monkeenyc) - Wednesday, 23 October 2013, 19:08 GMT
Last edited by Jan de Groot (JGC) - Thursday, 14 November 2013, 14:17 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: This is my first bug report, so please let me know if I'm not including enough information.
When updating to Linux 3.11.6-1 (through a standard pacman -Syu) my laptop won't boot.

Not sure what causes the breakage (or even where to find the failed log - assuming there is one - I only get a black screen on reboot), but if I roll back my system to linux and linux-headers to 3.11.5-1 my system boots properly.

Additional info:
* package version(s) - linux 3.11.6-1, linux-headers 3.11.6-1
I have my system set up without the use of a log in manager (I think I have the terminology correct). I log into the shell directly and manually execute startx to bring up XFCE (not sure if any of this information helps in debugging).

Again, if it helps I am using the latest version of gummiboot (38-1), as my UEFI boot manager - allowing dual boot into Arch and Windows 8.

Please advise if there is further information I can provide (and how to provide them, since I am somewhat new to linux ~4 months). I have tried the pacman -Syu and rolled it back about 3 different times (hoping it was just a fluke). I have no problem trying this again, in order to provide a proper log.

Steps to reproduce:
perform system update using pacman -Syu and reboot. Get Blank Screen. Can only boot through backup disc, and can fix by downgrading linux and linux-headers to 3.11.5-1.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 14 November 2013, 14:17 GMT
Reason for closing:  Fixed
Comment by dangerginger (jkav77) - Monday, 28 October 2013, 04:15 GMT
I have this same problem. Upgrading by Pacman -Syu to 3.11.6-1 from 3.11.5-1 causes my system not to boot. I get the acer logo in the bios screen and the logo never disappears it just hangs there. No EFI shell or anything. If I hold space I can get to the gummiboot menu but every combination of kernel arguments I can think of result in a blank screen with no information. I have an Acer Aspire S7-392.
Comment by Ulf Winkelvos (uwinkelvos) - Sunday, 03 November 2013, 23:10 GMT
this is probably a dublicate of this bug here: https://bugs.archlinux.org/task/33745
Comment by Mike Mercer (monkeenyc) - Tuesday, 05 November 2013, 12:36 GMT
It is possibly related - thanks Ulf!

I hadn't seen this breakage until specifically the 3.11.6-1 version, but that might just make me lucky. Do you suggest moving away from gummiboot/rEFInd due to issues with the handoff?

If so which boot loader do you recommend? Grub?
Comment by Ulf Winkelvos (uwinkelvos) - Wednesday, 06 November 2013, 00:04 GMT
I use syslinux on all systems, as it is way simpler than grub2. I would like to go back and use gummiboot, as you can see in the bug report, it's just an on and off thing. For some systems like mine some kernel version ranges work, others don't. For other no kernel since 3.9 works. There is a patch I posted over there, you might give that a try, but even if that works its cumbersome to recompile every kernel. So I can only recommend to stick to syslinux for now.
Comment by Mike Mercer (monkeenyc) - Wednesday, 06 November 2013, 22:43 GMT
Syslinux seems to be the most stable from what you say - though according to the wiki, it does not sound like I could chain load Windows 8 EFI.

So for the time being I guess I'll need to be careful when upgrading the kernel.

Any other thoughts?
Comment by Ulf Winkelvos (uwinkelvos) - Thursday, 07 November 2013, 00:54 GMT
i would be interesting to know if the patch posted here works foor you too: https://bugs.archlinux.org/task/33745#comment114120
Comment by Mike Mercer (monkeenyc) - Thursday, 14 November 2013, 12:41 GMT
This issue does not appear in the 3.12.1 version of the kernel. Since the longer running bug referenced by Ulf has more of the history of this bug, this one should be marked closed.

Thanks!

Loading...