Bug 18665 - [6sta1] text displayed at start of boot
Summary: [6sta1] text displayed at start of boot
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Low minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: 6sta1
Depends on:
Blocks:
 
Reported: 2016-06-09 11:32 CEST by Ben McMonagle
Modified: 2016-07-24 15:44 CEST (History)
4 users (show)

See Also:
Source RPM: kernel, systemd
CVE:
Status comment:


Attachments

Description Ben McMonagle 2016-06-09 11:32:25 CEST
Description of problem: the following text is displayed after choosing an i586 6sta1 installed system from the new Grub2 menu:

early console in decompress_kernel 
input_data: 0x007b9101
input_len: 0x005e5eab
output: 0x00100000
output_len: 0x00c8d8b4
run_size: 0x00e5b000
KASLR disabled by default...

Decompressing Linux...Parsing ELF...No relocation needed...
Booting the kernel.
Failed to get cgroup: No medium Found
starting version 229
rw,noaruntime,data = ordered 


perhaps it should be hidden?


Version-Release number of selected component (if applicable):
Mageia-6-sta1-i586-DVD.iso
DATE.txt: Mon Jun  6 23:20:56 CEST 2016

How reproducible:every time


Steps to Reproduce:
1.install a DE from above .iso and reboot
2.select the just installed 6sta1 system from grub2 menu
3.
Ben McMonagle 2016-06-09 11:32:40 CEST

Keywords: (none) => 6sta1

Comment 1 Ben McMonagle 2016-06-09 11:49:41 CEST
updating to version 230 hides all the above,

so marking as fixed

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

Comment 2 Ben McMonagle 2016-06-25 02:47:54 CEST
except for "rw,notime,data = ordered"

valid for 

Mageia-6-sta1-i586-DVD.iso
DATE.txt: Mon Jun 20 23:38:16 CEST 2016

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

Thierry Vignaud 2016-06-30 10:39:03 CEST

Priority: Normal => Low
CC: (none) => mageia, thierry.vignaud, tmb
Source RPM: (none) => kernel, systemd
Severity: normal => minor

Comment 3 Otto Leipälä 2016-07-21 16:06:34 CEST
No i don't get in my main install Mga6 that error anymore and upstream systemd have already fixed it.

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

CC: (none) => ozkyster

Comment 4 Thierry Vignaud 2016-07-24 15:44:22 CEST
Closing then

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


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