Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #78569 > unrolled thread

Bug#1033058: Booting mini.iso : kernel hangs on ppc64el

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Cyril Brulebois <kibi@debian.org> - 2023-03-21 17:50 +0100
    Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Frédéric Bonnard <frediz@debian.org> - 2023-03-22 12:30 +0100
      Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Cyril Brulebois <kibi@debian.org> - 2023-03-22 23:20 +0100
        Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Frédéric Bonnard <frediz@debian.org> - 2023-03-23 11:30 +0100
          Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Cyril Brulebois <kibi@debian.org> - 2023-04-12 10:50 +0200
            Processed: Re: Bug#1033058: Booting mini.iso : kernel hangs on  ppc64el "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-04-12 10:50 +0200
            Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Cyril Brulebois <kibi@debian.org> - 2023-04-12 12:20 +0200
            Bug#1033058: Booting mini.iso : kernel hangs on ppc64el Frédéric Bonnard <frediz@debian.org> - 2023-04-12 13:10 +0200

#78569 — Bug#1033058: Booting mini.iso : kernel hangs on ppc64el

[Multipart message — attachments visible in raw view] — view raw

Frédéric Bonnard <frediz@debian.org> (2023-03-17):
> > It would be helpful to confirm which exact kernel version is getting
> > used in both cases (last 6.1.0-4 working, and first 6.1.0-5 not
> > working), then look at the changes between both versions, in src:linux
> > (and resulting udebs).
> 
> From linux changelog (
> https://tracker.debian.org/media/packages/l/linux/changelog-6.1.15-1 )
> and http://snapshot.debian.org/package/linux/,
> I see :
> 6.1.11-1 -> Bump ABI to 4 http://snapshot.debian.org/archive/debian/20230211T151657Z/
> 6.1.12-1 -> Bump ABI to 5 http://snapshot.debian.org/archive/debian/20230217T033139Z/
> 
> and tested from those (rebuilding the same d-i source with the 2 kernels
> from snapshot.d.o . 6.1.12-1 clearly doesn't work.
> I had already have a look at the kernel changelog but missed that one :
> ---
> linux (6.1.12-1) unstable; urgency=medium
> ...
>     - of: Make OF framebuffer device names unique
> ...
> ---
> 
> I recompiled the kernel deb source without that one (
> https://github.com/torvalds/linux/commit/241d2fb56a18473af5f2ff0d512992a996eb64dd.patch
> ) and the mini.iso actually made it to the menu... and given the
> behaviour, a framebuffer actually makes sense.
> 
> Now, that patch does not harm when the kernel is installed on disk.
> But it does in the installer...

Adding the kernel team to the loop: d-i regression on ppc64el.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [next] | [standalone]

#78577

[Multipart message — attachments visible in raw view] — view raw

Thanks Cyril.
Another important detail ... I only get that behavior in qemu in
graphical mode.
On LPARs there is no issue. I didn't try on baremetal so far.

F.

On Tue, 21 Mar 2023 17:44:49 +0100 Cyril Brulebois <kibi@debian.org> wrote:
> Frédéric Bonnard <frediz@debian.org> (2023-03-17):
> > > It would be helpful to confirm which exact kernel version is getting
> > > used in both cases (last 6.1.0-4 working, and first 6.1.0-5 not
> > > working), then look at the changes between both versions, in src:linux
> > > (and resulting udebs).
> > 
> > From linux changelog (
> > https://tracker.debian.org/media/packages/l/linux/changelog-6.1.15-1 )
> > and http://snapshot.debian.org/package/linux/,
> > I see :
> > 6.1.11-1 -> Bump ABI to 4 http://snapshot.debian.org/archive/debian/20230211T151657Z/
> > 6.1.12-1 -> Bump ABI to 5 http://snapshot.debian.org/archive/debian/20230217T033139Z/
> > 
> > and tested from those (rebuilding the same d-i source with the 2 kernels
> > from snapshot.d.o . 6.1.12-1 clearly doesn't work.
> > I had already have a look at the kernel changelog but missed that one :
> > ---
> > linux (6.1.12-1) unstable; urgency=medium
> > ...
> >     - of: Make OF framebuffer device names unique
> > ...
> > ---
> > 
> > I recompiled the kernel deb source without that one (
> > https://github.com/torvalds/linux/commit/241d2fb56a18473af5f2ff0d512992a996eb64dd.patch
> > ) and the mini.iso actually made it to the menu... and given the
> > behaviour, a framebuffer actually makes sense.
> > 
> > Now, that patch does not harm when the kernel is installed on disk.
> > But it does in the installer...
> 
> Adding the kernel team to the loop: d-i regression on ppc64el.
> 
> 
> Cheers,
> -- 
> Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]

#78583

[Multipart message — attachments visible in raw view] — view raw

Hi Frédéric,

Frédéric Bonnard <frediz@debian.org> (2023-03-22):
> Another important detail ... I only get that behavior in qemu in
> graphical mode. On LPARs there is no issue. I didn't try on baremetal
> so far.

Could you please guide me into reproducing this issue in QEMU? #987368
had hints, but at least the openpower.xyz part no longer works (it's no
longer resolving).


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]

#78584

[Multipart message — attachments visible in raw view] — view raw

Hi Cyril!

> Could you please guide me into reproducing this issue in QEMU? #987368
> had hints, but at least the openpower.xyz part no longer works (it's no
> longer resolving).

much simpler actually because in the current case, we won't emulate a
full baremetal PowerNV machine.
For example, using this mini.iso from http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso
you can just try those 2 cases  (from an x86 machine or other) :

---
$ qemu-system-ppc64le -nographic -nodefaults -serial mon:stdio -cdrom /tmp/mini.iso
---
here we just start a ppc64le vm with no graphic card, and boot the iso.
You should reach the debian installer menu on the serial console in your
terminal (if you want to go further, provide a disk file for example).

But if you try a vm with a graphic card like so :
---
qemu-system-ppc64le  -cdrom /tmp/mini.iso
---

You'll see you won't have the d-i menu displayed on the default
graphical output.
Not sure the pointed patch is at fault, but at least it emphasis some
issue in the installer environment in the context of a framebuffer
display in qemu.
I see the installer media gets build from a kernel-image udeb which I
guess provides a different kernel runtime env from the machine installed
with linux-image on disk (which works).


F.

[toc] | [prev] | [next] | [standalone]

#78743

[Multipart message — attachments visible in raw view] — view raw

Control: forwarded -1 https://salsa.debian.org/kernel-team/linux/-/merge_requests/695
Control: reassign -1 src:linux 6.1.12-1
Control: severity -1 important
Control: tag -1 patch

Hello Frédéric,

Frédéric Bonnard <frediz@debian.org> (2023-03-23):
> ---
> $ qemu-system-ppc64le -nographic -nodefaults -serial mon:stdio -cdrom /tmp/mini.iso
> ---
> here we just start a ppc64le vm with no graphic card, and boot the iso.
> You should reach the debian installer menu on the serial console in your
> terminal (if you want to go further, provide a disk file for example).
> 
> But if you try a vm with a graphic card like so :
> ---
> qemu-system-ppc64le  -cdrom /tmp/mini.iso
> ---

ACK on both, thanks! That was indeed super easy and super useful.

> I see the installer media gets build from a kernel-image udeb which I
> guess provides a different kernel runtime env from the machine installed
> with linux-image on disk (which works).

It's slightly more complicated than that, as both vmlinuz are actually
identical:

    $ dpkg -x kernel-image-6.1.0-7-powerpc64le-di_6.1.20-2_ppc64el.udeb foo
    $ dpkg -x linux-image-6.1.0-7-powerpc64le_6.1.20-2_ppc64el.deb bar
    $ cmp foo/boot/vmlinux bar/boot/vmlinux-6.1.0-7-powerpc64le; echo $?
    0

That being said, we don't have all modules shipped in the installer, and
some other module might be available and used in the installed system
(e.g. dedicated driver as opposed to fbdev during a graphical install on
amd64), which can explain differences. The bootloader configuration
might be different too.


As you suggested, this is a regression via a7f0ec26cd, first shipped in
v6.1.12, which didn't account for the disappearing of-display device
node in the framebuffer driver. I've tested a trivial patch (see MR)
and a netboot mini.iso d-i build (similar to daily builds, against udebs
from unstable) gives me the installer's interface. Available for 15 days
at: https://people.debian.org/~kibi/bug-1033058/

I'll open a bug report upstream and submit my patch there. In mainline
master, another module (not found in 6.1.y) is affected as well, so I
have this queued up too (but untested):

     drivers/gpu/drm/tiny/ofdrm.c | 2 +-
     1 file changed, 1 insertion(+), 1 deletion(-)

in addition to:

     drivers/video/fbdev/offb.c | 2 +-
     1 file changed, 1 insertion(+), 1 deletion(-)


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]

#78744 — Processed: Re: Bug#1033058: Booting mini.iso : kernel hangs on ppc64el

Processing control commands:

> forwarded -1 https://salsa.debian.org/kernel-team/linux/-/merge_requests/695
Bug #1033058 [installation-reports] Booting mini.iso : kernel hangs on ppc64el
Set Bug forwarded-to-address to 'https://salsa.debian.org/kernel-team/linux/-/merge_requests/695'.
> reassign -1 src:linux 6.1.12-1
Bug #1033058 [installation-reports] Booting mini.iso : kernel hangs on ppc64el
Bug reassigned from package 'installation-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #1033058 to the same values previously set
Ignoring request to alter fixed versions of bug #1033058 to the same values previously set
Bug #1033058 [src:linux] Booting mini.iso : kernel hangs on ppc64el
Marked as found in versions linux/6.1.12-1.
> severity -1 important
Bug #1033058 [src:linux] Booting mini.iso : kernel hangs on ppc64el
Severity set to 'important' from 'normal'
> tag -1 patch
Bug #1033058 [src:linux] Booting mini.iso : kernel hangs on ppc64el
Added tag(s) patch.

-- 
1033058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#78745

[Multipart message — attachments visible in raw view] — view raw

Cyril Brulebois <kibi@debian.org> (2023-04-12):
> I'll open a bug report upstream and submit my patch there.

Upstream bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=217328

> In mainline master, another module (not found in 6.1.y) is affected as well,
> so I have this queued up too (but untested):
> 
>      drivers/gpu/drm/tiny/ofdrm.c | 2 +-
>      1 file changed, 1 insertion(+), 1 deletion(-)

If you have a way to confirm ofdrm is broken without the patch and fixed
with the patch, please speak up!

Upstream patches:
  https://lore.kernel.org/all/20230412095509.2196162-1-cyril@debamax.com/T/#u


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]

#78748

[Multipart message — attachments visible in raw view] — view raw

Thank you so much Cyril!

> That being said, we don't have all modules shipped in the installer, and
> some other module might be available and used in the installed system
> (e.g. dedicated driver as opposed to fbdev during a graphical install on
> amd64), which can explain differences. The bootloader configuration
> might be different too.
> 
> As you suggested, this is a regression via a7f0ec26cd, first shipped in
> v6.1.12, which didn't account for the disappearing of-display device
> node in the framebuffer driver. I've tested a trivial patch (see MR)
> and a netboot mini.iso d-i build (similar to daily builds, against udebs
> from unstable) gives me the installer's interface. Available for 15 days
> at: https://people.debian.org/~kibi/bug-1033058/
> 
> I'll open a bug report upstream and submit my patch there. In mainline
> master, another module (not found in 6.1.y) is affected as well, so I
> have this queued up too (but untested):

Excellent!
I was worried seeing the issue coming in rc1 of Bookworm
but also in latest snapshots of Ubuntu 23.04 ( I also
pointed Canonical to this bug and your proposed fix :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994 ).

F.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web