7:30 a.m.
When I woke up this morning at 5:30 to head to the airport, I heard my
system fan going at full speed. I tried to log in to the locked system,
but no response. I had to power cycle. Looking back in messages, the
last messages were right after 4am:
# grep "Jul 15 04" messages
Jul 15 04:01:01 lx121e audit[6374]: USER_ACCT pid=6374 uid=0
auid=4294967295 ses=4294967295
subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting
grantors=pam_access,pam_unix,pam_localuser acct="rgm"
exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:01 lx121e audit[6374]: CRED_ACQ pid=6374 uid=0
auid=4294967295 ses=4294967295
subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:02 lx121e systemd[1]: Started Session 5 of user rgm.
Jul 15 04:01:02 lx121e audit[6374]: USER_START pid=6374 uid=0 auid=1000
ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd acct="rgm"
exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:02 lx121e audit[6374]: CRED_REFR pid=6374 uid=0 auid=1000
ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
hostname=? addr=? terminal=cron res=success'
And then nothing until the restart. Any recommendations on where to dig
to guess at what caused this?
Last night I had done an update and had rebooted the system, so it was a
fresh boot, but with all my processes running.
thanks
11:19 a.m.
On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
When I woke up this morning at 5:30 to head to the airport, I heard
my
system fan going at full speed. I tried to log in to the locked system,
but no response. I had to power cycle. Looking back in messages, the
last messages were right after 4am:
I've nothing similar in my logs, but have found my system hung twice now
in the last two mornings. Last night, there was an unexplained reboot
just before 5:00, with subsequent hang sometime later (I found the
situation at 8:45.)
This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came out
just a day later) doesn't seem to have changed it. I've booted back to
the dot-three version.
--
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
12:20 p.m.
On 07/15/2018 11:19 AM, Tim Evans wrote:
On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
> When I woke up this morning at 5:30 to head to the airport, I heard
> my system fan going at full speed. I tried to log in to the locked
> system, but no response. I had to power cycle. Looking back in
> messages, the last messages were right after 4am:
I've nothing similar in my logs, but have found my system hung twice now
in the last two mornings. Last night, there was an unexplained reboot
just before 5:00, with subsequent hang sometime later (I found the
situation at 8:45.)
This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came out
just a day later) doesn't seem to have changed it. I've booted back to
the dot-three version.
I too have been having hangs that require a power cycle. I've dropped
back from kernel 4.17.5 to 4.17.4 to see if it's a kernel update issue.
--
-- Steve
12:56 p.m.
On Sun, 2018-07-15 at 12:20 -0500, SternData wrote:
On 07/15/2018 11:19 AM, Tim Evans wrote:
> On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
> > When I woke up this morning at 5:30 to head to the airport, I heard
> > my system fan going at full speed. I tried to log in to the locked
> > system, but no response. I had to power cycle. Looking back in
> > messages, the last messages were right after 4am:
>
> I've nothing similar in my logs, but have found my system hung twice now
> in the last two mornings. Last night, there was an unexplained reboot
> just before 5:00, with subsequent hang sometime later (I found the
> situation at 8:45.)
>
> This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came out
> just a day later) doesn't seem to have changed it. I've booted back to
> the dot-three version.
>
>
I too have been having hangs that require a power cycle. I've dropped
back from kernel 4.17.5 to 4.17.4 to see if it's a kernel update issue.
I've had hangs with 4.17.4 and 4.17.5, but not with 4.17.3. I use
QEMU/KVM and the hangs seemed to be triggered by that, though there's
nothing in the logs.
poc
1:40 p.m.
On 07/15/2018 01:56 PM, Patrick O'Callaghan wrote:
On Sun, 2018-07-15 at 12:20 -0500, SternData wrote:
> On 07/15/2018 11:19 AM, Tim Evans wrote:
>> On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
>>> When I woke up this morning at 5:30 to head to the airport, I heard
>>> my system fan going at full speed. I tried to log in to the locked
>>> system, but no response. I had to power cycle. Looking back in
>>> messages, the last messages were right after 4am:
>>
>> I've nothing similar in my logs, but have found my system hung twice now
>> in the last two mornings. Last night, there was an unexplained reboot
>> just before 5:00, with subsequent hang sometime later (I found the
>> situation at 8:45.)
>>
>> This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came out
>> just a day later) doesn't seem to have changed it. I've booted back to
>> the dot-three version.
>>
>>
>
> I too have been having hangs that require a power cycle. I've dropped
> back from kernel 4.17.5 to 4.17.4 to see if it's a kernel update issue.
I've had hangs with 4.17.4 and 4.17.5, but not with 4.17.3. I use
QEMU/KVM and the hangs seemed to be triggered by that, though there's
nothing in the logs.
No QEMU/KVM here.
--
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
1:40 p.m.
On 07/15/2018 01:56 PM, Patrick O'Callaghan wrote:
On Sun, 2018-07-15 at 12:20 -0500, SternData wrote:
> On 07/15/2018 11:19 AM, Tim Evans wrote:
>> On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
>>> When I woke up this morning at 5:30 to head to the airport, I heard
>>> my system fan going at full speed. I tried to log in to the locked
>>> system, but no response. I had to power cycle. Looking back in
>>> messages, the last messages were right after 4am:
>> I've nothing similar in my logs, but have found my system hung twice now
>> in the last two mornings. Last night, there was an unexplained reboot
>> just before 5:00, with subsequent hang sometime later (I found the
>> situation at 8:45.)
>>
>> This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came out
>> just a day later) doesn't seem to have changed it. I've booted back to
>> the dot-three version.
>>
>>
> I too have been having hangs that require a power cycle. I've dropped
> back from kernel 4.17.5 to 4.17.4 to see if it's a kernel update issue.
I've had hangs with 4.17.4 and 4.17.5, but not with 4.17.3. I use
QEMU/KVM and the hangs seemed to be triggered by that, though there's
nothing in the logs.
I was running QEMU at the time of the hang.
5:41 p.m.
I never saw this problem with 4.17.4. Since I upgraded to 4.17.5 I've
seen it happen 3 times. In all the cases as far as I can tell the
system was idle. I wasn't even in front of the computer when it
happened. I have 2 systems running 4.17.5 and the problem has occurred
on only one of those systems, my laptop.
Paolo
On 07/15/2018 11:40 AM, Robert Moskowitz wrote:
On 07/15/2018 01:56 PM, Patrick O'Callaghan wrote:
> On Sun, 2018-07-15 at 12:20 -0500, SternData wrote:
>> On 07/15/2018 11:19 AM, Tim Evans wrote:
>>> On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
>>>> When I woke up this morning at 5:30 to head to the airport, I heard
>>>> my system fan going at full speed. I tried to log in to the locked
>>>> system, but no response. I had to power cycle. Looking back in
>>>> messages, the last messages were right after 4am:
>>> I've nothing similar in my logs, but have found my system hung
>>> twice now
>>> in the last two mornings. Last night, there was an unexplained reboot
>>> just before 5:00, with subsequent hang sometime later (I found the
>>> situation at 8:45.)
>>>
>>> This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came
>>> out
>>> just a day later) doesn't seem to have changed it. I've booted
>>> back to
>>> the dot-three version.
>>>
>>>
>> I too have been having hangs that require a power cycle. I've dropped
>> back from kernel 4.17.5 to 4.17.4 to see if it's a kernel update issue.
> I've had hangs with 4.17.4 and 4.17.5, but not with 4.17.3. I use
> QEMU/KVM and the hangs seemed to be triggered by that, though there's
> nothing in the logs.
I was running QEMU at the time of the hang.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
12:37 p.m.
On Sun, Jul 15, 2018 at 6:19 PM, Tim Evans <tkevans(a)tkevans.com> wrote:
On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
> When I woke up this morning at 5:30 to head to the airport, I heard my
> system fan going at full speed. I tried to log in to the locked system,
> but no response. I had to power cycle. Looking back in messages, the last
> messages were right after 4am:
>
I've nothing similar in my logs, but have found my system hung twice now
in the last two mornings. Last night, there was an unexplained reboot just
before 5:00, with subsequent hang sometime later (I found the situation at
8:45.)
This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which came out
just a day later) doesn't seem to have changed it. I've booted back to the
dot-three version.
Hi,
Similar issues here, started since kernel-4.17.4.
Don't know how to reproduce this problem.
It happened under different situations (e.g., when running a backup program
or when watching a live video)
Cheers,
Marco
--
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.or
g/archives/list/users(a)lists.fedoraproject.org/message/LXRXR3
IRJAN3QGXIGPAINZBEJL7NODIG/
1:23 p.m.
On 07/15/2018 01:37 PM, Marco Guazzone wrote:
On Sun, Jul 15, 2018 at 6:19 PM, Tim Evans <tkevans(a)tkevans.com
<mailto:tkevans@tkevans.com>> wrote:
On 07/15/2018 08:30 AM, Robert Moskowitz wrote:
When I woke up this morning at 5:30 to head to the airport, I
heard my system fan going at full speed. I tried to log in to
the locked system, but no response. I had to power cycle.
Looking back in messages, the last messages were right after 4am:
I've nothing similar in my logs, but have found my system hung
twice now in the last two mornings. Last night, there was an
unexplained reboot just before 5:00, with subsequent hang sometime
later (I found the situation at 8:45.)
This started with kernel-4.17.4-200.fc28.x86_64, but .5 (which
came out just a day later) doesn't seem to have changed it. I've
booted back to the dot-three version.
Hi,
Similar issues here, started since kernel-4.17.4.
Don't know how to reproduce this problem.
It happened under different situations (e.g., when running a backup
program or when watching a live video)
I was running 4.17.4 (updated to it on friday) when I hung.
Where do I set how many kernels to keep? If I have to fall back to
17.3, I am going to have more than 3 available...
thanks
5:26 a.m.
On 07/16/2018 04:46 AM, Tom Yates wrote:
On Sun, 15 Jul 2018, Robert Moskowitz wrote:
> Where do I set how many kernels to keep? If I have to fall back to
> 17.3, I am going to have more than 3 available...
As I understand it, it's
installonly_limit=3
in /etc/yum.conf .
Thanks. In F28 that is: /etc/dnf/dnf.conf
Upped mine to 5 for now.
Tom Yates
Cambridge, UK.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:23 a.m.
On Mon, 16 Jul 2018, Robert Moskowitz wrote:
On 07/16/2018 04:46 AM, Tom Yates wrote:
As I understand it, it's
installonly_limit=3
in /etc/yum.conf .
Thanks. In F28 that is: /etc/dnf/dnf.conf
Thanks, you're of course right, and I'm an idiot who *still* can't get the
yum->dnf thing sorted out (d'oh).
That said, I wonder: how old is my F28 box, and how many upgrades has it
been through, that it still has a bunch of files in /etc/yum ?
Tom Yates
Cambridge, UK.
6:54 a.m.
On 07/16/2018 07:23 AM, Tom Yates wrote:
On Mon, 16 Jul 2018, Robert Moskowitz wrote:
> On 07/16/2018 04:46 AM, Tom Yates wrote:
>
> As I understand it, it's
>
> installonly_limit=3
>
> in /etc/yum.conf .
>
> Thanks. In F28 that is: /etc/dnf/dnf.conf
Thanks, you're of course right, and I'm an idiot who *still* can't get
the yum->dnf thing sorted out (d'oh).
That said, I wonder: how old is my F28 box, and how many upgrades has
it been through, that it still has a bunch of files in /etc/yum ?
I did a clean install and /etc/yum/ ONLY has protected.d
All the repo files are still in /etc/yum.repo.d
I always do a clean install, but tend to copy too many . directories
from my backup to my personal home.
7:37 a.m.
On Mon, 2018-07-16 at 06:26 -0400, Robert Moskowitz wrote:
On 07/16/2018 04:46 AM, Tom Yates wrote:
> On Sun, 15 Jul 2018, Robert Moskowitz wrote:
>
>> Where do I set how many kernels to keep? If I have to fall back to
>> 17.3, I am going to have more than 3 available...
>
> As I understand it, it's
>
> installonly_limit=3
>
> in /etc/yum.conf .
Thanks. In F28 that is: /etc/dnf/dnf.conf
Upped mine to 5 for now.
Ditto, though it would be nice to be able to mark a specific kernel as
non-removable, rather than just relying on the window not overflowing.
poc
5:35 p.m.
On 07/16/2018 05:37 AM, Patrick O'Callaghan wrote:
On Mon, 2018-07-16 at 06:26 -0400, Robert Moskowitz wrote:
> On 07/16/2018 04:46 AM, Tom Yates wrote:
>> On Sun, 15 Jul 2018, Robert Moskowitz wrote:
>>
>>> Where do I set how many kernels to keep? If I have to fall back to
>>> 17.3, I am going to have more than 3 available...
>>
>> As I understand it, it's
>>
>> installonly_limit=3
>>
>> in /etc/yum.conf .
>
> Thanks. In F28 that is: /etc/dnf/dnf.conf
>
> Upped mine to 5 for now.
Ditto, though it would be nice to be able to mark a specific kernel as
non-removable, rather than just relying on the window not overflowing.
As long as you are using the kernel you want to keep at the time you
upgrade, it will not get removed. The next oldest one will be removed
instead. Or you could just manually remove one of the other ones.
6:09 p.m.
On 07/20/2018 06:35 PM, Samuel Sieb wrote:
On 07/16/2018 05:37 AM, Patrick O'Callaghan wrote:
> On Mon, 2018-07-16 at 06:26 -0400, Robert Moskowitz wrote:
>> On 07/16/2018 04:46 AM, Tom Yates wrote:
>>> On Sun, 15 Jul 2018, Robert Moskowitz wrote:
>>>
>>>> Where do I set how many kernels to keep? If I have to fall back to
>>>> 17.3, I am going to have more than 3 available...
>>>
>>> As I understand it, it's
>>>
>>> installonly_limit=3
>>>
>>> in /etc/yum.conf .
>>
>> Thanks. In F28 that is: /etc/dnf/dnf.conf
>>
>> Upped mine to 5 for now.
>
> Ditto, though it would be nice to be able to mark a specific kernel as
> non-removable, rather than just relying on the window not overflowing.
As long as you are using the kernel you want to keep at the time you
upgrade, it will not get removed. The next oldest one will be removed
instead. Or you could just manually remove one of the other ones.
Nice to know. I can see that would be bad if the kernel you are using
gets deleted!
6:10 p.m.
On 07/20/2018 03:35 PM, Samuel Sieb wrote:
On 07/16/2018 05:37 AM, Patrick O'Callaghan wrote:
> On Mon, 2018-07-16 at 06:26 -0400, Robert Moskowitz wrote:
>> On 07/16/2018 04:46 AM, Tom Yates wrote:
>>> On Sun, 15 Jul 2018, Robert Moskowitz wrote:
>>>
>>>> Where do I set how many kernels to keep? If I have to fall back to
>>>> 17.3, I am going to have more than 3 available...
>>>
>>> As I understand it, it's
>>>
>>> installonly_limit=3
>>>
>>> in /etc/yum.conf .
>>
>> Thanks. In F28 that is: /etc/dnf/dnf.conf
>>
>> Upped mine to 5 for now.
>
> Ditto, though it would be nice to be able to mark a specific kernel as
> non-removable, rather than just relying on the window not overflowing.
As long as you are using the kernel you want to keep at the time you
upgrade, it will not get removed. The next oldest one will be removed
instead. Or you could just manually remove one of the other ones.
Supposedly, you could do something like:
echo "kernel-4.17.3-200" >/etc/dnf/protected.d/kernel.conf
That's supposed to make sure dnf doesn't remove that package. Note that
the "kernel" package is really a meta package that includes the
kernel-core, kernel-modules and whatnot. I've never relied on this
bit of dnf magic, but it's supposed to work.
I just tested it on a VM by "protecting" an old kernel and it seemed to
work (that kernel wasn't removed, even though it was old). Your mileage
may vary.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
----------------------------------------------------------------------
4:05 a.m.
On Fri, 2018-07-20 at 16:10 -0700, Rick Stevens wrote:
On 07/20/2018 03:35 PM, Samuel Sieb wrote:
> On 07/16/2018 05:37 AM, Patrick O'Callaghan wrote:
> > On Mon, 2018-07-16 at 06:26 -0400, Robert Moskowitz wrote:
> > > On 07/16/2018 04:46 AM, Tom Yates wrote:
> > > > On Sun, 15 Jul 2018, Robert Moskowitz wrote:
> > > >
> > > > > Where do I set how many kernels to keep? If I have to fall back
to
> > > > > 17.3, I am going to have more than 3 available...
> > > >
> > > > As I understand it, it's
> > > >
> > > > installonly_limit=3
> > > >
> > > > in /etc/yum.conf .
> > >
> > > Thanks. In F28 that is: /etc/dnf/dnf.conf
> > >
> > > Upped mine to 5 for now.
> >
> > Ditto, though it would be nice to be able to mark a specific kernel as
> > non-removable, rather than just relying on the window not overflowing.
>
> As long as you are using the kernel you want to keep at the time you
> upgrade, it will not get removed. The next oldest one will be removed
> instead. Or you could just manually remove one of the other ones.
Supposedly, you could do something like:
echo "kernel-4.17.3-200" >/etc/dnf/protected.d/kernel.conf
That's supposed to make sure dnf doesn't remove that package. Note that
the "kernel" package is really a meta package that includes the
kernel-core, kernel-modules and whatnot. I've never relied on this
bit of dnf magic, but it's supposed to work.
I just tested it on a VM by "protecting" an old kernel and it seemed to
work (that kernel wasn't removed, even though it was old). Your mileage
may vary.
Interesting. I must look at that. It would be easy to work up into a
script.
poc
4:04 a.m.
On Fri, 2018-07-20 at 15:35 -0700, Samuel Sieb wrote:
On 07/16/2018 05:37 AM, Patrick O'Callaghan wrote:
> On Mon, 2018-07-16 at 06:26 -0400, Robert Moskowitz wrote:
> > On 07/16/2018 04:46 AM, Tom Yates wrote:
> > > On Sun, 15 Jul 2018, Robert Moskowitz wrote:
> > >
> > > > Where do I set how many kernels to keep? If I have to fall back to
> > > > 17.3, I am going to have more than 3 available...
> > >
> > > As I understand it, it's
> > >
> > > installonly_limit=3
> > >
> > > in /etc/yum.conf .
> >
> > Thanks. In F28 that is: /etc/dnf/dnf.conf
> >
> > Upped mine to 5 for now.
>
> Ditto, though it would be nice to be able to mark a specific kernel as
> non-removable, rather than just relying on the window not overflowing.
As long as you are using the kernel you want to keep at the time you
upgrade, it will not get removed. The next oldest one will be removed
instead. Or you could just manually remove one of the other ones.
Yes, I'm aware of that. Just a thought to protect against temporary
insanity (or PEBKAC).
poc
11:39 p.m.
When I woke up this morning at 5:30 to head to the airport, I heard
my
system fan going at full speed. I tried to log in to the locked system, but
no response.
Same here with 4.17.5.
Hung during my backup yesterday night. Found the computer still
running this morning with noisy fan and computer not responding,
neither to Alt+SysRq keys.
Last messages in the log:
Jul 15 22:27:27 alpha dbus-daemon[1035]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' requested by ':1.41'
(uid=1000 pid=1712 comm="/usr/libexec/org_kde_powerdevil "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023") (using
servicehelper)
Jul 15 22:27:27 alpha dbus-daemon[1035]: [system] Successfully
activated service 'org.kde.powerdevil.backlighthelper'
Jul 15 22:40:30 alpha dbus-daemon[1035]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' requested by ':1.41'
(uid=1000 pid=1712 comm="/usr/libexec/org_kde_powerdevil "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023") (using
servicehelper)
Jul 15 22:40:30 alpha dbus-daemon[1035]: [system] Successfully
activated service 'org.kde.powerdevil.backlighthelper'
Jul 15 22:43:00 alpha dbus-daemon[1035]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' requested by ':1.41'
(uid=1000 pid=1712 comm="/usr/libexec/org_kde_powerdevil "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023") (using
servicehelper)
Jul 15 22:43:00 alpha dbus-daemon[1035]: [system] Successfully
activated service 'org.kde.powerdevil.backlighthelper'
F
12:12 a.m.
Same here with 4.17.5.
Hung during my backup yesterday night. Found the computer still
running this morning with noisy fan and computer not responding,
neither to Alt+SysRq keys.
Note that I am running F27.
I've just retried the backup this morning and it stopped again during
the backup so that may be linked.
I was backuping my hard drive + some data from a remote computer to a
USB3 drive plugged on a USB-C adapter where I also have the ethernet
plugged in.
The backup program is rsnapshot.
I will retry with the drive plugged in directly to a USB3 port of the computer.
F
12:24 a.m.
I've been getting these hangs on all 4.17 kernels that I've tried (up to
4.17.6)
kernel 4.16 works like a charm.
Might be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1598462
--
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia
ngaywood(a)une.edu.au http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062
Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
1:22 a.m.
Might be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1598462
Looking forward to get 4.17.7 then!
I just finished my backup with the drive plugged in directly to the
computer instead of via the USB-C adapter -> no hang...
My drive is ext4 luks encrypted.
F
5:08 a.m.
On Mon, 2018-07-16 at 15:24 +1000, Norman Gaywood wrote:
I've been getting these hangs on all 4.17 kernels that I've
tried (up to
4.17.6)
kernel 4.16 works like a charm.
Might be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1598462
In my case this is not associated with USB3. I backup to a local NAS
and only at night. My hangs were during normal daytime use. I did
notice a page fault error in one of the logs (mentioned in the links in
https://bugzilla.redhat.com/show_bug.cgi?id=1598462#c30) so there may
be more than one trigger.
poc
5:23 a.m.
On 07/16/2018 01:24 AM, Norman Gaywood wrote:
I've been getting these hangs on all 4.17 kernels that I've
tried (up
to 4.17.6)
kernel 4.16 works like a charm.
Might be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1598462
hmmm. I did have an SD card in my laptop's SD slot and it was mounted
and I *THINK* had a doc opened in Libre write. But it would have been
idling.
--
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia
ngaywood(a)une.edu.au <mailto:ngaywood@une.edu.au>
http://turing.une.edu.au/~ngaywood <http://turing.une.edu.au/%7Engaywood>
Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062
Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
7:20 a.m.
On Mon, Jul 16, 2018 at 7:24 AM, Norman Gaywood <ngaywood(a)une.edu.au> wrote:
I've been getting these hangs on all 4.17 kernels that I've
tried (up to
4.17.6)
kernel 4.16 works like a charm.
Might be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1598462
Just tried to rerun my backup program (duplicity writing to Google Drive):
With kernel 4.17.5 -> system hangs
With kernel 4.17.3 -> no problem.
Marco
--
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia
ngaywood(a)une.edu.au http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412 Mobile: +61 (0)4 7862 0062
Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.
fedoraproject.org/message/HKJWOZ6XEPRUQWDJTBWFFY6D2MW2EM3H/
10:35 a.m.
Robert Moskowitz wrote:
When I woke up this morning at 5:30 to head to the airport, I heard
my
system fan going at full speed. I tried to log in to the locked system,
but no response. I had to power cycle. Looking back in messages, the
last messages were right after 4am:
# grep "Jul 15 04" messages
Jul 15 04:01:01 lx121e audit[6374]: USER_ACCT pid=6374 uid=0
auid=4294967295 ses=4294967295
subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting
grantors=pam_access,pam_unix,pam_localuser acct="rgm"
exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:01 lx121e audit[6374]: CRED_ACQ pid=6374 uid=0
auid=4294967295 ses=4294967295
subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:02 lx121e systemd[1]: Started Session 5 of user rgm.
Jul 15 04:01:02 lx121e audit[6374]: USER_START pid=6374 uid=0 auid=1000
ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd acct="rgm"
exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:02 lx121e audit[6374]: CRED_REFR pid=6374 uid=0 auid=1000
ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
hostname=? addr=? terminal=cron res=success'
And then nothing until the restart. Any recommendations on where to dig
to guess at what caused this?
Last night I had done an update and had rebooted the system, so it was a
fresh boot, but with all my processes running.
thanks
I've been experience locks every few hours!
I also noticed /var/log/messages being spammed with errors:
Jul 15 03:47:05 nbecker2 systemd[1180]: Starting Tracker metadata
extractor...
Jul 15 03:47:05 nbecker2 dbus-daemon[1212]: [session uid=1000 pid=1212]
Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Jul 15 03:47:05 nbecker2 systemd[1180]: Started Tracker metadata extractor.
Jul 15 03:47:05 nbecker2 journal[2489]: Could not insert metadata for item
"file:///home/nbecker/Downloads/multibeam_joint.pdf": 46.34: invalid UTF-8
character
Jul 15 03:47:05 nbecker2 journal[2489]: If the error above is recurrent for
the same item/ID, consider running "tracker-extract" in the terminal with
the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the
additional information
I have no need for tracker, so I uninstalled it.
So far, no lock (but maybe haven't waited long enough yet)
12:04 p.m.
I don't know if this is related to the problem, but my system crashed
over night again. However, the last thing I saw while running tail -f
/var/log/messages was the following:
Jul 16 05:09:23 terrapin kernel: ------------[ cut here ]------------
Jul 16 05:09:23 terrapin kernel: kernel BUG at mm/page_alloc.c:2019!
Jul 16 05:09:23 terrapin kernel: invalid opcode: 0000 [#1] SMP PTI
Jul 16 05:09:23 terrapin kernel: Modules linked in: rfcomm xt_CHECKSUM
ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns
nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
xt_conntrack binfmt_misc ip_set nfnetlink ebtable_nat ebtable_broute
bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
ip6table_mangle ip6table_raw ip6table_security iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter
ebtables ip6table_filter ip6_tables vmnet(OE) ppdev parport_pc parport
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) fuse
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) cmac bnep vfat fat
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2
videobuf2_common videodev btusb
Jul 16 05:09:23 terrapin kernel: btrtl btbcm btintel bluetooth media
ecdh_generic snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal
intel_powerclamp coretemp snd_hda_codec_generic snd_hda_codec_hdmi
kvm_intel snd_hda_intel arc4 kvm iwlmvm snd_hda_codec mac80211 irqbypass
snd_hda_core snd_hwdep crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
intel_cstate wmi_bmof snd_seq snd_seq_device intel_uncore dell_wmi
sparse_keymap intel_rapl_perf snd_pcm iTCO_wdt iTCO_vendor_support
dell_laptop dell_smbios dell_wmi_descriptor dcdbas dell_smm_hwmon
rtsx_pci_ms dell_rbtn joydev snd_timer memstick iwlwifi cfg80211 wmi
mei_me lpc_ich rfkill snd soundcore i2c_i801 mei shpchp dell_smo8800
hid_multitouch i915 uas usb_storage rtsx_pci_sdmmc mmc_core i2c_algo_bit
drm_kms_helper drm crc32c_intel serio_raw r8169 rtsx_pci mii video
Jul 16 05:09:23 terrapin kernel: CPU: 3 PID: 2792 Comm: Xorg Tainted:
G OE 4.17.5-100.fc27.x86_64 #1
Jul 16 05:09:23 terrapin kernel: Hardware name: Dell Inc. Inspiron
7537/0F5R3Y, BIOS A14 10/04/2016
Jul 16 05:09:23 terrapin kernel: RIP: 0010:move_freepages_block+0x2d4/0x2e0
Jul 16 05:09:23 terrapin kernel: RSP: 0018:ffffba8ac916b7d8 EFLAGS: 00010083
Jul 16 05:09:23 terrapin kernel: RAX: ffff9dc13f5d5680 RBX:
0000000000100000 RCX: ffff9dc13f5d5000
Jul 16 05:09:23 terrapin kernel: RDX: 0000000000000002 RSI:
0000000000000000 RDI: 0000000000000003
Jul 16 05:09:23 terrapin kernel: RBP: ffffba8ac916b83c R08:
0000000000000004 R09: ffff9dc13f5d58f0
Jul 16 05:09:23 terrapin kernel: R10: ffffffff8de28048 R11:
ffffe09a80000000 R12: 0000000000000002
Jul 16 05:09:23 terrapin kernel: R13: ffff9dc13f5d5680 R14:
ffffe09a82988000 R15: ffff9dc13f5d5680
Jul 16 05:09:23 terrapin kernel: FS: 00007fc46d8a9a80(0000)
GS:ffff9dc13f2c0000(0000) knlGS:0000000000000000
Jul 16 05:09:23 terrapin kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Jul 16 05:09:23 terrapin kernel: CR2: 00007fc44c184000 CR3:
0000000428c40006 CR4: 00000000001606e0
Jul 16 05:09:23 terrapin kernel: Call Trace:
Jul 16 05:09:23 terrapin kernel: steal_suitable_fallback+0x14c/0x1a0
Jul 16 05:09:23 terrapin kernel: get_page_from_freelist+0x639/0x16f0
Jul 16 05:09:23 terrapin kernel: __alloc_pages_nodemask+0x11e/0x2a0
Jul 16 05:09:23 terrapin kernel: alloc_pages_vma+0x7c/0x200
Jul 16 05:09:23 terrapin kernel: shmem_alloc_page+0x78/0xc0
Jul 16 05:09:23 terrapin kernel: ? release_pages+0x1d1/0x460
Jul 16 05:09:23 terrapin kernel: ? __radix_tree_insert+0x45/0x220
Jul 16 05:09:23 terrapin kernel: ? page_evictable+0xe/0x40
Jul 16 05:09:23 terrapin kernel: ? __vm_enough_memory+0x5f/0x1b0
Jul 16 05:09:23 terrapin kernel: shmem_alloc_and_acct_page+0x72/0x1b0
Jul 16 05:09:23 terrapin kernel: shmem_getpage_gfp+0x192/0xd60
Jul 16 05:09:23 terrapin kernel: ? __sg_alloc_table+0x9b/0x150
Jul 16 05:09:23 terrapin kernel: shmem_read_mapping_page_gfp+0x42/0x80
Jul 16 05:09:23 terrapin kernel:
i915_gem_object_get_pages_gtt+0x1ae/0x670 [i915]
Jul 16 05:09:23 terrapin kernel: __i915_gem_object_get_pages+0x52/0x60
[i915]
Jul 16 05:09:23 terrapin kernel: i915_gem_set_domain_ioctl+0x1fa/0x250
[i915]
Jul 16 05:09:23 terrapin kernel: ?
i915_gem_obj_prepare_shmem_write+0x140/0x140 [i915]
Jul 16 05:09:23 terrapin kernel: drm_ioctl_kernel+0x5b/0xb0 [drm]
Jul 16 05:09:23 terrapin kernel: drm_ioctl+0x2c3/0x360 [drm]
Jul 16 05:09:23 terrapin kernel: ?
i915_gem_obj_prepare_shmem_write+0x140/0x140 [i915]
Jul 16 05:09:23 terrapin kernel: ? ep_poll+0xaa/0x3f0
Jul 16 05:09:23 terrapin kernel: ? do_signal+0x194/0x610
Jul 16 05:09:23 terrapin kernel: do_vfs_ioctl+0xa4/0x620
Jul 16 05:09:23 terrapin kernel: ksys_ioctl+0x70/0x80
Jul 16 05:09:23 terrapin kernel: __x64_sys_ioctl+0x16/0x20
Jul 16 05:09:23 terrapin kernel: do_syscall_64+0x5b/0x160
Jul 16 05:09:23 terrapin kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 16 05:09:23 terrapin kernel: RIP: 0033:0x7fc46abb80f7
Jul 16 05:09:23 terrapin kernel: RSP: 002b:00007ffdfafd4008 EFLAGS:
00000246 ORIG_RAX: 0000000000000010
Jul 16 05:09:23 terrapin kernel: RAX: ffffffffffffffda RBX:
0000000002922e30 RCX: 00007fc46abb80f7
Jul 16 05:09:23 terrapin kernel: RDX: 00007ffdfafd4084 RSI:
00000000400c645f RDI: 000000000000000c
Jul 16 05:09:23 terrapin kernel: RBP: 00007ffdfafd4084 R08:
0000000002922e30 R09: 0000000000000008
Jul 16 05:09:23 terrapin kernel: R10: 0000000001182010 R11:
0000000000000246 R12: 00000000400c645f
Jul 16 05:09:23 terrapin kernel: R13: 000000000000000c R14:
00000000011dd790 R15: 00000000007f8000
Jul 16 05:09:23 terrapin kernel: Code: 48 89 c6 48 c1 e8 33 48 c1 ee 36
83 e0 07 48 8d 3c 40 48 8d 04 b8 48 c1 e0 07 48 03 04 f5 80 59 38 8e 48
39 c1 0f 84 fe fd ff ff <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
00 00 41 57 41 56
Jul 16 05:09:23 terrapin kernel: RIP: move_freepages_block+0x2d4/0x2e0
RSP: ffffba8ac916b7d8
Jul 16 05:09:23 terrapin kernel: ---[ end trace fbe506e094db9a5f ]---
Paolo
On 07/16/2018 08:35 AM, Neal Becker wrote:
Robert Moskowitz wrote:
> When I woke up this morning at 5:30 to head to the airport, I heard my
> system fan going at full speed. I tried to log in to the locked system,
> but no response. I had to power cycle. Looking back in messages, the
> last messages were right after 4am:
>
> # grep "Jul 15 04" messages
> Jul 15 04:01:01 lx121e audit[6374]: USER_ACCT pid=6374 uid=0
> auid=4294967295 ses=4294967295
> subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting
> grantors=pam_access,pam_unix,pam_localuser acct="rgm"
> exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
> Jul 15 04:01:01 lx121e audit[6374]: CRED_ACQ pid=6374 uid=0
> auid=4294967295 ses=4294967295
> subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
> grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
> hostname=? addr=? terminal=cron res=success'
> Jul 15 04:01:02 lx121e systemd[1]: Started Session 5 of user rgm.
> Jul 15 04:01:02 lx121e audit[6374]: USER_START pid=6374 uid=0 auid=1000
> ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023
> msg='op=PAM:session_open
> grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd acct="rgm"
> exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
> Jul 15 04:01:02 lx121e audit[6374]: CRED_REFR pid=6374 uid=0 auid=1000
> ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
> grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
> hostname=? addr=? terminal=cron res=success'
>
> And then nothing until the restart. Any recommendations on where to dig
> to guess at what caused this?
>
> Last night I had done an update and had rebooted the system, so it was a
> fresh boot, but with all my processes running.
>
> thanks
>
I've been experience locks every few hours!
I also noticed /var/log/messages being spammed with errors:
Jul 15 03:47:05 nbecker2 systemd[1180]: Starting Tracker metadata
extractor...
Jul 15 03:47:05 nbecker2 dbus-daemon[1212]: [session uid=1000 pid=1212]
Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Jul 15 03:47:05 nbecker2 systemd[1180]: Started Tracker metadata extractor.
Jul 15 03:47:05 nbecker2 journal[2489]: Could not insert metadata for item
"file:///home/nbecker/Downloads/multibeam_joint.pdf": 46.34: invalid UTF-8
character
Jul 15 03:47:05 nbecker2 journal[2489]: If the error above is recurrent for
the same item/ID, consider running "tracker-extract" in the terminal with
the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the
additional information
I have no need for tracker, so I uninstalled it.
So far, no lock (but maybe haven't waited long enough yet)
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
1:13 p.m.
This seems to be https://bugzilla.redhat.com/show_bug.cgi?id=1598462
There should be a fix in the next update/rawhide kernels.
kevin
5:52 a.m.
Kevin Fenzi wrote:
This seems to be https://bugzilla.redhat.com/show_bug.cgi?id=1598462
There should be a fix in the next update/rawhide kernels.
kevin
Not for me - I don't have any external usb drive.
My system locked again yesterday, this time while waking up from sleep.
Trying kernel 4.17.3
7:10 a.m.
On Tue, 2018-07-17 at 06:52 -0400, Neal Becker wrote:
Kevin Fenzi wrote:
> This seems to be https://bugzilla.redhat.com/show_bug.cgi?id=1598462
>
> There should be a fix in the next update/rawhide kernels.
>
> kevin
Not for me - I don't have any external usb drive.
My system locked again yesterday, this time while waking up from sleep.
Trying kernel 4.17.3
Ditto. I've added a comment to the above BZ report.
poc
8:22 a.m.
Probably a completely different problem, but my system also
crashed last night, and my router crashed as well. In fact
I suspect the router crash took down my system. The last
thing in the log was a message I've never seen before
about networkd service watchdog timeout. (didn't appear
in any of the old logs still on the system).
I'd hate to think a bad router could crash the system
but it sure looks like what happened :-(.
8:34 a.m.
On 07/17/2018 09:22 AM, Tom Horsley wrote:
Probably a completely different problem, but my system also
crashed last night, and my router crashed as well. In fact
I suspect the router crash took down my system. The last
thing in the log was a message I've never seen before
about networkd service watchdog timeout. (didn't appear
in any of the old logs still on the system).
I'd hate to think a bad router could crash the system
but it sure looks like what happened :-(.
I think there is something in there related to networking. With kernels
17.4 and .5 my suspend hangs are right where the network shutdown
normally occurs. And I got this only when QEMU is running with some VM
active on the virtual network. 17.3 seems stable wrt to my problems.
9:07 a.m.
On 07/17/18 21:34, Robert Moskowitz wrote:
On 07/17/2018 09:22 AM, Tom Horsley wrote:
> Probably a completely different problem, but my system also
> crashed last night, and my router crashed as well. In fact
> I suspect the router crash took down my system. The last
> thing in the log was a message I've never seen before
> about networkd service watchdog timeout. (didn't appear
> in any of the old logs still on the system).
>
> I'd hate to think a bad router could crash the system
> but it sure looks like what happened :-(.
I think there is something in there related to networking. With kernels 17.4 and
.5 my suspend hangs are right where the network shutdown normally occurs. And I
got this only when QEMU is running with some VM active on the virtual network.
17.3 seems stable wrt to my problems.
FWIW, it seems there may be a few nasty hard to diagnose issues with recent kernels.
4.17.7 may be key to fixing issues...
https://lkml.org/lkml/2018/7/17/434
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
9:04 a.m.
On 07/17/18 21:22, Tom Horsley wrote:
Probably a completely different problem, but my system also
crashed last night, and my router crashed as well. In fact
I suspect the router crash took down my system. The last
thing in the log was a message I've never seen before
about networkd service watchdog timeout. (didn't appear
in any of the old logs still on the system).
I'd hate to think a bad router could crash the system
but it sure looks like what happened :-(.
Could it have been a simple case of a spike on mains power?
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
9:36 a.m.
On Tue, 17 Jul 2018 22:04:49 +0800
Ed Greshko wrote:
Could it have been a simple case of a spike on mains power?
I suppose, but there were no messages from my UPS which
generally whines about stuff like that. Maybe it was
a test of an alien EMP device :-).
I guess I'll see if it happens again, or was just a one time thing.
9:56 a.m.
On 07/17/2018 10:36 AM, Tom Horsley wrote:
On Tue, 17 Jul 2018 22:04:49 +0800
Ed Greshko wrote:
> Could it have been a simple case of a spike on mains power?
I suppose, but there were no messages from my UPS which
generally whines about stuff like that. Maybe it was
a test of an alien EMP device :-).
I guess I'll see if it happens again, or was just a one time thing.
I have more problems from sags than spikes. That is why I use at line
conditioners (like Tripp Lite LC line) or UPS with line conditioning
(prevents constant switching to batteries when a sag drops the voltage
below 90v). Notebooks tend not to be affected too much, but switches
and APs reset. The utility (DTE) says I am 'within specs', but you can
see incandescent bulbs dim when anything heavy comes on line. And my
kill-a-watt reports the voltage drops.
I had a wireless extender plugged directly into a regular surge
protector, and my notebook would regularly drop its WiFi connection then
have to reassociate and release its address. I had to get a LC just for
the one device.
6:42 a.m.
On Tue, 17 Jul 2018 10:36:30 -0400
Tom Horsley wrote:
I guess I'll see if it happens again, or was just a one time
thing.
It did OK for 1 night, then I found it crashed again this
morning, and the router crashed the same way as well.
I'm booted back on the 4.16.16-300.fc28.x86_64 kernel now and
I'll see if it stays up for a while.
The router interaction is weird. If it is a kernel bug, how
does it crash the router. If it is a router bug, why did it
just show up as soon as I got the suspicious kernel? There
is nothing in the router configuration that should require
my computer to be up.
7:12 a.m.
On 07/19/2018 07:42 AM, Tom Horsley wrote:
On Tue, 17 Jul 2018 10:36:30 -0400
Tom Horsley wrote:
> I guess I'll see if it happens again, or was just a one time thing.
It did OK for 1 night, then I found it crashed again this
morning, and the router crashed the same way as well.
I'm booted back on the 4.16.16-300.fc28.x86_64 kernel now and
I'll see if it stays up for a while.
The router interaction is weird. If it is a kernel bug, how
does it crash the router. If it is a router bug, why did it
just show up as soon as I got the suspicious kernel? There
is nothing in the router configuration that should require
my computer to be up.
What model router?
What services? First place I would look at is DHCPD there.
Unless you are doing something fancy with gaming or web proxying
Electrical? Summertime brownouts can be REALLY bad on low end stuff.
Get a Tripp Lite Line Conditioner (LC line; they have been making
stuff like this since '47)
Also check the condition of your notebook's battery.
Perhaps the cleaning help plugged the vacumn into the same outlet
as your router :)
This happened to us at one branch office; ouch!
Or maybe it is gremlins. :) :)
7:55 a.m.
On Thu, 19 Jul 2018 08:12:12 -0400
Robert Moskowitz wrote:
What model router?
It is an ASUS RT-AC5300
https://tomhorsley.com/hardware/rt-ac5300/rt-ac5300.html
(from the way the router is positioned you can also
deduce I'm not married :-).
What services? First place I would look at is DHCPD there.
Unless you are doing something fancy with gaming or web proxying
Nothing fancy. The router is doing all the work, acting as DNS and
DHCP for the home network. Don't have it configured to transfer logs
to the main computer or anything like that. In fact I've often used
phones and tablets on it when the main computer was down for a re-gen
or something like that.
Electrical? Summertime brownouts can be REALLY bad on low end
stuff.
Get a Tripp Lite Line Conditioner (LC line; they have been making
stuff like this since '47)
I've got a line conditioner (Panamax, not Tripp Lite). Also I'd think
brownouts would be more likely at the hottest time of the day, not
at 4 am when it is more likely to be relatively cool (though in Florida,
the "relative" modifier definitely applies this time of year).
Also check the condition of your notebook's battery.
Not a notebook, a desktop, and the UPS has plenty of reserve.
Perhaps the cleaning help plugged the vacumn into the same
outlet
as your router :)
This happened to us at one branch office; ouch!
Or maybe it is gremlins. :) :)
It is at home, not work, and I'm sure I wasn't running the vacuum at
4 am when the crash happened. It probably was doing a backup to USB
drive, which might make the bugzilla that has been pointed at
here the culprit, I just don't understand the router involvement.
I'll be interested to see if both stay up for several days now,
or perhaps the router keeps crashing, but at least the system stays
up. (In which case it is time for new router I guess, or at least time
to check for new router firmware).
10:51 a.m.
On 07/19/2018 08:55 AM, Tom Horsley wrote:
On Thu, 19 Jul 2018 08:12:12 -0400
Robert Moskowitz wrote:
> What model router?
It is an ASUS RT-AC5300
https://tomhorsley.com/hardware/rt-ac5300/rt-ac5300.html
(from the way the router is positioned you can also
deduce I'm not married :-).
> What services? First place I would look at is DHCPD there.
> Unless you are doing something fancy with gaming or web proxying
Nothing fancy. The router is doing all the work, acting as DNS and
DHCP for the home network. Don't have it configured to transfer logs
Consider that you are running out of temp space with logs and this space
is freed up on restart from the crash. With an old router, many
permanent things can eat up storage such that there is little space for
temp logs.
to the main computer or anything like that. In fact I've often
used
phones and tablets on it when the main computer was down for a re-gen
or something like that.
> Electrical? Summertime brownouts can be REALLY bad on low end stuff.
> Get a Tripp Lite Line Conditioner (LC line; they have been making
> stuff like this since '47)
I've got a line conditioner (Panamax, not Tripp Lite). Also I'd think
brownouts would be more likely at the hottest time of the day, not
at 4 am when it is more likely to be relatively cool (though in Florida,
the "relative" modifier definitely applies this time of year).
4am. That is about the time the cleaning staff came through. We had to
put a camera into the area to figure out what was happening and we saw
the staff plug the vacuum into the server's power strip. We had to screw
plates into those outlets to get them to stop!
But you might be having a utility event then in the middle of night that
is producing the electrical glitch. "Oh no we don't to anything like
that to our customers." Yeah, right. A good line conditioner should be
keeping those gremlins away from your electronics. I have been up at
3am (on a conference call to my colleagues in China and Germany) and
heard my Tripp Lite doing its job and no motors in the house started up
at that time.
> Also check the condition of your notebook's battery.
Not a notebook, a desktop, and the UPS has plenty of reserve.
Provided it has line conditioning circuitry. (showing my bias here)
> Perhaps the cleaning help plugged the vacumn into the same outlet
> as your router :)
> This happened to us at one branch office; ouch!
> Or maybe it is gremlins. :) :)
It is at home, not work, and I'm sure I wasn't running the vacuum at
4 am when the crash happened. It probably was doing a backup to USB
drive, which might make the bugzilla that has been pointed at
here the culprit, I just don't understand the router involvement.
Finding where the gremlins are popping out can be soooo much fun.
Not.
I'll be interested to see if both stay up for several days now,
or perhaps the router keeps crashing, but at least the system stays
up. (In which case it is time for new router I guess, or at least time
to check for new router firmware).
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
2:15 p.m.
On Thu, 19 Jul 2018 08:55:58 -0400
Tom Horsley wrote:
I'll be interested to see if both stay up for several days now,
or perhaps the router keeps crashing, but at least the system stays
up. (In which case it is time for new router I guess, or at least time
to check for new router firmware).
Well, for two days since I booted back to old kernel there
have been no crashes of the computer or the router, and USB
backups have been working OK. It is looking like it was the
kernel doing it, but how it can crash the router is still
very mysterious.
Must be that disguised code inserted in linux by evil hackers
that completely rewrote in a totally obfuscated fashion the
entire network stack under the guise of improving network
performance by 0.0001%, but really attempts to attack routers
from the inside rather than the outside :-).
2:04 p.m.
On 07/26/2018 11:42 AM, Frédéric wrote:
Hi,
Has anyone tested the new kernel 4.17.7? Any issues during backups?
Define "backups." I'm using it and had no issues using rsync to back up
to an external drive on both a desktop machine and a laptop:
# nice -n 19 /bin/rsync -av -S --exclude-from=/etc/skipdirs.rsync /
/media/external-3TB-Drive
where "/etc/skipdirs.rsync" contains:
/proc/*
/sys/*
/dev/*
/media/**
/mnt/**
/var/log/journal/*
/run/media/**
/var/lib/docker/*
The only issues I've heard of are anecdotal regarding suspend and such
(it fixes a lot of problems that 4.17.4-200 through 4.17.6-200 had, but
not all of them) and it's unclear if it's a kernel issue or a particular
set of ancillary processes (VMs and the like) that's causing it. The
only thing that seems definitive is that it behaves "differenly" than
4.17.3-200 and earlier kernels, whatever "differently" means.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- The world is coming to an end ... SAVE YOUR FILES!!! -
----------------------------------------------------------------------
3:32 a.m.
> Has anyone tested the new kernel 4.17.7? Any issues during
backups?
Define "backups.
I refer to the previous posts about broken backups. Personnaly I use
rsnapshot that uses rsync.
I'm using it and had no issues using rsync to back up
to an external drive on both a desktop machine and a laptop
The only issues I've heard of are anecdotal regarding suspend
Thanks, I may consider upgrading then.
3:11 p.m.
On Thu, Jul 26, 2018 at 8:42 PM, Frédéric <ufospoke(a)gmail.com> wrote:
Hi,
Has anyone tested the new kernel 4.17.7? Any issues during backups?
Hi,
Before kernerl 4.17.7, I had issues during my duplicity-based backups.
With kernel 4.17.7, no issue to date.
I've been testing it since its release in Fedora 28.
Cheers,
Marco
1:21 p.m.
On 07/27/2018 02:11 PM, Samuel Sieb wrote:
On 07/26/2018 11:42 AM, Frédéric wrote:
> Has anyone tested the new kernel 4.17.7? Any issues during backups?
I don't know about backups, but so far I haven't had any random system
lockups like I was getting before.
4.17.7 has been solid for me as well for the better par of a week now.
(I was one of the folks who reported this issues a couple of weeks back.
My system was hanging during backups to an NFS-mounted NAS.)
--
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
1:29 p.m.
On Fri, 2018-07-27 at 11:11 -0700, Samuel Sieb wrote:
On 07/26/2018 11:42 AM, Frédéric wrote:
> Has anyone tested the new kernel 4.17.7? Any issues during backups?
I don't know about backups, but so far I haven't had any random system
lockups like I was getting before.
Same here.
poc
1:23 p.m.
On 07/15/2018 07:30 AM, Robert Moskowitz wrote:
When I woke up this morning at 5:30 to head to the airport, I heard
my
system fan going at full speed. I tried to log in to the locked system,
but no response. I had to power cycle. Looking back in messages, the
last messages were right after 4am:
# grep "Jul 15 04" messages
Jul 15 04:01:01 lx121e audit[6374]: USER_ACCT pid=6374 uid=0
auid=4294967295 ses=4294967295
subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting
grantors=pam_access,pam_unix,pam_localuser acct="rgm"
exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:01 lx121e audit[6374]: CRED_ACQ pid=6374 uid=0
auid=4294967295 ses=4294967295
subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:02 lx121e systemd[1]: Started Session 5 of user rgm.
Jul 15 04:01:02 lx121e audit[6374]: USER_START pid=6374 uid=0 auid=1000
ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd acct="rgm"
exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
Jul 15 04:01:02 lx121e audit[6374]: CRED_REFR pid=6374 uid=0 auid=1000
ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
hostname=? addr=? terminal=cron res=success'
And then nothing until the restart. Any recommendations on where to dig
to guess at what caused this?
Last night I had done an update and had rebooted the system, so it was a
fresh boot, but with all my processes running.
thanks
Tried 4.17.6, but still have the problem. Back on 4.17.3
--
-- Steve
11:19 p.m.
SternData ha scritto il 18/07/2018 alle 20:23:
On 07/15/2018 07:30 AM, Robert Moskowitz wrote:
> When I woke up this morning at 5:30 to head to the airport, I heard my
> system fan going at full speed. I tried to log in to the locked system,
> but no response. I had to power cycle. Looking back in messages, the
> last messages were right after 4am:
>
> # grep "Jul 15 04" messages
> Jul 15 04:01:01 lx121e audit[6374]: USER_ACCT pid=6374 uid=0
> auid=4294967295 ses=4294967295
> subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:accounting
> grantors=pam_access,pam_unix,pam_localuser acct="rgm"
> exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
> Jul 15 04:01:01 lx121e audit[6374]: CRED_ACQ pid=6374 uid=0
> auid=4294967295 ses=4294967295
> subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
> grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
> hostname=? addr=? terminal=cron res=success'
> Jul 15 04:01:02 lx121e systemd[1]: Started Session 5 of user rgm.
> Jul 15 04:01:02 lx121e audit[6374]: USER_START pid=6374 uid=0 auid=1000
> ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023
> msg='op=PAM:session_open
> grantors=pam_loginuid,pam_keyinit,pam_limits,pam_systemd acct="rgm"
> exe="/usr/sbin/crond" hostname=? addr=? terminal=cron res=success'
> Jul 15 04:01:02 lx121e audit[6374]: CRED_REFR pid=6374 uid=0 auid=1000
> ses=5 subj=system_u:system_r:crond_t:s0-s0:c0.c1023 msg='op=PAM:setcred
> grantors=pam_env,pam_localuser,pam_unix acct="rgm"
exe="/usr/sbin/crond"
> hostname=? addr=? terminal=cron res=success'
>
> And then nothing until the restart. Any recommendations on where to dig
> to guess at what caused this?
>
> Last night I had done an update and had rebooted the system, so it was a
> fresh boot, but with all my processes running.
>
> thanks
>
Tried 4.17.6, but still have the problem. Back on 4.17.3
https://bugzilla.redhat.com/show_bug.cgi?id=1598462
--
Antonio Montagnani
Linux Fedora 28 (Workstation)
2097
days inactive
2109
days old
51 comments
16 participants
participants (16)
-
antonio montagnani -
Ed Greshko -
Frédéric -
Kevin Fenzi -
Marco Guazzone -
Neal Becker -
Norman Gaywood -
Paolo Galtieri -
Patrick O'Callaghan -
Rick Stevens -
Robert Moskowitz -
Samuel Sieb -
SternData -
Tim Evans -
Tom Horsley -
Tom Yates