linux-kernel - Re: Bug reporting on Raydium touchscreen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d3d7b101-eb19-4169-94ce-25e6f969f035@suse.com>
Date: Thu, 15 Feb 2024 10:37:16 +0100
From: Oliver Neukum <oneukum@...e.com>
To: Vanja Pogacic <vanja@...acic.net>, linux-pci@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: Bug reporting on Raydium touchscreen

On 15.02.24 09:59, Vanja Pogacic wrote:
> Hello,
> I am trying to find the best way to submit a kernel bug for a raydium touchscreen driver (raydium_i2c_ts) which stops working after waking up from sleep.
> The hardware in question is a converted Chromebook (Acer Spin 512) with coreboot uefi bios.
> 
> You can find more details and logs about the issue here:
> bbs.archlinux.org/viewtopic.php
> 
> Since I observed the same behavior under Fedora, Ubuntu and Arch, I concluded it would be best to contact the upstream people :)
> 
> Any guidance will be highly appreciated.

Hi,

in your specific case I would suggest making a bug report on bugzilla.kernel.org
to collect your logs in one place. Then based on your logs, decide whether your issue is rather
input or power management and make a bug report to the appropriate list.

	HTH
		Oliver