-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Newer 4.19.x kernels do not load bcm2835_wdt automatically resulting in a system that will not reboot #3187
Comments
Yes, this was a regression with conversion of power management to a MFD driver. Unfortunately i missed to a add a Fixes tag. @popcornmix @pelwell |
popcornmix
added a commit
to raspberrypi/firmware
that referenced
this issue
Aug 28, 2019
kernel: watchdog: bcm2835_wdt: Fix module autoload See: raspberrypi/linux#3187 kernel: staging: bcm2835-codec: remove unnecessary padding on encoder input See: raspberrypi/linux#3179 kernel: staging: bcm2835-codec: add support for V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME See: raspberrypi/linux#3175 firmware: AWB: Fix for manual WB settings in capture See: #1215
popcornmix
added a commit
to Hexxeh/rpi-firmware
that referenced
this issue
Aug 28, 2019
kernel: watchdog: bcm2835_wdt: Fix module autoload See: raspberrypi/linux#3187 kernel: staging: bcm2835-codec: remove unnecessary padding on encoder input See: raspberrypi/linux#3179 kernel: staging: bcm2835-codec: add support for V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME See: raspberrypi/linux#3175 firmware: AWB: Fix for manual WB settings in capture See: raspberrypi/firmware#1215
I've send this patch to [email protected], so it should be applied to Linux 5.2 (linux-stable) soon. |
Thanks. It's been cherry-picked to 4.19 and 5.2 for now. |
Thanks folks! closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run Gentoo, and build my kernel from this repo. Since the last two tagged releases (20190718-1, 20190819-1) both on arm32 and arm64, my Pi's no longer automatically load the watchdog driver. This will require a physical power cycle to reboot the machine if I forget to load the driver myself.
I can work around it by just making the OS modprobe the driver, but I would expect it to be handled by DT like before. I checked, and unlike another similar report, it is not blacklisted. I have tried adding dtparam=watchdog=on to my config.txt but that didn't load it either. I guess I could also just build the driver into the kernel as well since it seems to be required in order to reboot the device whether it is being used in userspace?
This happens on RPi B (old 256MB, and later 512MB), RPi0-W, as well as Rpi3-B running 64bit. For the time being I just manually load the module to work around.
The text was updated successfully, but these errors were encountered: