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: Thu, 05 Jan 2017 19:37:55 +0000 [thread overview]
Message-ID: <bug-176951-11613-RJGsNdq6Ca@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-176951-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=176951
--- Comment #16 from mus.svz@gmail.com ---
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...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-05 19:38 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
2016-12-31 4:27 ` bugzilla-daemon
2016-12-31 11:59 ` bugzilla-daemon
2017-01-05 19:37 ` bugzilla-daemon [this message]
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-RJGsNdq6Ca@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).