Re: Slow boot on F32 Workstation

2020-03-28 Thread Andreas Tunek 
Den tors 26 mars 2020 kl 05:56 skrev Przemek Klosowski via devel <
devel@lists.fedoraproject.org>:

> On 3/21/20 8:45 AM, Andreas Tunek wrote:
> > I sidegraded my rawhide install to F32 a couple of weeks ago and from
> > the start I noticed that booting F32 was really slow. I assumed this
> > was some kind of bug or some devel stuff and would get solved.
> >
> What did you upgrade from? There were Radeon firmware deficiencies
> introduced around February that cause about 10 1-sec timeouts on boot
> and every time the driver is awakened ( [Bug 1802641] kernel 5.4 Bug
> Radeon ).
>

I side-graded from rawhide. It is an fully Intel laptop.


> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-25 Thread Przemek Klosowski via devel 

On 3/21/20 8:45 AM, Andreas Tunek wrote:
I sidegraded my rawhide install to F32 a couple of weeks ago and from 
the start I noticed that booting F32 was really slow. I assumed this 
was some kind of bug or some devel stuff and would get solved.


What did you upgrade from? There were Radeon firmware deficiencies 
introduced around February that cause about 10 1-sec timeouts on boot 
and every time the driver is awakened ( [Bug 1802641] kernel 5.4 Bug 
Radeon ).

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-23 Thread Chris Murphy 
On Mon, Mar 23, 2020 at 5:03 AM Andreas Tunek  wrote:
>
> I did a new install without LVM. Booting is still slow but everything works 
> correctly (I did not get bug 1815787). So there is some problem with my 
> hardware. For which component do you think I should create a bug?

No idea. It requires diagnosis. I start with a complete journal for
one boot (-b option) and monotonic times, as described. Sometimes it's
necessary to add boot parameter rd.debug to debug dracut/initramfs
assembly time stuff to see if there are loops, and what it's waiting
for that it keeps looping. Sometimes use parameter
systemd.log_level=debug if I think it's a systemd logic problem, or
some unit dragging in another that it should't. I usually don't use
both at the same time because they slow down boot quite a lot. Another
one is rd.udev.debug to look at udev specific issues with device
discovery (or non-discovery).

I think this is on-topic for devel@ but you might get more help with
technique and what else to try or how to interpret the logs, on test@
list, or on #fedora-qa. It's tedious but there really is no other way
to figure it out. That you have a clean install with no LVM, and yet
there is a huge hit to LVM related service units is really suspicious
that there's something stale somewhere causing those to trigger and
look for something.

-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-23 Thread Andreas Tunek 
Den mån 23 mars 2020 kl 06:23 skrev Chris Murphy :

> On Sat, Mar 21, 2020 at 6:46 AM Andreas Tunek 
> wrote:
> >
> > I sidegraded my rawhide install to F32 a couple of weeks ago and from
> the start I noticed that booting F32 was really slow. I assumed this was
> some kind of bug or some devel stuff and would get solved.
> >
> > However, I still have the problem and I wonder if this a problem unique
> to my hardware or a general bug when you move from rawhide to a version. If
> it is a bug, does anyone know if there is a "slow boot on F32" bug
> somewhere?
> >
> > Here is my "systemd-analyse blame" output:
> >
> >   2min 266ms systemd-udev-settle.service
> > 1min 10.312s lvm2-monitor.service
> >  1min 6.118s lvm2-pvscan@8:3.service
> >  30.125s NetworkManager-wait-online.service
>
> These are excessive values. systemd-udev-settle is deprecated for a
> couple of years and nothing should be using it by now.
>
> You should check /etc/fstab for stale LVM LV's or fs UUIDs that no
> longer exist on this system. The delays are consistent with something
> missing. You can also get more information looking at;
> # journalctl -b -o short-monotonic
>
> And checking for large gaps in time, what was recently started right
> before that gap, or right after it if there are any timeouts. But as
> it is, there's not enough information to know for sure what's going on
> other than, yes in fact it's taking an excessive amount of time to
> start up. And I think it is a local problem because I'm not seeing it
> on three systems with clean installs, and dozens of VM's, so at the
> least it's not a consistent problem.
>
>
>
I did a new install without LVM. Booting is still slow but everything works
correctly (I did not get bug 1815787). So there is some problem with my
hardware. For which component do you think I should create a bug?

/Andreas


> --
> Chris Murphy
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-22 Thread Chris Murphy 
On Sat, Mar 21, 2020 at 6:46 AM Andreas Tunek  wrote:
>
> I sidegraded my rawhide install to F32 a couple of weeks ago and from the 
> start I noticed that booting F32 was really slow. I assumed this was some 
> kind of bug or some devel stuff and would get solved.
>
> However, I still have the problem and I wonder if this a problem unique to my 
> hardware or a general bug when you move from rawhide to a version. If it is a 
> bug, does anyone know if there is a "slow boot on F32" bug somewhere?
>
> Here is my "systemd-analyse blame" output:
>
>   2min 266ms systemd-udev-settle.service
> 1min 10.312s lvm2-monitor.service
>  1min 6.118s lvm2-pvscan@8:3.service
>  30.125s NetworkManager-wait-online.service

These are excessive values. systemd-udev-settle is deprecated for a
couple of years and nothing should be using it by now.

You should check /etc/fstab for stale LVM LV's or fs UUIDs that no
longer exist on this system. The delays are consistent with something
missing. You can also get more information looking at;
# journalctl -b -o short-monotonic

And checking for large gaps in time, what was recently started right
before that gap, or right after it if there are any timeouts. But as
it is, there's not enough information to know for sure what's going on
other than, yes in fact it's taking an excessive amount of time to
start up. And I think it is a local problem because I'm not seeing it
on three systems with clean installs, and dozens of VM's, so at the
least it's not a consistent problem.


-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-22 Thread Andreas Tunek 
Den sön 22 mars 2020 kl 03:26 skrev Tony Nelson <
tonynel...@georgeanelson.com>:

> On 20-03-21 08:45:09, Andreas Tunek wrote:
> > I sidegraded my rawhide install to F32 a couple of weeks ago and from
> > the
> > start I noticed that booting F32 was really slow. I assumed this was
> > some
> > kind of bug or some devel stuff and would get solved.
> >
> > However, I still have the problem and I wonder if this a problem
> > unique to
> > my hardware or a general bug when you move from rawhide to a version.
> > If it
> > is a bug, does anyone know if there is a "slow boot on F32" bug
> > somewhere?
> >
> > Here is my "systemd-analyse blame" output:
>   ...
>
> I think your system is using the graphical boot.  Try the text boot, by
> removing "rhgb" and "quiet" from the kernel command line during boot
> (you may need to set a non-zero grub timeout once booted and try again).
> I expect you will see some "a start job is running" text animations.
> The longest one is probably your problem.
>
>
How would that differ from the systemd-analyse output?

/Andreas

-- 
> 
> TonyN.:'   
>'  
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-21 Thread Samuel Sieb 

On 3/21/20 7:25 PM, Tony Nelson wrote:

On 20-03-21 08:45:09, Andreas Tunek wrote:

I sidegraded my rawhide install to F32 a couple of weeks ago and from the
start I noticed that booting F32 was really slow. I assumed this was some
kind of bug or some devel stuff and would get solved.

However, I still have the problem and I wonder if this a problem 
unique to
my hardware or a general bug when you move from rawhide to a version. 
If it
is a bug, does anyone know if there is a "slow boot on F32" bug 
somewhere?


Here is my "systemd-analyse blame" output:

  ...

I think your system is using the graphical boot.  Try the text boot, by
removing "rhgb" and "quiet" from the kernel command line during boot
(you may need to set a non-zero grub timeout once booted and try again).
I expect you will see some "a start job is running" text animations.
The longest one is probably your problem.


You just need to press the ESC key to see those, no need to edit the 
grub entry.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-21 Thread Tony Nelson 

On 20-03-21 08:45:09, Andreas Tunek wrote:
I sidegraded my rawhide install to F32 a couple of weeks ago and from  
the
start I noticed that booting F32 was really slow. I assumed this was  
some

kind of bug or some devel stuff and would get solved.

However, I still have the problem and I wonder if this a problem  
unique to
my hardware or a general bug when you move from rawhide to a version.  
If it
is a bug, does anyone know if there is a "slow boot on F32" bug  
somewhere?


Here is my "systemd-analyse blame" output:

 ...

I think your system is using the graphical boot.  Try the text boot, by
removing "rhgb" and "quiet" from the kernel command line during boot
(you may need to set a non-zero grub timeout once booted and try again).
I expect you will see some "a start job is running" text animations.
The longest one is probably your problem.

--

TonyN.:'   
  '  
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-21 Thread Andreas Tunek 
Den lör 21 mars 2020 kl 15:24 skrev Stephen John Smoogen :

>
>
> On Sat, Mar 21, 2020 at 08:46 Andreas Tunek 
> wrote:
>
>> I sidegraded my rawhide install to F32 a couple of weeks ago and from the
>> start I noticed that booting F32 was really slow. I assumed this was some
>> kind of bug or some devel stuff and would get solved.
>>
>> However, I still have the problem and I wonder if this a problem unique
>> to my hardware or a general bug when you move from rawhide to a version. If
>> it is a bug, does anyone know if there is a "slow boot on F32" bug
>> somewhere?
>>
>> Here is my "systemd-analyse blame" output:
>>
>>   2min 266ms systemd-udev-settle.service
>>
>> 1min 10.312s lvm2-monitor.service
>>
>>  1min 6.118s lvm2-pvscan@8:3.service
>>
>
> The above sounds like hardware problems trying to find disk drives. I
> would look at dmesg and similar things for when this is happening to see
> why the system is either not finding drives or searching for other ones
> that don’t exist?
>
>
>>
Maybe, but I never had that problem on earlier versions of Fedora (or
rawhide). So something must have changed in F32, but I have no idea what
that could be. I'll make a bug report, but I found other problems in F32 (
https://bugzilla.redhat.com/show_bug.cgi?id=1815787).

Best regards
/Andreas

___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Slow boot on F32 Workstation

2020-03-21 Thread Stephen John Smoogen 
On Sat, Mar 21, 2020 at 08:46 Andreas Tunek  wrote:

> I sidegraded my rawhide install to F32 a couple of weeks ago and from the
> start I noticed that booting F32 was really slow. I assumed this was some
> kind of bug or some devel stuff and would get solved.
>
> However, I still have the problem and I wonder if this a problem unique to
> my hardware or a general bug when you move from rawhide to a version. If it
> is a bug, does anyone know if there is a "slow boot on F32" bug somewhere?
>
> Here is my "systemd-analyse blame" output:
>
>   2min 266ms systemd-udev-settle.service
>
> 1min 10.312s lvm2-monitor.service
>
>  1min 6.118s lvm2-pvscan@8:3.service
>

The above sounds like hardware problems trying to find disk drives. I would
look at dmesg and similar things for when this is happening to see why the
system is either not finding drives or searching for other ones that don’t
exist?


>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org