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, open list <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Date: Fri, 6 Apr 2018 17:23:42 +0200 [thread overview] Message-ID: <20180406172342.4a2a3f15@laptop64.home> (raw) In-Reply-To: <CAKf6xpu4=kLuqZqFsxqFCzLMyLBZyi3C9W_yyssEt=56dhF6RA@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 535 bytes --] My boot issue happens right after the BIOS when the initrd should be loaded and then no grub (v2.0) menu appears. It seems I could fix it for me disabling Host Notify + Interrupts with options i2c_i801 disable_features=0x30 and then rebuilding initrd. The touchpad is still working. Still testing more days if it will hang again. Is there anything further I can do to help? I can't tell when this hang was introduced. When I received the HP Arch was running 4.9 lts kernel and it already hung there. -Andy Arch linux [-- Attachment #2: Digitale Signatur von OpenPGP --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-06 15:24 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 [this message] 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=20180406172342.4a2a3f15@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: linkBe 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).