Hi Steve,
awesome, couldn't wait to test it, so I built udpkg 1.20 from salsa and
integrated in latest debian-installer built to have a mini.iso to play
with.
I tried that iso 5-6 times on each of the 2 physical Power machines on
which I encountered the bug and it worked every single time.
From
On Thu, Jun 10, 2021 at 12:11:05AM +0100, Steve McIntyre wrote:
>
>Looking at the history in this bug, things are not working as we hoped
>when we added the multi-console support. When I initially worked with
>Wookey on this, we didn't see errors like this at all in
>testing. That's not to say
Argh...
Minor thing: James, please don't top-post on Debian lists. It breaks
conversation threads, particularly when others are doing inline
quoting.
On Sun, Jun 06, 2021 at 10:08:09PM +0100, James Addison wrote:
>Thanks Cyril, Frédéric - it feels like we're reaching a consensus that
>udpkg may
Thanks Cyril, Frédéric - it feels like we're reaching a consensus that
udpkg may not be multi-process safe (although, strictly speaking, I
would say we haven't proven that yet).
The authors of multi-console support could be the best people to
recommend a path forward, as they may have close
Hi Cyril/all,
sorry that the process takes long, but that was the only way to
reproduce that bug (which I think may not be specific to ppc64el)
without having Power hardware (and a LPAR/HMC setup).
> Looking at that log, one sees two PIDs for main-menu (272 and 278),
> which could explain a very
Hi James,
[cc-ing submitter back, and youpi for the final comment]
James Addison (2021-05-28):
> Does d-i tend to use udpkg for bootstrapping?
>
> If so, I think
> https://salsa.debian.org/installer-team/udpkg/-/blob/master/status.c#L390
> could be a potential section of code to investigate
Hi Frédéric,
Frédéric Bonnard (2021-05-28):
> Actually you need to "wget" the vmlinux and initrd.gz files inside the
> emulated system, in the same place where you'll kexec. So just re-run
> your wget commands from the petitboot shell and you
> should be good :)
I think that was just an
Does d-i tend to use udpkg for bootstrapping?
If so, I think
https://salsa.debian.org/installer-team/udpkg/-/blob/master/status.c#L390
could be a potential section of code to investigate further.
It doesn't look like full-fat dpkg performs these kind of renames on
the status file.
This might also be the same issue as reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944125
(some kind of race condition where multiple consoles are available and
entered into the inittab, and a /var/lib/dpkg/status.bak is found
instead of the expected status file)
On Fri, 28 May 2021 14:39:56 +0200, Cyril Brulebois wrote:
> Hi Frédéric,
>
> Frédéric Bonnard (2021-05-25):
> > Get that one too :
> > https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/skiboot.lid
> >
> > and give it
Hi Frédéric,
Frédéric Bonnard (2021-05-25):
> Get that one too :
> https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/skiboot.lid
>
> and give it to qemu-system-ppc64 by adding "-bios skiboot.lid" to the qemu
> line (got
Hey Cyril,
thanks for trying!
Get that one too :
https://openpower.xyz/job/openpower/job/openpower-op-build/label=slave,target=witherspoon/lastSuccessfulBuild/artifact/images/skiboot.lid
and give it to qemu-system-ppc64 by adding "-bios skiboot.lid" to the qemu
line (got the same issue. Last
Hi Frédéric,
Frédéric Bonnard (2021-04-26):
> Thanks for willing to investigate !
Thanks for the detailed steps!
> LPAR setup in PowerVM can not be reproduced to my knowledge with qemu;
> this a partitioning configuration with PHYP proprietary firmware by
> IBM. Using a ppc64el vm, I never
Vagrant Cascadian, le dim. 02 mai 2021 14:36:46 -0700, a ecrit:
> On 2021-04-22, Frédéric Bonnard wrote:
> > Machine: Power10 machine but got it on Power8 as well
>
> > This happens randomly when the installer menu starts, I get to the first
> > menu "Choose language", but it is red saying "An
On 2021-04-22, Frédéric Bonnard wrote:
> Machine: Power10 machine but got it on Power8 as well
> This happens randomly when the installer menu starts, I get to the first
> menu "Choose language", but it is red saying "An installation failed...
> The failing step is: Choose language".
FWIW, I've
Hi Cyril,
Thanks for willing to investigate !
LPAR setup in PowerVM can not be reproduced to my knowledge with qemu ; this a
partitioning configuration with PHYP proprietary firmware by IBM.
Using a ppc64el vm, I never had the issue, since I think, hvc0 does not
exist and thus does not create
Hello Frédéric,
Frédéric Bonnard (2021-04-22):
> Boot method: CD
> Image version:
> http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso
> Date: April 21st 2021
>
> Machine: Power10 machine but got it on Power8 as well
>
> This happens randomly when the installer menu starts, I
Package: installation-reports
Boot method: CD
Image version: http://d-i.debian.org/daily-images/ppc64el/daily/netboot/mini.iso
Date: April 21st 2021
Machine: Power10 machine but got it on Power8 as well
This happens randomly when the installer menu starts, I get to the first
menu "Choose
18 matches
Mail list logo
