From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: Hitting WARN_ON_ONCE in i2c-designware-common.c
Date: Tue, 15 Apr 2025 14:45:55 +0200 [thread overview]
Message-ID: <4493e1f6-eb08-4384-9257-575491a57c40@kernel.org> (raw)
In-Reply-To: <715d883f-184f-474a-a222-208d3aa03d2c@linux.intel.com>
On 15/04/2025 14.28, Jarkko Nikula wrote:
> Hi
>
> On 4/15/25 3:03 PM, Jesper Dangaard Brouer wrote:
>> Hi Maintainers,
>>
>> I'm hitting a WARN_ON_ONCE in drivers/i2c/busses/i2c-designware-common.c
>> when booting the kernel on our Gen12 hardware.
>>
>> I'm using devel kernel net-next at commit 1a9239bb425 (merge tag 'net-
>> next-6.15').
>>
> Is this a regression so was this working before?
>
I'm seeing this when doing kernel development and booting net-next on
our Gen12 servers[1]. [1] https://blog.cloudflare.com/gen-12-servers/
I've not seen this WARN on our production kernels (stable 6.6 and 6.12).
This is likely due to different kernel configs.
> Support for this platform was added back in 2016 by the commit
> e4e666ba74d4 ("i2c: designware: Add device HID for future AMD I2C
> controller").
>
Maybe we have just not enabled the module on our prod kernels.
>> [ 10.062651] i2c_designware AMDI0010:00: Unknown Synopsys component type: 0xffffffff
>> [ 10.073312] pps_core: LinuxPPS API ver. 1 registered
>> [ 10.073372] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
>> [ 10.075433] i2c_designware AMDI0010:01: Unknown Synopsys component type: 0xffffffff
>
> These "Unknown Synopsys component type: 0xffffffff" errors indicate IP
> is not alive. Perhaps linked to the missing clock or not powered.
It is possible that this hardware is special as I believe it is
customized for us.
The dmesg output also contained:
Hardware name: Lenovo HR355M-V3-G12/HR355M_V3_HPM
(see the extra -G12 to the SKU.)
--Jesper
prev parent reply other threads:[~2025-04-15 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:03 Hitting WARN_ON_ONCE in i2c-designware-common.c Jesper Dangaard Brouer
2025-04-15 12:17 ` Andy Shevchenko
2025-04-15 12:19 ` Andy Shevchenko
2025-04-15 12:30 ` Jesper Dangaard Brouer
2025-04-16 6:37 ` Andy Shevchenko
2025-04-15 12:28 ` Jarkko Nikula
2025-04-15 12:45 ` Jesper Dangaard Brouer [this message]
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=4493e1f6-eb08-4384-9257-575491a57c40@kernel.org \
--to=hawk@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.