WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: raspberry is suddenly rebooting: how to find the reason?  (Read 4344 times)

Offline gestein

  • WikiUser
  • *
  • Posts: 14
raspberry is suddenly rebooting: how to find the reason?
« on: July 10, 2019, 02:08:59 PM »
Dear all,

I am quite  a newby to linux and especially Tiny Core Linux.
But I managed to run Tiny Core Linux on my raspberry pi zero with Wlan (in fact it is the latest piCorePlayer-Installation).

Unfortunately my raspberry is restarting without any reason - at least for me - all approx. 5-10min.
I am not able to find the reason behind the reboots.

in dmesg there are some entries that might be a problem, but I can't locate the problem.
Code: [Select]
[   31.359260] wlan0: authenticate with f4:06:8d:7d:6c:e9
[   31.448722] wlan0: send auth to f4:06:8d:7d:6c:e9 (try 1/3)
[   31.458634] wlan0: authenticated
[   31.462587] wlan0: associate with f4:06:8d:7d:6c:e9 (try 1/3)
[   31.467308] wlan0: RX AssocResp from f4:06:8d:7d:6c:e9 (capab=0x431 status=0 aid=1)
[   31.487807] wlan0: associated
[   32.482684] ------------[ cut here ]------------
[   32.483602] WARNING: CPU: 0 PID: 10 at net/wireless/reg.c:418 restore_regulatory_settings+                                                                                                0xb8/0x478 [cfg80211]
[   32.483615] Unexpected user alpha2: "A
[   32.483619] Modules linked in: ctr ccm spidev arc4 rt2800usb rt2x00usb rt2800lib crc_ccitt                                                                                                 rt2x00lib mac80211 sha256_generic cfg80211 snd_soc_bcm2835_i2s regmap_mmio snd_soc_core snd_                                                                                                bcm2835(C) snd_compress snd_pcm_dmaengine snd_pcm rfkill snd_timer snd i2c_bcm2835 spi_bcm283                                                                                                5 fixed squashfs sch_fq_codel lz4 lz4_compress zram zsmalloc
[   32.483733] CPU: 0 PID: 10 Comm: kworker/0:1 Tainted: G         C        4.19.40-pcpCore #                                                                                                1
[   32.483738] Hardware name: BCM2835
[   32.484574] Workqueue: events_power_efficient crda_timeout_work [cfg80211]
[   32.484625] [<c0017dac>] (unwind_backtrace) from [<c0014c68>] (show_stack+0x20/0x24)
[   32.484647] [<c0014c68>] (show_stack) from [<c065e39c>] (dump_stack+0x20/0x28)
[   32.484672] [<c065e39c>] (dump_stack) from [<c00244e4>] (__warn+0xe0/0x108)
[   32.484690] [<c00244e4>] (__warn) from [<c0024560>] (warn_slowpath_fmt+0x54/0x74)
[   32.485520] [<c0024560>] (warn_slowpath_fmt) from [<bf11bc88>] (restore_regulatory_setting                                                                                                s+0xb8/0x478 [cfg80211])
[   32.487122] [<bf11bc88>] (restore_regulatory_settings [cfg80211]) from [<bf11c1a4>] (crda_                                                                                                timeout_work+0x30/0x3c [cfg80211])
[   32.487946] [<bf11c1a4>] (crda_timeout_work [cfg80211]) from [<c003cc24>] (process_one_wor                                                                                                k+0x1f8/0x45c)
[   32.487973] [<c003cc24>] (process_one_work) from [<c003cec4>] (worker_thread+0x3c/0x5a4)
[   32.487990] [<c003cec4>] (worker_thread) from [<c0042d00>] (kthread+0x14c/0x164)
[   32.488005] [<c0042d00>] (kthread) from [<c00090ac>] (ret_from_fork+0x14/0x28)
[   32.488013] Exception stack(0xdd559fb0 to 0xdd559ff8)
[   32.488021] 9fa0:                                     00000000 00000000 00000000 00000000
[   32.488032] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   32.488041] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   32.488049] ---[ end trace a30419487df2513f ]---
[   40.491038] Finished piCorePlayer v5.0.0 startup.

I also have the syslogd in my /opt/bootlocal.sh:
Code: [Select]
syslogd -O /mnt/mmcblk0p2/log/messages
There are always entries like this:
Code: [Select]
Jul 10 23:01:43 piCorePlayer syslog.info syslogd started: BusyBox v1.30.1
Jul 10 23:02:24 piCorePlayer auth.info sshd[7902]: Accepted password for tc from 192.168.0.135 port 63727 ssh2
Jul 10 23:02:24 piCorePlayer auth.info sshd[7902]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jul 10 23:02:24 piCorePlayer auth.info sshd[7902]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
Jul 10 23:02:24 piCorePlayer local2.notice sudo:       tc : TTY=unknown ; PWD=/home/tc ; USER=root ; COMMAND=/usr/bin/tee /etc/sysconfig/backup
Jul 10 23:02:24 piCorePlayer local2.notice sudo:       tc : TTY=unknown ; PWD=/home/tc ; USER=root ; COMMAND=/usr/bin/tee /etc/sysconfig/backup
Jul 10 23:05:19 piCorePlayer local2.notice sudo:     root : TTY=unknown ; PWD=/home/tc/www/cgi-bin ; USER=root ; COMMAND=/sbin/reboot
Jul 10 21:05:19 piCorePlayer daemon.info : starting pid 8284, tty '': '/etc/init.d/rc.shutdown'

Does anyone know how to solve this?

Thanks a lot in advance
Best regards
Gerhard

Offline andyj

  • Hero Member
  • *****
  • Posts: 750
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #1 on: July 10, 2019, 04:07:06 PM »
Try a new power supply.

Offline gestein

  • WikiUser
  • *
  • Posts: 14
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #2 on: July 10, 2019, 09:41:19 PM »
Hi,

thanks for the hint.
I tried it now, but it does not help.
A new power supply does not change anything.

Best regards
Gerhard

Offline gestein

  • WikiUser
  • *
  • Posts: 14
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #3 on: July 11, 2019, 03:17:56 AM »
It seems that something in the hardware is broken (or bad setup of software).
I tried another raspberry zero with the same software: it works just fine.

Is there any possibility to check the hardware?

Thanks and best regards
Gerhard

Offline PDP-8

  • Sr. Member
  • ****
  • Posts: 469
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #4 on: July 11, 2019, 01:31:54 PM »
Overheating?  Throwing some thoughts out here...

Are *both* of the zero's using heatsinks? Especially with a multimedia streaming application?  Is the zero actually the best hardware for this project, rather than say a 3x model?

Is one encased and the other one free-standing?

General:

Is the dongle you use to connect to the micro-usb ports for ethernet (assuming ethernet) the same?  Could one be defective or loose?  Or could one just simply be a corner-case that tips over with a streaming application?

Are there any configuration differences in your config.txt file?

Are you following the advice of the piCorePlayer project that since it uses TinyCore running in ram, it is totally ok to just shutdown by just pulling the plug?  On paper, you can.  In the real world, possibly not the best idea.

That's a UNIX book! - cool  -- Garth

Offline gestein

  • WikiUser
  • *
  • Posts: 14
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #5 on: July 11, 2019, 04:26:44 PM »
Dear PDP-8,

thanks for the hint.
No, no heatsinks on both zeros.

I using the zeros as client for Homematic devices.
So the power of the zero is more then enough.

Yes, the dongle for Wifi is the same.
regarding config.txt I have to check.

Yes, I am following the advice and jut pull the plug. Will this damage my sd-card?
Because it looks like.

Thanks and best regards
Gerhard

Offline Greg Erskine

  • Sr. Member
  • ****
  • Posts: 269
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #6 on: July 11, 2019, 06:53:18 PM »
hi Gerhard,

From our experience "standard" piCoreplayer will not corrupt SD cards if you pull the plug.

If you have added LMS then it should be shutdown properly.

If you have added non-standard software then we don't know.

regards
Greg

Offline PDP-8

  • Sr. Member
  • ****
  • Posts: 469
Re: raspberry is suddenly rebooting: how to find the reason?
« Reply #7 on: July 11, 2019, 10:58:34 PM »
Ah, does picoreplayer dismount the card after loading in preparation for an abrupt power off?
That's a UNIX book! - cool  -- Garth