xbianonpi / xbian

XBMC on Raspberry Pi, Bleeding Edge
https://xbian.org
GNU General Public License v3.0
294 stars 44 forks source link

RPI2 xbian kernel panic while intense use #715

Closed ErickPH closed 8 years ago

ErickPH commented 9 years ago

I now have an RPI2, and I think Im facing same issues as in RPI1 when I was in the middle of massive downloads (lots of IO to my USB3 BTRFS disk) perhaps is the same as issue @f1vefour do you have a kernel for RPI2 as the one you provided for issue 709?

Attached are screen captures. Can I please be reffered to an article that can help me setup a proper capture process?

uname -a
Linux xbian 3.18.8+ #1 SMP PREEMPT Thu Mar 5 03:13:36 CET 2015 armv7l GNU/Linux

xbian@xbian /boot $ cat config.txt
#initramfs initramfs.gz  0x1000000
gpu_mem_1024=256
gpu_mem_512=144
gpu_mem_256=100
initial_turbo=3
hdmi_ignore_cec_init=1
disable_overscan=1
disable_splash=1
xbian@xbian /boot $

xbian@xbian /boot $ cat cmdline.txt
telnet zswap.enabled=1 zswap.compressor=lz4 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootflags=subvol=root/@,thread_pool=2,autodefrag,compress=lz4,commit=120 rootfstype=btrfs rootwait smsc95xx.turbo_mode=N logo.nologo quiet noswap loglevel=0 mod_scsi.scan=sync partswap startevent=mountall splash nohdparm --startup-event mountall
xbian@xbian /boot $

thanks screen1 screen2 screen3

FatFairFoot commented 9 years ago

Got the same issue here ! img_20150426_202442

root@xbian /boot # uname -a Linux xbian 3.18.8+ #1 SMP PREEMPT Thu Mar 5 03:13:36 CET 2015 armv7l GNU/Linux root@xbian /boot # cat config.txt

initramfs initramfs.gz 0x1000000

gpu_mem_1024=256 gpu_mem_512=144 gpu_mem_256=100 initial_turbo=3 hdmi_ignore_cec_init=1 disable_overscan=1 disable_splash=1 arm_freq=1000 core_freq=500 sdram_freq=500 over_voltage=2 root@xbian /boot # cat cmdline.txt telnet zswap.enabled=1 zswap.compressor=lz4 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootflags=subvol=root/@,thread_pool=2,autodefrag,compress=lz4,commit=120 rootfstype=btrfs rootwait smsc95xx.turbo_mode=N logo.nologo quiet noswap loglevel=0 mod_scsi.scan=sync partswap startevent=mountall splash nohdparm --startup-event mountall root@xbian /boot #

Thanks for your help ! This could happen several times per day !!

wlatendresse commented 9 years ago

Running on Pi2 as well and using transmission pretty extensively, nut no kernel panics yet (thank god). But today I had a complete crash (everything simply stops, no network connections possible anymore), will try to reproduce it these days. But since I regularly backup my SD it's not (yet) a BIG issue for me right now ...

By the way: I am really missing the "screen" deb package on xbian ;-)

CurlyMoo commented 9 years ago

Screen is available from the default debian repository.

wlatendresse commented 9 years ago

So WHAT exactly is right now? I thought one should NOT install packages from the default repositories? Or is this just true for the apt utility to upgrade the system? What is OK and what should be avoided in the meaning of package management? Thanks for your help CurlyMoo.

BTW: Does CurlyMoo mean that you are some hairy cow? o.O :-D

CurlyMoo commented 9 years ago

Ofc you can install packages from the normal repository. That's the whole point of us building on top of debian. Just don't run apt-get dist-upgrade or rpi-update.

wlatendresse commented 9 years ago

Thanks for the correction of my mental error, this makes many of my wishes true :-D (How could one ever live WITHOUT screen on remote logins ;-) )

I have an idea and would love a comment from you about this, CurlyMoo:

How about a little wrapper script (well 2 scripts to be precise of course) in /usr/local for apt-get and rpi-update that simply would warn the user upon running a dist-upgrade command or the rpi-update script? This really should not be very much work and maybe would help some new users to prevent to make this error. I even would volunteer to do this ;-)

HugoAdrian commented 9 years ago

The first time you install Xubuntu was a success, but the second I get this error in the Raspberry Pi b 2 in the installation of Xubuntu of https://wiki.ubuntu.com/ARM/RaspberryPi following the video https://www.youtube.com/watch?v=UGSQ7nzVCs4 in the last step, but not my desktop image below appears
panic kernal

HugoAdrian commented 9 years ago

help

CurlyMoo commented 9 years ago

EU call 112, US call 911.

The-Exnor commented 9 years ago

Did i miss something here? Is this a Xubuntu help request or a Xbian related problem?

HugoAdrian commented 9 years ago

Xubuntu is a problem running on Raspberry Pi B 2, in the images below is the first test tube successfully but the other image is an error on the second installation I did, please help, not to do 11377357_1583524848582794_7848433983846682533_n panic kernal

CurlyMoo commented 9 years ago

So back to the question of @The-Exnor:

Is this a Xubuntu help request or a Xbian related problem?

The-Exnor commented 9 years ago

@CurlyMoo i still don't understand if this guy is mistaken or i missed something... isn't this Xbian issues section?

CurlyMoo commented 9 years ago

Ofc, that's why i repeated your question.

The-Exnor commented 9 years ago

@CurlyMoo lol. We should tell him that he is mistaken... and maybe try to help him write better English?

s47 commented 9 years ago

I've got the exact same problem as @ErickPH when using transmission downloading big files. Any news on this?

CurlyMoo commented 9 years ago

Maybe you guys can try this: http://forum.xbian.org/thread-2783-post-29202.html#pid29202

wlatendresse commented 9 years ago

I got the same problem over here, already two times right now:

20150519_160923_richtone hdr 20150605_121927

In case you need more info, just tell me, but it simply seems to be a kernel issue.

s47 commented 9 years ago

I ended up removing my wifi dongle and switching to cable and the issue hasn't happened to me since

wlatendresse commented 9 years ago

Well, thanks for the info. But I have never seen the colors-square so I assume my cable should be ok.

coderpop commented 9 years ago

Same here on a pi2.

This time on wired ethernet (no wifi). Happens while remuxing videos using avconv. Oddly it seems to complete the task of remuxing the videos and then crashes sometime after it's finished. (?)... Only way out is to pul the power cord and restart the pi. Screen looks similar to the first (erik PH) pictures above with the kodi desktop showing under the text from the kernel panic.

mkreisl commented 9 years ago

@coderpop Do you overclock the RPi2? I had same trouble with my brand new RPi2 (1GHz clocked) which I bought for testing. I used a lot of kernels (3.18, 3.19, 4.01), nothing helped. Only back to standard clock (900MHz) seems to help, no kernel oops/panic since many days.

coderpop commented 9 years ago

mkreisl,

You are correct yet again!

I was running in overclock mode and went back to default last night. I left the pi remuxing videos for 12 hours and no problems. Then it was left alone for 8 hours and is now remuxing again. No panic and no reboots.

Thanks!

CP

wlatendresse commented 9 years ago

Well, MINE is NOT overclocked. Never do that since the performance gain is marginal and all you possible get from it is PROBLEMS ;-)

mkreisl commented 9 years ago

@OtakuWally

Well, MINE is NOT overclocked. Never do that since the performance gain is marginal and all you possible get from it is PROBLEMS ;-)

Sounds bad :-(

In case of RPi2 you are right. But on RPi1 there is a difference if you run it with 700MHz or 1Ghz (like my 2 RPI1's). Never had trouble overclocking my RPi1's up to 1GHz.

wlatendresse commented 9 years ago

You mean, you never had trouble you were able to notice ;-) Data can get corrupted in RAM etc ... Overclocking is useless in my eyes, but you can of course do whatever you want ;-)