RPi 2 Model B Locking Up

[Leeclark1983]

Hi all,

I have installed raspbian using the latest NOOBS setup from the website and I'm experiencing problems.

After a minute or so the pi 'locks up' and wont respond to keyboard or mouse input.

I am using a standard hdmi lead and a good 2A power supply. My micro SD card is a class 4 8gb card.

Any help appreciated,

Thanks in advance!

[DirkS]

Is the red power led on all the time?
Anything connected to the USB ports?

[Leeclark1983]

yeah the red led is on.

I had it connected to an Ethernet cable with a keyboard and mouse that was shipped with my pi 1 model b.
it does last longer without the Ethernet cable however...

is there a definitive list of compatible peripherals for the pi 2?

[pluggy]

No there isn't.

If you suspect the peripherals you could leave 'em unplugged and run it headless via the Ethernet.

[calmyabadselfdown]

Hi

I got my RPI 2 yesterday since then I have tried all the images that I can find and I have also put them on all the different sd cards I have (I know the cards are ok because they work with my other PIs and a Odroid C1 I have as well).
In every instance I can not get it to work. Openelec stops with a kernel panic. Raspian gets to cli I do startx and after a few seconds it stops and the only fix is to unplug it. I have also tried to flash the images using windows and Lubuntu from the CLI.

Any advise would be appreciated.

[Leeclark1983]

Maybe it's just the images then? They all say they support rpi2...

[jamesh]

Hi

I got my RPI 2 yesterday since then I have tried all the images that I can find and I have also put them on all the different sd cards I have (I know the cards are ok because they work with my other PIs and a Odroid C1 I have as well).
In every instance I can not get it to work. Openelec stops with a kernel panic. Raspian gets to cli I do startx and after a few seconds it stops and the only fix is to unplug it. I have also tried to flash the images using windows and Lubuntu from the CLI.

Any advise would be appreciated.

That could be a defective device if every single image is failing. Do you know anyone else with a Pi2 you can try.

Only other thing it might be is a power supply issue - can you try a different USB lead?

[calmyabadselfdown]

just tried a different usb cable but same power supply (from a Nexus 7) and I've now got Openelec , Snappy and raspbian all working.
thanks

[pluggy]

The choice of a USB power solution for the Pi has always been one of its failings. Yes, yes, I get all the upsides, but something designed for charging smart phones was always going to be a challenge for something wanting solid power.

Particularly with the advent of switch mode power regulators on the later ones, feeding it 7 - 20 volts through a decent DC plug holds a certain attraction.....

[mrlinux2u]

I've also experienced the 'lock-up' on my new RPi 2 (keyboard and mouse both dead), and I've also had the network fail to respond to ssh login attempts (I can still ping the Pi).

I'm using a brand new 2A power supply (there's no little rainbow coloured box in the corner indicating insufficent power).

I'm now running it headless using the latest Raspbian image and the Pi is still stopping after several hours (it's gone 24hours max before locking up) and the only solution is to pull the plug.

Any ideas, as apart from the lock-ups the Pi 2 is amazing?

Cheers

mrlinux2u

[pluggy]

Your previous posts suggest you have a B+, If you swap all the bits from the 2B to the B+, what happens then ?

[mrlinux2u]

Further update to my problems..

I updated the kernel friday night using rpi-update and plugged my pi back into it's monitor. I'm still getting crashes, but this time since the monitor was still working I saw the output from a kernel issue, and checking syslog I came across the following errors:

Feb 8 21:29:40 pi2 kernel: [28135.703483] Unable to handle kernel paging request at virtual address 0007688c
Feb 8 21:29:40 pi2 kernel: [28135.710971] pgd = b4170000
Feb 8 21:29:40 pi2 kernel: [28135.713744] [0007688c] *pgd=340b2831, *pte=00000000, *ppte=00000000
Feb 8 21:29:40 pi2 kernel: [28135.720696] Internal error: Oops: 80000007 [#1] PREEMPT SMP ARM
Feb 8 21:29:40 pi2 kernel: [28135.726682] Modules linked in: arc4 ecb md4 md5 hmac nls_utf8 cifs snd_bcm2835 snd_pcm snd_se$
Feb 8 21:29:40 pi2 kernel: [28135.740356] CPU: 0 PID: 2658 Comm: gvfs-afc-volume Not tainted 3.18.6-v7+ #749
Feb 8 21:29:40 pi2 kernel: [28135.747641] task: b8594ac0 ti: b4116000 task.ti: b4116000
Feb 8 21:29:40 pi2 kernel: [28135.753089] PC is at 0x7688c
Feb 8 21:29:40 pi2 kernel: [28135.756000] LR is at __inode_permission+0x8c/0xc8
Feb 8 21:29:40 pi2 kernel: [28135.760746] pc : [<0007688c>] lr : [<8014d1d0>] psr: 20000013
Feb 8 21:29:40 pi2 kernel: [28135.760746] sp : b4117d48 ip : b4117d68 fp : b4117d64
Feb 8 21:29:40 pi2 kernel: [28135.772321] r10: b4117e60 r9 : b9067015 r8 : b4116000
Feb 8 21:29:40 pi2 kernel: [28135.777590] r7 : b4117e60 r6 : b4117d98 r5 : 00000081 r4 : b9652558
Feb 8 21:29:40 pi2 kernel: [28135.784172] r3 : 0007688e r2 : 00000051 r1 : 00000081 r0 : b9652558
Feb 8 21:29:40 pi2 kernel: [28135.790755] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Feb 8 21:29:40 pi2 kernel: [28135.797951] Control: 10c5387d Table: 3417006a DAC: 00000015
Feb 8 21:29:40 pi2 kernel: [28135.803745] Process gvfs-afc-volume (pid: 2658, stack limit = 0xb4116238)
Feb 8 21:29:40 pi2 kernel: [28135.810590] Stack: (0xb4117d48 to 0xb4118000)
Feb 8 21:29:40 pi2 kernel: [28135.814987] 7d40: ba766c00 b4117da0 00000003 b4117d98 b4117d74 b4117d68
Feb 8 21:29:40 pi2 kernel: [28135.823237] 7d60: 8014d230 8014d150 b4117ddc b4117d78 8014eee4 8014d218 00000001 80056440

These appear to be the most relevant parts of the dump,but the Pi was working perfectly fine @ 21:28:01.

Now I've updated the kernel again tonight to the following version...

Linux pi2 3.18.6-v7+ #753 SMP PREEMPT Sun Feb 8 14:53:56 GMT 2015 armv7l GNU/Linux

My /etc/sysctl.conf file has 'vm.min_free_kbytes = 65000' added to the end, so I shouldn't be running out of memory.

I'll update everyone on how the new kernel goes (and if it suffer's the same problem).

Just to confirm I'm using a 2A power supply from a well known supplier, and the only things that are plugged in are the ethernet cable, keyboard/mouse and hdmi to vga adaptor (although the previous crashes happened with only the ethernet cable plugged in).


Cheers

mrlinux2u

[mrlinux2u]

Further updates,

Came home from work around 17:40PM to find all 4 cores were maxed out and the pi had stopped responding properly. Checked syslog to see it had crashed around 17:28.

I'm now trying it without motion running and using a usb-to-ethernet adaptor rather than the onboard network,to see if that's the culprit, failing that I'm utterly stumped at what can be causing the problem's.

As usual I'll keep you updated.

Cheers

mrlinux2u

[turbocrow]

I am experiencing the same problem its the most frustrating thing.

[mrlinux2u]

Yep, frustating - but I'm not gonna give up on the Pi2 yet (if nothing else it works as a desktop PC quite well)....

[sfk]

Would definitely try JamesH solution of a different cable. Not sure why it makes a difference but it did !! Also noticed with the previous cable I used the display dimmed a bit every second or two, which led me to think it was something to do with the power source rather than the cable.....

[Hoofee]

Hi,

I would just like to say that changing the USB cable between the power adapter and RPi2 also fixed my issue. I tried three cables, two of them didn't work and failed differently to each other (both 2 meter cables). The one that worked was a short 1 meter cable.

In my situation the RPi 2 had a kernel panic during boot with messages like the following. This 'mostly' occurred when USB devices were connected such as a Flirc - sometimes it occurred when no USB devices were connected.

Kernel Panic - not syncing: Fatal exception in interrupt.

or

Internal Error: oops :5 [#1] Preempt SMP Arm

or

BUG: Bad page state in process udevadm

Anyway, adding those there for searchability.

Cheers,
Dave.

[stevecody]

My RPI2 just came in last night (Feb 9, 2015) and I am having kernel panic issue as well.

Initially, under Noobs, it was panicking whenever I ran a startx. I'm systematically removing/replacing various devices right now to see if there is anything that stops the crashing.

I am now running the latest Raspbian image 1-31-15. I've changed from a 2.1a power supply to 2.4a. Changed the USB cable.

Testing with the following devices:
USB Keyboard
USB Mouse
USB Wifi Adapter
RPI Camera (NoIR)

Since the troubleshooting s taking some time, I don't have an answer yet on which causes the crashing. It seems to consistently crash with the CanaKit wifi adapter. I've switched it out with a RTL8188CUS chipset adapter.

Waiting...

Steve

[stevecody]

Ok. I've had the most success with the most recent change. I changed wireless adapters from the CanaKit adapter (not sure of the firmware) to the Edimax EW7811Un (Realtek TTL8188CUS) adapter and it has been completely stable.

I'm also running Motion, as someone else mentioned.

[mrlinux2u]

Right, time for another update...

Last night I swapped out the on-board ethernet for a realtek based one, I updated the kernel again with rpi-update and I reset the Rpi's speed back to 900mhz from the 1000mz overclock I'd been running.

So far I've had 18 hours solid performance (just running htop and no motion), so I've now re-launched motion and I'll see if it survives.

I'm not sure it's the the on-board usb-ethernet that's causing the problem (possible kernel module problem?), but since removing it from the equation (i.e. not plugging a network cable into it) my Pi2's been rock solid (so-far).

As usual I'll keep you updated with my progress...

[mhelin]

I'm able to run without any problems Jessie with x-windows and XFCE installed on top of the distro @ http://sjoerd.luon.net/posts/2015/02/de ... e-on-rpi2/ but for some reason with the official (raspberrypi.org/downloads version 2015-01-31) Raspbian I'm getting kernel panic quite soon (without being able to run through the preconfiguration). The microSD is 8GB Kingston Class 4.

Edit: Is it that the Jessie version doesn't have all GPU stuff enabled and because of that draws less current than Raspbian?

[mhelin]

Another cable solved the problem. Samsung U6 cable confirmed working.

[mrlinux2u]

Right, this is hopefully my last update regarding the issues I've been having.

As of today the Pi2 has been running successfully for :

17:27:50 up 1 day, 17:51

Which is the longest I've had it running without crashing on me.

Using a different network adapter (along with updating the kernel on monday night and making sure I didn't overclock the Pi in any way.) seems to have given the Pi some stability (even running motion for the last 20 hours or so).

The adapter is a Realtek gigabit adapter with the following chipset :

r8152 1-1.4:1.0 eth1: v1.07.0 (2014/10/09)

I'm not saying this is the solution for everyone's problems, but this has worked for me (so far...),

Cheers for now

mrlinux2u

[dom]

Using a different network adapter (along with updating the kernel on monday night and making sure I didn't overclock the Pi in any way.) seems to have given the Pi some stability (even running motion for the last 20 hours or so).

Can you go back to on-board ethernet, but leave the overclock disabled?
I suspect the overclock was more likely to be causing the issue.
Note: not all Pi's (Pi1 or Pi2) can handle 1GHz reliably, so disable overclock if you are getting stability issues.

[mrlinux2u]

@ dom,

I've now reverted back to the on board networking (using the 900mhz default) and I'll see if it keeps going. I'll report back tomorrow after I get home from work.

Cheers

mrlinux2u