Guillaume GARDET changed bug 1225352
What Removed Added
Flags needinfo?(guillaume.gardet@arm.com)  

Comment # 8 on bug 1225352 from Guillaume GARDET
(In reply to Fabian Vogt from comment #7)
> (In reply to Guillaume GARDET from comment #6)
> > (In reply to Fabian Vogt from comment #5)
> > > (In reply to Guillaume GARDET from comment #4)
> > > > Created attachment 875148 [details]
> > > > 15.5 serial boot log with a longer timeout
> > > > 
> > > > With a longer timeout, it manages to boot until login prompt and starts
> > > > jeos-fisrtboot on serial.
> > > >
> > > > I think jeos-fisrtboot should not be started as it blocks the start of the
> > > > ssh server.
> > > 
> > > Why does it start jeos-firstboot? AFAIK it shouldn't be enabled in this
> > > image?
> > > 
> > > In my local test run it did not.
> > 
> > Ah no, sorry, an additional boot from a Tumbleweed test polluted the serial
> > log.
> > 
> > It hanged after:
> > **********
> > [  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
> >          Starting Security Auditing Service...
> >          Starting Rebuild Journal Catalog...
> > [  OK  ] Finished Commit a transient machine-id on disk.
> >          Starting Load/Save RF Kill Switch Status...
> > **********
> 
> Did it completely hang or just take a long time? Can you get the full
> journal?

Looks like a hang. I waited more than 10 min after the boot and the serial was
unresponsive after those lines. (No login prompt)

I will try to get more traces on serial.


You are receiving this mail because: