-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
raspberrypi-clk: Failed to get / change pllb frequency: -12 #3479
Comments
Trying the commands:
seems to work fine in that situation. |
I grepped through the logs and found the following, potentially related messages:
So I add my usb device tree here in addition in case it helps:
The hub is a self-powered USB 2 hub with a USB 3 HDD attached to it (I plan to replace the hub with a USB 3 capable model in the future). The HDD access is still fine, though. |
After reading through #3040 which might be related(?), I have now added:
to my |
Hi @olifre, the -12 means ENOMEM and this is a typical cases when you running out of memory. I assume there is at least one memory leak. In case you are able to rebuild your kernel, try to enable CONFIG_DEBUG_KMEMLEAK in the kernel config under kernel hacking -> memory debugging. After that you should be able to see the leaks in /sys/kernel/debug/kmemleak. |
HI @lategoodbye , thanks! I wondered whether this is a leak or "just" fragmentation within the coherent memory region. While I regularly compile my own kernel on Desktops, I've not done so on Raspbian / Debian yet. I'm already stuck at the point where to get the upstream kernel config and Raspbian patches (if these exist) to build "the same" kernel with just a single flag changed — the docs at https://www.raspberrypi.org/documentation/linux/kernel/building.md only mention So if somebody can help me out here, I can do it, but I would presume the issue is reproducible with any USB 2 hub + USB 3 mass storage device connected to a USB 3 port of the RPi 4. |
The docs you linked to are how the standard raspbian kernel is built. |
@popcornmix Thanks, compiling now. Hope it'll be straightforward to go back to the upstream built kernel (i.e."just upgrade"). Will report back once I found something. I wonder if:
has any performance implications (if not, it might be helpful to have that by default in case these issues appear regularly). |
Modified kernel is running, at least there is no immediate leak visible (even when triggering an active |
I have by now executed all the workloads I execute on the device, including SMART tests of the attached HDD, running No leak seen yet. Any other ideas, or should we just wait for ~a week to see if anything changes? |
@lategoodbye , Since I increased to Any other ideas on how to debug? If not, I would revert to a stock kernel (the |
@lategoodbye , the issue is now back after 23 days of uptime, so the increase to However:
gives me only empty output. Any ideas? Can I reboot the system and revert to a "stock" kernel, or do you have anything you'd like to get extracted? |
Since there were still no leaks and no further ideas, I've now:
I'll report back if it happens again, or in a month if it does not. Any other ideas welcome. |
I had the same issue. Logs being filled with the exact same messages. Filled my SD with logs.
In case it helps: I have a WiFi dongle in a USB 2 port, and an external hard drive in a USB 3 port. The only change I've made to the RPI itself is that I've disabled the built in WiFi via Everything else is stock. Raspbian Lite 2020-02-05 iso. Non official 4a PSU. I'm trying the |
I'm also getting these errors all of a sudden, will report back if I find anything out. |
seeing this on a Raspberry Pi 4 Model B Rev 1.1 with a modified kernel
eeprom update maybe worth trying? i dont have any usb devices plugged in
|
I'm currently running with Current info (apart from the high
Interestingly, with this hub / firmware / Kernel, I regularly get USB disconnects and reconnects when the drive goes to standby and comes back. |
i rebuilt to 5.4.39 with CONFIG_DEBUG_KMEMLEAK=Y oot@test:~# cat /boot/bcm2711-rpi-4-b.dtb | grep pool 24 hours in haven't seen this error yet |
It came back now after 48 days. Since I often reboot more often for updates anyways, |
and its back
nothing there but i have a feeling i'm not using these tool correctly
|
|
still present when using 5.4.52 aarch64 GNU/Linux (patched kernel with mptcp on OpenWRT) |
this might be related
|
logs still being flooded on 5.4.69
|
I am seeing this too. |
Same here!
|
I have the same problem pi@domotica:~ $ cat /etc/os-release |
You seem to be running buster (which is deprecated) with a latest (rpi-update?) kernel. What does |
Describe the bug
After anything between 1-2 weeks of runtime, kernel log is flooded with messages such as:
The system still runs normally, though.
To reproduce
Let the system run for 1-2 weeks. No overclocking, no cooling issues, official power supply, no extra loads attached, no preceding kernel messages.
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
cat /etc/rpi-issue
)?vcgencmd version
)?uname -a
)?Logs
See report above.
Additional context
Sadly, no real trigger leading up to the issue. Reboot solves it.
The text was updated successfully, but these errors were encountered: