[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250501095049.156c5d8d@hboeck.de>
Date: Thu, 1 May 2025 09:50:49 +0200
From: Hanno Böck <hanno@...eck.de>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
david@...t.cz
Subject: Re: linux/rmi4 driver: "BUG: kernel NULL pointer dereference" when
accessing update_fw_status or bootloader_id
On Wed, 30 Apr 2025 20:03:11 -0700
Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
> Do you have anything earlier in your dmesg referencing "F34" by
> chance?
Probably this?
[ 3.297406] hub 2-1.2:1.0: 4 ports detected
[ 3.324410] rmi4_f34 rmi4-00.fn34: rmi_f34v7_probe: Unrecognized bootloader v) 16 (\x10)(
[ 3.326641] rmi4_f34 rmi4-00.fn34: probe with driver rmi4_f34 failed with error -22
[ 3.350673] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
Synaptics, product: TM3288-011, fw id: 2812761
I'm attaching the full dmesg output.
--
Hanno Böck
https://hboeck.de/
View attachment "dmesg-bootloader_id.txt" of type "text/plain" (78304 bytes)
Powered by blists - more mailing lists