boot fails unless acpi=off Acer Travelmate X-349
A message that is not in the archive (sent off-list or not yet received): [email protected]/
https://bugzilla.kernel.org/show_bug.cgi?id=176951
Len Brown <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Config-Tables |Other
Assignee|acpi_config-tables@kernel-b |scsi_drivers-other@kernel-b
|ugs.osdl.org |ugs.osdl.org
Product|ACPI |SCSI DriversSignature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #6 from [email protected] ---
I can confirm this issue on my Acer Swift 3 Model SF314-51-59RF. Arch Linux x64 with kernel 4.8.11 and 4.9.rc7 hang with a black screen on boot.
However, I can also confirm some reports from this acer thread that this seems to be a x64 specific issue:
I'm typing this from a perfectly fine working Fedora 25 32-Bit Live system with kernel 4.8.6. The x64 version hangs on boot just like Arch Linux.
btw, there is no BIOS update available for the Swift 3 yet (BIOS version 1.05).
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #7 from [email protected] ---
Update:
It seems like this was partly fixed by BIOS upgrade 1.07 (only available via Windows Update).
Fedora x64 and Ubuntu x64 are confirmed to boot after the BIOS upgrade (see the mentioned acer community thread).
However, Arch Linux x64 still doesn't boot and I haven't figured out the difference yet. Arch has kernel 4.8.11 while Fedora boots fine with 4.8.6 and 4.8.13, so I doubt it's the kernel version.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
Martin Goyot <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #8 from Martin Goyot <[email protected]> --- I confirm, I have this exact same problem with TravelMate X349-M.
Fedora 25 32-Bit Live system working, but impossible to boot the x64 version, black frozen screen after boot menu.
I cannot confirm for the BIOS update because of course I don't have windows anymore so I don't know how I will install it...
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #9 from Martin Goyot <[email protected]> --- Can now confirm. Updated Bios, can now run the x64 version.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #10 from [email protected] ---
Created attachment 248381
--> https://bugzilla.kernel.org/attachment.cgi?id=248381&action=edit
Kernel Panic Arch Linux x64 kernel 4.9
Attached is a kernel panic I get with Arch Linux x64 and kernel 4.9. Unfortunately I can't get the whole stack trace. I tried to up the resolution with the vga= parameter but then the screen stays black. I actually got it to boot once, but had no other success after 10 other tries.
The stacktrace looks very similiar to Bug 58201 (comment 20 on this bug also mentions the same problem with vga=).
Since Fedora and Ubuntu are fixed by the BIOS upgrade but Arch Linux still doesn't boot, I guess this may be related to different kernel configs? Any hints on which configs could affect this?
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #11 from Zhang Rui <[email protected]> ---
please check if the latest upstream kernel works for you or not. If yes, I will close this bug as the original bug has been fixed by BIOS upgrade, and the arch linux 4.9 kernel issue sounds like a Distro problem to me.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #12 from Zhang Rui <[email protected]> --- (In reply to Zhang Rui from comment #11)
Quoted 4 lines
please check if the latest upstream kernel works for you or not. If yes, I will close this bug as the original bug has been fixed by BIOS upgrade, and the arch linux 4.9 kernel issue sounds like a Distro problem to me.
If no, please also check upstream 4.8 kernel to see if this is a upstream kernel regression and use git bisect to find out the offending commit.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #13 from [email protected] ---
I'm reporting the same problem with Acer Travelmate X349-M, BIOS v1.07, 64bit in all tests.
Also, I can get to the login prompt of gdm with everything working good (including battery status, touchpad, wifi, special keys...) using Arch Linux with replaced Kernel 4.10r1 from Ubuntu distribution and acpi=force acpi_osi='!Windows 2012',
but (unless acpi=off) it freezes on black screen just after successfull login (the same with GNOME, GNOME Classic, GNOME Xorg).
Tried Kernel 4.0.9 from Ubuntu with acpi on, and it worked good for 10 minutes on GNOME, but then stopped and didn't work at all for the following tries. Tried Kernel 4.4.0: acpi=off, login ok; acpi on, crash with stack traces at boot, behavior similar to 4.0.9.
Also note that Ubuntu 16.10 Live official image (linux-image-4.8.0-22-generic) works perfectly.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #14 from [email protected] ---
I now report complete functionality and stability with kernel linux-grsec 4.8.15.r201612151923-1 from Arch Linux community repository.
Also, in order to fix a different problem, I have always put in mkinitcpio.conf the following: MODULES="crc32_generic crc32-pclmul libcrc32c crc32c_generic crc32c-intel"
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #15 from [email protected] ---
I just made an actual Arch Linux Installation instead of just trying to boot the USB device - and on the installation everything works fine, including the standard kernel (4.8.3 and 4.9.0) without any acpi parameters.
The kernel on my USB image and the installed kernel (both 4.8.3) even have the same md5sum, but the USB one doesn't boot while the installed system works fine. They also have the same bootloader (systemd-boot).
So for some reason this problem only happens on Arch Linux kernels and only when booted via USB...!?
I'm gonna try the latest upstream kernel and bisect it...
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #16 from [email protected] ---
Created attachment 250411
--> https://bugzilla.kernel.org/attachment.cgi?id=250411&action=edit
dmesg with ACPI errors (kernel 4.10rc2)
Bisecting this is really frustrating because it randomly works in different combinations, depending on whether UEFI or Legacy boot is enabled in BIOS and whether you boot via USB or SSD and sometimes pure chance...
The good(?) news is: kernel 4.10rc2 boots in almost all circumstances. But the only combination that is actually stable is the same one that already works with 4.8 and 4.9: booting with legacy mode enabled from the internal SSD.
When I boot 4.10rc2 with UEFI mode enabled in BIOS or via USB, the system doesn't hang like with previous kernels. Instead I get quite a few ACPI errors and the system manages to boot completely most of the time, but freezes completely after a few seconds.
The full dmesg is attached. This is with UEFI mode enabled in BIOS and booting 4.10rc2 from the internal SSD. Hopefully the ACPI warnings and errors help narrow this down...
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
Dmitry Sysoletin <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #17 from Dmitry Sysoletin <[email protected]> --- Created attachment 253181
--> https://bugzilla.kernel.org/attachment.cgi?id=253181&action=edit
Stacktrace screenshot 1
Screenshot of hung kernel 4.10.0-rc5
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #18 from Dmitry Sysoletin <[email protected]> --- Created attachment 253191
--> https://bugzilla.kernel.org/attachment.cgi?id=253191&action=edit
Stacktrace screenshot 2
Another 4.10.0-rc5 fail
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #19 from Dmitry Sysoletin <[email protected]> --- (In reply to Zhang Rui from comment #11)
Quoted 4 lines
please check if the latest upstream kernel works for you or not. If yes, I will close this bug as the original bug has been fixed by BIOS upgrade, and the arch linux 4.9 kernel issue sounds like a Distro problem to me.
I'am checked 4.10.0-rc5, and have about one successful reboot for 10 reboot attempts. I have 2 different types of fail - most often it happens about at 0.5 second uptime, but I catched another failure on ~24 second (screenshots attached).
System is 64-bit, booting with legacy mode, BIOS updated to 1.07 (it seems like switching legacy <-> UEFI don't make sense). Sometimes I able to boot, if I press F2 at power-up moment, enter EFI-shell, press ctrl+alt+del - seems like this increasing boot chances.
I tried with acpi=ht also, but this don't changes behaviour.
I'am able to boot ubuntu with 4.2 kernel from liveusb - and I see messages that some people able to run other distros. That distros use vanilla kernel, or have some patches? I guess ubuntu not using vanilla kernel - there must be some patches fixing/masking this issue.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #20 from Martin Goyot <[email protected]> --- A new Bios update is available on Acer's website:
https://www.acer.com/ac/en/GB/content/support-product/6917?b=1
v1.08 apparently. If anyone has tried it, does it solve the remaining problems?
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #21 from Dmitry Sysoletin <[email protected]> --- (In reply to Martin Goyot from comment #20)
Quoted 5 lines
A new Bios update is available on Acer's website:
https://www.acer.com/ac/en/GB/content/support-product/6917?b=1v1.08 apparently. If anyone has tried it, does it solve the remaining problems?
I tried it - and it not helps. Still have crashes at boot.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
Alan Welsh ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #22 from Alan Welsh ([email protected]) --- I can confirm the system does not boot unless either: a) passed with the acpi=off parameter in legacy mode or, b) booted in UEFI mode.
As for (a): This issue is resolved with grsecurity kernel.
As for (b): UEFI cannot be used because all linux bootloaders fail to be recognized by the firmware. There is not one distribution which boots after installation. The bootloader never loads. Only receive error message "disk not found" or something to that effect.
Acer swift 3 (bios 1.08)
All x64 flavors from: Ubuntu, Fedora, Gentoo, Arch, opensuse.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
Max ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #23 from Max ([email protected]) ---
I can confirm the bug on my Acer Swift 3 Model SF314-51 (bios 1.08). I able to install just Mint 18.1. I found that it freezes when:
1. ~4 times of 5 when my machine start ups (boot logo/black screen);
2. usually when chrome starts;
3. when brightness changes very fast;
4. when shut down.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
Alberto Tiboni ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #24 from Alberto Tiboni ([email protected]) --- I can confirm issue is still here: update bios at 1.08, nothing changed!
Tried Ubuntu and Lubuntu distro, 16.04, 16.10 and 17.04, both 64 and 32bits.
The only one that booted after installation was Lubuntu 16.04 32bit in legacy mode, with grub without "quite splash" parameters.
but it works rarely: 9 on 10 times it produces a kernel panic on apci init.
Now I'm trying linux Mint, but i'm quite sure problem will be there too.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #25 from Alberto Tiboni ([email protected]) --- (In reply to Alberto Tiboni from comment #24)
Quoted 10 lines
I can confirm issue is still here: update bios at 1.08, nothing changed!
Tried Ubuntu and Lubuntu distro, 16.04, 16.10 and 17.04, both 64 and 32bits.
The only one that booted after installation was Lubuntu 16.04 32bit in legacy mode, with grub without "quite splash" parameters.
but it works rarely: 9 on 10 times it produces a kernel panic on apci init.
Now I'm trying linux Mint, but i'm quite sure problem will be there too.
Hi there, found this
https://www.reddit.com/r/linuxmint/comments/5lu69k/installing_linux_mint_181_on_an_acer_swift_3/
don't know if can help, but at second install attempt the system is stable with kernel 4.4.0-53-generic
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #26 from Alan Welsh ([email protected]) --- [Arch system, Legacy mode, 64 bit]
Can now boot with the "mainline" kernel [4.12.0-rc5-mainline] as well as the "hardened" kernel [4.11.6.a-1]. The latter is purposed as a replacement for the grsecurity kernel.
Does this mean we can expect a working kernel for our machines from the various distributions in the near future?
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #27 from [email protected] ---
Can confirm, this seems to be fixed in 4.12-rc5 mainline (Arch Linux x64). Machine boots and works fine now, even in UEFI mode.
Signature · 2 lines
You are receiving this mail because: You are watching the assignee of the bug.