I have exactly the same today. I rebooted y running OH2 on a RPI3 and it never returned checked what was going on and see the same kernel panic that you have indicated in your photo.
I backed up my image and then rewrote the SD using the network install, watched it install and then when it did its final reboot to bring up OH2 it did the same thing.
I currently cannot work out if OH2 is the cause or if its the underlying rspbian update that interferes with the OH2 image.
I am thinking I need to try another platform while this is resolved.
Until I understand what update causes this, OS or OH2 I am not so keen on spending effort on getting my system back up and working for it to update and on its next reboot panic.
I am actually downloading the image you suggested currently as I am interested in what changes so early on to cause the kernal to crash. so I figured it could be a good reference system to work out whats causing the issue.
I commented out some liens in the /boot/config.txt file when I had my SD mounted in my windows machine.
Upon reboot I was able to get to the login prompt and login.
I notice that my IP address was no longer that allocated by my DHCP as a psuedo static IPv4 address instead it was getting an address from the my default pool, the MAC address has changed on eth0???
This is why I could not see the web page or ssh into the box initially.
My /boot/config.txt file looks like this before my changes
[pi3]
kernel=vmlinuz-4.4.0-1-rpi2
initramfs initrd.img-4.4.0-1-rpi2 followkernel
# enable the serial console for the installed system
#enable_uart=1
gpu_mem=16
dtparam=audio=on
I commented out the following three lines,
#kernel=vmlinuz-4.4.0-1-rpi2
#initramfs initrd.img-4.4.0-1-rpi2 followkernel
#enable_uart=1
I finally reduced it to the last line (enable_uart) being commented out and I could still boot and login at the console.
.
That line needs to remain commented out otherwise it panic’s.
Can anyone confirm what I have above works for them too?
Well I have reached the position where I now have my RPi3 able to stay on its original MAC address which means it gets the same IP address dished out from the DHCP server based on its known MAC, prior to this I was seeing the MAC address change all the time.
I looked at a post regarding the serial number changing but that was an early hardware issue and was not our problem.
I think the issue is that the kernel was not being passed or not accepting the parameter for the MAC, still not sure is this is a debian/raspbian issue or a OH2 one.
I looked at multiple options to solve and finaly settled on the one below as it will work now and in the future and corrects the MAC parameter pasing early in the boot so rectifys the issue very early on.
edit the /boot/cmdline.txt file and insert the command
smsc95xx.macaddr=00:00:00:00:00:00
where 00:00:00:00:00:00 is the actual MAC you want to be used.
I inserted it after ‘elevator=deadline’ and before 'net.ifnames=0’
Space either side… see below for an example
Hi Paul,
you’re right. I experienced the same problems of having a new MAC address on every reboot after installing the newest updates. I applied the fixes you described and everything worked as before.
thanks for the 2 fixes. After I commented the uart-line in the config.txt and fixed the old mac-address in the cmdline.txt it seems to work again indeed. No green led anymore, but I suppose that’s controlled using the uart then?
Sorry really difficult for me to read the screen shot, but after asking for sighted help from my a friend; it sounds like your MAC address is set as all zeros, you need to set the one you have not use the example of zeros.
That is an illegal MAC address and will not work.
Please follow the instructions earlier in this thread and set the MAC address to what it was previously if you know it. if not make one up using an online generator such as:
Incidentally at the weekend I see the latest OS update now includes a fix for the MAC address part of the fix, it works too, the uart line is still causing kernel panic though.
Hi Paul, many thanks for your support.
Setting the MAC to the old one, (I found it in my old router logs) fixed the issue. I will make a clean new inst of openHABian.
Well… it booted up, but e.g. mosquitto didn’t work anymore, it seemed some things were broken.
no idea
At least I could browse the files so I decided to backup my openhab configs etc. and do a complete reinstall with the other openhabian image (not the net-install!).
First of all, if you have enough HDD space on your computer, create a complete image of your SD card using e.g. win32diskimager. That would be your emergency backup image…
Important: Don’t forget to copy the these new backup folders to your PC before formatting the SD
If you have mosquitto or homgear etc. running you might want to save their config files to your PC too.
Then format your SD > write new raspbian image > boot > (maybe install homegear again) and copy your backup files back to the Pi. Use the link above for the How to restore.
