From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Taprogge <jens.taprogge@taprogge.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Thomas Hellstrom <thellstrom@vmware.com>,
linux-input@vger.kernel.org
Subject: Re: Regression: commit e696c68363740d3a8fe495e353de3ff26b86257a prevents Linux 3.13 from booting on Lenovo X1 Carbon.
Date: Mon, 20 Jan 2014 15:53:58 -0800 [thread overview]
Message-ID: <20140120235358.GC5012@kroah.com> (raw)
In-Reply-To: <20140120232652.GA5815@weetamoe.luzern.taprogge.wh>
On Tue, Jan 21, 2014 at 12:26:52AM +0100, Jens Taprogge wrote:
> Hello,
>
> I have bisected the boot failure of a Lenovo Thinkpad X1 Carbon to the
> merge ea4ebd1cb093c8ec5d7f4bf9070dc444184c3971. What I call "boot
> failure" refers to the fact that no console is shown, the machine only
> reads from the disc for a very short time, and the machine does not
> respond to Ctrl-Alt-Del, etc.
>
> As it turns out reverting e696c68363740d3a8fe495e353de3ff26b86257a
> (Input: serio - fix sysfs layout) on top of v3.13 makes the machine boot
> again. So far I have now clue how this commit can affect early boot
> / showing of the console.
>
> Does it ring any bells for you?
No, not at all, I don't see how that patch could prevent booting,
especially as it is fixing a regression (i.e. putting things back the
way they originally were.)
very odd.
greg k-h
next prev parent reply other threads:[~2014-01-20 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 23:26 Regression: commit e696c68363740d3a8fe495e353de3ff26b86257a prevents Linux 3.13 from booting on Lenovo X1 Carbon Jens Taprogge
2014-01-20 23:53 ` Greg Kroah-Hartman [this message]
2014-01-21 0:20 ` Jens Taprogge
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=20140120235358.GC5012@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jens.taprogge@taprogge.org \
--cc=linux-input@vger.kernel.org \
--cc=thellstrom@vmware.com \
/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