KERNEL CRASHES WITH RASPBERRY PI ZERO W

613 views
Skip to first unread message

David Hitchins

unread,
Apr 16, 2018, 2:07:14 AM4/16/18
to motioneye
Hello all,
After battling for a week trying to get MOTION to work on both the Raspberry Pi 3 B+ and the Pi Zero W I only succeeded in getting a stable system on the PI3.
So I tried MotionEye  on both these little beasts (installing the recommend versions on each - different) and again it worked fine on the Pi 23b+ but the same
crash occurs on the Pi Zero W.

The screen fills with an endlessly running line of kernel error messages which I strongly suspect are due to a bug in Motion, not MotionEye. Or are they?
I couldn't capture the lines as text but a screenshot is attached.

Any idea how this problem can be fixed or what is causing it?

The crash seems to be triggered mainly when movement is detected, not so much while the frame is static.

As I say, works fine with the Pi 3+.

I used the same Raspberry pi camera on both boards and the same power supply (recommended 5.1 volts one)

Thanks
David Hitchins

Photo 16-4-18, 11 49 27 am.jpg
Photo 16-4-18, 11 49 24 am.jpg

Brent Goodman

unread,
Apr 24, 2018, 2:23:28 PM4/24/18
to motioneye
What type of camera are you attaching? Any other devices attached to the USB port? Do the Pi's fire up and work for any brief period of time before the kernel errors show up? If they do, you should be able to access one of the many log files that MotionEye generates. Are you running the most up to date version of the software?

Could be your camera's or SD Card causing the issue.

I have 5 PiZero W and 1 PiZero with a Wi-Fi dongle, and all use the standard Pi Camera's. These have all been running for the last 3 months with no down time. A few restarts over that time due to changing various settings. They were all running the update from the January time frame, and have just all been recently updated to the most up to date version of the software. I have a Raspberry Pi 3 that runs as the central hub.

Willbird BCR

unread,
Apr 30, 2018, 6:41:55 AM4/30/18
to motioneye
I tend to ask a lot of a pi....asking it to both stream video and write high quality videos. The Zero and ZeroW when doing that had very high cpu loading. I was using Pi2B outdoors and they were freezing up, swapped into pi3B and they seem to really work nice so far. In the case of the Pi2B I did not dig much deeper than seeing they had frozen up. Using the V2 Rpi camera in all cases.

Raniere Machado

unread,
Sep 1, 2018, 9:33:44 PM9/1/18
to motioneye
Hi David Hitchins!

I would like ask you if your system with RPi0W work good. I have same problem, and have'nt idea of problem.

Thanks advance.

Raniere

Bob Findlay

unread,
Sep 2, 2018, 2:53:44 AM9/2/18
to Raniere Machado, motioneye

You could have a bad pi0?  I had kernel crashes on a new 0 (but it couldn't even finish booting) which were fixed with a replacement 0


--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/240636a2-0847-4f85-aace-99da0afc5855%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--

cheers
Bob

Raniere

unread,
Sep 2, 2018, 12:30:24 PM9/2/18
to prfi...@gmail.com, moti...@googlegroups.com
I dont think this, i have 22 Pi0W, and they crashes in ~30minutes or 3days random.

I disabled some processes, for reduces chances of crashes:

sudo systemctl disable sound.target
sudo systemctl disable triggerhappy.service
sudo systemctl disable dhcpcd.service
sudo systemctl disable apt-daily-upgrade.timer
sudo systemctl disable apt-daily.timer
sudo systemctl disable bluetooth.service
sudo systemctl disable bthelper.service
sudo systemctl disable getty@.service
sudo systemctl disable hciuart.service
sudo systemctl disable systemd-timesyncd.service
sudo systemctl disable avahi-daemon
sudo systemctl disable triggerhappy.socket
sudo systemctl disable cron.service
sudo systemctl disable temp_monitor.service
sudo systemctl disable nfs-client.target
sudo systemctl disable remote-fs.target
sudo systemctl disable rpi-display-backlight.service
sudo systemctl disable raspberrypi-net-mods.service
sudo systemctl disable console-setup.service
sudo systemctl disable dbus-org.bluez.service
sudo systemctl disable bluetooth.service

Basicaly run only picamera application, wifi service and apache with fixed address IP.

I would like of compare settings with one that work good.


Raniere Machado
Cel: (48) 9922-1224
GTalk: raniere.ee@gmail.com

Reply all
Reply to author
Forward
0 new messages