[ISSUE] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[ISSUE] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

New issue by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.69_1 aarch64 Unknown uptodate rFFF

### Package(s) Affected

rpi5-kernel-6.6.69_1, rpi-firmware-20250102_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://forums.raspberrypi.com/viewtopic.php?t=366030
https://forums.raspberrypi.com/viewtopic.php?t=369470

### Expected behaviour

The error message should not show up.

### Actual behaviour

If i look at the kernel log, there are a lot of error messages like this:
```
[  195.894223] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
[  199.041062] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
[  278.840334] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
```



### Steps to reproduce

In the linked forum posts a Raspberry Pi Engineer says said that error message can occour if:

- Too high an overclock
- Inadequate power supply
- Sending invalid messages (less likely on the pi5 where firmware does a lot less).
- Corrupting firmware's memory (would likely need sudo/mmap to be allowed to do this outside of kernel)
- Faulty hardware

I do not overclock my PI.
I use the official PSU.
I don't have faulty hardware since if i boot Raspberry Pi OS, the errors are gone.

So it must either be "Sending invalid messages" or "Corrupting firmware's memory".

I am not an expert so i don't know what package could be the culprit nor if this is even the right place to post this.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 467 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2641913321

Comment:
can't reproduce this (rpi5, rpi-kernel, aarch64-musl):
```
# dmesg | rg raspberrypi         
[    0.015999] raspberrypi-firmware soc:firmware: Attached to firmware from 2024-11-12T16:10:44, variant start_cd
[    0.020001] raspberrypi-firmware soc:firmware: Firmware hash is 4b01994600000000000000000000000000000000
```

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2641913321

Comment:
can't reproduce this (rpi5, rpi-kernel, aarch64-musl):
```
# dmesg | rg raspberrypi         
[    0.015999] raspberrypi-firmware soc:firmware: Attached to firmware from 2024-11-12T16:10:44, variant start_cd
[    0.020001] raspberrypi-firmware soc:firmware: Firmware hash is 4b01994600000000000000000000000000000000
```
the kernel config for rpi-kernel vs rpi5-kernel is almost identical, only a couple values related to page size are changed

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643675943

Comment:
Just to avoid any misunderstandings.

The errors don't occour at booting or shortly after. 

I need to use the OS for a couple of minutes or hours. The frequency of these errors seem random to me.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643675943

Comment:
Just to avoid any misunderstandings.

The errors don't occur at booting or shortly after. 

I need to use the OS for a couple of minutes or hours. The frequency of these errors seem random to me.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643675943

Comment:
Just to avoid any misunderstandings.

The errors don't occur at booting or shortly after. 

I need to use the OS for a couple of minutes or hours. The frequency of these errors seem random to me.

For example:

```
[   11.855541] elogind-daemon[494]: Watching system buttons on /dev/input/event6 (vc4-hdmi-1)
[   11.856762] elogind-daemon[494]: New session 1 of user foo.
[   12.001306] platform kgdboc: deferred probe pending
[   12.911691] Xorg[461]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set

---- Here booting has finished ----

--- a couple of minutes later
[  421.766731] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
```

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643682229

Comment:
I checked on a pi that has been up for several weeks

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643686347

Comment:
Ok, i try to reproduce these error using your setup with a musl build (i use glibc) and the default rpi-kernel. Maybe it does make a difference.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643708632

Comment:
I get a different error using a musl build and the rpi-kernel:

![Image](https://github.com/user-attachments/assets/974eb7ba-5f98-4842-b525-50ae72f4c982)

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643708632

Comment:
~~I get a different error using a musl build and the rpi-kernel:~~

![Image](https://github.com/user-attachments/assets/974eb7ba-5f98-4842-b525-50ae72f4c982)

Edit:
Please ignore this, this error is unrelated, i accidentally booted with my SD card reader plugged in.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2643708632

Comment:
~~I get a different error using a musl build and the rpi-kernel:~~

![Image](https://github.com/user-attachments/assets/974eb7ba-5f98-4842-b525-50ae72f4c982)

Edit:
Please ignore this error which is unrelated, i accidentally booted with my SD card reader plugged in.

And yes, i could not reproduce the original error with a musl build until now.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 427 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2644212094

Comment:
I think i solved this issue.

I added `over_voltage_delta=5`to my `/boot/config.txt` and the errors are gone.

Can it be that Void needs a bit more voltage than Raspberry Pi OS? I use the official PSU and i don't see these errors there.

Feel free to close this issue, i am happy.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 428 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2644212094

Comment:
I think i solved this issue.

I added `over_voltage_delta=5` to my `/boot/config.txt` and the errors are gone.

Can it be that Void needs a bit more voltage than Raspberry Pi OS? I use the official PSU and i don't see these errors there.

Feel free to close this issue, i am happy.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 190 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2644215721

Comment:
might be based on whatever you're running

Re: [ISSUE] [CLOSED] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

Closed issue by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.69_1 aarch64 Unknown uptodate rFFF

### Package(s) Affected

rpi5-kernel-6.6.69_1, rpi-firmware-20250102_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://forums.raspberrypi.com/viewtopic.php?t=366030
https://forums.raspberrypi.com/viewtopic.php?t=369470

### Expected behaviour

The error message should not show up.

### Actual behaviour

If i look at the kernel log, there are a lot of error messages like this:
```
[  195.894223] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
[  199.041062] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
[  278.840334] raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000
```



### Steps to reproduce

I run Void Linux on a Raspberry Pi 5 and see a lot of these error messages in the kernel log.

In the linked forum posts a Raspberry Pi Engineer says said that **something has killed the firmware** and that the error message can occour if:

- Too high an overclock
- Inadequate power supply
- Sending invalid messages (less likely on the pi5 where firmware does a lot less).
- Corrupting firmware's memory (would likely need sudo/mmap to be allowed to do this outside of kernel)
- Faulty hardware

I do not overclock my PI.
I use the official PSU.
I don't have faulty hardware since if i boot Raspberry Pi OS, the errors are gone.

So it must either be "Sending invalid messages" or "Corrupting firmware's memory".

I am not an expert so i don't know what package could be the culprit nor if this is even the right place to post this.

Edit:

Just discovered another error message which might be related:
```
[12157.764742] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-arm frequency: -22
```

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 467 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2651590860

Comment:
Just in case anyone stumbles on this:

The `over_voltage_delta` setting was a red hering and didn't to anything, the errors came back.

I asked the Raspberry Pi folks and it was the fault of the current eeprom, which will be fixed in a new release.

See https://github.com/raspberrypi/firmware/issues/1944 for more info.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2644212094

Comment:
~~I think i solved this issue.~~ Edit: See my next post

I added `over_voltage_delta=5` to my `/boot/config.txt` and the errors are gone.

Can it be that Void needs a bit more voltage than Raspberry Pi OS? I use the official PSU and i don't see these errors there.

Feel free to close this issue, i am happy.

Re: raspberrypi-firmware soc:firmware: Request 0x00030002 returned status 0x00000000

[randomMesh]

[-- Attachment #1: Type: text/plain, Size: 468 bytes --]

New comment by randomMesh on void-packages repository

https://github.com/void-linux/void-packages/issues/54234#issuecomment-2651590860

Comment:
Just in case anyone stumbles on this:

The `over_voltage_delta` setting was a red herring and didn't to anything, the errors came back.

I asked the Raspberry Pi folks and it was the fault of the current eeprom, which will be fixed in a new release.

See https://github.com/raspberrypi/firmware/issues/1944 for more info.