B.Goode
Posts: 5980
Joined: Mon Sep 01, 2014 4:03 pm
Location: UK

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 8:44 am

I have reported the issue to the retailer and referred them to this thread. Unfortunately they have chosen to blame Lbreelec/Kodi and have insisted that I install and test with Raspian. I have no interest in doing that and don't see it is relevant. They have refused to replace the Pi without me doing this. Considering this is now a well established issue I find this very annoying and disappointing.
So for now I have reverted to the Pi 3B and put the 3B+ back in its box.

Disclaimer: just another forum reader, not a spokesperson for RPF or a supplier.

I'm puzzled that you wouldn't spend 20 minutes or so gathering the evidence requested by the seller. I don't think there is any hint that you have to run Raspbian on a long term basis - it is simply a diagnostic tool: if the RPF hardware fails when running the RPF-supported Operating System it will be clear to everyone's (dis)satisfaction that the hardware is suspect.

User avatar
Gavinmc42
Posts: 2032
Joined: Wed Aug 28, 2013 3:31 am

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 11:57 am

Run every piece of software and OS you can, try to identify the common issues.
The Pi3B+ is an over clocked Pi3B, basically this 40nm silicon has been pushed to it's limits and it looks like past the limits sometimes.

Returning to retailer because it does not run x software is NOT going to solve the issues.

I have two Pi3B+s, same SDcard will lock one of them up.
But I am running Gentoo64 and have 15GBs of software, so right on the bleeding edge and perhaps over the edge.
I have two new Sandisk 16GB A1 cards, one locks up and the other runs compiling all night long.

What are the clock speeds that run without fail,which OS, which SD card etc.
Pi are about learning, learning the answers to these questions helps everyone.
A quick read suggests lowering SDRAM clock might help, so I will try that.

Anyone who overclocks Intel/AMD cpu's don't run whining back to retailers.
There are lots of combinations to try before saying these new Pi's are crap.
Has anyone had lock ups at the old Pi3 clocks?

Test hardware first as everyones software combinations are different.
How to do this? Stress testing code?
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

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

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 12:42 pm

Gavinmc42 wrote:
Fri May 11, 2018 11:57 am

Anyone who overclocks Intel/AMD cpu's don't run whining back to retailers.
But nobody is overclocking anything here.


Some Pi 3B+ couldn't run at the original settings, they are trying to resolve this by altering settings that are not set in stone, i.e. not part of the spec published specifications.
It should add increased stability for all.

Their official OS that they know is up to date is Raspbian. They cannot vouch for other OSs.

They (RPT) do not sell (or make) the Pi3B+, but they did design it. If a retailer wants you to test before sending back, then that is a fair thing to do, it is done with a lot of white goods too. It saves the hassle of trying to fix a problem that may actually be a simple fix or w.r.t. software, something elses fault.

Your contract is with them, the shop, not RaspberryPi.
Countries may vary and your laws for returns should be checked. Either way, if it was a manufacturing defect it would still need to go via the shop. (Or Element14/Farnell as they are the manufacturer).
At least that's the way I see it.

I guess it is overall hard to diagnose problems, when you don't have the problems on the samples you are trying to diagnose it on.

Run the test, give the feedback or use your local retruns laws.

:-)
Mines still chugging away happily though, sorry.

Tozzi1
Posts: 18
Joined: Thu Apr 20, 2017 11:05 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 2:54 pm

jamesh wrote:
Fri May 11, 2018 8:37 am
That's a weird one. Obviously not the same batch, and to have 4 that exhibit the same problem when we in house have difficulty making anything go wrong with random selections of Pi's is very odd. I can only suggest trying RPI update to get the latest settings. Only working at SDRAM 500 is also very very strange, and does me wonder if there are some environmental issues coming in to play.
Since I've done the rpi-update, no more lockups so far, fingers crossed.
So mine must have been a different issue, perhaps something network/WiFi related?

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 19792
Joined: Sat Jul 30, 2011 7:41 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 3:12 pm

Tozzi1 wrote:
Fri May 11, 2018 2:54 pm
jamesh wrote:
Fri May 11, 2018 8:37 am
That's a weird one. Obviously not the same batch, and to have 4 that exhibit the same problem when we in house have difficulty making anything go wrong with random selections of Pi's is very odd. I can only suggest trying RPI update to get the latest settings. Only working at SDRAM 500 is also very very strange, and does me wonder if there are some environmental issues coming in to play.
Since I've done the rpi-update, no more lockups so far, fingers crossed.
So mine must have been a different issue, perhaps something network/WiFi related?
Possible. If using wired ethernet, how long are the cables you were using? There was a very recent fix concerning long cables.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

Tozzi1
Posts: 18
Joined: Thu Apr 20, 2017 11:05 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 3:28 pm

jamesh wrote:
Fri May 11, 2018 3:12 pm
Possible. If using wired ethernet, how long are the cables you were using? There was a very recent fix concerning long cables.
I am using a wired connection on one of the machines, but the cable length (to the switch) is just 1 m and the cable itself is rather new.
That one is also connected to another network via WiFi. The other 3 are running headless, connected to that same WLAN.
Can it possibly be related to 5 Ghz WLAN?

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 19792
Joined: Sat Jul 30, 2011 7:41 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 4:14 pm

Tozzi1 wrote:
Fri May 11, 2018 3:28 pm
jamesh wrote:
Fri May 11, 2018 3:12 pm
Possible. If using wired ethernet, how long are the cables you were using? There was a very recent fix concerning long cables.
I am using a wired connection on one of the machines, but the cable length (to the switch) is just 1 m and the cable itself is rather new.
That one is also connected to another network via WiFi. The other 3 are running headless, connected to that same WLAN.
Can it possibly be related to 5 Ghz WLAN?
Very difficult to tell. We are dealing with a number of issues all at the same time - not uncommon when you launch a new product with a number of new devices (New SoC, new ethernet chip, new wireless chip). Even though the network chips have been around for a while, with well supported Linux drivers, suddenly using them in the huge variety of environments the Pi find themselves can often show up latent issues. Anyway, we are slowing getting through the issues, and there have been a number of issues fixed in the networking area already.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

gawkmeister
Posts: 7
Joined: Mon Apr 30, 2018 4:00 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 11, 2018 7:03 pm

Just a datapoint for jamesh -- my ethernet/samba issues were fixed by the rpi-update, however, my ethernet cable was also only 1m long.

Tozzi1
Posts: 18
Joined: Thu Apr 20, 2017 11:05 pm

Re: Raspberry Pi 3 B+ lockups

Sat May 12, 2018 10:22 pm

gawkmeister wrote:
Fri May 11, 2018 7:03 pm
Just a datapoint for jamesh -- my ethernet/samba issues were fixed by the rpi-update, however, my ethernet cable was also only 1m long.
Uptime here now: 43 hours. sdram_freq=500. No failures since rpi-update.
Still occasionally broken pipes on ssh connections, but so far no reboots and, most importantly, no more freezing.
This is now the longest uptime I've had so far on the 3B+. Fingers crossed.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 19792
Joined: Sat Jul 30, 2011 7:41 pm

Re: Raspberry Pi 3 B+ lockups

Sun May 13, 2018 7:56 am

Tozzi1 wrote:
Sat May 12, 2018 10:22 pm
gawkmeister wrote:
Fri May 11, 2018 7:03 pm
Just a datapoint for jamesh -- my ethernet/samba issues were fixed by the rpi-update, however, my ethernet cable was also only 1m long.
Uptime here now: 43 hours. sdram_freq=500. No failures since rpi-update.
Still occasionally broken pipes on ssh connections, but so far no reboots and, most importantly, no more freezing.
This is now the longest uptime I've had so far on the 3B+. Fingers crossed.
That's great. Thanks for the update.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

baallrog
Posts: 9
Joined: Mon Jul 08, 2013 7:44 pm

Re: Raspberry Pi 3 B+ lockups

Tue May 15, 2018 10:59 am

Since I exchange my RPI3B+ I’ve got no issues.
The sdram frequency is also manually set to 500 and everything works fine.

I use LibreElec 8.2.5.

Tozzi1
Posts: 18
Joined: Thu Apr 20, 2017 11:05 pm

Re: Raspberry Pi 3 B+ lockups

Wed May 16, 2018 3:14 pm

While it's definitely much better after the rpi-update, I've had another lockup last night, after ~130h uptime.
I noticed a few "hickups" where the machine becomes completely unresponsive for up to 4 hours and then recovers.
This still seems network related to me, and while it's better now, it's not completely fixed yet.

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 19792
Joined: Sat Jul 30, 2011 7:41 pm

Re: Raspberry Pi 3 B+ lockups

Wed May 16, 2018 3:26 pm

Tozzi1 wrote:
Wed May 16, 2018 3:14 pm
While it's definitely much better after the rpi-update, I've had another lockup last night, after ~130h uptime.
I noticed a few "hickups" where the machine becomes completely unresponsive for up to 4 hours and then recovers.
This still seems network related to me, and while it's better now, it's not completely fixed yet.
Anything in the logs? 130h is odd, I would expect frequency related issues to show up much earlier than that, so maybe, as you surmise, still a networking issue in there somewhere. Unresponsive for 4h is also a weird one!
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

Tozzi1
Posts: 18
Joined: Thu Apr 20, 2017 11:05 pm

Re: Raspberry Pi 3 B+ lockups

Wed May 16, 2018 4:46 pm

jamesh wrote: Anything in the logs? 130h is odd, I would expect frequency related issues to show up much earlier than that, so maybe, as you surmise, still a networking issue in there somewhere. Unresponsive for 4h is also a weird one!
I'll wait a little to see if it recovers (it's in lockdown mode right now) and try to pull some corresponding log entries.
Any log files I should particularly look at?

Tozzi1
Posts: 18
Joined: Thu Apr 20, 2017 11:05 pm

Re: Raspberry Pi 3 B+ lockups

Thu May 17, 2018 12:55 am

OK so, the one Pi 3B+ I'm monitoring atm was down from less than 15 minutes after 10:03 this morning, until I cold started it again an hour ago by pulling the plug.
There's nothing unusual in the logs. At least not in the "standard" ones (messages, syslog, debug, kern).
Some of them seem to be littered with ^@ (ASCII 0) however, in between.

I can tell pretty much exactly when the PI became unresponsive.
As a hobby brewer, I have got a Model 3B in my basement, which is receiving temperature and gravity readings from my fermentation vessels, currently every 15 minutes, and forwards them via generic TCP Socket to the 3B+ I have here on the second floor.

These temperature graphs, taken from both devices, show exactly when my 3B+ went belly-up but got well again, until it finally(?) flatlined and had to be revived brute-force today:
Screen Shot 2018-05-17 at 02.16.54.png
Model 3B (not Plus)
Screen Shot 2018-05-17 at 02.16.54.png (15.28 KiB) Viewed 1014 times
Screen Shot 2018-05-17 at 02.14.57.png
3B+ with hickup and ultimate failure
Screen Shot 2018-05-17 at 02.14.57.png (11.54 KiB) Viewed 1014 times

As you can see, the 3B+ had a "hickup" for a few hours, some 2-3 days ago, but recovered, then died ultimately last morning.
(Intermittently, there is data missing on the "old" 3B, too, but that is due to other causes. The forwarded data should have come through.)

I agree that this is highly unlikely to be related to frequency issues. As I said before, I can run memtester like forever w/o any issues.
Thermal problems can be ruled out as well, as the temperature never exceeds 59˚C under full load (FLIRC case).
There is, however, a lot of network traffic this Pi has to deal with, at both 2,4 and 5 GHz as well as wired Ethernet..

//EDIT: I just noticed there is yet a new rpi-update available; I'm trying that one now.

mangodan2003
Posts: 24
Joined: Thu Apr 23, 2015 1:10 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 18, 2018 4:09 pm

TL;DR rsyncing a system via LAN to local SD card is a good way to show up if the system is vulnerable to locking up. (rpi-update'd only an hour or so ago)

I'm also having problems with frequent lockups. I've just run rpi-update and just been able to reproduce a lockup.

I'm running a Master and 8 slaves, all of which PXE boot from the master. I was having a few issues with this, both with the PXE boot process and then with crashes later on in boot. I tried to workaround by making a script that runs at boot and rsyncs the system to an SD card if present (checking it for updates on the master on subsequent boots). However the RPis often crash during the rysync. sometimes the rsync just seems to hang part way through, no trace of the rsync process on the master, slave just sits waiting indefinitely. Other times either the master or a slave has just locked up entirely, sometimes with a full screen kernel oops, tho most of the time they are headless so this is not always visible. I have definitely seen a number of lockups where there is no output on the screen though. I have worked around the rsync issue by making the SD unbootable until the rsync succeeds such that if they freeze can just power cycle and let it try again. But I suspect the system is not going to be very stable at all at present and may have to revert to using the Rpi3 B for it for now.

balboah
Posts: 14
Joined: Sat May 12, 2018 11:45 pm

Re: Raspberry Pi 3 B+ lockups

Fri May 18, 2018 7:29 pm

hjimbens wrote:
Wed Mar 28, 2018 7:38 am
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.
I've experienced the same from start on my 3B+, unable to get any logs as everything just freeze. But it also gets very hot when in the frozen state.
Haven't seen an uptime for more than a day so far, with no more than 20% cpu utilization

wagnbeu0
Posts: 18
Joined: Mon Apr 30, 2018 4:23 pm

Re: Raspberry Pi 3 B+ lockups

Mon May 21, 2018 1:36 pm

I have also problems with my Pi3+. Whenever I add a ISCSI or NFs Share and create high OI on the mounted device, my pi3+ freezes.
I don´t know the problem from my Pi1,2 and Pi3 where I used USB Devices, and also don´t now the problem from work where we heavily use NFS and ISCSI on servers, but the pi3+ seems to have a driver problem here.
I just downloaded via rpi-update tha latest kernel (4.14.41) and just rerun a dd backup of my sdcard. Will check if it runs through.

wagnbeu0
Posts: 18
Joined: Mon Apr 30, 2018 4:23 pm

Re: Raspberry Pi 3 B+ lockups

Mon May 21, 2018 2:02 pm

No, it does not, even a rpu-update does not help. This is dmesg while backup up my sdcard via raspibackup using tar:

[Mai21 15:56] INFO: task dd:2360 blocked for more than 120 seconds.
[ +0,000012] Tainted: G C 4.14.41-v7+ #1113
[ +0,000006] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this m essage.
[ +0,000006] dd D 0 2360 2166 0x00000000
[ +0,000041] [<8079af38>] (__schedule) from [<8079b5b0>] (schedule+0x50/0xa8)
[ +0,000017] [<8079b5b0>] (schedule) from [<8014b0b4>] (io_schedule+0x20/0x40)
[ +0,000018] [<8014b0b4>] (io_schedule) from [<8021ca94>] (wait_on_page_bit+0x1 10/0x130)
[ +0,000016] [<8021ca94>] (wait_on_page_bit) from [<8021cb94>] (__filemap_fdata wait_range+0xe0/0x114)
[ +0,000016] [<8021cb94>] (__filemap_fdatawait_range) from [<8021f074>] (filema p_write_and_wait_range+0x68/0xa4)
[ +0,000016] [<8021f074>] (filemap_write_and_wait_range) from [<80396c20>] (nfs _file_fsync+0x3c/0x290)
[ +0,000018] [<80396c20>] (nfs_file_fsync) from [<802c0580>] (vfs_fsync_range+0 x68/0xc8)
[ +0,000017] [<802c0580>] (vfs_fsync_range) from [<802c0614>] (vfs_fsync+0x34/0 x3c)
[ +0,000019] [<802c0614>] (vfs_fsync) from [<803d1ab4>] (nfs4_file_flush+0x84/0 x94)
[ +0,000018] [<803d1ab4>] (nfs4_file_flush) from [<80286b98>] (filp_close+0x40/ 0x8c)
[ +0,000015] [<80286b98>] (filp_close) from [<802aae10>] (__close_fd+0xc8/0xec)
[ +0,000014] [<802aae10>] (__close_fd) from [<80286c14>] (SyS_close+0x30/0x58)
[ +0,000017] [<80286c14>] (SyS_close) from [<80108060>] (ret_fast_syscall+0x0/0 x28)
[Mai21 15:57] nfs: server 192.168.10.2 not responding, still trying
[ +0,000019] nfs: server 192.168.10.2 not responding, still trying
[ +0,000024] nfs: server 192.168.10.2 not responding, still trying
[ +0,000060] nfs: server 192.168.10.2 not responding, still trying
[ +0,000233] nfs: server 192.168.10.2 not responding, still trying
[ +1,042453] nfs: server 192.168.10.2 not responding, still trying
[ +0,002951] nfs: server 192.168.10.2 OK
[ +0,000794] nfs: server 192.168.10.2 not responding, still trying
[ +0,002543] nfs: server 192.168.10.2 OK
[ +0,000926] nfs: server 192.168.10.2 not responding, still trying
[ +0,002620] nfs: server 192.168.10.2 not responding, still trying
[ +0,001038] nfs: server 192.168.10.2 OK
[ +0,001951] nfs: server 192.168.10.2 not responding, still trying
[ +0,001051] nfs: server 192.168.10.2 OK
[ +0,002189] nfs: server 192.168.10.2 not responding, still trying
[ +0,002696] nfs: server 192.168.10.2 not responding, still trying
[ +0,000554] nfs: server 192.168.10.2 OK
[ +0,001281] nfs: server 192.168.10.2 OK
[ +0,001184] nfs: server 192.168.10.2 not responding, still trying
[ +0,002352] nfs: server 192.168.10.2 OK
[ +0,001219] nfs: server 192.168.10.2 not responding, still trying
[ +0,002545] nfs: server 192.168.10.2 OK
[Mai21 15:58] INFO: task dd:2360 blocked for more than 120 seconds.
[ +0,000012] Tainted: G C 4.14.41-v7+ #1113
[ +0,000005] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this m essage.
[ +0,000007] dd D 0 2360 2166 0x00000000
[ +0,000040] [<8079af38>] (__schedule) from [<8079b5b0>] (schedule+0x50/0xa8)
[ +0,000018] [<8079b5b0>] (schedule) from [<8014b0b4>] (io_schedule+0x20/0x40)
[ +0,000017] [<8014b0b4>] (io_schedule) from [<8021ca94>] (wait_on_page_bit+0x1 10/0x130)
[ +0,000016] [<8021ca94>] (wait_on_page_bit) from [<8021cb94>] (__filemap_fdata wait_range+0xe0/0x114)
[ +0,000015] [<8021cb94>] (__filemap_fdatawait_range) from [<8021f074>] (filema p_write_and_wait_range+0x68/0xa4)
[ +0,000017] [<8021f074>] (filemap_write_and_wait_range) from [<80396c20>] (nfs _file_fsync+0x3c/0x290)
[ +0,000018] [<80396c20>] (nfs_file_fsync) from [<802c0580>] (vfs_fsync_range+0 x68/0xc8)
[ +0,000017] [<802c0580>] (vfs_fsync_range) from [<802c0614>] (vfs_fsync+0x34/0 x3c)
[ +0,000019] [<802c0614>] (vfs_fsync) from [<803d1ab4>] (nfs4_file_flush+0x84/0 x94)
[ +0,000018] [<803d1ab4>] (nfs4_file_flush) from [<80286b98>] (filp_close+0x40/ 0x8c)
[ +0,000016] [<80286b98>] (filp_close) from [<802aae10>] (__close_fd+0xc8/0xec)
[ +0,000014] [<802aae10>] (__close_fd) from [<80286c14>] (SyS_close+0x30/0x58)
[ +0,000017] [<80286c14>] (SyS_close) from [<80108060>] (ret_fast_syscall+0x0/0 x28)
[ +36,880263] nfs: server 192.168.10.2 not responding, still trying
[ +0,005436] nfs: server 192.168.10.2 OK
[ +0,002941] nfs: server 192.168.10.2 OK
[ +0,004619] nfs: server 192.168.10.2 OK
[ +0,002820] nfs: server 192.168.10.2 OK
[ +0,003281] nfs: server 192.168.10.2 OK
[ +0,005023] nfs: server 192.168.10.2 not responding, still trying
[ +0,000293] nfs: server 192.168.10.2 OK
[ +0,002250] nfs: server 192.168.10.2 OK
[ +0,007815] nfs: server 192.168.10.2 OK

mangodan2003
Posts: 24
Joined: Thu Apr 23, 2015 1:10 pm

Re: Raspberry Pi 3 B+ lockups

Mon May 21, 2018 2:06 pm

It seems to me the problem may have been resolved with the latest from rpi-update

4.14.41-v7+

However it introduces a new problem whereby the kernel often crashes very early in startup.

I had previously posted the problem persisted and seemed to be resolved by

ethtool --offload eth0 rx off tx off (as found in another thread on this forum)

However I think I may have made experimental error and not tested enough before posting.

wybielacz
Posts: 29
Joined: Wed Nov 06, 2013 9:37 pm

Re: Raspberry Pi 3 B+ lockups

Sun May 27, 2018 8:14 am

wybielacz wrote:
Sat May 05, 2018 11:21 am

I am struggling with this issue since i updated to the new Pi 3 B+ in March and was trying to find a solution to the problem, did change power supply, sd card, reinstalled raspbian many times without any solution. Just today i found this topic...

Fresh install raspbian scratch, nothing installed, just firmware update. Pi always hangs over night, at the morning the cpu heatsink is pretty hot and pi dead. I need to do a hard reboot.
So i got a replacement for my RPi 3B+, and exactly the same issue is still happening with the replacement unit... Specially I bought a new sd card to make sure that all my other sd cards aren't faulty...

I already wasted so much money (bought new sd cards, power supplies) on this piece of thrash and nothing helped. I am really disappointed about the quality of the Raspberry Pi 3B+. Why this piece of crap can't survive a night??

I guess they rushed so much with the 3B+ that they didn't do proper quality testing and released a product which is literally defective. Will there finally be an official statement about this and a proper recall of all defective units?

User avatar
Gavinmc42
Posts: 2032
Joined: Wed Aug 28, 2013 3:31 am

Re: Raspberry Pi 3 B+ lockups

Sun May 27, 2018 10:15 am

What version of firmware are you running?
4.14.41 seems better to me. Whoops that's 10days old now, 4.14.43 is two days old.
https://github.com/raspberrypi/firmware/commits/master

When you are talking crap, be specific, which crap you are talking about, the hardware or software?

How many defective units are there do you know?
What is the defect?
Which line of source code is the problem?
Is it the new Lan chip or new RF combo chip or new power supply chip?

The Pi3B+ is basically a new design with most of the major parts changed.
Some parts are so new RPT is the first and only company using them.
New chips end up with things called errata, these are found by users, ways around the issues are figured out and solutions are found.

This is called engineering.
As chips are now very complex it would take millions of years to check everything and even then cosmic rays can cause issues.
Check NASA websites about tin whiskers killing space vehicles.
$Millions lost due to tiny wires that grow 100th the size of a human hair and still nobody knows how this happens in some metals.
Raspberry Pi's are much more complex than NASA computers.

Raspberry Pi firmware github etc are the appropriate place to put in details of faults.
Just saying it is brown and smells could mean it is great compost but does not help isolate the issue to a repeatable problem and hence fixable solution ;)
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

swockan
Posts: 1
Joined: Sun May 27, 2018 10:28 am

Re: Raspberry Pi 3 B+ lockups

Sun May 27, 2018 10:31 am

So I'm joining the club of locked up Pi:s. Bought mine on launch. Havent touched it untill last night. tried a ton of images and I get maybe 20 minutes and then lockups. It's frustrating trying 3 different psu, including the original one. Very instable operation. Doing a update on the firmware as suggested now and we will see. Have attached massive heatsinks on all chips but nothing helps. Going to contact dealer to get a replacement.

wybielacz
Posts: 29
Joined: Wed Nov 06, 2013 9:37 pm

Re: Raspberry Pi 3 B+ lockups

Sun May 27, 2018 12:45 pm

Gavinmc42 wrote:
Sun May 27, 2018 10:15 am
The Pi3B+ is basically a new design with most of the major parts changed.
Some parts are so new RPT is the first and only company using them.
New chips end up with things called errata, these are found by users, ways around the issues are figured out and solutions are found.
The 3B was a new design and it was running fine since day 1 without any issues, 3B+ is just an update to that design.
I owned every Pi since the original RPi1 and never had any troubles, uptime of 300 days was nothing special on that devices.

With the 3B+ i have issues since day once (over 2 months now), the RPi can't survive the night , my new replacement unit also has exactly the same issues as the first one, which is literary impossible to have such bad luck. Many people here on this forum have the same or similar issues so this definitely leads to a conclusion that they released broken hardware to the market without proper quality checks. And it has been over 2 months since launch and the issues are still not fixed by "software" that means that they don't have it under control.

The hardware of the 3B+ is crap, it has obviously some design flaws. They should take responsibility now and recall all defective units for replacement.

User avatar
Nachteule
Posts: 22
Joined: Tue May 03, 2016 9:23 pm

Re: Raspberry Pi 3 B+ lockups

Sun May 27, 2018 1:01 pm

wybielacz wrote:
Sun May 27, 2018 12:45 pm
The 3B was a new design and it was running fine since day 1 without any issues, 3B+ is just an update to that design.
I owned every Pi since the original RPi1 and never had any troubles, uptime of 300 days was nothing special on that devices.

With the 3B+ i have issues since day once (over 2 months now), the RPi can't survive the night , my new replacement unit also has exactly the same issues as the first one, which is literary impossible to have such bad luck. Many people here on this forum have the same or similar issues so this definitely leads to a conclusion that they released broken hardware to the market without proper quality checks. And it has been over 2 months since launch and the issues are still not fixed by "software" that means that they don't have it under control.

The hardware of the 3B+ is crap, it has obviously some design flaws. They should take responsibility now and recall all defective units for replacement.
Absolutely agree, you speak out what I think.

But unfortunately all we get as response from RPF is: we already sold 250k of parts and only a negligible percentage of sales has problems (analogous).

Return to “Troubleshooting”

Who is online

Users browsing this forum: lorenw74, NOsen and 53 guests