All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-rpi-kernel@lists.infradead.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	rcu <rcu@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Phil Elwell <phil@raspberrypi.com>
Subject: Re: WARNING: CPU: 2 PID: 3331 at drivers/firmware/raspberrypi.c:63 rpi_firmware_property_list
Date: Mon, 23 May 2022 21:47:28 +0200	[thread overview]
Message-ID: <129470ff-7570-4643-2dfc-3a187b3fc39f@i2se.com> (raw)
In-Reply-To: <CA+G9fYvF7HGmJQtk7ktmakwQNjjraK3EoBeiMr+3NuEvsixi6Q@mail.gmail.com>

Hi Naresh,

Am 23.05.22 um 14:35 schrieb Naresh Kamboju:
> On Mon, 23 May 2022 at 16:43, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>> Hi Naresh,
>>
>> Am 23.05.22 um 11:04 schrieb Naresh Kamboju:
>>> The following kernel warning was noticed on raspberrypi4 device while
>>> running LTP controllers with Linus mainline kernel tree.
>>>
>>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>>
>>> metadata:
>>>     git_ref: master
>>>     git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>>     git_sha: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
>>>     git_describe: v5.18
>>>     kernel_version: 5.18.0
>>>     kernel-config: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu/config
>>>     artifact-location: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu
>>>     toolchain: gcc-11
>>>     System.map: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu/System.map
>>>     vmlinux.xz: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu/vmlinux.xz
>> thanks for your report.
>>
>> Do you know this worked before (e.g. 5.17)?
> Yes. it worked before.
>
>> Am I correct that you are using GPU firmware 2021-02-25T12:10:40?
> Correct.

Since i also experienced firmware crashes [1] with 5.18, it possible for 
you to update to a more recent firmware?

Best regards

[1] - 
https://lore.kernel.org/all/3dd4e0cb-8ba5-e0c7-cde5-29c56a5caa95@i2se.com/

>
> - Naresh

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	linux-rpi-kernel@lists.infradead.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	lkft-triage@lists.linaro.org, regressions@lists.linux.dev,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	rcu <rcu@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Phil Elwell <phil@raspberrypi.com>
Subject: Re: WARNING: CPU: 2 PID: 3331 at drivers/firmware/raspberrypi.c:63 rpi_firmware_property_list
Date: Mon, 23 May 2022 21:47:28 +0200	[thread overview]
Message-ID: <129470ff-7570-4643-2dfc-3a187b3fc39f@i2se.com> (raw)
In-Reply-To: <CA+G9fYvF7HGmJQtk7ktmakwQNjjraK3EoBeiMr+3NuEvsixi6Q@mail.gmail.com>

Hi Naresh,

Am 23.05.22 um 14:35 schrieb Naresh Kamboju:
> On Mon, 23 May 2022 at 16:43, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>> Hi Naresh,
>>
>> Am 23.05.22 um 11:04 schrieb Naresh Kamboju:
>>> The following kernel warning was noticed on raspberrypi4 device while
>>> running LTP controllers with Linus mainline kernel tree.
>>>
>>> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>>>
>>> metadata:
>>>     git_ref: master
>>>     git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>>     git_sha: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
>>>     git_describe: v5.18
>>>     kernel_version: 5.18.0
>>>     kernel-config: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu/config
>>>     artifact-location: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu
>>>     toolchain: gcc-11
>>>     System.map: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu/System.map
>>>     vmlinux.xz: https://builds.tuxbuild.com/29XDpgnCMxtWJ6lVJ9M0x3hTNWu/vmlinux.xz
>> thanks for your report.
>>
>> Do you know this worked before (e.g. 5.17)?
> Yes. it worked before.
>
>> Am I correct that you are using GPU firmware 2021-02-25T12:10:40?
> Correct.

Since i also experienced firmware crashes [1] with 5.18, it possible for 
you to update to a more recent firmware?

Best regards

[1] - 
https://lore.kernel.org/all/3dd4e0cb-8ba5-e0c7-cde5-29c56a5caa95@i2se.com/

>
> - Naresh

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-23 19:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  9:04 WARNING: CPU: 2 PID: 3331 at drivers/firmware/raspberrypi.c:63 rpi_firmware_property_list Naresh Kamboju
2022-05-23  9:04 ` Naresh Kamboju
2022-05-23 11:13 ` Stefan Wahren
2022-05-23 11:13   ` Stefan Wahren
2022-05-23 12:35   ` Naresh Kamboju
2022-05-23 12:35     ` Naresh Kamboju
2022-05-23 19:47     ` Stefan Wahren [this message]
2022-05-23 19:47       ` Stefan Wahren
2022-05-23 13:46 ` Paul E. McKenney
2022-05-23 13:46   ` Paul E. McKenney

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=129470ff-7570-4643-2dfc-3a187b3fc39f@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nsaenz@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=phil@raspberrypi.com \
    --cc=rcu@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rf@opensource.cirrus.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.