From: Dave Hansen <dave.hansen@intel.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: hid-related 5.2-rc1 boot hang
Date: Tue, 28 May 2019 11:11:20 -0700 [thread overview]
Message-ID: <8a17e6e2-b468-28fd-5b40-0c258ca7efa9@intel.com> (raw)
In-Reply-To: <CAO-hwJJzNAuFbdMVFZ4+h7J=bh6QHr_MioyK2yTV=M5R6CTm=A@mail.gmail.com>
On 5/28/19 10:45 AM, Benjamin Tissoires wrote:
> On Tue, May 28, 2019 at 7:15 PM Jiri Kosina <jikos@kernel.org> wrote:
>> Just to confirm -- I guess reverting 4ceabaf79 and a025a18fe would work
>> this around, right?
Yes, reverting that pair on top of 5.2-rc1 works around the issue.
> It would be also interesting to know which distribution and which
> systemd version you are running (if you are on systemd).
$ systemd --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD -IDN
on "Ubuntu 16.04.6"
next prev parent reply other threads:[~2019-05-28 18:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 16:43 hid-related 5.2-rc1 boot hang Dave Hansen
2019-05-28 17:14 ` Jiri Kosina
2019-05-28 17:45 ` Benjamin Tissoires
2019-05-28 18:11 ` Dave Hansen [this message]
2019-05-29 9:17 ` Hans de Goede
2019-05-30 16:56 ` Dave Hansen
2019-05-31 22:15 ` Jiri Kosina
2019-06-03 9:11 ` Hans de Goede
2019-06-03 9:32 ` Hans de Goede
2019-06-03 9:51 ` Hans de Goede
2019-06-03 13:55 ` Benjamin Tissoires
2019-06-03 14:17 ` Hans de Goede
2019-06-04 7:51 ` Benjamin Tissoires
2019-06-04 8:05 ` Hans de Goede
2019-06-04 8:36 ` Hans de Goede
2019-06-04 8:53 ` Benjamin Tissoires
2019-06-04 21:08 ` Jiri Kosina
2019-06-05 12:29 ` Benjamin Tissoires
2019-06-04 10:08 ` Benjamin Tissoires
2019-06-04 10:50 ` Hans de Goede
2019-06-04 12:25 ` Benjamin Tissoires
2019-06-04 13:12 ` Hans de Goede
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=8a17e6e2-b468-28fd-5b40-0c258ca7efa9@intel.com \
--to=dave.hansen@intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).