public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Martin Volf <martin.volf.42@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jean Delvare <jdelvare@suse.com>,
	Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [regression] nct6775 does not load in 5.4 and 5.5, bisected to b84398d6d7f90080
Date: Sat, 22 Feb 2020 07:41:18 -0800	[thread overview]
Message-ID: <1bdbac08-86f8-2a57-2b0d-8cd2beb2a1c0@roeck-us.net> (raw)
In-Reply-To: <CAM1AHpQ4196tyD=HhBu-2donSsuogabkfP03v1YF26Q7_BgvgA@mail.gmail.com>

On 2/22/20 3:13 AM, Martin Volf wrote:
> Hello,
> 
> hardware monitoring sensors NCT6796D on my Asus PRIME Z390M-PLUS
> motherboard with Intel i7-9700 CPU don't work with 5.4 and newer linux
> kernels, the driver nct6775 does not load.
> 
> It is working OK in version 5.3. I have used almost all released stable
> versions from 5.3.8 to 5.3.16; I didn't try older kernels.
> 
> Even on new kernels the sensors-detect finds the sensors:
>          Found `Nuvoton NCT6796D Super IO Sensors' Success!
>              (address 0x290, driver `nct6775')
> but "modprobe nct6775" says:
>          ERROR: could not insert 'nct6775': No such device
> There is nothing interesting in dmesg.
> 

My wild guess would be that the i801 driver is a bit aggressive with
reserving memory spaces, but I don't immediately see what it does
differently in that regard after the offending patch. Does it work
if you unload the i2c_i801 driver first ?

You could also try to compare the output of /proc/ioports with
the old and the new kernel, and see if the IO address space used
by nct6775 in v5.3 is assigned to the i801 driver (or some other
driver, such as the watchdog driver) in v5.4.

If you are into hacking the kernel, you could also add some
debug messages into the nct6775 driver to find out where exactly
it fails. If that helps, maybe we can then add those messages into
into the driver source to help others if this is observed again.

Thanks,
Guenter

  parent reply	other threads:[~2020-02-22 15:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-22 11:13 [regression] nct6775 does not load in 5.4 and 5.5, bisected to b84398d6d7f90080 Martin Volf
2020-02-22 11:51 ` Wolfram Sang
2020-02-22 15:41 ` Guenter Roeck [this message]
2020-02-22 17:55   ` Martin Volf
2020-02-22 19:05     ` Guenter Roeck
2020-02-22 20:49       ` Martin Volf
2020-02-22 21:26         ` Guenter Roeck
2020-02-23  7:06           ` Martin Volf
2020-02-23 16:39           ` Wolfram Sang
2020-02-24 10:18           ` Mika Westerberg
2020-02-24 10:37             ` Andy Shevchenko
2020-02-24 10:51               ` Mika Westerberg
2020-02-24 11:27                 ` Mika Westerberg
2020-02-24 17:30                   ` Martin Volf
2020-02-25 12:13                     ` Mika Westerberg
2020-02-24 18:27                   ` Guenter Roeck
2020-02-25 12:14                     ` Mika Westerberg
2020-02-23 17:56 ` Gabriel C

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=1bdbac08-86f8-2a57-2b0d-8cd2beb2a1c0@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.volf.42@gmail.com \
    --cc=mika.westerberg@linux.intel.com \
    --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