Octoprint requires Raspbian Jessie based distro to work with Raspberry Pi 3

[alex-gibson]

I have been testing ahead of the launch today, and noticed that the standard OctoPi distro gives rainbow screen of death on the Pi 3, and I could not follow the instructions (due to errors) to install for Jessie, using latest NOOBS distro as at last night.

For hassle free OctoPrint on the Pi 3 I recommend starting with the latest Jessie nightly build, which worked well enough that I demo'd it at the Pi 3 launch party today :)

Happy to contribute testing to get a stable Jessie/Pi3 build!!!

[taxilian]

I just ran into this as well; I appreciate knowing that I'm not the only one, and I'll proceed following those instructions =]

[nophead]

I have OctoPrint running on a RPi3 by installing latest NOOBS and then following the OctoPrint install instructions for Linux. Tedious but they work and they also work on Ubuntu on an Orange Pi.

[gammy]

I installed Raspbian Jessie Lite (2016-02-26), but did so manually rather than via NOOBS. I then followed the OctoPrint installation instructions, except that I checked out v1.2.9(the latest stable version as of writing) rather than using the master. Tedious indeed @nophead! It all works though, including optional dependencies such as mjpg-streamer and cura-engine.

[nophead]

What it needs is an OctoPrint install script that runs on any Linux and does what the Linux instructions specify. Then you don't really need OctoPi.

[guysoft]

Hey guys, have you tried the nightly build? http://docstech.net/OctoPiMirror/nightly/ eg. https://storage.googleapis.com/octoprint/2016-03-02_2016-02-26-octopi-jessie-lite-0.13.0.zip

[pmbdk]

The latest nightly build works fine with RPi3 (although I havn't actually tried printing with it yet)

[A-Nesh]

I have also installed a nightly build (2016-03-02_2016-02-26-octopi-jessie-lite-0.13.0.zip) on RPi 3. The Pi freezes half way through a print.

[seefood]

Wow, people got their RP3 quickly :-) Now @guysoft only needs to take care of a Pine64 version and.... Hey, isn't it time to just create a PPA? :)

[foosel]

The Pi freezes half way through a print.

I've run into a similar issue with the Pi3 I just got, mine just sat idly though and suddenly stopped responding altogether, several times. On first look it seems to be power related, switched to a different PSU, haven't been able to reproduce the issue since then (still observing it though).

Since the Pi3 does consume more power than the Pi2, it might be that one simply can't get away with the same power supplies anymore as was still possible with Pi1/Pi2. Just an idea though. I certainly never had a Pi2 just freeze on me with that PSU while doing basically nothing.

[A-Nesh]

I don't believe that it's a power issue in my case as mine PPi is connected to a ATX PSU which can deliver 25A on a 5V rail.

[foosel]

After it just happened again, I have to agree, doesn't seem to be power related.

I also have to correct myself, it apparently doesn't freeze completely after all, it just looses wifi connectivity. Funny thing is, it believes it still does have connectivity, has an IP and everything, but cannot be pinged or SSH'd into. Until I ping the router from the Pi3, then suddenly connectivity is back:

$ ping -t 192.168.1.204

Pinging 192.168.1.204 with 32 bytes of data:
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.3: Destination host unreachable.
Reply from 192.168.1.204: bytes=32 time=2030ms TTL=64

Happens very reproducibly after some idle time. Maybe some power safe feature of the wifi chipset that's misbehaving (like it also happens with some dongles out there)?

@A-Nesh did it really freeze for you during printing (print stopped) or could it be that just the network connection broke down (print didn't stop, but anything relying on network didn't work anymore, so OctoPrint, SSH, ...).

[A-Nesh]

@foosel my printer just stopped printing, after some printing (an hour or so). The extruder and the heated bed was still on. It happened two times today. I don't know if the whole Pi freeze or not but it was not accessible either by HTTP or SSH. I'll check it next time it misbehave.

[foosel]

If it even stopped printing, that sounds like a different issue then. We are running the same image, so if it's an image issue, I should hopefully see it too during my tests.

From what you describe it indeed sounds like the whole Pi crashes completely. Do you have a chance to attach a monitor to it? That might show what's happening when it goes down. Also of interest would be your /var/log/syslog and you dmesg, maybe something got logged there when it went down.

[A-Nesh]

i have now encountered same issue as you @foosel. It did not stop printing but the network died. I'll connect a monitor next time it happens.

Here are my syslog and dmesg: dmesg.txt syslog.txt

[A-Nesh]

It died again now, after 77%

PING 192.178.1.88 (192.178.1.88): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4

[A-Nesh]

I have connected a monitor to the RPi, there is no signal = the RPi is dead

[foosel]

I asked in the G+ community if people were seeing this too with OctoPi and the RPi3. So far no definitive answer, but a good question:

If they're running an ATX PSU have they got any dummy load resistors to flatten out the power? I too thought it'd be no problem but noticed under load my ATX was dropping to 4 volts. Added a dummy load and it stabilized the output.

and some good advice I have to agree with:

Check your power supply. Try it without the printer turned on and see if stays up. Try with a separate 5V power supply and running a print. More troubleshooting is needed.

Try a different memory card?

Regarding the wifi going down, that's definitely caused by power management. I disabled it via /boot/octopi-network by adding wireless-power off to my wlan0 config, right after the SSID/PSK combo (basically as described here) and since doing that I couldn't reproduce the "un-ping-able" issue any more. Removed the line again and bam, issue returned. So something appears to be broken with the power management of the Pi3's own wifi.

I've seen older RPis freezing (exact same symptoms you are observing) due to issues with the wired interface, power supply issues (especially when under load), USB devices drawing too much power (which is why I prefer to have a powered hub between my Pi's and their peripherals), etc etc.

[A-Nesh]

ok, thanx. Ill try a separate power adapter and report later

[nophead]

If you are using an ATX PSU it is much better to use the 5V standby power rather than the main 5V. It is actually a separate power supply so isn't affected by the loads on the other outputs and you can also then use the RPi to control the other half of the PSU.

On 6 March 2016 at 17:41, A-Nesh notifications@github.com wrote:

ok, thanx. Ill try a separate power adapter and report later

— Reply to this email directly or view it on GitHub https://github.com/guysoft/OctoPi/issues/207#issuecomment-192943700.

[A-Nesh]

Have tried both 5v standby and ordinary 5v rails with no luck. I also believe that it is a power issue. I have connected usb power monitor and can see that there almost no current consumption when the printer is on. Which means that the power must come from the printer to RPi via USB. I use geeetech gt2650 board. It was never issue with OctoPi on mi Raspberry Pi 1.

[nophead]

Power should only flow from host to device on a USB cable. If device power is powering the host it is faulty. It wouldn't surprise me from Geeetech.

[A-Nesh]

I have left the Pi over night connected to a 3A USB power supply and it was dead this morning. I have connected a monitor and as it was not responding i have restarted the Pi. A couple minutes later, i have found the issue. I am new to linux but it looks to me like file system error.

[foosel]

That looks like a kernel panic. Download /var/log/syslog (eg via Womack), upload it somewhere (Dropbox or similar), share the link here.

The full log output of the kernel panic might tell us what's up, if it's a hardware issue, a flash gone wrong etc.

Just for the record, my pi3 has been up now since my last post yesterday without issues, using the same image and the above mentioned change to disable the Wi-Fi power management.

[taxilian]

Just as a datapoint, I installed using the raspbian image and then followed the octoprint install instructions and have been printing back to back jobs since Friday night with no issues.

Have not used Wi-Fi our changed any other settings.

[A-Nesh]

@foosel here is my syslog syslog.txt

[A-Nesh]

@taxilian actually it worked fine for me to when i installed latest Jessie and manually installed OctoPi. I don't know why did i install a nightly build instead when everything worked fine.

[foosel]

@A-Nesh because giving us early feedback on how the nightlies perform is the only way to root out issues before release, and you knew that and wanted to help? ;)

[A-Nesh]

@foosel yes, it's was pretty much my plan :)

[foosel]

@A-Nesh I took a look into your syslog. Seems like the issue you made a picture of above didn't make it into the log :/ But there are a LOT of errors with the wifi interface, including some traces while trying to get an IP via dhcp. Have you tried disabling WiFi power management as described above? It's just a complete shot in the dark... if that doesn't help, I'd suggest reflashing/another SD card, to rule out issues with the flash and the card.

Can't help myself, I don't have the feeling that their drivers are all "there" yet, the raspberry forums are also quite full with "doesn't work" posts in the wifi thread at the moment.

Might also be interesting to see if they maybe did things differently between the lite and the full raspbian image. OctoPi uses the lite image.

[A-Nesh]

@foosel Yes, i also notice a DHCP attempt today. It still connects to the manual IP (.88). My DHCP range is .100 an up. I also took a look in the syslog and couldn't find the error message. Maybe it died died before it could write the log.

I have used the full Jessie image earlier. I will try to to flash a new nightly image to a new SD card, as soon i find it. :) just to eliminate sd card issue

I didn't have a chance yet to disable wifi power management, i'll do it first now.

[A-Nesh]

I have tested fresh nightly image with wireless-power off, on a new SD card.... same issue. Here is my syslog. syslog.txt

I am now installing full Jessie image...

[A-Nesh]

Nope, same freeze during print issue. This time 54%. I give up, back to my RPi1

[foosel]

Oh, but that syslog was way more interesting:

Mar  7 11:56:44 octopi kernel: [ 1483.101088] Unable to handle kernel NULL pointer dereference at virtual address 00000000
Mar  7 11:56:44 octopi kernel: [ 1483.117168] pgd = 80004000
Mar  7 11:56:45 octopi kernel: [ 1483.123041] [00000000] *pgd=00000000
Mar  7 11:56:45 octopi kernel: [ 1483.130335] Internal error: Oops: 17 [#1] SMP ARM
Mar  7 11:56:45 octopi kernel: [ 1483.139454] Modules linked in: bnep hci_uart btbcm bluetooth brcmfmac brcmutil cfg80211 ftdi_sio rfkill joydev evdev usbserial snd_bcm2835 snd_pcm bcm2835_gpiomem snd_timer bcm2835_rng snd uio_pdrv_genirq uio ipv6
Mar  7 11:56:45 octopi kernel: [ 1483.175090] CPU: 1 PID: 42 Comm: kworker/1:1 Not tainted 4.1.18-v7+ #846
Mar  7 11:56:45 octopi kernel: [ 1483.187596] Hardware name: BCM2709
Mar  7 11:56:45 octopi kernel: [ 1483.194773] Workqueue: events brcmf_fweh_event_worker [brcmfmac]
Mar  7 11:56:45 octopi kernel: [ 1483.206209] task: b5b68000 ti: b5b2a000 task.ti: b5b2a000
Mar  7 11:56:45 octopi kernel: [ 1483.216669] PC is at cfg80211_get_bss_channel+0xf8/0x190 [cfg80211]
Mar  7 11:56:45 octopi kernel: [ 1483.228505] LR is at 0xfffffff6
Mar  7 11:56:45 octopi kernel: [ 1483.235206] pc : [<7f12eb48>]    lr : [<fffffff6>]    psr: 60000013
Mar  7 11:56:45 octopi kernel: [ 1483.235206] sp : b5b2bcc8  ip : 00000003  fp : b5b2bcec
Mar  7 11:56:45 octopi kernel: [ 1483.257060] r10: 00000064  r9 : 00000000  r8 : 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.267106] r7 : 000000c5  r6 : 000000b4  r5 : b2d60160  r4 : b3f90095
Mar  7 11:56:45 octopi kernel: [ 1483.279271] r3 : 00000000  r2 : 000000c5  r1 : b3f90084  r0 : 0000000d
Mar  7 11:56:45 octopi kernel: [ 1483.291417] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
Mar  7 11:56:45 octopi kernel: [ 1483.304842] Control: 10c5383d  Table: 32da806a  DAC: 00000015
Mar  7 11:56:45 octopi kernel: [ 1483.315699] Process kworker/1:1 (pid: 42, stack limit = 0xb5b2a210)
Mar  7 11:56:45 octopi kernel: [ 1483.327372] Stack: (0xb5b2bcc8 to 0xb5b2c000)
Mar  7 11:56:45 octopi kernel: [ 1483.335969] bcc0:                   00000000 b2d60160 000000c5 000000c5 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.352402] bce0: b5b2bd74 b5b2bcf0 7f12fa18 7f12ea5c 80819cdc 00000c11 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.368889] bd00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.385386] bd20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.401948] bd40: 00000000 00000000 b5247c40 b2d60160 000000d0 000000c5 00000064 00000c11
Mar  7 11:56:45 octopi kernel: [ 1483.418617] bd60: 00000000 b3f90004 b5b2bde4 b5b2bd78 7f251700 7f12f9b4 b3f9000c b2d60160
Mar  7 11:56:45 octopi kernel: [ 1483.435392] bd80: 00000000 00000000 00000c11 00000064 b3f90084 000000c5 ffffeae8 000000d0
Mar  7 11:56:45 octopi kernel: [ 1483.452310] bda0: 8056be54 00000c11 00000800 7f2598a4 b5b2bde4 b5b2bdc0 7f2598a4 b3f90004
Mar  7 11:56:45 octopi kernel: [ 1483.469432] bdc0: b3f90000 b5247c40 00000000 b2d60160 b2e3b248 b2e3b000 b5b2be0c b5b2bde8
Mar  7 11:56:45 octopi kernel: [ 1483.486644] bde0: 7f252204 7f25163c b5b2be88 b2d60340 b5b2bea0 b2d60340 b5247800 b5247c40
Mar  7 11:56:45 octopi kernel: [ 1483.503926] be00: b5b2be5c b5b2be10 7f252474 7f25219c 80056f60 80056a28 ffffffff 00ffffff
Mar  7 11:56:45 octopi kernel: [ 1483.521267] be20: 00000001 b6fc0ac0 0001ce82 00000001 b6fc0ad0 00000013 b2c36098 b2c360a8
Mar  7 11:56:45 octopi kernel: [ 1483.532236] be40: 00200200 00100100 b2c360ac b2c34000 b5b2be74 b5b2be60 7f259de0 7f2523c8
Mar  7 11:56:45 octopi kernel: [ 1483.542567] be60: b2de3cc3 b2de3c80 b5b2bee4 b5b2be78 7f259ea4 7f259da4 b529a8c0 b2e8e780
Mar  7 11:56:45 octopi kernel: [ 1483.552898] be80: b6fc0580 00000002 00000002 00000013 00000000 00000001 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.563230] bea0: e5ef7b10 6c77669d 00000030 00000000 00000000 00000000 80569d94 b2c36098
Mar  7 11:56:45 octopi kernel: [ 1483.573562] bec0: b5b15a00 b6fc0094 b6fc0080 b6fc3f00 00000000 00000000 b5b2bf24 b5b2bee8
Mar  7 11:56:45 octopi kernel: [ 1483.583906] bee0: 8003dbf8 7f259e48 b6fc0080 b6fc0094 b5b2a000 00000008 b5b15a00 b6fc0080
Mar  7 11:56:45 octopi kernel: [ 1483.594236] bf00: b5b15a18 b6fc0094 b5b2a000 00000008 b5b15a00 b6fc0080 b5b2bf5c b5b2bf28
Mar  7 11:56:45 octopi kernel: [ 1483.604569] bf20: 8003dec4 8003dab0 8003de70 80818900 00000000 00000000 b5978080 b5b15a00
Mar  7 11:56:45 octopi kernel: [ 1483.614898] bf40: 8003de70 00000000 00000000 00000000 b5b2bfac b5b2bf60 8004364c 8003de7c
Mar  7 11:56:45 octopi kernel: [ 1483.625229] bf60: b5b2bf94 00000000 8004a260 b5b15a00 00000000 00000000 b5b2bf78 b5b2bf78
Mar  7 11:56:45 octopi kernel: [ 1483.635560] bf80: 00000000 00000000 b5b2bf88 b5b2bf88 b5978080 80043560 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.645893] bfa0: 00000000 b5b2bfb0 8000faf8 8004356c 00000000 00000000 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.656229] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar  7 11:56:45 octopi kernel: [ 1483.666561] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 55555575 55555755
Mar  7 11:56:45 octopi kernel: [ 1483.676941] [<7f12eb48>] (cfg80211_get_bss_channel [cfg80211]) from [<7f12fa18>] (cfg80211_inform_bss_width+0x70/0x234 [cfg80211])
Mar  7 11:56:45 octopi kernel: [ 1483.690965] [<7f12fa18>] (cfg80211_inform_bss_width [cfg80211]) from [<7f251700>] (brcmf_inform_single_bss+0xd0/0x140 [brcmfmac])
Mar  7 11:56:45 octopi kernel: [ 1483.704867] [<7f251700>] (brcmf_inform_single_bss [brcmfmac]) from [<7f252204>] (brcmf_update_bss_info.part.8+0x74/0x130 [brcmfmac])
Mar  7 11:56:45 octopi kernel: [ 1483.719036] [<7f252204>] (brcmf_update_bss_info.part.8 [brcmfmac]) from [<7f252474>] (brcmf_notify_roaming_status+0xb8/0x1a0 [brcmfmac])
Mar  7 11:56:45 octopi kernel: [ 1483.733559] [<7f252474>] (brcmf_notify_roaming_status [brcmfmac]) from [<7f259de0>] (brcmf_fweh_call_event_handler+0x48/0xa4 [brcmfmac])
Mar  7 11:56:45 octopi kernel: [ 1483.748080] [<7f259de0>] (brcmf_fweh_call_event_handler [brcmfmac]) from [<7f259ea4>] (brcmf_fweh_event_worker+0x68/0x2d0 [brcmfmac])
Mar  7 11:56:45 octopi kernel: [ 1483.762320] [<7f259ea4>] (brcmf_fweh_event_worker [brcmfmac]) from [<8003dbf8>] (process_one_work+0x154/0x3cc)
Mar  7 11:56:45 octopi kernel: [ 1483.774520] [<8003dbf8>] (process_one_work) from [<8003dec4>] (worker_thread+0x54/0x500)
Mar  7 11:56:45 octopi kernel: [ 1483.784763] [<8003dec4>] (worker_thread) from [<8004364c>] (kthread+0xec/0x104)
Mar  7 11:56:45 octopi kernel: [ 1483.793213] [<8004364c>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)
Mar  7 11:56:45 octopi kernel: [ 1483.801556] Code: 0afffff1 e3520015 9affffef e5d10002 (e5931000) 
Mar  7 11:56:46 octopi kernel: [ 1483.810443] ---[ end trace b08645ac099d9c8f ]---
Mar  7 11:56:46 octopi kernel: [ 1483.810537] Unable to handle kernel paging request at virtual address ffffffec
Mar  7 11:56:46 octopi kernel: [ 1483.810540] pgd = 80004000
Mar  7 11:56:46 octopi kernel: [ 1483.810549] [ffffffec] *pgd=36ffa821, *pte=00000000, *ppte=00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810555] Internal error: Oops: 17 [#2] SMP ARM
Mar  7 11:56:46 octopi kernel: [ 1483.810586] Modules linked in: bnep hci_uart btbcm bluetooth brcmfmac brcmutil cfg80211 ftdi_sio rfkill joydev evdev usbserial snd_bcm2835 snd_pcm bcm2835_gpiomem snd_timer bcm2835_rng snd uio_pdrv_genirq uio ipv6
Mar  7 11:56:46 octopi kernel: [ 1483.810593] CPU: 1 PID: 42 Comm: kworker/1:1 Tainted: G      D         4.1.18-v7+ #846
Mar  7 11:56:46 octopi kernel: [ 1483.810594] Hardware name: BCM2709
Mar  7 11:56:46 octopi kernel: [ 1483.810602] task: b5b68000 ti: b5b2a000 task.ti: b5b2a000
Mar  7 11:56:46 octopi kernel: [ 1483.810613] PC is at kthread_data+0x18/0x20
Mar  7 11:56:46 octopi kernel: [ 1483.810619] LR is at wq_worker_sleeping+0x1c/0xe0
Mar  7 11:56:46 octopi kernel: [ 1483.810623] pc : [<80043d0c>]    lr : [<8003ecf4>]    psr: 00000193
Mar  7 11:56:46 octopi kernel: [ 1483.810623] sp : b5b2ba08  ip : b5b2ba18  fp : b5b2ba14
Mar  7 11:56:46 octopi kernel: [ 1483.810626] r10: 367c8000  r9 : b5b682ec  r8 : 8081a0a4
Mar  7 11:56:46 octopi kernel: [ 1483.810628] r7 : 807f8580  r6 : 807f8580  r5 : b6fc0580  r4 : 00000001
Mar  7 11:56:46 octopi kernel: [ 1483.810631] r3 : 00000000  r2 : 00000000  r1 : 00000001  r0 : b5b68000
Mar  7 11:56:46 octopi kernel: [ 1483.810635] Flags: nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
Mar  7 11:56:46 octopi kernel: [ 1483.810638] Control: 10c5383d  Table: 32da806a  DAC: 00000015
Mar  7 11:56:46 octopi kernel: [ 1483.810640] Process kworker/1:1 (pid: 42, stack limit = 0xb5b2a210)
Mar  7 11:56:46 octopi kernel: [ 1483.810643] Stack: (0xb5b2ba08 to 0xb5b2c000)
Mar  7 11:56:46 octopi kernel: [ 1483.810648] ba00:                   b5b2ba2c b5b2ba18 8003ecf4 80043d00 b5b68000 b6fc0580
Mar  7 11:56:46 octopi kernel: [ 1483.810654] ba20: b5b2ba7c b5b2ba30 80569f88 8003ece4 800775cc 8007729c b5b2ba94 b5b2ba48
Mar  7 11:56:46 octopi kernel: [ 1483.810659] ba40: 80027e54 800775b4 00000001 807f4240 b5b38124 b5b2a000 b5b2b81c b5b2baa0
Mar  7 11:56:46 octopi kernel: [ 1483.810665] ba60: b5b68268 00000001 00000001 b5900000 b5b2ba94 b5b2ba80 8056a264 80569bb0
Mar  7 11:56:46 octopi kernel: [ 1483.810671] ba80: 0420806c b5b68000 b5b2bad4 b5b2ba98 800299f8 8056a224 b5b2bac4 80824dcc
Mar  7 11:56:46 octopi kernel: [ 1483.810677] baa0: b5b2baa0 b5b2baa0 8081dad4 808822c4 60000113 8081dad4 0000000b 7f12eb4c
Mar  7 11:56:46 octopi kernel: [ 1483.810682] bac0: 00000001 7f12eb4a b5b2bb5c b5b2bad8 80014138 800292a4 b5b2a210 0000000b
Mar  7 11:56:46 octopi kernel: [ 1483.810687] bae0: 00000000 8067a6f8 00000008 00000000 00000000 8081dad4 3006d06c 66666661
Mar  7 11:56:46 octopi kernel: [ 1483.810693] bb00: 20316666 32353365 35313030 66613920 65666666 35652066 30303164 28203230
Mar  7 11:56:46 octopi kernel: [ 1483.810699] bb20: 33393565 30303031 80002029 80568168 806be44c 00000000 00000017 b5b2bc80
Mar  7 11:56:46 octopi kernel: [ 1483.810704] bb40: 00000000 b5b68000 00000000 00000064 b5b2bb74 b5b2bb60 80567ea4 80013ef0
Mar  7 11:56:46 octopi kernel: [ 1483.810709] bb60: b5b2bc80 00000000 b5b2bbcc b5b2bb78 8056ed94 80567e3c ffffffff 80054460
Mar  7 11:56:46 octopi kernel: [ 1483.810715] bb80: b5b68048 80054490 b5b68048 b6fc05c0 00004017 00000000 b5b2bbdc b5b2bba8
Mar  7 11:56:46 octopi kernel: [ 1483.810720] bba0: 000003ff 8081e084 00000017 8056eb08 00000000 b5b2bc80 00000000 00000064
Mar  7 11:56:46 octopi kernel: [ 1483.810726] bbc0: b5b2bc7c b5b2bbd0 800091e8 8056eb14 b5b2bc5c b5b2bbe0 80057cc0 80056a28
Mar  7 11:56:46 octopi kernel: [ 1483.810731] bbe0: b6fc0580 00000002 b5b2bc2c 80055218 8008e8b0 80450f0c ffffffff b5b68048
Mar  7 11:56:46 octopi kernel: [ 1483.810737] bc00: b2e8e7c8 b5b68000 00000000 8005522c b5b68048 b2e8e7c8 b5b2bc54 b5b2bc28
Mar  7 11:56:46 octopi kernel: [ 1483.810742] bc20: 8005522c 80053f08 00000010 00000000 b5b68000 b6fc0580 b2e8e780 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810748] bc40: 00000001 8067ad70 b5b2bc6c b5b2bc58 8004cf9c 7f12eb48 60000013 7f12eb48
Mar  7 11:56:46 octopi kernel: [ 1483.810753] bc60: 60000013 ffffffff b5b2bcb4 00000000 b5b2bcec b5b2bc80 8056e2dc 800091ac
Mar  7 11:56:46 octopi kernel: [ 1483.810758] bc80: 0000000d b3f90084 000000c5 00000000 b3f90095 b2d60160 000000b4 000000c5
Mar  7 11:56:46 octopi kernel: [ 1483.810764] bca0: 00000000 00000000 00000064 b5b2bcec 00000003 b5b2bcc8 fffffff6 7f12eb48
Mar  7 11:56:46 octopi kernel: [ 1483.810769] bcc0: 60000013 ffffffff 00000000 b2d60160 000000c5 000000c5 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810774] bce0: b5b2bd74 b5b2bcf0 7f12fa18 7f12ea5c 80819cdc 00000c11 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810779] bd00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810784] bd20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810790] bd40: 00000000 00000000 b5247c40 b2d60160 000000d0 000000c5 00000064 00000c11
Mar  7 11:56:46 octopi kernel: [ 1483.810796] bd60: 00000000 b3f90004 b5b2bde4 b5b2bd78 7f251700 7f12f9b4 b3f9000c b2d60160
Mar  7 11:56:46 octopi kernel: [ 1483.810802] bd80: 00000000 00000000 00000c11 00000064 b3f90084 000000c5 ffffeae8 000000d0
Mar  7 11:56:46 octopi kernel: [ 1483.810807] bda0: 8056be54 00000c11 00000800 7f2598a4 b5b2bde4 b5b2bdc0 7f2598a4 b3f90004
Mar  7 11:56:46 octopi kernel: [ 1483.810812] bdc0: b3f90000 b5247c40 00000000 b2d60160 b2e3b248 b2e3b000 b5b2be0c b5b2bde8
Mar  7 11:56:46 octopi kernel: [ 1483.810818] bde0: 7f252204 7f25163c b5b2be88 b2d60340 b5b2bea0 b2d60340 b5247800 b5247c40
Mar  7 11:56:46 octopi kernel: [ 1483.810823] be00: b5b2be5c b5b2be10 7f252474 7f25219c 80056f60 80056a28 ffffffff 00ffffff
Mar  7 11:56:46 octopi kernel: [ 1483.810829] be20: 00000001 b6fc0ac0 0001ce82 00000001 b6fc0ad0 00000013 b2c36098 b2c360a8
Mar  7 11:56:46 octopi kernel: [ 1483.810834] be40: 00200200 00100100 b2c360ac b2c34000 b5b2be74 b5b2be60 7f259de0 7f2523c8
Mar  7 11:56:46 octopi kernel: [ 1483.810840] be60: b2de3cc3 b2de3c80 b5b2bee4 b5b2be78 7f259ea4 7f259da4 b529a8c0 b2e8e780
Mar  7 11:56:46 octopi kernel: [ 1483.810845] be80: b6fc0580 00000002 00000002 00000013 00000000 00000001 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810851] bea0: e5ef7b10 6c77669d 00000030 00000000 00000000 00000000 80569d94 b2c36098
Mar  7 11:56:46 octopi kernel: [ 1483.810856] bec0: b5b15a00 b6fc0094 b6fc0080 b6fc3f00 00000000 00000000 b5b2bf24 b5b2bee8
Mar  7 11:56:46 octopi kernel: [ 1483.810862] bee0: 8003dbf8 7f259e48 b6fc0080 b6fc0094 b5b2a000 00000008 b5b15a00 b6fc0080
Mar  7 11:56:46 octopi kernel: [ 1483.810867] bf00: b5b15a18 b6fc0094 b5b2a000 00000008 b5b15a00 b6fc0080 b5b2bf5c b5b2bf28
Mar  7 11:56:46 octopi kernel: [ 1483.810872] bf20: 8003dec4 8003dab0 8003de70 80818900 00000000 00000000 b5978080 b5b15a00
Mar  7 11:56:46 octopi kernel: [ 1483.810878] bf40: 8003de70 00000000 00000000 00000000 b5b2bfac b5b2bf60 8004364c 8003de7c
Mar  7 11:56:46 octopi kernel: [ 1483.810883] bf60: b5b2bf94 00000000 8004a260 b5b15a00 00000000 00000000 b5b2bf78 b5b2bf78
Mar  7 11:56:46 octopi kernel: [ 1483.810889] bf80: 00000001 00010001 b5b2bf88 b5b2bf88 b5978080 80043560 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810894] bfa0: 00000000 b5b2bfb0 8000faf8 8004356c 00000000 00000000 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810899] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Mar  7 11:56:46 octopi kernel: [ 1483.810904] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 55555575 55555755
Mar  7 11:56:46 octopi kernel: [ 1483.810918] [<80043d0c>] (kthread_data) from [<8003ecf4>] (wq_worker_sleeping+0x1c/0xe0)
Mar  7 11:56:46 octopi kernel: [ 1483.810931] [<8003ecf4>] (wq_worker_sleeping) from [<80569f88>] (__schedule+0x3e4/0x674)
Mar  7 11:56:46 octopi kernel: [ 1483.810939] [<80569f88>] (__schedule) from [<8056a264>] (schedule+0x4c/0xa4)
Mar  7 11:56:46 octopi kernel: [ 1483.810947] [<8056a264>] (schedule) from [<800299f8>] (do_exit+0x760/0x9f8)
Mar  7 11:56:46 octopi kernel: [ 1483.810957] [<800299f8>] (do_exit) from [<80014138>] (die+0x254/0x43c)
Mar  7 11:56:46 octopi kernel: [ 1483.810965] [<80014138>] (die) from [<80567ea4>] (__do_kernel_fault.part.0+0x74/0x84)
Mar  7 11:56:46 octopi kernel: [ 1483.810973] [<80567ea4>] (__do_kernel_fault.part.0) from [<8056ed94>] (do_page_fault+0x28c/0x398)
Mar  7 11:56:46 octopi kernel: [ 1483.810980] [<8056ed94>] (do_page_fault) from [<800091e8>] (do_DataAbort+0x48/0xc4)
Mar  7 11:56:46 octopi kernel: [ 1483.810986] [<800091e8>] (do_DataAbort) from [<8056e2dc>] (__dabt_svc+0x3c/0x60)
Mar  7 11:56:46 octopi kernel: [ 1483.810988] Exception stack(0xb5b2bc80 to 0xb5b2bcc8)
Mar  7 11:56:46 octopi kernel: [ 1483.810994] bc80: 0000000d b3f90084 000000c5 00000000 b3f90095 b2d60160 000000b4 000000c5
Mar  7 11:56:46 octopi kernel: [ 1483.810999] bca0: 00000000 00000000 00000064 b5b2bcec 00000003 b5b2bcc8 fffffff6 7f12eb48
Mar  7 11:56:46 octopi kernel: [ 1483.811002] bcc0: 60000013 ffffffff
Mar  7 11:56:46 octopi kernel: [ 1483.811032] [<8056e2dc>] (__dabt_svc) from [<7f12eb48>] (cfg80211_get_bss_channel+0xf8/0x190 [cfg80211])
Mar  7 11:56:46 octopi kernel: [ 1483.811075] [<7f12eb48>] (cfg80211_get_bss_channel [cfg80211]) from [<7f12fa18>] (cfg80211_inform_bss_width+0x70/0x234 [cfg80211])
Mar  7 11:56:46 octopi kernel: [ 1483.811111] [<7f12fa18>] (cfg80211_inform_bss_width [cfg80211]) from [<7f251700>] (brcmf_inform_single_bss+0xd0/0x140 [brcmfmac])
Mar  7 11:56:46 octopi kernel: [ 1483.811140] [<7f251700>] (brcmf_inform_single_bss [brcmfmac]) from [<7f252204>] (brcmf_update_bss_info.part.8+0x74/0x130 [brcmfmac])
Mar  7 11:56:46 octopi kernel: [ 1483.811169] [<7f252204>] (brcmf_update_bss_info.part.8 [brcmfmac]) from [<7f252474>] (brcmf_notify_roaming_status+0xb8/0x1a0 [brcmfmac])
Mar  7 11:56:46 octopi kernel: [ 1483.811202] [<7f252474>] (brcmf_notify_roaming_status [brcmfmac]) from [<7f259de0>] (brcmf_fweh_call_event_handler+0x48/0xa4 [brcmfmac])
Mar  7 11:56:46 octopi kernel: [ 1483.811240] [<7f259de0>] (brcmf_fweh_call_event_handler [brcmfmac]) from [<7f259ea4>] (brcmf_fweh_event_worker+0x68/0x2d0 [brcmfmac])
Mar  7 11:56:46 octopi kernel: [ 1483.811264] [<7f259ea4>] (brcmf_fweh_event_worker [brcmfmac]) from [<8003dbf8>] (process_one_work+0x154/0x3cc)
Mar  7 11:56:46 octopi kernel: [ 1483.811272] [<8003dbf8>] (process_one_work) from [<8003dec4>] (worker_thread+0x54/0x500)
Mar  7 11:56:46 octopi kernel: [ 1483.811280] [<8003dec4>] (worker_thread) from [<8004364c>] (kthread+0xec/0x104)
Mar  7 11:56:46 octopi kernel: [ 1483.811288] [<8004364c>] (kthread) from [<8000faf8>] (ret_from_fork+0x14/0x3c)
Mar  7 11:56:46 octopi kernel: [ 1483.811294] Code: e24cb004 e52de004 e8bd4000 e59032c0 (e5130014) 
Mar  7 11:56:46 octopi kernel: [ 1483.811297] ---[ end trace b08645ac099d9c90 ]---
Mar  7 11:56:46 octopi kernel: [ 1483.811299] Fixing recursive fault but reboot is needed!

Big kernel oops there. Apparently in the wifi driver. Did I mention that I have a feeling that the drivers for the included wifi chipset aren't quite there yet?

[A-Nesh]

@foosel do you think that using a USB WIFI adapter will solv the issue?

[foosel]

Absolutely no idea. Might be worth a try. Maybe even blacklisting the driver of the built-in wifi.

What will definitely solve a lot though is the RPi people fixing their drivers ;)

[A-Nesh]

I can confirm now that blacklisting the brcmfmac driver solvs the issue for me. It now works flawlessly with a USB WiFi adapter.

[foosel]

@A-Nesh I forwarded this thread to someone at raspberry pi, the engineering team suggested a different power supply, replied that you already tried that, they also suggested to try stock raspbian - just for the record, when you talked about the "full image" further up, did you mean stock raspbian/noobs?

[A-Nesh]

@foosel I have used this: RASPBIAN JESSIE Full desktop image based on Debian Jessie Version:February 2016 Release date:2016-02-26

I have tested 4 different power supplies, 2 SD cards, tested setting max_usb_current=1and wireless-power off... it freeze after a while with and without 3D printer connected.

Since i have blacklisted brcmfmac it printed flawlessly with 1.0A chromecast power supply while running hardinfo :)

[techied]

;D so happy I discovered this thread Can confirm that latest octopi (not nightly) does not work on my brand-new pi 3 and stock psu Will follow directions here and either use nightly build or Jessie =D @A-Nesh could you tell your installation instructions if it's not too much trouble? Octoprint is the whole reason I got the pi3

[foosel]

I can only recommend to follow OctoPrint on G+, Twitter or Facebook, because among OctoPrint specific announcements those outlets do also cover OctoPi related things, such as the Pi3 situation ;)

[A-Nesh]

i have now switched to octopi nightly build and blacklisted brcmfmac. It has now been printing for two hours without problems.

[techied]

It works with the latest nightly build (released on the ninth of March) Haven't tried printing yet, but thanks for the help =D

[techied]

Finished a print on the nightly build no problem :D I used the stock wifi and camera module, and a 2.4amp psu no crashes or anything :)

[A-Nesh]

Yeah, it just proves that i have some kind of hardware issue with my WiFi chip.

[picclock]

Brilliant helpful thread. Same issues with RPi3, been driving me mad. Have a wifi dongle but how do you blacklist the brcmfmac file, or is there an image with it blacklisted?

[foosel]

@picclock have you the same crashing issues as @A-Nesh? You definitely should verify first that it isn't just your Wi-Fi going to sleep by disabling it's power management as described above. Only if that doesn't work should you test if black listing the module works. To black list it, I think this should work:

sudo -s
echo "blacklist brcmfmac" > /etc/modprobe.d/brcmfmac.conf
depmod -ae
update-initramfs -u

[foosel]

Argh, misclicked, sorry.

The mobile view really makes hitting the wrong button a bit too easy, especially when fighting the Android keyboard ;)

[picclock]

Hi Foosel, Thx for the help. I will do the wifi power bit. I can use a LAN connection to edit it as the wifi is all over the place. Am running 2016-02-26-octopi-jessie-lite-0.13.0.img. Many Thx

[A-Nesh]

Yes, i have tried to disable wifi power management with no sucess. It completely freezes, does not recognize monitor and keyboard. The only solution i found working for me is blacklisting brcmfmacin /etc/modprobe.d/raspi-blacklist.conf

On the bright side OctoPi nigtly build works great, has been printing with it for ower a week now.

[picclock]

@ A.Nesh Exactly the same experience. Followed instructions to disable wifi power mgmt and no wifi. Plugged in LAN cable, ssh, restored backup interfaces file, blacklisted driver and plugged in wifi adapter. Rock solid. !!!!

Clearly some issues that need sorting.

Many , many thx

best regards

picclock