As a last-ditch attempt to diagnose a temperature-related problem, I strapped a (suitably wrapped) ice pack to my Pi this evening. This seemed to cure the random shutdowns and the Pi booted and remained stable/functional for much longer than it ever did before. In fact it didn't hang. Bearing in mind that I had not changed anything about the set-up from my last attempt(s) this seems to have proved that, when warm, my Pi was unstable as it was stable when cooled. The next step was to unstrap the ice pack, reboot the Pi, and see if reverted to random shutdowns once it had reached normal temperature. It's now been running for a good hour and hasn't hung yet even when I elevated its ambient temperature with gentle heat from a hairdryer!!
I'm still inclined to believe that there's an intermittent fault with my Pi and that the 'ice pack' fix is only temporary. I guess time will tell. But it might be worth others conducting a similar exercise and chilling the Pi with a poly-bag wrapped ice-pack to see if it becomes more stable.
It's worth emphasising that I doubt it's power-related - ditto the SD card - since I'm using the same PSU and SD card that were used when the Pi was hanging before. Perhaps, the 'chill' has helped close a minute fracture. Who knows!?
I'll leave the Pi running for now and will report back if it starts acting up again. Any suggestions for the easiest way to stress a Pi without user interaction? E.g. a simple script that'll impose a continuous 100% load?
I have tried that new firmware/kernel and my Pi still hangs after a short while. Usually it gets to the login prompt phase of booting and most of the time I get to remotely login. I also ping the Pi so I can monitor its connection. However, normally, within a few minutes the Pi hangs, the Ethernet connection is lost and the HDMI output dropped (i.e. the tv complains that the signal is lost). The 'time-to-hang' is variable but usually less than 5-10 minutes and sometimes just a few seconds. In my experience keeping the Pi 'chilled' results in reliable operation - hours of uptime.jbeale wrote:Have you seen this thread? Does the new firmware & kernel today help your SD card problem?
"There was a new kernel pushed to github today. It includes another patch for failing sdcards. [...]"
http://www.raspberrypi.org/phpBB3/viewt ... f=2&t=6093
Apparently it has fixed some issues at least.
Code: Select all
Waiting for root device /dev/mmcblk0p2... mmc0: problem reading SD Status register. mmc0: new SDHC card at address 1234 mmcblk0: mmc0:1234 SA04G 3.63 GiB mmcblk0: p1 p2 p3
Code: Select all
Waiting for root device /dev/mmcblk0p2... mmc0: problem reading SD Status register. mmc0: new SDHC card at address 1234 mmcblk0: mmc0:1234 SA08G 7.42 GiB mmcblk0: p1 p2 p3
Code: Select all
Waiting for root device /dev/mmcblk0p2... mmc0: problem reading SD Status register. mmc0: new SDHC card at address b368 mmcblk0: mmc0:b368 00000 7.51 GiB mmcblk0: p1 p2 p3
Thanks for the info. This is further evidence that my Pi is faulty since I believe I've satisfied the conditions for a known good SD card and a good PSU - a nokia AC-10X 5V 1200ma - that supplies at least 4.9V between the test points.BarryMead wrote:PROBLEM-SOLVED!!!
When I combined the Known-good Kingston SDHC 8Gb Class4 sd card with a known-good high-current power supply with LARGE-CONDUCTOR wires, measuring a good voltage on the test points, then my problems did indeed vanish! Thanks to Raspberry Pi foundation for publishing the new "Troubleshooting Wiki" This new wiki clearly shows how to resolve the common issues with the raspberry pi.