Hi all,
Confirm:
"...came back, and the monitor (tv in this case) was off, as it shuts itself off after not getting a signal for x amount of time. The keyboard didn't respond to any input. The ssh session I had open locked up, and I couldn't connect to it on the IP address the router said it was using..."
Seems exactly the same for me :(
Winfried
-----Oorspronkelijke bericht-----
Datum: Wed, 1 Feb 2017 23:54:25 +0000 (UTC)
I have a 2.5amp power supply too. It stopped responding twice since I have updated (which took around 10 hours.)
I went to dinner and came back, and the monitor (tv in this case) was off, as it shuts itself off after not getting a signal for x amount of time. The keyboard didn't respond to any input. The ssh session I had open locked up, and I couldn't connect to it on the IP address the router said it was using. (it keeps incrementing, which is annoying and strange in it's own right.) This is the last part of that log.
It is connected to the network via a wireless dongle. But I didn't have issues with that adapter on x86 when I had other network issues with the built-in adapter.
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net NetworkManager[742]: <info> [1485989019.9453] manager: NetworkManager state is now CONNECTED_SITE
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=742 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount is masked.
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel: alloc_contig_range: [21fdc, 21fe0) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel: alloc_contig_range: [220c0, 220c4) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel: alloc_contig_range: [220c4, 220c8) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net nm-dispatcher[2019]: req:1 'connectivity-change': new request (5 scripts)
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net nm-dispatcher[2019]: req:1 'connectivity-change': start running ordered scripts...
Feb 01 17:43:50 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net NetworkManager[742]: <info> [1485989065.1881] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=742 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount is masked.
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net nm-dispatcher[2039]: req:1 'connectivity-change': new request (5 scripts)
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net nm-dispatcher[2039]: req:1 'connectivity-change': start running ordered scripts...
Feb 01 17:44:35 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 18:01:01 unknownc83a35b012e1.attlocal.net CROND[2082]: (root) CMD (run-parts /etc/cron.hourly)
Feb 01 18:01:02 unknownc83a35b012e1.attlocal.net run-parts[2085]: (/etc/cron.hourly) starting 0anacron
Feb 01 18:01:02 unknownc83a35b012e1.attlocal.net run-parts[2091]: (/etc/cron.hourly) finished 0anacron
________________________________
From: Rafael Leiva-Ochoa <spawn@rloteck.net>
To: Peter Robinson <pbrobinson@gmail.com>; Winfried de Heiden <wdh@dds.nl>
Cc: arm@lists.fedoraproject.org
Sent: Wednesday, February 1, 2017 5:04 PM
Subject: [fedora-arm] Re: Raspberry PI 3 locking up
I will try my 2.5 amp power supply tonight. If I still see the same problems I will go ahead and respond back to the same email.
On Wed, Feb 1, 2017 at 11:41 AM Winfried de Heiden <wdh@dds.nl> wrote:
Hi all,
Double checked: 2.5A power supply.Winfried
Op 01-02-17 om 13:58 schreef Winfried de Heiden:
Hi all,
I don't know by head but it should be enough; it worked for weeks and it is sold as "the official PI power supply".
I'll check tonight to be shure.
Winfried
-----Oorspronkelijke bericht-----
Datum: Wed, 1 Feb 2017 11:27:45 +0000
Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
Cc: arm@lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn@rloteck.net>
Aan: Winfried de Heiden <wdh@dds.nl>
Van: Peter Robinson <pbrobinson@gmail.com>
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh@dds.nl> wrote:
Hi all, Same for me, since a couple of days the Rapsbery Pi 3 suddenly stops. One or
two time I was quick enough to catch a kernel panic on the screen. Looks like a kernel thing to me. I moved the SD-card to my " old" Raspberry
Pi 2 (two), the same installation is running fine for a couple of days.
What is the AMP rating of your power supplies?
Screen shot of the kernel panic attached. I think I' ll create a bugzilla on
this. Winfried Op wo, 1 feb 2017 om 1:26 , schreef Rafael Leiva-Ochoa <spawn@rloteck.net>: Hi Everyone, I've been running a raspberry pi 3 with Fedora release 25 (Twenty Five)
using kernal 4.9.6-200.fc25.armv7hl, and I have been noticing for the last 2
weeks that my Pi locks up. I tried hooking it up to an HDMI monitor, and USB
keyboard to see if the system generates any message, but I only get a blank
screen and no reaction from the keyboard. I have looked at the
/var/log/message, and dmesg, and I don't see anything that could be causing
the problem. I was thinking it could be overheating, but Fedara 25 does not
support any of the rasbian commands to run heat sensor checks. Any ideas? Thanks, Rafael _______________________________________________
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org