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, 26 Jan 2017 08:15:21 +0000 [thread overview]
Message-ID: <bug-176951-11613-4h6Uk5EL8U@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 #19 from Dmitry Sysoletin <dmitry.sysoletin@gmail.com> ---
(In reply to Zhang Rui from comment #11)
> 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.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-01-26 8:15 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
2017-01-26 8:07 ` bugzilla-daemon
2017-01-26 8:08 ` bugzilla-daemon
2017-01-26 8:15 ` bugzilla-daemon [this message]
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-4h6Uk5EL8U@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.