qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH qemu] spapr: Force 32bit when resetting a core


From: Mark Cave-Ayland
Subject: Re: [PATCH qemu] spapr: Force 32bit when resetting a core
Date: Tue, 18 Jan 2022 08:30:05 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0

On 17/01/2022 14:52, Cédric Le Goater wrote:

Initially, I installed a debian11 ppc64 on a QEMU mac99/970 machine.
Something went wrong with the bootloader at installation and I was
stuck with memory boot. I didn't manage to restore a decent boot
setup even after that.

Interesting. I had a similar issue using the debian ports images on mac99/ppc32: everything went well all up until the bootloader installation which failed. When I looked at the installer logs IIRC there was a kernel panic somewhere in the hfs module which I figured is likely an emulation bug somewhere.

I stole the HFS partition from a real G5 and after some manual tweaks
on the disk, I got it working.

There are a few harmless errors :
     >> =============================================================
     >> OpenBIOS 1.1 [Jan 15 2022 14:23]
     >> Configuration device id QEMU version 1 machine id 3
     >> CPUs: 1
     >> Memory: 1024M
     >> UUID: 00000000-0000-0000-0000-000000000000
     >> CPU type PowerPC,970
     milliseconds isn't unique.
     Welcome to OpenBIOS v1.1 built on Jan 15 2022 14:23
     Trying hd:,\\:tbxi...
     >> switching to new context:
     call-method color!: exception -21
     >> call-method color! failed with error ffffffdf
     call-method color!: exception -21
     ...
     call-method block-size: exception -21
     >> call-method block-size failed with error ffffffdf
     call-method block-size: exception -21
     >> call-method block-size failed with error ffffffdf

I guess the initial problem is in the debian installer. I will report.

I can certainly help out if you get stuck. If this is a more obscure combination then is it worth adding a tiny image for use with avocado?

No. It is really a standard setup :

     root@vm02:~# mac-fdisk -l /dev/sda
     /dev/sda
            #                    type name                length   base    ( size ) system     /dev/sda1     Apple_partition_map Apple                   63 @ 1       ( 31.5k) Partition map     /dev/sda2               Apple_HFS bootstrap           500001 @ 64      (244.1M) HFS     /dev/sda3         Apple_UNIX_SVR2 untitled           39634766 @ 500065  ( 18.9G)  Linux native     /dev/sda4         Apple_UNIX_SVR2 swap               1808208 @ 40134831 (882.9M)  Linux swap     /dev/sda5              Apple_Free Extra                    1 @ 41943039 ( 0.5k)  Free space
     Block size=512, Number of Blocks=41943040
     DeviceType=0x0, DeviceId=0x0
     root@vm02:~# cat /proc/cpuinfo
     processor    : 0
     cpu        : PPC970, altivec supported
     clock        : 900.000000MHz
     revision    : 2.2 (pvr 0039 0202)
     timebase    : 100000000
     platform    : PowerMac
     model        : PowerMac3,1
     machine        : PowerMac3,1
     motherboard    : PowerMac3,1 MacRISC MacRISC2 Power Macintosh
     detected as    : 0 ((null))
     pmac flags    : 00000000
     pmac-generation    : NewWorld
     root@vm02:~# uname -a
     Linux vm02 5.15.0-2-powerpc64 #1 SMP Debian 5.15.5-2 (2021-12-18) ppc64 
GNU/Linux

Fantastic! Glad everything is all working for you :)


ATB,

Mark.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]