LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de> To: Jason Andryuk <jandryuk@gmail.com> Cc: Andreas Radke <andyrtr@archlinux.org>, Wolfram Sang <wsa@the-dreams.de>, benjamin.tissoires@redhat.com, aduggan@synaptics.com, linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850 Date: Wed, 4 Apr 2018 16:02:11 +0200 [thread overview] Message-ID: <20180404160211.57ae77ea@endymion> (raw) In-Reply-To: <CAKf6xpu4=kLuqZqFsxqFCzLMyLBZyi3C9W_yyssEt=56dhF6RA@mail.gmail.com> Hi Jason, Andreas, On Wed, 4 Apr 2018 08:55:20 -0400, Jason Andryuk wrote: > On Tue, Apr 3, 2018 at 3:13 PM, Andreas Radke <andyrtr@archlinux.org> wrote: > > 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. > > Maybe verify the option is set by checking > /sys/module/i2c_i801/parameters/disable_features ? Looks like dmesg > should also report "SMBus Host Notify disabled by user" when disabled. > I run with i801 built-in, so I was specifying the option on the kernel > command line. Another thing to think of is that you may have to rebuild the initrd/initramfs after editing /etc/modprobe.d/i2c_i801.conf if i2c-i801 happens to be part of it (and make sure that /etc/modprobe.d/i2c_i801.conf is indeed included in initrd/initramfs then.) > > My system boots legacy grub in text mode (KMS) and seems to keep hanging > > even with that option set. > > Your cold boot hang is in legacy grub itself? Legacy grub text mode > actually doesn't hang my G3 850 - it was switching to the graphical > splash screen that seemed to do it. PXE booting via F12 was another > consistent way to hang. It was very early in the PXE boot code - > before it checked the link status. So you could try that with it just > plugged into a switch even if you don't have a PXE boot setup. > > From my previous post: > """ > The Boot Agent hang prints "Client Mac Addr 00-11-22-33-44-55<cursor>" > and hangs. A normal boot prints a GUID on the same line and > continues. > """ > > Otherwise, unfortunately, it might just be a different issue. I recall reports about hangs when we first added support for interrupts. I think we addressed all the bugs in this area since then but maybe not. So you may want to try disable_features=0x30 to disable both interrupts and SMBus Host Notify. -- Jean Delvare SUSE L3 Support
next prev parent reply other threads:[~2018-04-04 14:02 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 [this message] 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=20180404160211.57ae77ea@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=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).