Bug 17235 - Occasional boot errors
Summary: Occasional boot errors
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-26 21:38 CET by Davide Nifosi
Modified: 2015-12-14 07:52 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Journal of last boot with the problems (31.48 KB, application/gzip)
2015-11-26 21:38 CET, Davide Nifosi
Details
Journal of a boot without problems for comparison (27.86 KB, application/gzip)
2015-11-27 19:03 CET, Davide Nifosi
Details

Description Davide Nifosi 2015-11-26 21:38:56 CET
Created attachment 7240 [details]
Journal of last boot with the problems

Sometimes there are errors during boot that prevent logind from working correctly, making a few things not work (audio, polkit).

This doesn't happen every time, only about every 3-4 boots. I suspect a timing issue
Comment 1 Luke Jones 2015-11-27 08:51:03 CET
It looks like logind fails once and restarts, and then polkit etc timeout?

It doesn't really look like logind is at fault since it can restart and succeed. There's a number of strange looking messages in there. Can you get another log to compare to?

CC: (none) => luke.nukem.jones

Comment 2 Davide Nifosi 2015-11-27 19:02:49 CET
Well, it wasn't clear to me where the fault lies in this, I'd need some guidance to understand where to look.

I'm attaching the journal of a regular boot with everything working (network and samba services still fail, but it was like that before and the network works fine)
Comment 3 Davide Nifosi 2015-11-27 19:03:47 CET
Created attachment 7243 [details]
Journal of a boot without problems for comparison
Comment 4 Davide Nifosi 2015-12-01 19:07:47 CET
Strangely enough, there haven't been any more boot errors since the last message, and I haven't installed any package updates since then. I don't really know what the problem was, but if I can't reproduce it in a couple of says I'll close this bug
Comment 5 Luke Jones 2015-12-01 19:46:55 CET
I'm changing this to resolved since it seems virtually impossible to track down the error due to inability to replicate.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 6 Rémi Verschelde 2015-12-03 10:19:02 CET
Closing as WORKSFORME then, as we're not sure if it's properly fixed or just somewhat hard to reproduce.

Resolution: FIXED => WORKSFORME

Comment 7 Davide Nifosi 2015-12-14 07:52:04 CET
Just adding a closing comment: I think my issue was the one found here

https://github.com/systemd/systemd/issues/1505

(a deadlock in systemd, I believe)

It should be fixed in version 228. I have no hurry to get the fix since the bug has occurred only one more time since my last report

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