User avatar
LitterBugs
Posts: 36
Joined: Tue Feb 24, 2015 2:49 am

Re: Raspberry Pi 3 B+ lockups

Wed Apr 11, 2018 5:32 pm

I have a few PI3 and Pi2s running headless flight feeders 24x7x365 to FlightAware. Picked up a Pi3 B+ over the weekend and am having lockup issues as well. Currently it will run for 4-8 hours and then hang. When I get to it, the red power light is on solid and the board is really really warm. It will reboot immediately. I have swapped out the PS and SD already with known working equipment. Running the latest Raspbian-Stretch-Lite image downloaded on the 7th with all updates and then added the piaware software on top of that.

I Just found this thread and am going to test the previous recommendations to see if mine becomes more stable and will report back with my findings.

Regards,
LitterBug

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2490
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Raspberry Pi 3 B+ lockups

Wed Apr 11, 2018 8:38 pm

That's great - the more data points we have, the better.

drencor
Posts: 27
Joined: Sun Feb 16, 2014 11:45 pm

Re: Raspberry Pi 3 B+ lockups

Wed Apr 11, 2018 9:45 pm

PhilE wrote:
Tue Apr 10, 2018 8:02 am
@Nilpo That's a good point. You are correct that they come without anti-static bags, but the box is made is made of cardboard with an anti-static coating. We should have made that clear on the packaging.
Yes it would have helped with the confusion on these if there would have been a notice on the box about the special coating.

There are probably a lot of us that have been in the electronics and computer field that are use to the traditional anti-static bags for protecting the sensitive electronics over the years. Which when we opened our devices and saw no protective anti-static bag probably freaked out. I know I did.

horgh
Posts: 15
Joined: Wed Mar 28, 2018 12:10 am
Location: Vancouver, BC, Canada

Re: Raspberry Pi 3 B+ lockups

Thu Apr 12, 2018 1:12 am

I've continued running memtester.

So far no issues!

I ran for ~14h with:

Code: Select all

over_voltage_sdram_p=3
over_voltage_sdram_i=4
And ~6h with:

Code: Select all

over_voltage_sdram_p=3
over_voltage_sdram_i=3
I just started with this:

Code: Select all

over_voltage_sdram_p=2
over_voltage_sdram_i=3

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5372
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Raspberry Pi 3 B+ lockups

Thu Apr 12, 2018 1:41 pm

ejolson wrote:
Tue Apr 10, 2018 8:38 pm
Is there any way for educational purposes of providing more details what the schmoo flags do?
The bottom 4 nibbles allow the DLL phases to be adjusted (i.e. when data is sampled compared to clock edge).
The next 3 allow drive strengths to be adjusted.
The top one has flags related to low power modes.

These settings have allowed some determined overclockers to get more speed out of their specific Pi boards (by trial and error adjustments).
But tweaking these can also be useful when diagnosing an issue that is possibly sdram related.

If adjusting these settings, or the sdram voltage settings makes a bad board reliable then it narrows down where the problem is.

User avatar
LitterBugs
Posts: 36
Joined: Tue Feb 24, 2015 2:49 am

Re: Raspberry Pi 3 B+ lockups

Thu Apr 12, 2018 2:14 pm

I dropped arm_freq to 1200 and sdram_freq to 450 and have been stable for 12 hours. So it looks as if I am experiencing the same issue as others. Any particular settings you would like me to check and/or set for comparisons sake?

Regards,
LitterBug

PS: I have statistics logging on my box..... Periods with no graph are where the box was hung (and very hot)
Image
Last edited by LitterBugs on Thu Apr 12, 2018 2:59 pm, edited 3 times in total.

syadnom
Posts: 24
Joined: Tue Jan 31, 2012 2:43 am

Re: Raspberry Pi 3 B+ lockups

Thu Apr 12, 2018 2:49 pm

I'm also having a nightly lockup on the Pi 3 B+. I haven't tested any CPU or Memory speeds just yet, just wanted to chime in. Pi 3 B didn't have this issue.

I'll be setting cpu and mem to 1200/450 to test this afternoon.

User avatar
LitterBugs
Posts: 36
Joined: Tue Feb 24, 2015 2:49 am

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 2:43 am

Hmmm. Didn't make it 24 hours. Hung again tonight even with lower clocking. Definitely more stable, but still not reliable.

Any settings I should try before swapping it out at my local store where I purchased it?

Regards,
LitterBug

User avatar
RaTTuS
Posts: 10504
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK
Contact: Twitter YouTube

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 6:57 am

LitterBugs wrote:
Fri Apr 13, 2018 2:43 am
Hmmm. Didn't make it 24 hours. Hung again tonight even with lower clocking. Definitely more stable, but still not reliable.

Any settings I should try before swapping it out at my local store where I purchased it?

Regards,
LitterBug
report
vcgencmd get_config int | grep -E "(volt|sdram)"

you may be sufering the same
but that will not explain the heat

how hot ?
what does
vcgencmd measure_temp
say
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

e-raser
Posts: 71
Joined: Sat Apr 04, 2015 1:30 pm

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 12:23 pm

According to the (very very helpful) information from viewtopic.php?t=208821&start=125 it SHOULD run stable with everything at default (so arm freq = 1400 and sdram = 500) but adjusting the sdram overvoltage), right?

While I‘m trying this this evening (pi currently died again at home with arm 1500/sdram 500, I had a SD card crash this week and wanted to rule that out so set all overclocking back to default) I really like to know:

1) To everyone:
What are possible side effects of these (obviously working around the issue) over voltage settings? Only more power consumption? Hardware stress equals reduced lifetime? Lower performance?

Depending on the answer maybe some of us affected could live with that, some would need a return.

2) To the Pi developers/foundation:
What could happen when finding „the“ root cause: hardware exchange program, only software updates (rip-kernel), ...? I think nobody wants a kernel update which lowers performance or sth. like that.

#2 is a time critical question for me cause I can get a new 3 B+ for a good price.
1x Nextcloud & Pi-hole & ... on Raspbian @ Pi (4 4 GB)
1x Kodi media center on LibreELEC @ Pi 3 B+

syadnom
Posts: 24
Joined: Tue Jan 31, 2012 2:43 am

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 1:45 pm

vcgencmd get_config int | grep -E "(volt|sdram)"
over_voltage_avs=37500
over_voltage_avs_boost=0x23186
sdram_freq=450

for those interested.

1200x450 survived the night for me. I don't need more performance, I naively bought the B+ because it was 'newer', my stuff runs happily at lower clock speeds. If it locks up again I'm going to swap in a B and be done with it until there is some resolution.

User avatar
LitterBugs
Posts: 36
Joined: Tue Feb 24, 2015 2:49 am

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 3:06 pm

RaTTuS wrote:
Fri Apr 13, 2018 6:57 am
report
vcgencmd get_config int | grep -E "(volt|sdram)"

you may be sufering the same
but that will not explain the heat

how hot ?
what does
vcgencmd measure_temp
say
It only gets hot AFTER it locks up. It consistently runs 44C under normal operating conditions. Last night I just happened to catch it not too long after it hung and it wasn't all that hot yet. But after a couple hours sitting hung, it will be probably 80+C. (I'll have to get my infrared thermo on it next time to be sure)

pi@raspberrypi:~ $ vcgencmd get_config int |grep -E "(volt|sdram)"
over_voltage_avs=50000
over_voltage_avs_boost=0x249f0
sdram_freq=450

pi@raspberrypi:~ $ vcgencmd measure_temp
temp=44.0'C

Stats collected with this SDcard. Starting thursday, the Core and Mem clocks were reduced to 1200/450. The previous SDcard had runtimes from 2-6 hours before hanging.
Image

Regards,
LitterBug

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5372
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 5:21 pm

e-raser wrote:
Fri Apr 13, 2018 12:23 pm
What could happen when finding „the“ root cause: hardware exchange program, only software updates (rip-kernel), ...? I think nobody wants a kernel update which lowers performance or sth. like that.
It is likely to have a software solution (firmware rather than kernel).
We're hoping to be able to solve it by tweaking the sdram drive settings which won't have an effect on performance.
An temporary solution is to set sdram_freq=450, arm_freq=1200 (you may only need one of these) which seems to avoid the issue for most.

Obviously if you have a problem you can return the Pi to the seller.
Currently we're interested in getting any failing Pi's back here at Pi Towers for further testing,
so contact me or Phil if you are happy to do that. (The problem is actually quite rare, and we haven't been able to reproduce with any Pi's in the office - just the one returned by PeterO).

YorkshireTyke
Posts: 11
Joined: Wed May 24, 2017 12:28 pm
Location: Cambs. U.K.

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 5:40 pm

Having sent my first RPi 3B+ back to my supplier I received another one.
Yet again it's locking up.
I flashed Raspbian to a new SD card (32GB), usual apt-get update/upgrade (but not a rpi-update).
Edited config.txt, set arm_freq=1200 & sdram_freq=450.
I then ran memtester 512M, and it locked up within 10 minutes (stopped with "Bit Flip: testing 29").

Code: Select all

$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=62500
over_voltage_avs_boost=0x2932e
pause_burst_frames=1
program_serial_random=1
sdram_freq=450

Code: Select all

$dmesg

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.30-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1102 SMP Mon Mar 26 16:45:49 BST 2018
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x3ac00000
[    0.000000] On node 0 totalpages: 242688
[    0.000000] free_area_init_node: node 0, pgdat 80c7edc0, node_mem_map ba3a1000
[    0.000000]   Normal zone: 2133 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 242688 pages, LIFO batch:31
[    0.000000] random: fast init done
[    0.000000] percpu: Embedded 17 pages/cpu @ba34a000 s38720 r8192 d22720 u69632
[    0.000000] pcpu-alloc: s38720 r8192 d22720 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1600 bcm2708_fb.fbheight=900 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=a737ba7e-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 940260K/970752K available (7168K kernel code, 550K rwdata, 2048K rodata, 1024K init, 706K bss, 22300K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                   lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x80008000 - 0x80800000   (8160 kB)
                     .init : 0x80b00000 - 0x80c00000   (1024 kB)
                     .data : 0x80c00000 - 0x80c8986c   ( 551 kB)
                      .bss : 0x80c90f40 - 0x80d417f4   ( 707 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 24918 entries in 74 pages
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000018] Switching to timer-based delay loop, resolution 52ns
[    0.000271] Console: colour dummy device 80x30
[    0.000289] console [tty1] enabled
[    0.000314] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000329] pid_max: default: 32768 minimum: 301
[    0.000646] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000661] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001597] Disabling memory control group subsystem
[    0.001678] CPU: Testing write buffer coherency: ok
[    0.002075] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002455] Setting up static identity map for 0x100000 - 0x10003c
[    0.002573] Hierarchical SRCU implementation.
[    0.003207] smp: Bringing up secondary CPUs ...
[    0.003945] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004745] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.005528] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.005631] smp: Brought up 1 node, 4 CPUs
[    0.005642] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.005647] CPU: All CPU(s) started in HYP mode.
[    0.005651] CPU: Virtualization extensions available.
[    0.006504] devtmpfs: initialized
[    0.017218] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.017436] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.017454] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.018011] pinctrl core: initialized pinctrl subsystem
[    0.018750] NET: Registered protocol family 16
[    0.021466] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.026346] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.026354] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.026560] Serial: AMBA PL011 UART driver
[    0.028189] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.028647] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[    0.059903] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb813000, dmachans=0x1
[    0.061402] SCSI subsystem initialized
[    0.061628] usbcore: registered new interface driver usbfs
[    0.061685] usbcore: registered new interface driver hub
[    0.061769] usbcore: registered new device driver usb
[    0.070086] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-03-23 16:31
[    0.071486] clocksource: Switched to clocksource arch_sys_counter
[    0.147344] VFS: Disk quotas dquot_6.6.0
[    0.147430] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.147615] FS-Cache: Loaded
[    0.147814] CacheFiles: Loaded
[    0.156659] NET: Registered protocol family 2
[    0.157382] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.157491] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.157677] TCP: Hash tables configured (established 8192 bind 8192)
[    0.157806] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.157850] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.158077] NET: Registered protocol family 1
[    0.158515] RPC: Registered named UNIX socket transport module.
[    0.158521] RPC: Registered udp transport module.
[    0.158526] RPC: Registered tcp transport module.
[    0.158531] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.160074] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.162826] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.170720] FS-Cache: Netfs 'nfs' registered for caching
[    0.171308] NFS: Registering the id_resolver key type
[    0.171334] Key type id_resolver registered
[    0.171340] Key type id_legacy registered
[    0.173260] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.173379] io scheduler noop registered
[    0.173386] io scheduler deadline registered (default)
[    0.173663] io scheduler cfq registered
[    0.173670] io scheduler mq-deadline registered
[    0.173675] io scheduler kyber registered
[    0.175972] BCM2708FB: allocated DMA memory fad00000
[    0.175997] BCM2708FB: allocated DMA channel 0 @ bb813000
[    0.216374] Console: switching to colour frame buffer device 200x56
[    0.240682] bcm2835-rng 3f104000.rng: hwrng registered
[    0.240815] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.241278] vc-sm: Videocore shared memory driver
[    0.241585] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.251188] brd: module loaded
[    0.260047] loop: module loaded
[    0.260062] Loading iSCSI transport class v2.0-870.
[    0.260723] libphy: Fixed MDIO Bus: probed
[    0.260810] usbcore: registered new interface driver lan78xx
[    0.260864] usbcore: registered new interface driver smsc95xx
[    0.260880] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.489032] Core Release: 2.80a
[    0.489041] Setting default values for core params
[    0.489074] Finished setting default values for core params
[    0.689321] Using Buffer DMA mode
[    0.689328] Periodic Transfer Interrupt Enhancement - disabled
[    0.689333] Multiprocessor Interrupt Enhancement - disabled
[    0.689340] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.689351] Dedicated Tx FIFOs mode
[    0.689768] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xbad14000 dma = 0xfad14000 len=9024
[    0.689793] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.689801] dwc_otg: Microframe scheduler enabled
[    0.689849] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x805d2774
[    0.689859] WARN::hcd_init_fiq:460: FIQ ASM at 0x805d2adc length 36
[    0.689871] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87e000
[    0.689926] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.689959] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.689990] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[    0.690038] Init: Port Power? op_state=1
[    0.690043] Init: Power Port (0)
[    0.690252] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.690263] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.690271] usb usb1: Product: DWC OTG Controller
[    0.690280] usb usb1: Manufacturer: Linux 4.14.30-v7+ dwc_otg_hcd
[    0.690288] usb usb1: SerialNumber: 3f980000.usb
[    0.690879] hub 1-0:1.0: USB hub found
[    0.690921] hub 1-0:1.0: 1 port detected
[    0.691429] dwc_otg: FIQ enabled
[    0.691434] dwc_otg: NAK holdoff enabled
[    0.691439] dwc_otg: FIQ split-transaction FSM enabled
[    0.691448] Module dwc_common_port init
[    0.691719] usbcore: registered new interface driver usb-storage
[    0.691887] mousedev: PS/2 mouse device common for all mice
[    0.691962] IR NEC protocol handler initialized
[    0.691969] IR RC5(x/sz) protocol handler initialized
[    0.691974] IR RC6 protocol handler initialized
[    0.691978] IR JVC protocol handler initialized
[    0.691983] IR Sony protocol handler initialized
[    0.691988] IR SANYO protocol handler initialized
[    0.691993] IR Sharp protocol handler initialized
[    0.691998] IR MCE Keyboard/mouse protocol handler initialized
[    0.692004] IR XMP protocol handler initialized
[    0.692692] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.692949] bcm2835-cpufreq: min=600000 max=1400000
[    0.693297] sdhci: Secure Digital Host Controller Interface driver
[    0.693303] sdhci: Copyright(c) Pierre Ossman
[    0.693654] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.693973] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.694064] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.695458] ledtrig-cpu: registered to indicate activity on CPUs
[    0.695601] hidraw: raw HID events driver (C) Jiri Kosina
[    0.695769] usbcore: registered new interface driver usbhid
[    0.695774] usbhid: USB HID core driver
[    0.696384] vchiq: vchiq_init_state: slot_zero = bad80000, is_master = 0
[    0.697799] [vc_sm_connected_init]: start
[    0.707055] [vc_sm_connected_init]: end - returning 0
[    0.707625] Initializing XFRM netlink socket
[    0.707647] NET: Registered protocol family 17
[    0.707746] Key type dns_resolver registered
[    0.708274] Registering SWP/SWPB emulation handler
[    0.708839] registered taskstats version 1
[    0.714781] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.714869] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.716609] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.716618] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.772115] sdhost: log_buf @ bad13000 (fad13000)
[    0.810689] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.812261] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.813815] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.816601] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.851510] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.852516] of_cfs_init
[    0.852664] of_cfs_init: OK
[    0.853220] Waiting for root device PARTUUID=a737ba7e-02...
[    0.901105] mmc1: new high speed SDIO card at address 0001
[    0.901570] Indeed it is in host mode hprt0 = 00021501
[    1.031666] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.035474] mmc0: new high speed SDHC card at address aaaa
[    1.035934] mmcblk0: mmc0:aaaa SC32G 29.7 GiB
[    1.038344]  mmcblk0: p1 p2
[    1.065954] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    1.065962] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    1.111528] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.111669] Indeed it is in host mode hprt0 = 00001101
[    1.270344] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[    1.272336] EXT4-fs (mmcblk0p2): 1 orphan inode deleted
[    1.272343] EXT4-fs (mmcblk0p2): recovery complete
[    1.304929] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.304993] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.306770] devtmpfs: mounted
[    1.310208] Freeing unused kernel memory: 1024K
[    1.351819] usb 1-1: New USB device found, idVendor=0424, idProduct=2514
[    1.351832] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.352423] hub 1-1:1.0: USB hub found
[    1.352511] hub 1-1:1.0: 4 ports detected
[    1.671539] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.699548] systemd[1]: System time before build time, advancing clock.
[    1.801782] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514
[    1.801797] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.802520] hub 1-1.1:1.0: USB hub found
[    1.802686] hub 1-1.1:1.0: 3 ports detected
[    1.819698] NET: Registered protocol family 10
[    1.820903] Segment Routing with IPv6
[    1.832641] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.854860] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    1.855422] systemd[1]: Detected architecture arm.
[    1.856352] systemd[1]: Set hostname to <RPI-3B-Plus-PiDAC-Plus>.
[    1.901587] usb 1-1.2: new low-speed USB device number 4 using dwc_otg
[    2.058437] usb 1-1.2: New USB device found, idVendor=04f3, idProduct=0103
[    2.058452] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.070972] input: HID 04f3:0103 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:04F3:0103.0001/input/input0
[    2.071627] hid-generic 0003:04F3:0103.0001: input,hidraw0: USB HID v1.11 Keyboard [HID 04f3:0103] on usb-3f980000.usb-1.2/input0
[    2.083504] input: HID 04f3:0103 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2:1.1/0003:04F3:0103.0002/input/input1
[    2.083725] hid-generic 0003:04F3:0103.0002: input,hidraw1: USB HID v1.11 Device [HID 04f3:0103] on usb-3f980000.usb-1.2/input1
[    2.151541] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg
[    2.284756] usb 1-1.1.2: New USB device found, idVendor=05dc, idProduct=b051
[    2.284771] usb 1-1.1.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[    2.284780] usb 1-1.1.2: Product: microSD RDR 
[    2.284788] usb 1-1.1.2: Manufacturer: Lexar
[    2.284796] usb 1-1.1.2: SerialNumber: 000000000001
[    2.285626] usb-storage 1-1.1.2:1.0: USB Mass Storage device detected
[    2.285966] scsi host0: usb-storage 1-1.1.2:1.0
[    2.303652] systemd[1]: Listening on Journal Socket (/dev/log).
[    2.304326] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.305136] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    2.305451] systemd[1]: Listening on udev Control Socket.
[    2.305650] systemd[1]: Listening on fsck to fsckd communication Socket.
[    2.305946] systemd[1]: Listening on Journal Socket.
[    2.306192] systemd[1]: Listening on Syslog Socket.
[    2.381607] usb 1-1.1.3: new low-speed USB device number 6 using dwc_otg
[    2.422753] i2c /dev entries driver
[    2.537592] usb 1-1.1.3: New USB device found, idVendor=1bcf, idProduct=0005
[    2.537614] usb 1-1.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[    2.537625] usb 1-1.1.3: Product: USB Optical Mouse
[    2.554664] input: USB Optical Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:1BCF:0005.0003/input/input2
[    2.555215] hid-generic 0003:1BCF:0005.0003: input,hidraw2: USB HID v1.10 Mouse [USB Optical Mouse] on usb-3f980000.usb-1.1.3/input0
[    2.742656] nf_conntrack version 0.5.0 (15360 buckets, 61440 max)
[    2.793281] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    2.844824] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    2.851624] usb 1-1.1.1: new high-speed USB device number 7 using dwc_otg
[    2.932583] systemd-journald[91]: Received request to flush runtime journal from PID 1
[    2.984826] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800
[    2.984845] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.259945] libphy: lan78xx-mdiobus: probed
[    3.353011] scsi 0:0:0:0: Direct-Access     Lexar    microSD RDR      0815 PQ: 0 ANSI: 6
[    3.356395] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    3.989562] snd-rpi-iqaudio-dac soc:sound: ASoC: CPU DAI (null) not registered - will retry
[    3.992429] snd-rpi-iqaudio-dac soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[    4.010474] snd-rpi-iqaudio-dac soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok
[    4.060790] brcmfmac: F1 signature read @0x18000000=0x15264345
[    4.070423] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[    4.071229] usbcore: registered new interface driver brcmfmac
[    4.149875] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    4.324031] random: crng init done
[    4.365507] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    4.366137] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28 
[    5.478199] uart-pl011 3f201000.serial: no DMA platform data
[    5.816297] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    5.816330] brcmfmac: power management disabled
[    6.334118] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.717629] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[    9.734009] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   11.689414] Bluetooth: Core ver 2.22
[   11.689468] NET: Registered protocol family 31
[   11.689471] Bluetooth: HCI device and connection manager initialized
[   11.689487] Bluetooth: HCI socket layer initialized
[   11.689494] Bluetooth: L2CAP socket layer initialized
[   11.689512] Bluetooth: SCO socket layer initialized
[   11.694270] Bluetooth: HCI UART driver ver 2.3
[   11.694281] Bluetooth: HCI UART protocol H4 registered
[   11.694285] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   11.876264] fuse init (API version 7.26)
[   11.894822] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.894831] Bluetooth: BNEP filters: protocol multicast
[   11.894846] Bluetooth: BNEP socket layer initialized
[   11.963673] Bluetooth: RFCOMM TTY layer initialized
[   11.963704] Bluetooth: RFCOMM socket layer initialized
[   11.963729] Bluetooth: RFCOMM ver 1.11
[   66.243449] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:6c:b0:ce:b2:51:66:08:00:46:c0:00:20:00:00:40:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  146.865679] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
[  191.686271] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:6c:b0:ce:b2:51:66:08:00:46:c0:00:20:00:00:40:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
[  317.130239] [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:00:01:6c:b0:ce:b2:51:66:08:00:46:c0:00:20:00:00:40:00 SRC=0.0.0.0 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
What to do next?

User avatar
bensimmo
Posts: 4187
Joined: Sun Dec 28, 2014 3:02 pm
Location: East Yorkshire

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 6:37 pm

Is it a particular batch from the same supplier?
A less good set of RAM chips or possibly voltage regulator (since that's a new part)?


I've been running memtest on mine since last night and it just will not break.
(from Pimoroni shortly after release, boxed)

User avatar
davidcoton
Posts: 4259
Joined: Mon Sep 01, 2014 2:37 pm
Location: Cambridge, UK

Re: Raspberry Pi 3 B+ lockups

Fri Apr 13, 2018 9:17 pm

YorkshireTyke wrote:
Fri Apr 13, 2018 5:40 pm
What to do next?
Read the post immediately above yours and PM dom about sending your Pi to Pi Towers (in Cambridge!)

EDIT:typos
Last edited by davidcoton on Sun Apr 15, 2018 12:07 pm, edited 1 time in total.
Signature retired

e-raser
Posts: 71
Joined: Sat Apr 04, 2015 1:30 pm

Re: Raspberry Pi 3 B+ lockups

Sat Apr 14, 2018 1:07 am

Hi,

just my two cents: after running stable for two days with only sdram freq set to 450 I now spent some time with memchecker and over voltage and no "underclocking" (everything else default):
over_voltage_sdram_p=3
over_voltage_sdram_i=3
[

Don´t know if "..._c" (so all three) also needs to be set.

13.04 22:14 „sudo memtester 512M“
—> after ~ 2 h (Loop 7?) 1x short freeze, memory errors on console (only smartphone picture available)
—> after ~ 3 h (Loop 12?) 1x freeze again + memory errors on console (only smartphone picutre available)


For both events the system stayed alive but was unresponsive and freezing for maybe 30 to 90 seconds. Unfortunately I don´t have much more time for testing. Anyone from the licensed "The Pi Hut" reseller here on this thread?
1x Nextcloud & Pi-hole & ... on Raspbian @ Pi (4 4 GB)
1x Kodi media center on LibreELEC @ Pi 3 B+

horgh
Posts: 15
Joined: Wed Mar 28, 2018 12:10 am
Location: Vancouver, BC, Canada

Re: Raspberry Pi 3 B+ lockups

Sat Apr 14, 2018 2:48 am

I've continued to test, slowly decreasing these two values one at a time. I've not had any crashes while running memtester yet.

Latest:

24h at

Code: Select all

over_voltage_sdram_p=2
over_voltage_sdram_i=3
18.5h at

Code: Select all

over_voltage_sdram_p=2
over_voltage_sdram_i=2
6.5h at

Code: Select all

over_voltage_sdram_p=1
over_voltage_sdram_i=2

e-raser
Posts: 71
Joined: Sat Apr 04, 2015 1:30 pm

Re: Raspberry Pi 3 B+ lockups

Sat Apr 14, 2018 11:14 am

Good for you, no luck for me.

Even with...
over_voltage_sdram_p=3
over_voltage_sdram_i=3
...my Pi rebooted this morning (08:06) and now (13:13) once again. I‘m totally done with that crappy piece of hardware.

Anyone interested in analyzing it?

I‘ll send it to anyone who‘ll cover my expenses (price: I paid 40,91 € to „The Pi Hut“ via Amazon + return shipping costs: 9 € using DHL standard shipping from Germany to the UK which makes 49 € in total - according to all the time I spent on this faulty Pi during the last 2-3 weeks really nothing *very-frustrated*).

Otherwise I‘ll return it to the seller on Monday, don‘t know what he‘ll do with it. I can get a new Pi 3B+ from a local dealer for 36 €, I‘ll give it a (second and last) try.
1x Nextcloud & Pi-hole & ... on Raspbian @ Pi (4 4 GB)
1x Kodi media center on LibreELEC @ Pi 3 B+

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5372
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Raspberry Pi 3 B+ lockups

Sat Apr 14, 2018 12:25 pm

e-raser wrote:
Sat Apr 14, 2018 11:14 am
I‘ll send it to anyone who‘ll cover my expenses (price: I paid 40,91 € to „The Pi Hut“ via Amazon + return shipping costs: 9 € using DHL standard shipping from Germany to the UK which makes 49 € in total - according to all the time I spent on this faulty Pi during the last 2-3 weeks really nothing *very-frustrated*).
We can't refund money for postage, but we can send you a replacement Pi 3 B+ with a free gift to compensate for postage (e.g. a Pi0W, or a second Pi 3 B+). PM if you are interested.

ejolson
Posts: 3826
Joined: Tue Mar 18, 2014 11:47 am

Re: Raspberry Pi 3 B+ lockups

Sat Apr 14, 2018 6:59 pm

e-raser wrote:
Sat Apr 14, 2018 11:14 am
Even with...
over_voltage_sdram_p=3
over_voltage_sdram_i=3
...my Pi rebooted this morning (08:06) and now (13:13) once again. I‘m totally done with that crappy piece of hardware.
Stability is almost always more important than speed. Related to stability is error-free operation of the entire SOC. For example, if the floating point hardware is experiencing all sorts of errors, this won't affect the stability of an operating system kernel which doesn't use floating point arithmetic. When I use computers, getting correct answers is as important as stability. To this end, it would be interesting to know whether those people who were able to solve their stability issues by changing settings in the boot directory get correct results when running the calculation described in this thread.

Rather than floating point arithmetic errors, the problems reported here seem related to memory speed. While reducing this from 500 to 450 could decrease performance by as much as 10 percent, it likely won't because most of the program executes out of cache. Therefore, while reduced memory speed may be measurable using benchmarks, the final user experience is likely about the same.

To put things in perspective, the Meltdown mitigations recently implemented for most Intel x86 CPUs slow the system call mechanism by a factor of 3. Theoretically this could decrease system performance by 66 percent (note that a 100 percent performance loss would imply the system doesn't work at all); however, most programs do more than make system calls and most system calls do a nontrivial amount of work between each invocation. Thus, a performance reduction of less than 10 percent has been observed in almost all real use cases.

The rule practiced in many circles is to reduce clock speeds for which the system appears stable by an additional 10 percent to obtain the final recommended settings. In the case of the Pi 3B+, this might result in a memory clock setting of 400 MHz. From my point of view, a memory speed of 400 MHz is still reasonable and not uncommon for single board computers. At the same time, I would be surprised if a further reduction to 400 MHz would be necessary after the correct schmoo settings (thanks to the information provided in this post) and voltage profiles have been worked out.

leon22
Posts: 8
Joined: Sun Apr 15, 2018 3:21 pm

Re: Raspberry Pi 3 B+ lockups

Sun Apr 15, 2018 3:26 pm

dom wrote:
Sat Apr 14, 2018 12:25 pm
e-raser wrote:
Sat Apr 14, 2018 11:14 am
I‘ll send it to anyone who‘ll cover my expenses (price: I paid 40,91 € to „The Pi Hut“ via Amazon + return shipping costs: 9 € using DHL standard shipping from Germany to the UK which makes 49 € in total - according to all the time I spent on this faulty Pi during the last 2-3 weeks really nothing *very-frustrated*).
We can't refund money for postage, but we can send you a replacement Pi 3 B+ with a free gift to compensate for postage (e.g. a Pi0W, or a second Pi 3 B+). PM if you are interested.
Hi!

I have the same problem with my new Pi 3 B+! Always crashes with OpenElec during video playback or other operations like updating the library! So I bought my Model over Amazon -> how can I pm you or should I send it back to Amazon and order a new one?

Thank you!

PS: I did no Firmware updates or speed changes in config file

User avatar
LitterBugs
Posts: 36
Joined: Tue Feb 24, 2015 2:49 am

Re: Raspberry Pi 3 B+ lockups

Sun Apr 15, 2018 4:21 pm

Mine is still hanging every 24 hours or so even reduced to 1200/450. I'm swinging by MicroCenter today to swap it out.

Regards,
LitterBug

milhouse
Posts: 641
Joined: Mon Jan 16, 2012 12:59 pm

Re: Raspberry Pi 3 B+ lockups

Sun Apr 15, 2018 4:26 pm

leon22 wrote:
Sun Apr 15, 2018 3:26 pm
Hi!

I have the same problem with my new Pi 3 B+! Always crashes with OpenElec during video playback or other operations like updating the library! So I bought my Model over Amazon -> how can I pm you or should I send it back to Amazon and order a new one?

Thank you!

PS: I did no Firmware updates or speed changes in config file
OpenELEC does not support RPi3+ - do you mean LibreELEC, or are you using Berryboot?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2490
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Raspberry Pi 3 B+ lockups

Sun Apr 15, 2018 4:29 pm

@leon22 Click on my user ID and you will see an option to send a private message, but you may find it more convenient to email me at phil@raspberrypi.org.

Return to “Troubleshooting”