I’m getting a kernel oops on startup that is similar to https://patchwork.kernel.org/patch/10282365/
I updated an instance on my pi3 then cloned it.
Any thoughts ?
So, looking closer at my oops screenshot.
It was the snmpd process that triggered it in my case.
I’ve disabled snmpd and it now appears to work fine.
I suspect we still have the bug I refererenced above, but snmpd seems to start early in the boot process (S02snmpd) and is probably similarly triggering the issue.
Hi @penfold42. I hope you’re doing well.
I’ve added the patch as a precaution. Can you give it a test?
- Login via the command line
- Edit the file
- Add the following line:
deb http://apt.osmc.tv stretch-devel main
- Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot
- Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit
/etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.
Thanks for the quick work.
it took a few hours for the updated kernel to appear - CDN network delay ?
It appears to have worked.
I may have been too hasty… whilst the box boots fine, what i didnt realise until now is that ethernet doesnt work.
the gui thinks “Status: No wired connection”
grab-logs -A are at https://paste.osmc.tv/yoqecicefo
Nov 04 04:16:42 newpi3.home systemd: networking.service: Cannot add dependency job, ignoring: Unit networking.service is masked.
What’s the output from running
systemctl status networking.service ?
I’m not sure if the patch is suitable.
It would be good if others could try it and comment
What’s the easiest way to roll back the kernel ?
# systemctl status networking.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)
Not sure if this is the “right” way to do it, but I just did:
cp /boot/vmlinuz-4.14.26-2-osmc /boot/kernel.img
Seems to have done the trick and now i have wired ethernet back (with no snmpd)
Almost. There’s one more step to do.
You need to cd to /boot and remove all the
bcm-xxxxx.dtb files and the
overlays directory + its contents (
sudo rm -r overlays)
Then (using sudo) you need to copy the
bcm-xxxxx.dtb files and
overlays directory + its contents from /boot/dtb-4.14.26-2-osmc to /boot.
I guess I’m lucky for now - such a minor kernel rollback, there might not have been any significant differences in the overlays
Indeed. Your new kernel might have contained a few other small changes but overall was a minor update.
And some other commits last night claim to fix the issue
Waiting for a couple of improvements yet before I’ll make any further testing available.