From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 176951] boot fails unless acpi=off Acer Travelmate X-349
Date: Fri, 30 Dec 2016 15:32:55 +0000 [thread overview]
Message-ID: <bug-176951-11613-ATNyD7x73H@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-176951-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=176951
matteo.terruzzi@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matteo.terruzzi@gmail.com
--- Comment #13 from matteo.terruzzi@gmail.com ---
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.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-12-30 15:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-176951-11613@https.bugzilla.kernel.org/>
2016-10-24 23:55 ` [Bug 176951] boot fails unless acpi=off Acer Travelmate X-349 bugzilla-daemon
2016-12-02 21:11 ` bugzilla-daemon
2016-12-14 17:48 ` bugzilla-daemon
2016-12-21 9:20 ` bugzilla-daemon
2016-12-21 12:32 ` bugzilla-daemon
2016-12-22 20:30 ` bugzilla-daemon
2016-12-26 1:53 ` bugzilla-daemon
2016-12-26 1:54 ` bugzilla-daemon
2016-12-30 15:32 ` bugzilla-daemon [this message]
2016-12-31 4:27 ` bugzilla-daemon
2016-12-31 11:59 ` bugzilla-daemon
2017-01-05 19:37 ` bugzilla-daemon
2017-01-26 8:07 ` bugzilla-daemon
2017-01-26 8:08 ` bugzilla-daemon
2017-01-26 8:15 ` bugzilla-daemon
2017-01-29 16:19 ` bugzilla-daemon
2017-01-30 13:25 ` bugzilla-daemon
2017-03-22 15:37 ` bugzilla-daemon
2017-05-03 5:59 ` bugzilla-daemon
2017-05-04 11:07 ` bugzilla-daemon
2017-05-07 10:19 ` bugzilla-daemon
2017-06-18 10:20 ` bugzilla-daemon
2017-06-19 19:13 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-176951-11613-ATNyD7x73H@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).