LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	benjamin.tissoires@redhat.com, andyrtr@archlinux.org,
	aduggan@synaptics.com, stable@vger.kernel.org,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
Date: Tue, 10 Apr 2018 09:38:36 +0200	[thread overview]
Message-ID: <20180410093836.1e39d9d8@endymion> (raw)
In-Reply-To: <20180405183824.13333-1-jandryuk@gmail.com>

On Thu,  5 Apr 2018 14:38:24 -0400, Jason Andryuk wrote:
> The HP EliteBook G3 850 has a weird bug where a subsequent cold boot
> hangs while plugged in if Linux enables the Host Notify features of
> i2c-i801.  The cold boot hang depends on how the system boots.  It does
> not hang on UEFI Grub text boot or legacy Grub text boot.  But it does
> hang on legacy Grub graphical boot and Intel Boot Agent PXE text boot.
> Booting unplugged is not affected.
> 
> Disabling the Host Notify feature with disable_feature=0x20 works around
> the bug, so automatically do so based on DMI information.
> 
> More information can be found here:
> https://www.spinics.net/lists/linux-i2c/msg33938.html
> 
> Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
> Reviewed-by: Jean Delvare <jdelvare@suse.de>
> Cc: stable@vger.kernel.org
> ---
> v3: Switch to DMI_EXACT_MATCH and add empty element to array
> 
>  drivers/i2c/busses/i2c-i801.c | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)
> (...)

Wolfram and stable, please hold on with this patch, Jason and I may have
found a proper fix so blacklisting would no longer be needed.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2018-04-10  7:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 12:25 [PATCH] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Jason Andryuk
2018-04-02 12:34 ` [PATCH v2] " Jason Andryuk
2018-04-03 19:13   ` Andreas Radke
2018-04-04 12:55     ` Jason Andryuk
2018-04-04 14:02       ` Jean Delvare
2018-04-06 15:23       ` Andreas Radke
2018-04-04 20:56   ` Jean Delvare
2018-04-05 18:38     ` [PATCH v3] " Jason Andryuk
2018-04-10  7:38       ` Jean Delvare [this message]
2018-04-10  9:10         ` Wolfram Sang

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=20180410093836.1e39d9d8@endymion \
    --to=jdelvare@suse.de \
    --cc=aduggan@synaptics.com \
    --cc=andyrtr@archlinux.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jandryuk@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).