6:26 p.m.
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
1:52 a.m.
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.
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(a)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
2:09 a.m.
Bugzilla created: https://bugzilla.redhat.com/show_bug.cgi?id=1418183
Winfried
Op wo, 1 feb 2017 om 8:52 , schreef Winfried de Heiden <wdh(a)dds.nl>:
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.
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(a)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
5:27 a.m.
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
6:58 a.m.
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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
Aan: Winfried de Heiden <wdh(a)dds.nl>
Van: Peter Robinson <pbrobinson(a)gmail.com>
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
9:58 a.m.
The AMP rating is 2.0 amps for mine. Its been working fine since the first
release of Fedora 25. I have been noticing that the Pi does go a little hot
compared to my other Pi's that don't run Fedora. I don't know if that is
related.
Thanks,
Rafael
On Wed, Feb 1, 2017 at 4:58 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net
<Rafael%20Leiva-Ochoa%20%3cspawn(a)rloteck.net%3e>>
*Aan*: Winfried de Heiden <wdh(a)dds.nl
<Winfried%20de%20Heiden%20%3cwdh(a)dds.nl%3e>>
*Van*: Peter Robinson <pbrobinson(a)gmail.com
<Peter%20Robinson%20%3cpbrobinson(a)gmail.com%3e>>
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
10:42 a.m.
On Wed, Feb 1, 2017 at 3:58 PM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> wrote:
The AMP rating is 2.0 amps for mine. Its been working fine since the
first
release of Fedora 25. I have been noticing that the Pi does go a little hot
compared to my other Pi's that don't run Fedora. I don't know if that is
related.
As outlined in the Fedora perquisites [1] as documented by the RPi
Foundation [2] you need a 2.5 Amp PSU for the Pi3. There was quite a
bit of change between the 4.8 and 4.9 kernel series so it might be
we've enabled extra functionality that's drawing a little extra power
when you do something (eg I add patches that use higher speed SD card
support) and that might have been enough to trip us over the "it
works" on a 2 AMP PSU.
[1] https://fedoraproject.org/wiki/Raspberry_Pi#Prerequisites
[2] https://www.raspberrypi.org/help/faqs/#power
> Thanks,
>
> Rafael
>
> On Wed, Feb 1, 2017 at 4:58 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
>>
>> 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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>> Aan: Winfried de Heiden <wdh(a)dds.nl>
>> Van: Peter Robinson <pbrobinson(a)gmail.com>
>>
>> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>>
>>
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
>
4:04 p.m.
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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net
<Rafael%20Leiva-Ochoa%20%3cspawn(a)rloteck.net%3e>>
*Aan*: Winfried de Heiden <wdh(a)dds.nl
<Winfried%20de%20Heiden%20%3cwdh(a)dds.nl%3e>>
*Van*: Peter Robinson <pbrobinson(a)gmail.com
<Peter%20Robinson%20%3cpbrobinson(a)gmail.com%3e>>
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
5:54 p.m.
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(a)rloteck.net To: Peter
Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden <wdh(a)dds.nl>
Cc: arm(a)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(a)dds.nl> wrote:
Hi all,
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net >Aan: Winfried de Heiden <wdh(a)dds.nl >Van: Peter Robinson <pbrobinson(a)gmail.com >On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden
<wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an email to
arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an email to
arm-leave(a)lists.fedoraproject.org
arm mailing list --
arm(a)lists.fedoraproject.org To unsubscribe send an email to
arm-leave(a)lists.fedoraproject.org
1:44 a.m.
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)
Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson <pbrobinson
@gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
Van: Sean Omalley <omalley_s(a)rocketmail.com>
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(a)rloteck.net>
To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden <wdh@dds.
nl>Â
Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn@rloteck.
> net>
> Aan: Winfried de Heiden <wdh(a)dds.nl>
> Van: Peter Robinson <pbrobinson(a)gmail.com>
> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an
email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
email to arm-leave(a)lists.fedoraproject.org
>
> _______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
1:08 a.m.
Hi Peter, it locked up again with the 2.5 amp plug. No reaction from the
keyboard or HDMI display.....
On Wed, Feb 1, 2017 at 11:44 PM Winfried de Heiden <wdh(a)dds.nl> wrote:
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)
*Onderwerp*: [fedora-arm] Re: Raspberry PI 3 locking up
*Cc*: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org
<%22arm@lists.fedoraproject.org%22%20%3carm(a)lists.fedoraproject.org%3e>>
*Aan*: Rafael Leiva-Ochoa <spawn(a)rloteck.net
<Rafael%20Leiva-Ochoa%20%3cspawn(a)rloteck.net%3e>>, Peter Robinson <
pbrobinson(a)gmail.com <Peter%20Robinson%20%3cpbrobinson(a)gmail.com%3e>>,
Winfried de Heiden <wdh(a)dds.nl <Winfried%20de%20Heiden%20%3cwdh(a)dds.nl%3e>
>
Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
*Van*: Sean Omalley <omalley_s(a)rocketmail.com
<Sean%20Omalley%20%3comalley_s(a)rocketmail.com%3e>>
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(a)rloteck.net>
To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden <wdh(a)dds.nl>
Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
Aan: Winfried de Heiden <wdh(a)dds.nl>
Van: Peter Robinson <pbrobinson(a)gmail.com>
On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an email to
arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an email to
arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an email to
arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
3:12 a.m.
On Fri, Feb 3, 2017 at 7:08 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> wrote:
Hi Peter, it locked up again with the 2.5 amp plug. No reaction from
the
keyboard or HDMI display.....
I'm suspecting this is some type of thermal issue. I was home very
briefly and got two devices setup (I have around 6 various RPis) and
they both seemed to be OK, and the RPi3 wasn't hot to touch but in the
interim since I left it appears to have locked up so I'll have to look
at this closer when I get some spare cycles and am actually in the
same location as the devices.
If someone can do some debug and identify which kernel it regressed (I
suspect when we moved to 4.9.x) it would help as at the moment I have
limited time to deal with this (It's a personal not $dayjob project).
Peter
> On Wed, Feb 1, 2017 at 11:44 PM Winfried de Heiden <wdh(a)dds.nl> wrote:
>>
>> 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)
>> Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
>> Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
>> Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson
>> <pbrobinson(a)gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
>> Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
>> Van: Sean Omalley <omalley_s(a)rocketmail.com>
>>
>> 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(a)rloteck.net>
>> To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden
<wdh(a)dds.nl>
>> Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>> Aan: Winfried de Heiden <wdh(a)dds.nl>
>> Van: Peter Robinson <pbrobinson(a)gmail.com>
>> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an
>> email to arm-leave(a)lists.fedoraproject.org
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> email to arm-leave(a)lists.fedoraproject.org
>>
>>
>>
>>
>> _______________________________________________
>>
>>
>> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> email to arm-leave(a)lists.fedoraproject.org
>>
>>
>>
>>
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
11:03 p.m.
Any updates on this issue?
I can't seem to capture the kernel panic.
On Fri, Feb 3, 2017 at 3:12 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Fri, Feb 3, 2017 at 7:08 AM, Rafael Leiva-Ochoa
<spawn(a)rloteck.net>
wrote:
> Hi Peter, it locked up again with the 2.5 amp plug. No reaction from the
> keyboard or HDMI display.....
I'm suspecting this is some type of thermal issue. I was home very
briefly and got two devices setup (I have around 6 various RPis) and
they both seemed to be OK, and the RPi3 wasn't hot to touch but in the
interim since I left it appears to have locked up so I'll have to look
at this closer when I get some spare cycles and am actually in the
same location as the devices.
If someone can do some debug and identify which kernel it regressed (I
suspect when we moved to 4.9.x) it would help as at the moment I have
limited time to deal with this (It's a personal not $dayjob project).
Peter
> On Wed, Feb 1, 2017 at 11:44 PM Winfried de Heiden <wdh(a)dds.nl> wrote:
>>
>> 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)
>> Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
>> Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
>> Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson
>> <pbrobinson(a)gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
>> Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
>> Van: Sean Omalley <omalley_s(a)rocketmail.com>
>>
>> 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(a)rloteck.net>
>> To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden <
wdh(a)dds.nl>
>> Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>> Aan: Winfried de Heiden <wdh(a)dds.nl>
>> Van: Peter Robinson <pbrobinson(a)gmail.com>
>> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an
>> email to arm-leave(a)lists.fedoraproject.org
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> email to arm-leave(a)lists.fedoraproject.org
>>
>>
>>
>>
>> _______________________________________________
>>
>>
>> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> email to arm-leave(a)lists.fedoraproject.org
>>
>>
>>
>>
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> _______________________________________________
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
3:59 a.m.
On Tue, Feb 7, 2017 at 5:03 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> wrote:
Any updates on this issue?
Two things on this:
1) I do the support for the Raspberry Pi in my own time when I have
the time and there's not other things more pressing. I have been
literally traveling for the last two weeks. Anyone is able to assist
with this.
2) If I've not explicitly sent an update or asked for people to test
there's probably not an update.
That said I worked on this until 2am and I think I've possibly got to
the cause of the problem and might have a short term solution to the
problem, Sadly it's going to need more work for 4.10 :-(
Based on 2) above I'll be replying to this thread when I have
something that people can actually test.
> I can't seem to capture the kernel panic.
>
> On Fri, Feb 3, 2017 at 3:12 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> On Fri, Feb 3, 2017 at 7:08 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>> wrote:
>> > Hi Peter, it locked up again with the 2.5 amp plug. No reaction from the
>> > keyboard or HDMI display.....
>>
>> I'm suspecting this is some type of thermal issue. I was home very
>> briefly and got two devices setup (I have around 6 various RPis) and
>> they both seemed to be OK, and the RPi3 wasn't hot to touch but in the
>> interim since I left it appears to have locked up so I'll have to look
>> at this closer when I get some spare cycles and am actually in the
>> same location as the devices.
>>
>> If someone can do some debug and identify which kernel it regressed (I
>> suspect when we moved to 4.9.x) it would help as at the moment I have
>> limited time to deal with this (It's a personal not $dayjob project).
>>
>> Peter
>>
>> > On Wed, Feb 1, 2017 at 11:44 PM Winfried de Heiden <wdh(a)dds.nl>
wrote:
>> >>
>> >> 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)
>> >> Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
>> >> Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
>> >> Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson
>> >> <pbrobinson(a)gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
>> >> Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
>> >> Van: Sean Omalley <omalley_s(a)rocketmail.com>
>> >>
>> >> 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(a)rloteck.net>
>> >> To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden
>> >> <wdh(a)dds.nl>
>> >> Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa
<spawn(a)rloteck.net>
>> >> Aan: Winfried de Heiden <wdh(a)dds.nl>
>> >> Van: Peter Robinson <pbrobinson(a)gmail.com>
>> >> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an
>> >> email to arm-leave(a)lists.fedoraproject.org
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> >> email to arm-leave(a)lists.fedoraproject.org
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >>
>> >>
>> >> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> >> email to arm-leave(a)lists.fedoraproject.org
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
12:39 p.m.
Not trying to pry, but what did you find out?
It locked up on me after it sat idle for a bit, then after I logged in and gnome started
it froze. sitting at the login itself didn't seem to freeze it.
The package solaar for my logitech k400 wireless keyboard, goes through the boot text then
stops like it started the graphical interface on another device. Removing the package
fixes it.
Also do you happen to know where the system time is being picked up from initially? Every
boot starts from july 25. It is a minor annoyance.
Jul 25 15:50:31 raspi3 chronyd[685]: System clock wrong by 17015391.894310 seconds,
adjustment started
Feb 07 13:20:23 raspi3 systemd[1]: Time has been changed
----- Original Message -----
From: Peter Robinson <pbrobinson(a)gmail.com>
To: Rafael Leiva-Ochoa <spawn(a)rloteck.net>
Cc: Sean Omalley <omalley_s(a)rocketmail.com>; Winfried de Heiden <wdh(a)dds.nl>;
"arm(a)lists.fedoraproject.org" <arm(a)lists.fedoraproject.org>
Sent: Tuesday, February 7, 2017 4:59 AM
Subject: Re: [fedora-arm] Re: Raspberry PI 3 locking up
On Tue, Feb 7, 2017 at 5:03 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> wrote:
Any updates on this issue?
Two things on this:
1) I do the support for the Raspberry Pi in my own time when I have
the time and there's not other things more pressing. I have been
literally traveling for the last two weeks. Anyone is able to assist
with this.
2) If I've not explicitly sent an update or asked for people to test
there's probably not an update.
That said I worked on this until 2am and I think I've possibly got to
the cause of the problem and might have a short term solution to the
problem, Sadly it's going to need more work for 4.10 :-(
Based on 2) above I'll be replying to this thread when I have
something that people can actually test.
> I can't seem to capture the kernel panic.
>
> On Fri, Feb 3, 2017 at 3:12 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
>>
>> On Fri, Feb 3, 2017 at 7:08 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>> wrote:
>> > Hi Peter, it locked up again with the 2.5 amp plug. No reaction from the
>> > keyboard or HDMI display.....
>>
>> I'm suspecting this is some type of thermal issue. I was home very
>> briefly and got two devices setup (I have around 6 various RPis) and
>> they both seemed to be OK, and the RPi3 wasn't hot to touch but in the
>> interim since I left it appears to have locked up so I'll have to look
>> at this closer when I get some spare cycles and am actually in the
>> same location as the devices.
>>
>> If someone can do some debug and identify which kernel it regressed (I
>> suspect when we moved to 4.9.x) it would help as at the moment I have
>> limited time to deal with this (It's a personal not $dayjob project).
>>
>> Peter
>>
>> > On Wed, Feb 1, 2017 at 11:44 PM Winfried de Heiden <wdh(a)dds.nl>
wrote:
>> >>
>> >> 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)
>> >> Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
>> >> Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
>> >> Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson
>> >> <pbrobinson(a)gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
>> >> Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
>> >> Van: Sean Omalley <omalley_s(a)rocketmail.com>
>> >>
>> >> 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(a)rloteck.net>
>> >> To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden
>> >> <wdh(a)dds.nl>
>> >> Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa
<spawn(a)rloteck.net>
>> >> Aan: Winfried de Heiden <wdh(a)dds.nl>
>> >> Van: Peter Robinson <pbrobinson(a)gmail.com>
>> >> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send an
>> >> email to arm-leave(a)lists.fedoraproject.org
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> >> email to arm-leave(a)lists.fedoraproject.org
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >>
>> >>
>> >> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
>> >> email to arm-leave(a)lists.fedoraproject.org
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>> >> _______________________________________________
>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
1:37 p.m.
On Tue, Feb 7, 2017 at 6:39 PM, Sean Omalley <omalley_s(a)rocketmail.com> wrote:
Not trying to pry, but what did you find out?
Issues with i2c drivers that were back ported from 4.10, see the issue
there as well, the issues that were fixed by can wait, I'll need to
see what the issue as it's seen there too.
It locked up on me after it sat idle for a bit, then after I logged
in and gnome started it froze. sitting at the login itself didn't seem to freeze it.
The package solaar for my logitech k400 wireless keyboard, goes through the boot text
then stops like it started the graphical interface on another device. Removing the package
fixes it.
No idea about any thing about that.
Also do you happen to know where the system time is being picked up
from initially? Every boot starts from july 25. It is a minor annoyance.
Possibly the date of creation of the filesystem, the Raspberry Pi
doesn't have an onboard battery backed RTC to ensure current time
across reboots.
>
>
> Jul 25 15:50:31 raspi3 chronyd[685]: System clock wrong by 17015391.894310 seconds,
adjustment started
> Feb 07 13:20:23 raspi3 systemd[1]: Time has been changed
>
>
>
>
>
> ----- Original Message -----
> From: Peter Robinson <pbrobinson(a)gmail.com>
> To: Rafael Leiva-Ochoa <spawn(a)rloteck.net>
> Cc: Sean Omalley <omalley_s(a)rocketmail.com>; Winfried de Heiden
<wdh(a)dds.nl>; "arm(a)lists.fedoraproject.org"
<arm(a)lists.fedoraproject.org>
> Sent: Tuesday, February 7, 2017 4:59 AM
> Subject: Re: [fedora-arm] Re: Raspberry PI 3 locking up
>
> On Tue, Feb 7, 2017 at 5:03 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net> wrote:
>> Any updates on this issue?
>
> Two things on this:
> 1) I do the support for the Raspberry Pi in my own time when I have
> the time and there's not other things more pressing. I have been
> literally traveling for the last two weeks. Anyone is able to assist
> with this.
> 2) If I've not explicitly sent an update or asked for people to test
> there's probably not an update.
>
> That said I worked on this until 2am and I think I've possibly got to
> the cause of the problem and might have a short term solution to the
> problem, Sadly it's going to need more work for 4.10 :-(
>
> Based on 2) above I'll be replying to this thread when I have
> something that people can actually test.
>
>
>> I can't seem to capture the kernel panic.
>>
>> On Fri, Feb 3, 2017 at 3:12 AM Peter Robinson <pbrobinson(a)gmail.com>
wrote:
>>>
>>> On Fri, Feb 3, 2017 at 7:08 AM, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>>> wrote:
>>> > Hi Peter, it locked up again with the 2.5 amp plug. No reaction from
the
>>> > keyboard or HDMI display.....
>>>
>>> I'm suspecting this is some type of thermal issue. I was home very
>>> briefly and got two devices setup (I have around 6 various RPis) and
>>> they both seemed to be OK, and the RPi3 wasn't hot to touch but in the
>>> interim since I left it appears to have locked up so I'll have to look
>>> at this closer when I get some spare cycles and am actually in the
>>> same location as the devices.
>>>
>>> If someone can do some debug and identify which kernel it regressed (I
>>> suspect when we moved to 4.9.x) it would help as at the moment I have
>>> limited time to deal with this (It's a personal not $dayjob project).
>>>
>>> Peter
>>>
>>> > On Wed, Feb 1, 2017 at 11:44 PM Winfried de Heiden <wdh(a)dds.nl>
wrote:
>>> >>
>>> >> 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)
>>> >> Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
>>> >> Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
>>> >> Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson
>>> >> <pbrobinson(a)gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
>>> >> Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
>>> >> Van: Sean Omalley <omalley_s(a)rocketmail.com>
>>> >>
>>> >> 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(a)rloteck.net>
>>> >> To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden
>>> >> <wdh(a)dds.nl>
>>> >> Cc: arm(a)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(a)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(a)lists.fedoraproject.org, Rafael Leiva-Ochoa
<spawn(a)rloteck.net>
>>> >> Aan: Winfried de Heiden <wdh(a)dds.nl>
>>> >> Van: Peter Robinson <pbrobinson(a)gmail.com>
>>> >> On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden
<wdh(a)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(a)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(a)lists.fedoraproject.org To unsubscribe send
an
>>> >> email to arm-leave(a)lists.fedoraproject.org
>>> >> _______________________________________________
>>> >> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send
an
>>> >> email to arm-leave(a)lists.fedoraproject.org
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >>
>>> >>
>>> >> arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send
an
>>> >> email to arm-leave(a)lists.fedoraproject.org
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>>> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>>> >> _______________________________________________
>>> >> arm mailing list -- arm(a)lists.fedoraproject.org
>>> >> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
2644
days inactive
2650
days old
16 comments
4 participants
participants (4)
-
Peter Robinson -
Rafael Leiva-Ochoa -
Sean Omalley -
Winfried de Heiden