Raspberry Pi 3 B+ lockups

[drencor]

Dear Support,

I bought a Raspberry Pi 3 B+ from Adafruit. I just got the Raspberry Pi 3 B+ in the mail today. I downloaded the most current official Raspbian Stretch image today and put it on a 32GB microSD. When booting the Raspberry Pi 3 B+ some times the eth0 doesn't show up in ifconfig, some times the wlan0 doesn't show up in ifconfig. Othertimes the system just flat out locks up at the Raspbian Desktop.

The other thing I noticed is when I opened the Raspberry Pi 3 B+ box that the Raspberry Pi 3 B+ was not in a anti-static bag like all the previous versions I have bought have been in. So not sure if I have a damaged unit, previous opened product, or something.

I tried using Adafruit's forums, but their forums shows any support for a Raspberry Pi device I must come here to Raspberry Pi foundation forums.

[wildfire]

The other thing I noticed is when I opened the Raspberry Pi 3 B+ box that the Raspberry Pi 3 B+ was not in a anti-static bag like all the previous versions

It probably did, a lot of folks are posting about receiving their 3B+'s in paper bags but they are actually anti-static.

Regarding your problems, I'd initially look at the OS (which I acknowledge you've done) followed by the PSU.

[rpdom]

I don't know about the other issues, but your Pi 3B+ should have come with a sheet of anti-static cardboard instead of a bag. It's a plain white bit of card with just a barcode on. It's more environmentally friendly than using plastic, and just as safe.

[RaTTuS]

what PSU are you using

[drencor]

Regarding your problems, I'd initially look at the OS (which I acknowledge you've done) followed by the PSU.

Yes the OS I am using is the only Raspbian image that is for download right now from the download site which is Raspbian Stretch date 2018-03-13.

PSU is the official 2.5A microUSB cable/PSU combo from Newark/Element14. I have tried all 3 of them that I own with this Raspberry Pi 3 B+ and it still has issues.

[mattmiller]

I'd try another sdcard or if you have another working Pi running Stretch, I'd try updating it using

Code: Select all

sudo apt-get update

sudo apt-get dist-upgrade

and then try it out in the Pi3B+ and see if that works

[jamesh]

You could try limiting to clock speed in case that is an issue, I think it's a config.txt change

arm_freq=1200

[drencor]

You could try limiting to clock speed in case that is an issue, I think it's a config.txt change

arm_freq=1200

Well what is sad is after doing this change to the config.txt file the Raspberry Pi 3 B+ now boots without locking up or giving kernel panic messages.

So now need to figure out what can be done to fix this so I can get full 1.4GHz usage.

[drencor]

I'd try another sdcard or if you have another working Pi running Stretch, I'd try updating it using

Code: Select all

sudo apt-get update

sudo apt-get dist-upgrade

and then try it out in the Pi3B+ and see if that works

Thank you for the tip.

Sadly I had already done this several times. didn't help.

[jamesh]

You could try limiting to clock speed in case that is an issue, I think it's a config.txt change

arm_freq=1200

Well what is sad is after doing this change to the config.txt file the Raspberry Pi 3 B+ now boots without locking up or giving kernel panic messages.

So now need to figure out what can be done to fix this so I can get full 1.4GHz usage.

OK, that a good data point. I'll flag it up to the people who work out there frequency scaling stuff.

[PhilE]

What does "vcgencmd get_config int" return?

[drencor]

What does "vcgencmd get_config int" return?

Code: Select all

pi@raspberrypi:~ $ vcgencmd get_config int
arm_freq=1200
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=400
desired_osc_freq=0x33e140
desired_osc_freq_boost=0x3c45b0
disable_commandline_tags=2
disable_l2cache=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=300
hdmi_force_cec_address=65535
init_uart_clock=0x2dc6c00
lcd_framerate=60
over_voltage_avs=50000
over_voltage_avs_boost=0x249f0
over_voltage_sdram_p=2
pause_burst_frames=1
program_serial_random=1
sdram_freq=500
sdram_schmoo=0x2000020

I hope that is what you are looking for?

Also after a half hour of usage at the 1.2GHz it locked up again. When I rebooted it I got a dump screen on startup.

[PhilE]

Yes, that's great. The next step is to compare those numbers with a few other units to see if your Pi is in any way an outlier.

[drencor]

Yes, that's great. The next step is to compare those numbers with a few other units to see if your Pi is in any way an outlier.

Well after a half hour of usage the unit locked up again. Then when I restarted it I got the dump screen on the HDMI output....

I have never had a problem with any previous Raspberry Pi till this one.... this is aggravating

[PhilE]

It's just possible there might be useful information in such a dump, so if it happens again a photo would be good. You can increase the amount of information that fits on one screen with this line in config.txt:

Code: Select all

framebuffer_height=2160

[drencor]

It's just possible there might be useful information in such a dump, so if it happens again a photo would be good. You can increase the amount of information that fits on one screen with this line in config.txt:

Code: Select all

framebuffer_height=2160

Yeah that does work nicely, but one small problem. I can't even read the text on my Samsung 720P TV

I will try to see if I can find a USB to 3.3V TTL seral adapter and see if I can enable serial debugging and capture the dump that way the next time it happens.

[PhilE]

Fair enough. I'll take whatever you have, though - 10 lines of a stack trace are better than nothing if it allows us to group your lockup with one of the other issues that have been reported. A serial port hooked up to GPIOs 14 & 15 (pins 8 & 10) would be perfect, but I think you would have mentioned if you had one of those at your disposal.

[drencor]

Fair enough. I'll take whatever you have, though - 10 lines of a stack trace are better than nothing if it allows us to group your lockup with one of the other issues that have been reported. A serial port hooked up to GPIOs 14 & 15 (pins 8 & 10) would be perfect, but I think you would have mentioned if you had one of those at your disposal.

Hmmm so I found a USB to TTL serial adapter that supports 3.3V.

I hooked it up and used raspi-config to enable the boot messages/shell on the serial terminal.

Sadly I am not getting any kernel messages out the serial port. Just the shell? Is there another setting some place I have to force on with the Raspberry Pi 3 B+???

[drencor]

A serial port hooked up to GPIOs 14 & 15 (pins 8 & 10) would be perfect.

Ok so I am attaching a dump that happened shortly after I had left the last comment.

Even though during boot up it didn't output anything to the serial port, but it sure did when it crashed. :O

[PhilE]

Thanks - I have seen a similar stack trace to that before, after hours of copying data under XBian. This has the feel of a race condition, or a fault in some error handling code, or a combination of the two.

[drencor]

Thanks - I have seen a similar stack trace to that before, after hours of copying data under XBian. This has the feel of a race condition, or a fault in some error handling code, or a combination of the two.

Yes, but in my case I am not doing hours of copying. I am just either trying to boot, reboot, or just use Raspbian Stretch release image 2018-03-13 with all updates done.

In this case that dump happened right after the system booted and was finishing loading the GUI.

[horgh]

I am having similar issues. Mine is crashing daily.

I've tried two power supplies: A 2.5A CanaKit and the official Raspberry Pi one. Both crash in similar fashions.

I am not powering anything else from the Pi (but it is connected to a powered USB hub with a USB hard drive).

After a few hours it locks up and goes offline. The red light is on afterwards still.

In one case I had some output from the kernel. I don't have the full output, but here are some hopefully relevant pieces:

Code: Select all

kernel:[57891.042414] page:bb302638 count:0 mapcount:-2228224 mapping:  (null) index:0x1
kernel:[57891.044375] flags: 0x0()
kernel:[58016.083155] page:bb302974 count:0 mapcount:-2097152 mapping:  (null) index:0x1
kernel:[58195.214151] Internal error: Oops: 817 [#1] SMP ARM
kernel:[58195.234299] Process kswapd0 (pid: 40, stack limit = 0xbab38210)
kernel:[58195.235382] Stack: (0xbab39cf8 to 0xbab3a000)

In case it might be overheating, I've also left the cover off its case (an official case). However each time I've checked the temperature it is around 47C apparently.

Code: Select all

root@rpi5:~# vcgencmd get_config int
arm_freq=1400
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=400
desired_osc_freq=0x33e140
desired_osc_freq_boost=0x3c45b0
disable_commandline_tags=2
disable_l2cache=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=300
hdmi_force_cec_address=65535
init_uart_clock=0x2dc6c00
lcd_framerate=60
over_voltage_avs=0x10c8e
over_voltage_avs_boost=0x2ab98
over_voltage_sdram_p=2
overscan_bottom=32
overscan_left=32
overscan_right=32
overscan_top=32
pause_burst_frames=1
program_serial_random=1
sdram_freq=500
sdram_schmoo=0x2000020

It is fully up to date.

[hjimbens]

I have a similar situation. I have two Pi 3 B+. The first one locks up after five or ten minutes of operation. Screen freezes, ssh connections freeze, the Pi no longer responds to keyboard. Both red and green leds are on. I am using the official power supply. I monitor temperature via a separate ssh connection, it is around 52 degrees Celsius at the time of lockup, but the processor feels extremely hot (as compared to luke warm before the lockup) when it is locked up. Lockups also occur when I set arm_freq=700 in config.txt.
The second 3 B+, with the SD card that locks up the first one, works fine. Other Pi 3 B (not plus) and Pi 2 also work fine with that SD card.

[rsterz]

I had lockup issues with my new 3B+ as well - I sent it back for replacement. I used the current Raspbian version (via NOOBS or directly with Etcher resulted in the same issue) using the 2.5A official power supply and tried two different SD cards. Temperature around 50 - 55C.

I had the chance to take a photo of one of the lockups. Maybe that helps anyone to find out what happens to those Pis. There are a few little colored dots above the error log. Maybe related to GPU/memory issue?

I posted this screenshot in another thread but received no response. Sorry for posting twice. But I thought the photo might be useful to find the issue. I hope that my replacement Pi will work stable (keeping my fingers crossed).

[PhilE]

I'm afraid there isn't much we can learn from that log - did running memtester seem to provoke the crashes?