kernel-5.5.0-1.fc32.x86_64 DOA?

[Chris Murphy]

Hi,
Two baremetal systems and one VM hang with kernel-5.5.0-1.fc32.x86_64
right after GRUB menu entry selection/timeout for this kernel. Black
screen, menu goes away, I see a white underscore, that's it. Doesn't
recover.

I put GRUB into debug mode and I can see the kernel file being loaded
block by block off the media, but oh man something is off with GRUB
because the text scroll is unbearably slow. So I just had to kill it.

Last working for me is kernel-5.5.0-0.rc6.git1.1.fc32.x86_64.

-- 
Chris Murphy

[Justin Forbes]

On Tue, Jan 28, 2020 at 12:35 AM Chris Murphy <lists(a)colorremedies.com&gt; wrote:
>  Hi,
>  Two baremetal systems and one VM hang with kernel-5.5.0-1.fc32.x86_64
>  right after GRUB menu entry selection/timeout for this kernel. Black
>  screen, menu goes away, I see a white underscore, that's it. Doesn't
>  recover.
>
>  I put GRUB into debug mode and I can see the kernel file being loaded
>  block by block off the media, but oh man something is off with GRUB
>  because the text scroll is unbearably slow. So I just had to kill it.
>
>  Last working for me is kernel-5.5.0-0.rc6.git1.1.fc32.x86_64.
>  
Yes, this seems to be entirely an issue of gcc10 produced kernels.
Rebuilding it against F31 boots just fine.  Still trying to figure out
what the issue is.

Justin

[Bruno Wolff III]

On Tue, Jan 28, 2020 at 10:00:39 -0600,
  Justin Forbes <jmforbes(a)linuxtx.org&gt; wrote:
> On Tue, Jan 28, 2020 at 12:35 AM Chris Murphy
> <lists(a)colorremedies.com&gt; wrote:
> >
> > Hi,
> > Two baremetal systems and one VM hang with kernel-5.5.0-1.fc32.x86_64
> > right after GRUB menu entry selection/timeout for this kernel. Black
> > screen, menu goes away, I see a white underscore, that's it. Doesn't
> > recover.
> >
> > I put GRUB into debug mode and I can see the kernel file being loaded
> > block by block off the media, but oh man something is off with GRUB
> > because the text scroll is unbearably slow. So I just had to kill it.
> >
> > Last working for me is kernel-5.5.0-0.rc6.git1.1.fc32.x86_64.
> >
> Yes, this seems to be entirely an issue of gcc10 produced kernels.
> Rebuilding it against F31 boots just fine.  Still trying to figure out
> what the issue is. 
5.6.0-0.rc0.git2.1.fc32.x86_64 is working for me.

[Jeremy Cline]

On Tue, 2020-02-04 at 15:10 -0600, Bruno Wolff III wrote:
>  On Tue, Jan 28, 2020 at 10:00:39 -0600,
>    Justin Forbes <jmforbes(a)linuxtx.org&gt; wrote:
>  > On Tue, Jan 28, 2020 at 12:35 AM Chris Murphy <
>  > lists(a)colorremedies.com&gt; wrote:
>  > > Hi,
>  > > Two baremetal systems and one VM hang with kernel-5.5.0-
>  > > 1.fc32.x86_64
>  > > right after GRUB menu entry selection/timeout for this kernel.
>  > > Black
>  > > screen, menu goes away, I see a white underscore, that's it.
>  > > Doesn't
>  > > recover.
>  > > 
>  > > I put GRUB into debug mode and I can see the kernel file being
>  > > loaded
>  > > block by block off the media, but oh man something is off with
>  > > GRUB
>  > > because the text scroll is unbearably slow. So I just had to kill
>  > > it.
>  > > 
>  > > Last working for me is kernel-5.5.0-0.rc6.git1.1.fc32.x86_64.
>  > > 
>  > Yes, this seems to be entirely an issue of gcc10 produced kernels.
>  > Rebuilding it against F31 boots just fine.  Still trying to figure
>  > out
>  > what the issue is.
>  
>  5.6.0-0.rc0.git2.1.fc32.x86_64 is working for me. 
The issue is https://bugzilla.redhat.com/show_bug.cgi?id=1796780. I've
temporarily disabled CONFIG_STACKPROTECTOR_STRONG on x86. Once I
resolve the final build issues with armv7hl there should be a bootable
Rawhide kernel again.

- Jeremy

[Bruno Wolff III]

On Tue, Feb 04, 2020 at 21:38:38 +0000,
  Jeremy Cline <jeremy(a)jcline.org&gt; wrote:
> The issue is https://bugzilla.redhat.com/show_bug.cgi?id=1796780. I've
> temporarily disabled CONFIG_STACKPROTECTOR_STRONG on x86. Once I
> resolve the final build issues with armv7hl there should be a bootable
> Rawhide kernel again. 
I grabbed the rpms from the koji build before it finished. The x86_64 rpms 
are often available well before the build finishes. I wanted to try it 
on my work desktop before heading home.