Bug 23090 - After latest update system stops booting after a few boots.
Summary: After latest update system stops booting after a few boots.
Status: RESOLVED DUPLICATE of bug 23060
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: High critical
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-27 18:54 CEST by Daniel Kalweit
Modified: 2018-05-30 07:38 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
package sources (135.54 KB, image/png)
2018-05-28 10:13 CEST, Daniel Kalweit
Details
failed boot (15.15 KB, application/x-xz)
2018-05-28 10:57 CEST, Daniel Kalweit
Details
working boot (with inserted USB stick) (25.75 KB, application/x-xz)
2018-05-28 10:58 CEST, Daniel Kalweit
Details

Description Daniel Kalweit 2018-05-27 18:54:48 CEST
Description of problem:
After latest update the system boots 5-6 times and then it doesn't boot anymore.


How reproducible:

I made a clean install of Mageia 6 and loaded the newest updates.
Not sure how often exactly it worked before the error occurs, but then it doesn't work anymore, no matter how often I try to boot.
When I choose in grub2 the older Kernel it boots again.
Daniel Kalweit 2018-05-27 18:55:08 CEST

Priority: Normal => High

Comment 1 Thomas Backlund 2018-05-27 19:00:15 CEST
you are probably hitting bug 23060.

There is now a kernel-4.14.44-1 in updates_testing that should work better...

Note that you need nonfree updates_testing enabled too in order to pull in the updated firmwares/microcode at the same time

CC: (none) => tmb

Comment 2 Daniel Kalweit 2018-05-27 19:06:19 CEST
Thanks I will try it later.

But I found out that the system boots again when I insert a USB stick :)) ...strange!!
Comment 3 Marja Van Waes 2018-05-27 21:55:43 CEST
(In reply to Daniel Kalweit from comment #2)
> Thanks I will try it later.
> 
> But I found out that the system boots again when I insert a USB stick :))
> ...strange!!

Please reproduce the failing boot and then boot with the inserted USB-stick and then run, as root:

   journalctl -b-1 > failed.txt

and 

   journalctl -b > with_USB.txt

And attach those two files.

(compress with xz if the files are too large to attach, e.g:

  xz failed.txt

will give failed.txt.xz that's much smaller)

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

Comment 4 Marja Van Waes 2018-05-27 21:57:20 CEST
Of course, if you already found that kernel-4.14.44-1 fixes the problem, those logs are no longer needed!
Comment 5 Daniel Kalweit 2018-05-28 10:12:03 CEST
I checked the testing sources but I can't update to kernel-4.14.44-1
Comment 6 Daniel Kalweit 2018-05-28 10:13:22 CEST
Created attachment 10203 [details]
package sources
Comment 7 Daniel Kalweit 2018-05-28 10:57:18 CEST
Created attachment 10204 [details]
failed boot

For me it seems that this error report is NOT from the failed boot. I don't know if I did something wrong.
Comment 8 Daniel Kalweit 2018-05-28 10:58:20 CEST
Created attachment 10205 [details]
working boot (with inserted USB stick)
Comment 9 Morgan Leijström 2018-05-28 20:46:33 CEST
(In reply to Daniel Kalweit from comment #5)
> I checked the testing sources but I can't update to kernel-4.14.44-1

Was it not found?
kernel.org have been off syncing but is catching up now.
Also, some other mirrors are syncing from it.
You may find 4.14.44-1 in a few hours on your mirror. If that was the problem.

CC: (none) => fri

Comment 10 Daniel Kalweit 2018-05-29 01:13:20 CEST
(In reply to Morgan Leijström from comment #9)
> (In reply to Daniel Kalweit from comment #5)
> > I checked the testing sources but I can't update to kernel-4.14.44-1
> 
> Was it not found?
> kernel.org have been off syncing but is catching up now.
> Also, some other mirrors are syncing from it.
> You may find 4.14.44-1 in a few hours on your mirror. If that was the
> problem.

Yes, I checked "core updates testing", "nonfree updates testing" und "tainted updates testing" as you can see on the attached screenshot, but nothing was found.
Comment 11 Morgan Leijström 2018-05-29 08:11:35 CEST
The *testing have no checkmark in column "Aktualisieren" so the GUI tools will not look in them for updates.

To put a checkmark there you could as root run
   # drakrpm-edit-media --expert

- But you should anyway be able to find the kernels in drakrpm.


Which mirror do you use?
There is a status page showing which are up to date:
http://mirrors.mageia.org/status
It is not perfectly reliable as it only checks a file at the mirror, but gives a hint.

Here you can see available mirrors and where they sync from: http://mirrors.mageia.org/

Also note: New kernel-4.14.44-2 came tonight, running it now :)
Comment 12 Daniel Kalweit 2018-05-29 13:12:46 CEST
(In reply to Morgan Leijström from comment #11)
> The *testing have no checkmark in column "Aktualisieren" so the GUI tools
> will not look in them for updates.
> 
> To put a checkmark there you could as root run
>    # drakrpm-edit-media --expert
> 
> - But you should anyway be able to find the kernels in drakrpm.
> 
> 
> Which mirror do you use?
> There is a status page showing which are up to date:
> http://mirrors.mageia.org/status
> It is not perfectly reliable as it only checks a file at the mirror, but
> gives a hint.
> 
> Here you can see available mirrors and where they sync from:
> http://mirrors.mageia.org/
> 
> Also note: New kernel-4.14.44-2 came tonight, running it now :)

Thanks, it works now (without inserted USB-stick)  :)

But nevertheless I had to install Mageia new, because the first time I ended up with a nonusable system because I choosed the wrong display-(login-) server.
At the moment it works exclusively with 'GNOMEonXORG' and no proprietary nVidia driver.
The default - after installing Mageia (Gnome) - is always GNOME (GDM). I had to switch to GNOMEonXorg before login.
Comment 13 Daniel Kalweit 2018-05-29 13:22:53 CEST
Sorry, maybe I messed up some things...

In the last sentence I meant that at the login screen you can choose which display-server you want to use for your session.
The default option is GNOME (I think it uses Wayland)
The second option is GNOMEonXorg and this is the only option that works for me.
(I never tried IceWM)
Comment 14 Morgan Leijström 2018-05-29 13:25:36 CEST
I think you should ask about Wayland on the forum.
Comment 16 Marja Van Waes 2018-05-30 07:38:54 CEST
(In reply to Daniel Kalweit from comment #12)
> (In reply to Morgan Leijström from comment #11)

> > 
> > Also note: New kernel-4.14.44-2 came tonight, running it now :)
> 
> Thanks, it works now (without inserted USB-stick)  :)
> 

So the original issue of this bug report is also a duplicate of bug 23060, then.

Did you indeed ask in the forums for help with the nVidia and the Wayland problems? They might need (or already have) separate bug reports.

*** This bug has been marked as a duplicate of bug 23060 ***

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


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