[SOLVED] Kernel Panic randomly on 2 units (rPi 1 model B)

[Exnor]

(22nd Mar, 2015 06:48 AM)f1vefour Wrote:  By trying to tail the syslog, I had someone do this but they said there was no panic showing in the recorded log.

Well out of frustration 2 days ago i've grab a new SDCard and installed fresh (no backups or nothing.. plain vanilla) and after less than 24h the same problem occurs ... so i can scratch being a problem related to my previous card/installation.

(i've downloaded the Win installer, flash the card, booted and updated... did not restore any of my previous setting or installed any add-on).

[namtih]

Did you already try to add "vm.min_free_kbytes" again?
The Pi1 had problems with kernel panic in combination with high network load. Adding this parameter fixed it. I've noticed that the parameter isn't set in the current Pi2 images.

So perhaps give it a try:
Add in "/etc/sysctl.conf" the parameter "vm.min_free_kbytes = 16384" or a higher value "vm.min_free_kbytes = 32768".
Reboot.


You could also try the newest Pi2 standard firmware:

Terminal

sync
sync
sudo wget -O /boot/fixup.dat https://github.com/Hexxeh/rpi-firmware/blob/master/fixup_x.dat?raw=true --no-check-certificate
sync
sudo wget -O /boot/start.elf https://github.com/Hexxeh/rpi-firmware/blob/master/start_x.elf?raw=true --no-check-certificate
sync
sync

Reboot.

[Diako]

I've tried the "vm.min_free_kbytes = 16384" setting on my RPi 1.
I hope avoiding my (multi) daily kernel panic freeze...

[CurlyMo]

Please try changing the btrfs compression from lz4 to lzo compress=lzo in /boot/cmdline.txt

[Exnor]

(27th Mar, 2015 07:28 AM)CurlyMo Wrote:  Please try changing the btrfs compression from lz4 to lzo compress=lzo in /boot/cmdline.txt

Doing that right now. i will post progress about the results.

Thks Curly

---

(27th Mar, 2015 04:33 AM)namtih Wrote:  Did you already try to add "vm.min_free_kbytes" again?
The Pi1 had problems with kernel panic in combination with high network load. Adding this parameter fixed it. I've noticed that the parameter isn't set in the current Pi2 images.

So perhaps give it a try:
Add in "/etc/sysctl.conf" the parameter "vm.min_free_kbytes = 16384" or a higher value "vm.min_free_kbytes = 32768".
Reboot.


You could also try the newest Pi2 standard firmware:

Terminal

sync
sync
sudo wget -O /boot/fixup.dat https://github.com/Hexxeh/rpi-firmware/blob/master/fixup_x.dat?raw=true --no-check-certificate
sync
sudo wget -O /boot/start.elf https://github.com/Hexxeh/rpi-firmware/blob/master/start_x.elf?raw=true --no-check-certificate
sync
sync

Reboot.

Thanks for your input
But this is the 1st time i have this problem and since i was using the rPis for viewing an average bit rate of 15Mbit/s x.264 files without any issue prior to the latest Kernel update it might not be the situation you describe.

Anyway i'm trying curly's idea and if it does not resolve the situation i'm going to try yours.

---

(27th Mar, 2015 05:52 AM)Diako Wrote:  I've tried the "vm.min_free_kbytes = 16384" setting on my RPi 1.
I hope avoiding my (multi) daily kernel panic freeze...

Please give us some feedback when you can.
thks.

[f1vefour]

I need someone with an RPi 2 to test this kernel, I'm hoping that the 3.18.y branch is simply buggy and 3.19.y is better.

https://db.tt/4xmGNDk2

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i linux-image-bcm2836_3.19.3+_armhf.deb

I can't test it myself as I'm still out of town. Let me know whoever tests if you still have the same issues.

@Exnor I had to target the RPi 2 since more folks seem to be having issues with it. I will update both when I return.

[CurlyMo]

Can you ask the same on github so all issue openers will test also?

[Diako]

(27th Mar, 2015 08:22 PM)Exnor Wrote:  

(27th Mar, 2015 05:52 AM)Diako Wrote:  I've tried the "vm.min_free_kbytes = 16384" setting on my RPi 1.
I hope avoiding my (multi) daily kernel panic freeze...

Please give us some feedback when you can.
thks.

And i've launched a download with nzbget and a few minutes later the RPi crashed again.
Unfortunately it's not the right solution

[Exnor]

(27th Mar, 2015 07:28 AM)CurlyMo Wrote:  Please try changing the btrfs compression from lz4 to lzo compress=lzo in /boot/cmdline.txt

Sorry but after less than 24h i've got another crash and another kernel panic on both units ....

Any suggestions?

---

(28th Mar, 2015 03:54 PM)f1vefour Wrote:  I need someone with an RPi 2 to test this kernel, I'm hoping that the 3.18.y branch is simply buggy and 3.19.y is better.

https://db.tt/4xmGNDk2

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i linux-image-bcm2836_3.19.3+_armhf.deb

I can't test it myself as I'm still out of town. Let me know whoever tests if you still have the same issues.

@Exnor I had to target the RPi 2 since more folks seem to be having issues with it. I will update both when I return.

Ok mate, but i don't have a Pi2 yet ... my situation occurs in 2 Pi 1 B models (one that i've even freshly installed without any addons ).

Thks

---

(28th Mar, 2015 10:18 PM)Diako Wrote:  

(27th Mar, 2015 08:22 PM)Exnor Wrote:  

(27th Mar, 2015 05:52 AM)Diako Wrote:  I've tried the "vm.min_free_kbytes = 16384" setting on my RPi 1.
I hope avoiding my (multi) daily kernel panic freeze...

Please give us some feedback when you can.
thks.

And i've launched a download with nzbget and a few minutes later the RPi crashed again.
Unfortunately it's not the right solution

So that idea is out too

[f1vefour]

@Exnor I will build a kernel for you to test now.

This is for RPi 1

https://db.tt/sNM5ty8M

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i xbian-package-kernel_3.19.3+_armhf.deb

[Exnor]

(29th Mar, 2015 02:27 AM)f1vefour Wrote:  @Exnor I will build a kernel for you to test now.

This is for RPi 1

https://db.tt/sNM5ty8M

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i xbian-package-kernel_3.19.3+_armhf.deb

Doing that now... thks for the help.

I will post results here and on GitHub.

---

(29th Mar, 2015 02:27 AM)f1vefour Wrote:  @Exnor I will build a kernel for you to test now.

This is for RPi 1

https://db.tt/sNM5ty8M

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i xbian-package-kernel_3.19.3+_armhf.deb

Updating as in GitHub:
Ok i have it installed and its running fine so far.. it past btrfs scrub without issues... i hope this is the one.
Do you want me to send you any log file or info?

[f1vefour]

You can just respond on github, I'm tracking there.

[Carpenter]

I will try this as well...

(29th Mar, 2015 02:27 AM)f1vefour Wrote:  @Exnor I will build a kernel for you to test now.

This is for RPi 1

https://db.tt/sNM5ty8M

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i xbian-package-kernel_3.19.3+_armhf.deb

[Exnor]

(29th Mar, 2015 05:47 AM)f1vefour Wrote:  You can just respond on github, I'm tracking there.

Ok, just in case anyone else is interested or this might help here is the dmesg file.

[Diako]

(28th Mar, 2015 03:54 PM)f1vefour Wrote:  I need someone with an RPi 2 to test this kernel, I'm hoping that the 3.18.y branch is simply buggy and 3.19.y is better.

https://db.tt/4xmGNDk2

Install by doing:

Terminal

sudo cp /boot/kernel.img /boot/kernel.good
sudo dpkg -i linux-image-bcm2836_3.19.3+_armhf.deb

I can't test it myself as I'm still out of town. Let me know whoever tests if you still have the same issues.

Now i've installed py RPi 2 with a stable version of xbian and of course i have the same problem than with my RPi 1.
I can test your kernel but before i want to be sure that i can still update simply my xbian. Do you confirm it's ok ?