From: Daniel Scally <djrscally@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Hans de Goede <hdegoede@redhat.com>, Mark Gross <mgross@linux.intel.com>
Subject: Re: [Bug 214453] New: skl_int3472_unregister_clock: kernel NULL pointer dereference (HP Elite x2 1013 G3)
Date: Tue, 5 Oct 2021 15:44:59 +0100 [thread overview]
Message-ID: <81329df6-b24d-e860-fcb1-b01c8b5caa91@gmail.com> (raw)
In-Reply-To: <YVsy5Gv3z6JAWnxj@zn.tnic>
Hi Borislav
On 04/10/2021 17:59, Borislav Petkov wrote:
> Adding more people to Cc.
>
> On Fri, Sep 17, 2021 at 12:18:27PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=214453
>>
>> Bug ID: 214453
>> Summary: skl_int3472_unregister_clock: kernel NULL pointer
>> dereference (HP Elite x2 1013 G3)
>> Product: Platform Specific/Hardware
>> Version: 2.5
>> Kernel Version: 5.14.5
>> Hardware: Intel
>> OS: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: low
>> Priority: P1
>> Component: x86-64
>> Assignee: platform_x86_64@kernel-bugs.osdl.org
>> Reporter: kernel-NTEO@vplace.de
>> Regression: No
>>
>> Created attachment 298863
>> --> https://bugzilla.kernel.org/attachment.cgi?id=298863&action=edit
>> dmesg oops log
>>
>> On a HP Elite x2 1013 G3 a kernel oops is caused by int3472:
>>
>> [ 8.820565] int3472-discrete INT3472:02: No sensor module config
>> [ 8.820569] int3472-discrete INT3472:02: error -EINVAL: Failed to map
>> regulator to sensor
>> [ 8.820574] BUG: kernel NULL pointer dereference, address: 0000000000000000
>> [...]
>> [ 8.820654] Call Trace:
>> [ 8.820657] clkdev_drop+0x1d/0x60
>> [ 8.820665] skl_int3472_unregister_clock+0x15/0x30 [intel_skl_int3472
>> a61329898df9463f8661b1eee1ed1e20b1626f62]
Thanks for the report; let me take a look and see if I can spot what's
going wrong.
>> --
>> You may reply to this email to add a comment.
>>
>> You are receiving this mail because:
>> You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-10-05 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-214453-6385@https.bugzilla.kernel.org/>
2021-10-04 16:59 ` Borislav Petkov
2021-10-05 14:44 ` Daniel Scally [this message]
2021-10-08 22:18 ` Daniel Scally
2021-10-09 8:14 ` Borislav Petkov
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=81329df6-b24d-e860-fcb1-b01c8b5caa91@gmail.com \
--to=djrscally@gmail.com \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
/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
all inboxes | Powered by JetHome®