Bug 22547 - hardware dropped
Summary: hardware dropped
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2018-02-09 08:54 CET by Mészáros Csaba
Modified: 2020-08-16 16:07 CEST (History)
4 users (show)

See Also:
Source RPM: kernel-desktop-4.14.16-1.mga6-1-1.mga6
CVE:
Status comment:


Attachments
journalctl_messages (10.23 KB, text/plain)
2018-02-09 08:55 CET, Mészáros Csaba
Details
this script ran (407 bytes, application/x-shellscript)
2018-02-09 09:08 CET, Mészáros Csaba
Details
Asus M3N78-EMH HDMI after fresh install error logs. (24.44 KB, application/x-bzip)
2018-02-10 21:05 CET, Mészáros Csaba
Details

Description Mészáros Csaba 2018-02-09 08:54:24 CET
Description of problem:
I have a big problem.
I recorded programs on the TV. But more recently, the recording will stop
But maybe because of the new kernel now within a specified time the recording will stop. Extremely annoying.
The mpv does not issue an error message even though --msg-level=all=error is specified.
So far, I found error message in journalctl alone.

How reproducible:
100%

Look at journalctl-messages.txt
Comment 1 Mészáros Csaba 2018-02-09 08:55:51 CET
Created attachment 9966 [details]
journalctl_messages
Mészáros Csaba 2018-02-09 08:56:21 CET

Attachment 9966 description: kernel messages => journalctl_messages

Comment 2 Mészáros Csaba 2018-02-09 09:08:19 CET
Created attachment 9967 [details]
this script ran

The run time 4800 sec = 80 minute
the hardware is dropping: after 2880 sec = 48 minute
Mészáros Csaba 2018-02-09 09:09:21 CET

CC: (none) => pingvin

Comment 3 Thomas Backlund 2018-02-09 09:12:09 CET
please test with kernel 4.14.18-1 currently in updates_testing

CC: (none) => tmb

Marja Van Waes 2018-02-09 09:36:35 CET

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 4 Mészáros Csaba 2018-02-09 19:12:12 CET
Well. I tried, though I did not.
The start of the system was extremely slow. :(

pam_systemd(su-1:session): Failed to create session.

After I logged in, the keyboard was discarded and computer frozen. 

I removed all new kernels and returned to 4.14.13-desktop-1.mga6
But the slow start has remained. Now I'm going to generate a new initrd.
Maybe it will help.
Comment 5 Thomas Backlund 2018-02-09 19:25:40 CET
ok, so that is an old amd system, so its not affected by the intel microcode mess...

and since 4.14.13 works, it means the meltdown fixes should be ok,

but 4.14.16 added spectre retpoline stuff, and 4.14.18 goes for full retpoline 


If you try to boot with "nospectre_v2" kernel command line, is your system more stable ?
Comment 6 Mészáros Csaba 2018-02-10 10:04:24 CET
I could not solve this slow start. So I reinstalled it all.
Especially since I installed a new PCI-x1 USB3 card.
Unfortunately, there is still a slow start but no error message.
This is a VIA chipset USB 3.0 card. The system was recognized without errors.
He loaded the xhci stuff. But why do you expect hardware detection for more than 1 minute during each boot? This many time.
Can not turn this hardware detector off?
Ma, holnap még kísérletezek az új kernelekkel is.
Today, tomorrow before I make the system sharp, I'll experiment with new kernels.
But this slow start would be good solve.
Comment 7 Mészáros Csaba 2018-02-10 21:05:09 CET
Created attachment 9976 [details]
Asus M3N78-EMH HDMI after fresh install error logs.

I've tested the new 4.14.18 kernel with the nospectre_v2 switch.
It seems all right. So far, the machine did not break and did not throw the hardware away. I've made a couple of logos for keeping it. I've created a few logs for viewing. The boot procedure still slow.

Now, I am sure that pam.systemd is a problematic.

pam_systemd(su-1:session): Failed to create session.
Comment 8 Mészáros Csaba 2018-02-10 21:07:50 CET
oops: logos - logs
hungarian word into logs: Helytelen - incorrect.
Comment 9 Aurelien Oudelet 2020-08-16 16:07:04 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien


Note You need to log in before you can comment on or make changes to this bug.