From: Kim Alvefur <zash@zash.se>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: 1106411@bugs.debian.org, Stephan Gerhold <stephan@gerhold.net>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: kernel NULL pointer dereference in bmc150_accel_core / RIP: 0010:bmc150_accel_set_interrupt+0x68/0x120 [bmc150_accel_core]
Date: Sun, 1 Jun 2025 00:05:02 +0200 [thread overview]
Message-ID: <aDt9DrWxKOUZHQ3K@spisula.zash.se> (raw)
In-Reply-To: <aDtZqwjKtpyguppg@eldamar.lan>
On Sat, May 31, 2025 at 09:34:03PM +0200, Salvatore Bonaccorso wrote:
>On Fri, May 30, 2025 at 07:42:12PM +0200, Kim Alvefur wrote:
>> So far it seems to happen on every boot, between unlocking LUKS and the
>> login manager starting.
>>
>> I wonder if this is related to another symptom this machine has, where
>> it fails to complete suspend and goes into a state where the only action
>> that has any effect is a long-press of the power button to turn it off.
>
>Looking through the boot log I'm noticing the following:
>
>> May 30 19:21:47 spisula kernel: bmc150_accel_i2c i2c-BOSC0200:00: supply vdd not found, using dummy regulator
>> May 30 19:21:47 spisula kernel: bmc150_accel_i2c i2c-BOSC0200:00: supply vddio not found, using dummy regulator
>[...]
>> May 30 19:21:47 spisula kernel: bmc150_accel_i2c i2c-BOSC0200:base: supply vdd not found, using dummy regulator
>> May 30 19:21:47 spisula kernel: bmc150_accel_i2c i2c-BOSC0200:base: supply vddio not found, using dummy regulator
>
>and iio-sensor-proxy might fail to handle then the bosch 0200
>accelerometer. You proobably cannot temporary purge the
>iio-sensor-proxy if installed by reverse dependencies, but might you
>try to temporarily mask the service and retest a boot?
That seems to have an effect, no "BUG: ..." in dmesg now, and the
machine made it trough a suspends and resume cycle.
--
Kim "Zash" Alvefur
prev parent reply other threads:[~2025-05-31 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <174809774197.3242.15028356144506391196.reportbug@spisula.zash.se>
[not found] ` <aDMuJsV4Mxb1IVoZ@eldamar.lan>
[not found] ` <aDnt9LkEZjb4DOO-@spisula.zash.se>
2025-05-31 19:34 ` Salvatore Bonaccorso
2025-05-31 22:05 ` Kim Alvefur [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=aDt9DrWxKOUZHQ3K@spisula.zash.se \
--to=zash@zash.se \
--cc=1106411@bugs.debian.org \
--cc=andy.shevchenko@gmail.com \
--cc=carnil@debian.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stephan@gerhold.net \
/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®