From: Tobias Dahms <dahms.tobias@web.de>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
stable@vger.kernel.org, regressions@lists.linux.dev
Cc: linux-wireless@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: kernel error at led trigger "phy0tpt"
Date: Tue, 21 Mar 2023 21:22:23 +0100 [thread overview]
Message-ID: <f8f7d7ae-7e4b-e0fb-6a21-1d4fdcc22035@web.de> (raw)
In-Reply-To: <be785bbb-d77d-9930-56d0-dcef26f07bb2@leemhuis.info>
Hi Thorsten,
all mentioned kernels are vanilla kernels. The "-bpi-r2" is only a
suffix from CONFIG_LOCALVERSION="-bpi-r2"
I will bisect on weekend and come back to you.
regards
Tobias
Am 21.03.23 um 15:40 schrieb Linux regression tracking (Thorsten Leemhuis):
> On 20.03.23 20:44, Tobias Dahms wrote:
>> Hello,
>>
>> since some kernel versions I get a kernel errror while setting led
>> trigger to phy0tpt.
>>
>> command to reproduce:
>> echo phy0tpt > /sys/class/leds/bpi-r2\:isink\:blue/trigger
>>
>> same trigger, other led location => no error:
>> echo phy0tpt > /sys/class/leds/bpi-r2\:pio\:blue/trigger
>>
>> other trigger, same led location => no error:
>> echo phy0tx > /sys/class/leds/bpi-r2\:isink\:blue/trigger
>>
>> last good kernel:
>> bpi-r2 5.19.17-bpi-r2
>>
>> error at kernel versions:
>> bpi-r2 6.0.19-bpi-r2
>> up to
>> bpi-r2 6.3.0-rc1-bpi-r2+
>
> Thx for the report.
>
> "5.19.17-bpi-r2" sounds like a vendor kernel. Is that one that is
> vanilla or at least close to vanilla? If not, you'll have to report this
> to your kernel vendor. If not: could you try to bisect this?
>
>> wireless lan card:
>> 01:00.0 Network controller: MEDIATEK Corp. MT7612E 802.11acbgn PCI
>> Express Wireless Network Adapter
>>
>> distribution:
>> Arch-Linux-ARM (with vanilla kernel instead of original distribution
>> kernel)
>>
>> board:
>> BananaPi-R2
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-03-21 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 19:44 kernel error at led trigger "phy0tpt" Tobias Dahms
2023-03-21 14:40 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-21 20:22 ` Tobias Dahms [this message]
[not found] ` <3fcc707b-f757-e74b-2800-3b6314217868@leemhuis.info>
2023-03-25 19:20 ` Tobias Dahms
2023-03-26 13:23 ` Bagas Sanjaya
2023-03-27 8:23 ` AngeloGioacchino Del Regno
2023-04-17 11:25 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 8:17 ` Thorsten Leemhuis
2023-06-05 11:37 ` Thorsten Leemhuis
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=f8f7d7ae-7e4b-e0fb-6a21-1d4fdcc22035@web.de \
--to=dahms.tobias@web.de \
--cc=linux-leds@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@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