LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andreas Radke <andyrtr@archlinux.org>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
benjamin.tissoires@redhat.com, aduggan@synaptics.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850
Date: Tue, 3 Apr 2018 21:13:26 +0200 [thread overview]
Message-ID: <20180403211326.4907f1bc@laptop64.home> (raw)
In-Reply-To: <20180402123435.5587-1-jandryuk@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2476 bytes --]
Am Mon, 2 Apr 2018 08:34:35 -0400
schrieb Jason Andryuk <jandryuk@gmail.com>:
> 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
I'm faced with similar cold boot issues on my HP ProBook 430 G4 model.
Trying your hint with adding
"options i2c_i801 disable_features=0x20"
to /etc/modprobe.d/i2c_i801.conf doesn't seem to solve it for me.
root@laptop64:/root # systool -v -m
i2c_i801 Module = "i2c_i801"
Attributes:
coresize = "28672"
initsize = "0"
initstate = "live"
refcnt = "0"
srcversion = "A40BF457CFB8C7887EB2045"
taint = ""
uevent = <store method only>
Parameters:
disable_features = "32"
Sections:
.bss = "0xffffffffc0801800"
.data = "0xffffffffc0801120"
.exit.text = "0xffffffffc07fe463"
.gnu.linkonce.this_module= "0xffffffffc08014c0"
.init.text = "0xffffffffc070b000"
.note.gnu.build-id = "0xffffffffc07ff000"
.orc_unwind = "0xffffffffc0800140"
.orc_unwind_ip = "0xffffffffc07ffe38"
.parainstructions = "0xffffffffc07ff548"
.rodata.str1.1 = "0xffffffffc07ff284"
.rodata.str1.8 = "0xffffffffc07ff028"
.rodata = "0xffffffffc07ff560"
.smp_locks = "0xffffffffc07ff280"
.strtab = "0xffffffffc070d350"
.symtab = "0xffffffffc070c000"
.text = "0xffffffffc07fc000"
__jump_table = "0xffffffffc0801000"
__mcount_loc = "0xffffffffc08005d0"
__param = "0xffffffffc07ffe10"
__verbose = "0xffffffffc0801220"
My system boots legacy grub in text mode (KMS) and seems to keep hanging
even with that option set.
Do you have any further idea?
-Andy
Arch linux
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-03 19:20 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 [this message]
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
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=20180403211326.4907f1bc@laptop64.home \
--to=andyrtr@archlinux.org \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jandryuk@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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).