Blue Swirl | 4 Jun 2011 10:20
Picon

Re: [PATCH 1/3] Introduce PRI*CELL macros

On Sat, May 28, 2011 at 2:37 PM, Andreas Färber <andreas.faerber <at> web.de> wrote:
> As done for prom_arg_t, introduce POSIX-like PRI* macros for [u]cell.

Looks OK.

> Signed-off-by: Andreas Färber <andreas.faerber <at> web.de>
> ---
>  include/arch/amd64/types.h   |    6 +++++-
>  include/arch/ia64/types.h    |    5 +++++
>  include/arch/ppc/types.h     |   12 ++++++++----
>  include/arch/sparc32/types.h |   12 ++++++++----
>  include/arch/sparc64/types.h |   12 ++++++++----
>  include/arch/x86/types.h     |   12 ++++++++----
>  6 files changed, 42 insertions(+), 17 deletions(-)
>
> diff --git a/include/arch/amd64/types.h b/include/arch/amd64/types.h
> index 83fd3e1..74503b9 100644
> --- a/include/arch/amd64/types.h
> +++ b/include/arch/amd64/types.h
>  <at>  <at>  -29,7 +29,11  <at>  <at>  typedef uint64_t    ucell;
>  typedef __int128_t  dcell;
>  typedef __uint128_t ducell;
>
> -#define FMT_ucellx  "%016" PRIx64
> +#define PRIdCELL PRId64
> +#define PRIuCELL PRIu64
> +#define PRIxCELL PRIx64
> +#define PRIXCELL PRIX64
> +#define FMT_ucellx  "%016" PRIxCELL
>
(Continue reading)

Nathan Kunkee | 6 Jun 2011 05:13
Picon
Favicon

Re: SS-10 and SS-20


  On 05/26/11 01:58 PM, Blue Swirl wrote:
> On Wed, May 25, 2011 at 12:25 AM, Brian
Vandenberg<phantall@...>  wrote:
>>   I'm curious whether support exists for sparcstation's 10&  20 yet.
>> Any comments?
> OpenBIOS can be used as the BIOS for QEMU and for this combination,
> SS-10 and SS-20 work pretty well.
>
> If instead you'd like to use OpenBIOS as a replacement for the OBP,
> then this is not supported. It would be possible to replace QEMU
> specific parts (for example fw_cfg) with bare metal versions, but so
> far nobody has been interested enough to start hacking. Being able to
> run on real HW would certainly improve the level of realism, for
> example SBus probing is not implemented.
>
Am I missing something, or do the QEMU SS-10 and SS-20 not have the 
CS4231 wired up as a serial console?

Nathan

Nathan Kunkee | 6 Jun 2011 05:37
Picon
Favicon

Re: Solaris anyone?


  On 05/13/11 05:10 PM, Artyom Tarasenko wrote:
> On Fri, May 13, 2011 at 9:14 AM, Mark Cave-Ayland
> <mark.cave-ayland@...>  wrote:
>> On 11/05/11 19:48, Artyom Tarasenko wrote:
>>
>>> Can you tell what Solaris 9 version did you use (CD/DVD and the patch
>>> level in the greeting message) and what is your host?
>>> I tried a Solaris 9 DVD on a Linux x86_64 host, but it hangs after the
>>> serial ports initialization.
>> Just a total stab in the dark but does the following OpenBIOS image solve
>> the issue with Solaris 9 at all?
>>
>> http://www.siriusit.co.uk/tmp/openbios-sparc32.artyom
> No difference, sorry. After talking to Nick it looks like
>
> - the very first Solaris 9 release (Generic) can be installed
> - the last Solaris 9 release (Generic_118558-34) hangs under OpenBIOS.
>
> HTH
> Artyom
>
My Solaris 9 04/04 image seems to hang in the same spot:

Configuration device id QEMU version 1 machine id 32
CPUs: 1 x FMI,MB86904
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.0 built on Apr 30 2011 02:11
   Type 'help' for detailed information
Trying disk...
(Continue reading)

Mark Cave-Ayland | 6 Jun 2011 21:42
Picon

Re: Solaris anyone?

On 06/06/11 04:37, Nathan Kunkee wrote:

> My Solaris 9 04/04 image seems to hang in the same spot:
>
>
> Configuration device id QEMU version 1 machine id 32
> CPUs: 1 x FMI,MB86904
> UUID: 00000000-0000-0000-0000-000000000000
> Welcome to OpenBIOS v1.0 built on Apr 30 2011 02:11
> Type 'help' for detailed information
> Trying disk...
> No valid state has been set by load or init-program
>
> 0 > boot cd:d -k -v -s Not a bootable ELF image
> Loading a.out image...
> Loaded 7680 bytes
> entry point is 0x4000
> bootpath: /iommu/sbus/espdma/esp/sd <at> 2,0:d
>
> Jumping to entry point 00004000 for type 00000005...
> switching to new context:
> Size: 0x45c9f+0xdaf1+0x1d6a7 Bytes
> SunOS Release 5.9 Version Generic_112233-12 32-bit
> Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
> Use is subject to license terms.
> Ethernet address = 52:54:0:12:34:56
> Using default device instance data
> vac: enabled in write through mode
> mem = 131072K (0x8000000)
> avail mem = 108797952
(Continue reading)

Tarl Neustaedter | 6 Jun 2011 21:54

Re: Solaris anyone?

>
>
> Hmmm it looks from reading the source code that QEMU doesn't actually 
> implement a proper audio device for SS-5 at all but merely provides a 
> dummy device with an empty mapped region. In that case it may be 
> possible to provide a simple mapping in OpenBIOS to match the one in 
> QEMU which may be enough to persuade Solaris to boot.

Ugh. I recall that audio chip being non-trivial...

It might be worth deleting that audio device from the device tree and 
see if Solaris really does get further.

Kenneth Salerno | 6 Jun 2011 22:04
Picon
Favicon

Re: Solaris anyone?

Really. Who has a sound card on a sparc server anyway? (I can feel the offended stares of the Sun Blade100 users)


From: Tarl Neustaedter <tarl-b2-72noq5hGnzM@public.gmane.org>;
To: The OpenBIOS Mailinglist <openbios-WyKcznhUmzJg9hUCZPvPmw@public.gmane.org>;
Subject: Re: [OpenBIOS] Solaris anyone?
Sent: Mon, Jun 6, 2011 7:54:39 PM

>
>
> Hmmm it looks from reading the source code that QEMU doesn't actually implement a proper audio device for SS-5 at all but merely provides a dummy device with an empty mapped region. In that case it may be possible to provide a simple mapping in OpenBIOS to match the one in QEMU which may be enough to persuade Solaris to boot.

Ugh. I recall that audio chip being non-trivial...

It might be worth deleting that audio device from the device tree and see if Solaris really does get further.


-- OpenBIOS                http://openbios.org/
Mailinglist:  http://lists.openbios.org/mailman/listinfo
Free your System - May the Forth be with you
<div>
<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top">
<p>Really. Who has a sound card on a sparc server anyway? (I can feel the offended stares of the Sun Blade100 users)</p>
</td></tr></table>
<div>
                <div>
                    <br><div>

                            
                                <span>From:</span>

                            Tarl Neustaedter &lt;tarl-b2@...&gt;;                            <br>
                                <span>To:</span>

                            The OpenBIOS Mailinglist &lt;openbios@...&gt;;                                                                                                     <br>
                                <span>Subject:</span>

                            Re: [OpenBIOS] Solaris anyone?                            <br>
                                <span>Sent:</span>

                            Mon, Jun 6, 2011 7:54:39 PM                            <br>
                            <br><table cellspacing="0" cellpadding="0" border="0"><tr>
<td valign="top">&gt; <br>&gt; <br>&gt; Hmmm it looks from reading the source code that QEMU doesn't actually implement a proper audio device for SS-5 at all but merely provides a dummy device with an empty mapped region. In that case it may be possible to provide a simple mapping in OpenBIOS to match the one in QEMU which may be enough to persuade Solaris to boot.<br><br>Ugh. I recall that audio chip being non-trivial...<br><br>It might be worth deleting that audio device from the device tree and see if Solaris really does get further.<br><br><br>-- OpenBIOS&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  <a href="http://openbios.org/" target="_blank">http://openbios.org/</a><br>Mailinglist:&nbsp; <a href="http://lists.o%0A%20penbios.org/mailman/listinfo" target="_blank">http://lists.openbios.org/mailman/listinfo</a><br>Free your System - May the Forth be with you<br>
</td>
                                    </tr></table>
</div>
                </div>
            </div>
</div>
Mark Cave-Ayland | 6 Jun 2011 23:43
Picon

Re: Solaris anyone?

On 06/06/11 20:42, Mark Cave-Ayland wrote:

> Hmmm it looks from reading the source code that QEMU doesn't actually
> implement a proper audio device for SS-5 at all but merely provides a
> dummy device with an empty mapped region. In that case it may be
> possible to provide a simple mapping in OpenBIOS to match the one in
> QEMU which may be enough to persuade Solaris to boot.

Okay - I've installed a simple memory mapping to a virtual address which 
is not used, and also tweaked the "intr" property which looked wrong 
compared to the sample prtconf output (0x5 instead of 0x39 high cell).

Does the OpenBIOS ROM at 
http://www.siriusit.co.uk/tmp/openbios-sparc32.emptysndmap help get you 
any further with Solaris 9?

ATB,

Mark.

--

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs

Nathan Kunkee | 6 Jun 2011 23:40
Picon
Favicon

Re: Solaris anyone?

> Date: Mon, 6 Jun 2011 15:54:39 -0400
> From: tarl-b2 <at> tarl.net
> To: openbios-WyKcznhUmzJg9hUCZPvPmw@public.gmane.org
> Subject: Re: [OpenBIOS] Solaris anyone?
>
> > Hmmm it looks from reading the source code that QEMU doesn't actually
> > implement a proper audio device for SS-5 at all but merely provides a
> > dummy device with an empty mapped region. In that case it may be
> > possible to provide a simple mapping in OpenBIOS to match the one in
> > QEMU which may be enough to persuade Solaris to boot.
>
> Ugh. I recall that audio chip being non-trivial...
>
> It might be worth deleting that audio device from the device tree and
> see if Solaris really does get further.
>
I've tried the same CD image with the SS-10 QEMU machine, which seems to lack the audio device, and I still hang. I get the first part of the kernel, no extra logging, and then the spinner to infinity...

nathan <at> xanth:/usr/local/build/qemu$ sparc-softmmu/qemu-system-sparc -bios openbios-builtin.elf -M SS-10 -cdrom /local/storage/ISO/solaris-9-sparc-d1.iso -nographic

Configuration device id QEMU version 1 machine id 64
CPUs: 1 x TI,TMS390Z55
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.0 built on Apr 30 2011 02:11
  Type 'help' for detailed information
Trying disk...
No valid state has been set by load or init-program

0 > boot cd:d -k -v Not a bootable ELF image
Loading a.out image...
Loaded 7680 bytes
entry point is 0x4000
bootpath: /iommu/sbus/espdma/esp/sd <at> 2,0:d

Jumping to entry point 00004000 for type 00000005...
switching to new context:
Size: 0x45c9f+0xdaf1+0x1d6a7 Bytes
SunOS Release 5.9 Version Generic_112233-12 32-bit
Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Ethernet address = 52:54:0:12:34:56
Using default device instance data
\


Does anyone know what loads on a real SS after the audio device?

Nathan

<div>
&gt; Date: Mon, 6 Jun 2011 15:54:39 -0400<br>&gt; From: tarl-b2 <at> tarl.net<br>&gt; To: openbios@...<br>&gt; Subject: Re: [OpenBIOS] Solaris anyone?<br>&gt; <br>&gt; &gt; Hmmm it looks from reading the source code that QEMU doesn't actually <br>&gt; &gt; implement a proper audio device for SS-5 at all but merely provides a <br>&gt; &gt; dummy device with an empty mapped region. In that case it may be <br>&gt; &gt; possible to provide a simple mapping in OpenBIOS to match the one in <br>&gt; &gt; QEMU which may be enough to persuade Solaris to boot.<br>&gt; <br>&gt; Ugh. I recall that audio chip being non-trivial...<br>&gt; <br>&gt; It might be worth deleting that audio device from the device tree and <br>&gt; see if Solaris really does get further.<br>&gt; <br>I've tried the same CD image with the SS-10 QEMU machine, which seems to lack the audio device, and I still hang. I get the first part of the kernel, no extra logging, and then the spinner to infinity...<br><br>nathan <at> xanth:/usr/local/build/qemu$ sparc-softmmu/qemu-system-sparc -bios openbios-builtin.elf -M SS-10 -cdrom /local/storage/ISO/solaris-9-sparc-d1.iso -nographic<br><br>Configuration device id QEMU version 1 machine id 64<br>CPUs: 1 x TI,TMS390Z55<br>UUID: 00000000-0000-0000-0000-000000000000<br>Welcome to OpenBIOS v1.0 built on Apr 30 2011 02:11<br>&nbsp; Type 'help' for detailed information<br>Trying disk...<br>No valid state has been set by load or init-program<br><br>0 &gt; boot cd:d -k -v Not a bootable ELF image<br>Loading a.out image...<br>Loaded 7680 bytes<br>entry point is 0x4000<br>bootpath: /iommu/sbus/espdma/esp/sd <at> 2,0:d<br><br>Jumping to entry point 00004000 for type 00000005...<br>switching to new context:<br>Size: 0x45c9f+0xdaf1+0x1d6a7 Bytes<br>SunOS Release 5.9 Version Generic_112233-12 32-bit<br>Copyright 1983-2003 Sun Microsystems, Inc.&nbsp; All rights reserved.<br>Use is subject to license terms.<br>Ethernet address = 52:54:0:12:34:56<br>Using default device instance data<br>\<br><br><br>Does anyone know what loads on a real SS after the audio device?<br><br>Nathan<br><br>
</div>
Nathan Kunkee | 7 Jun 2011 00:04
Picon
Favicon

Re: Solaris anyone?

> Date: Mon, 6 Jun 2011 22:43:23 +0100
> From: mark.cave-ayland-tXRqCrxWXta9FHfhHBbuYA@public.gmane.org
> To: openbios-WyKcznhUmzJg9hUCZPvPmw@public.gmane.org
> CC: nkunkee42-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
> Subject: Re: [OpenBIOS] Solaris anyone?
>
> On 06/06/11 20:42, Mark Cave-Ayland wrote:
>
> > Hmmm it looks from reading the source code that QEMU doesn't actually
> > implement a proper audio device for SS-5 at all but merely provides a
> > dummy device with an empty mapped region. In that case it may be
> > possible to provide a simple mapping in OpenBIOS to match the one in
> > QEMU which may be enough to persuade Solaris to boot.
>
> Okay - I've installed a simple memory mapping to a virtual address which
> is not used, and also tweaked the "intr" property which looked wrong
> compared to the sample prtconf output (0x5 instead of 0x39 high cell).
>
> Does the OpenBIOS ROM at
> http://www.siriusit.co.uk/tmp/openbios-sparc32.emptysndmap help get you
> any further with Solaris 9?
>

It seems to spin one time more, but still hang:


Configuration device id QEMU version 1 machine id 32
CPUs: 1 x FMI,MB86904
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.0 built on Jun 6 2011 21:31
  Type 'help' for detailed information
Trying disk...
No valid state has been set by load or init-program

0 > boot cd:d -k -v Not a bootable ELF image
Loading a.out image...
Loaded 7680 bytes
entry point is 0x4000
bootpath: /iommu/sbus/espdma/esp/sd <at> 2,0:d

Jumping to entry point 00004000 for type 00000005...
switching to new context:
Size: 0x45c9f+0xdaf1+0x1d6a7 Bytes
SunOS Release 5.9 Version Generic_112233-12 32-bit
Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Ethernet address = 52:54:0:12:34:56
Using default device instance data
vac: enabled in write through mode
mem = 262144K (0x10000000)
avail mem = 240328704
root nexus = SUNW,SPARCstation-5
iommu0 at root: obio 0x10000000
sbus0 at iommu0: obio 0x10001000
dma0 at sbus0: SBus slot 5 0x8400000
dma0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000
/iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000 (esp0):
        esp-options=0x46
esp0 at dma0: SBus slot 5 0x8800000 sparc ipl 4
esp0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000
sd2 at esp0: target 2 lun 0
sd2 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000/sd <at> 2,0
root on /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000/sd <at> 2,0:b fstype ufs
obio0 at root
obio0 at obio0: obio 0x100000, sparc ipl 12
zs0 is /obio/zs <at> 0,100000
obio1 at obio0: obio 0x0, sparc ipl 12
zs1 is /obio/zs <at> 0,0
cpu0: FMI,MB86904 (mid 0 impl 0x0 ver 0x5 clock 170 MHz)
Configuring /dev and /devices
pseudo-device: devinfo0
devinfo0 is /pseudo/devinfo <at> 0
tcx0 at sbus0: SBus slot 3 0x800000 and SBus slot 3 0x2000000 and SBus slot 3 0x4000000 and SBus slot 3 0x6000000 and SBus slot 3 0xa000000 and SBus slot 3 0xc000000 and SBus slot 3 0xe000000 and SBus slot 3 0x700000 and SBus slot 3 0x200000 and SBus slot 3 0x300000 and SBus slot 3 0x0 and SBus slot 3 0x240000 and SBus slot 3 0x280000 SBus level 5 sparc ipl 9
tcx0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,tcx <at> 3,800000
tcx0: revision 0, screen 1024x768
ledma0 at sbus0: SBus slot 5 0x8400010
le0 at ledma0: SBus slot 5 0x8c00000 sparc ipl 6
le0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/ledma <at> 5,8400010/le <at> 5,8c00000
pseudo-device: fssnap0
fssnap0 is /pseudo/fssnap <at> 0
sbusmem0 at sbus0: SBus slot 0 0x0
sbusmem0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 0,0
sbusmem1 at sbus0: SBus slot 1 0x0
sbusmem1 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 1,0
sbusmem2 at sbus0: SBus slot 2 0x0
sbusmem2 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 2,0
sbusmem3 at sbus0: SBus slot 3 0x0
sbusmem3 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 3,0
sbusmem4 at sbus0: SBus slot 4 0x0
sbusmem4 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 4,0
sbusmem5 at sbus0: SBus slot 5 0x0
sbusmem5 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 5,0
pseudo-device: ramdisk1024
ramdisk1024 is /pseudo/ramdisk <at> 1024
pseudo-device: winlock0
winlock0 is /pseudo/winlock <at> 0
pseudo-device: lockstat0
lockstat0 is /pseudo/lockstat <at> 0
pseudo-device: llc10
llc10 is /pseudo/llc1 <at> 0
pseudo-device: lofi0
lofi0 is /pseudo/lofi <at> 0
pseudo-device: fcp0
fcp0 is /pseudo/fcp <at> 0
NOTICE: Couldn't set value (../../sun/io/audio/sada/drv/audiocs/audio_4231.c, Line #1759 0x00 0x88)
audio may not work correctly until it is stopped and restarted
audiocs0 at sbus0: SBus slot 4 0xc000000 SBus level 5 sparc ipl 9
audiocs0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,CS4231 <at> 4,c000000
|

<div>
&gt; Date: Mon, 6 Jun 2011 22:43:23 +0100<br>&gt; From: mark.cave-ayland@...<br>&gt; To: openbios@...<br>&gt; CC: nkunkee42@...<br>&gt; Subject: Re: [OpenBIOS] Solaris anyone?<br>&gt; <br>&gt; On 06/06/11 20:42, Mark Cave-Ayland wrote:<br>&gt; <br>&gt; &gt; Hmmm it looks from reading the source code that QEMU doesn't actually<br>&gt; &gt; implement a proper audio device for SS-5 at all but merely provides a<br>&gt; &gt; dummy device with an empty mapped region. In that case it may be<br>&gt; &gt; possible to provide a simple mapping in OpenBIOS to match the one in<br>&gt; &gt; QEMU which may be enough to persuade Solaris to boot.<br>&gt; <br>&gt; Okay - I've installed a simple memory mapping to a virtual address which <br>&gt; is not used, and also tweaked the "intr" property which looked wrong <br>&gt; compared to the sample prtconf output (0x5 instead of 0x39 high cell).<br>&gt; <br>&gt; Does the OpenBIOS ROM at <br>&gt; http://www.siriusit.co.uk/tmp/openbios-sparc32.emptysndmap help get you <br>&gt; any further with Solaris 9?<br>&gt; <br><br>It seems to spin one time more, but still hang:<br><br><br>Configuration device id QEMU version 1 machine id 32<br>CPUs: 1 x FMI,MB86904<br>UUID: 00000000-0000-0000-0000-000000000000<br>Welcome to OpenBIOS v1.0 built on Jun 6 2011 21:31<br>&nbsp; Type 'help' for detailed information<br>Trying disk...<br>No valid state has been set by load or init-program<br><br>0 &gt; boot cd:d -k -v Not a bootable ELF image<br>Loading a.out image...<br>Loaded 7680 bytes<br>entry point is 0x4000<br>bootpath: /iommu/sbus/espdma/esp/sd <at> 2,0:d<br><br>Jumping to entry point 00004000 for type 00000005...<br>switching to new context:<br>Size: 0x45c9f+0xdaf1+0x1d6a7 Bytes<br>SunOS Release 5.9 Version Generic_112233-12 32-bit<br>Copyright 1983-2003 Sun Microsystems, Inc.&nbsp; All rights reserved.<br>Use is subject to license terms.<br>Ethernet address = 52:54:0:12:34:56<br>Using default device instance data<br>vac: enabled in write through mode<br>mem = 262144K (0x10000000)<br>avail mem = 240328704<br>root nexus = SUNW,SPARCstation-5<br>iommu0 at root: obio 0x10000000<br>sbus0 at iommu0: obio 0x10001000<br>dma0 at sbus0: SBus slot 5 0x8400000<br>dma0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000<br>/iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000 (esp0):<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; esp-options=0x46<br>esp0 at dma0: SBus slot 5 0x8800000 sparc ipl 4<br>esp0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000<br>sd2 at esp0: target 2 lun 0<br>sd2 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000/sd <at> 2,0<br>root on /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000/sd <at> 2,0:b fstype ufs<br>obio0 at root<br>obio0 at obio0: obio 0x100000, sparc ipl 12<br>zs0 is /obio/zs <at> 0,100000<br>obio1 at obio0: obio 0x0, sparc ipl 12<br>zs1 is /obio/zs <at> 0,0<br>cpu0: FMI,MB86904 (mid 0 impl 0x0 ver 0x5 clock 170 MHz)<br>Configuring /dev and /devices<br>pseudo-device: devinfo0<br>devinfo0 is /pseudo/devinfo <at> 0<br>tcx0 at sbus0: SBus slot 3 0x800000 and SBus slot 3 0x2000000 and SBus slot 3 0x4000000 and SBus slot 3 0x6000000 and SBus slot 3 0xa000000 and SBus slot 3 0xc000000 and SBus slot 3 0xe000000 and SBus slot 3 0x700000 and SBus slot 3 0x200000 and SBus slot 3 0x300000 and SBus slot 3 0x0 and SBus slot 3 0x240000 and SBus slot 3 0x280000 SBus level 5 sparc ipl 9<br>tcx0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,tcx <at> 3,800000<br>tcx0: revision 0, screen 1024x768<br>ledma0 at sbus0: SBus slot 5 0x8400010<br>le0 at ledma0: SBus slot 5 0x8c00000 sparc ipl 6<br>le0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/ledma <at> 5,8400010/le <at> 5,8c00000<br>pseudo-device: fssnap0<br>fssnap0 is /pseudo/fssnap <at> 0<br>sbusmem0 at sbus0: SBus slot 0 0x0<br>sbusmem0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 0,0<br>sbusmem1 at sbus0: SBus slot 1 0x0<br>sbusmem1 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 1,0<br>sbusmem2 at sbus0: SBus slot 2 0x0<br>sbusmem2 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 2,0<br>sbusmem3 at sbus0: SBus slot 3 0x0<br>sbusmem3 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 3,0<br>sbusmem4 at sbus0: SBus slot 4 0x0<br>sbusmem4 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 4,0<br>sbusmem5 at sbus0: SBus slot 5 0x0<br>sbusmem5 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 5,0<br>pseudo-device: ramdisk1024<br>ramdisk1024 is /pseudo/ramdisk <at> 1024<br>pseudo-device: winlock0<br>winlock0 is /pseudo/winlock <at> 0<br>pseudo-device: lockstat0<br>lockstat0 is /pseudo/lockstat <at> 0<br>pseudo-device: llc10<br>llc10 is /pseudo/llc1 <at> 0<br>pseudo-device: lofi0<br>lofi0 is /pseudo/lofi <at> 0<br>pseudo-device: fcp0<br>fcp0 is /pseudo/fcp <at> 0<br>NOTICE: Couldn't set value (../../sun/io/audio/sada/drv/audiocs/audio_4231.c, Line #1759 0x00 0x88)<br>audio may not work correctly until it is stopped and restarted<br>audiocs0 at sbus0: SBus slot 4 0xc000000 SBus level 5 sparc ipl 9<br>audiocs0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,CS4231 <at> 4,c000000<br>|<br><br>
</div>
Artyom Tarasenko | 7 Jun 2011 23:28
Picon

Re: Solaris anyone?

On Mon, Jun 6, 2011 at 9:42 PM, Mark Cave-Ayland
<mark.cave-ayland@...> wrote:
> On 06/06/11 04:37, Nathan Kunkee wrote:
>
>> My Solaris 9 04/04 image seems to hang in the same spot:
>>
>>
>> Configuration device id QEMU version 1 machine id 32
>> CPUs: 1 x FMI,MB86904
>> UUID: 00000000-0000-0000-0000-000000000000
>> Welcome to OpenBIOS v1.0 built on Apr 30 2011 02:11
>> Type 'help' for detailed information
>> Trying disk...
>> No valid state has been set by load or init-program
>>
>> 0 > boot cd:d -k -v -s Not a bootable ELF image
>> Loading a.out image...
>> Loaded 7680 bytes
>> entry point is 0x4000
>> bootpath: /iommu/sbus/espdma/esp/sd <at> 2,0:d
>>
>> Jumping to entry point 00004000 for type 00000005...
>> switching to new context:
>> Size: 0x45c9f+0xdaf1+0x1d6a7 Bytes
>> SunOS Release 5.9 Version Generic_112233-12 32-bit
>> Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
>> Use is subject to license terms.
>> Ethernet address = 52:54:0:12:34:56
>> Using default device instance data
>> vac: enabled in write through mode
>> mem = 131072K (0x8000000)
>> avail mem = 108797952
>> root nexus = SUNW,SPARCstation-5
>> iommu0 at root: obio 0x10000000
>> sbus0 at iommu0: obio 0x10001000
>> dma0 at sbus0: SBus slot 5 0x8400000
>> dma0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000
>> /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000 (esp0):
>> esp-options=0x46
>> esp0 at dma0: SBus slot 5 0x8800000 sparc ipl 4
>> esp0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000
>> sd2 at esp0: target 2 lun 0
>> sd2 is
>> /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000/sd <at> 2,0
>> root on
>> /iommu <at> 0,10000000/sbus <at> 0,10001000/espdma <at> 5,8400000/esp <at> 5,8800000/sd <at> 2,0:b
>> fstype
>> ufs
>> obio0 at root
>> obio0 at obio0: obio 0x100000, sparc ipl 12
>> zs0 is /obio/zs <at> 0,100000
>> obio1 at obio0: obio 0x0, sparc ipl 12
>> zs1 is /obio/zs <at> 0,0
>> cpu0: FMI,MB86904 (mid 0 impl 0x0 ver 0x5 clock 170 MHz)
>> Configuring /dev and /devices
>> pseudo-device: devinfo0
>> devinfo0 is /pseudo/devinfo <at> 0
>> tcx0 at sbus0: SBus slot 3 0x800000 and SBus slot 3 0x2000000 and SBus
>> slot 3 0x4000000 and SBus slot 3 0x6000000 and SBus slot 3 0xa000000 and
>> SBus slot 3 0xc000000 and SBus slot 3 0xe000000 and SBus slot 3 0x700000
>> and SBus slot 3 0x200000 and SBus slot 3 0x300000 and SBus slot 3 0x0
>> and SBus slot 3 0x240000 and SBus slot 3 0x280000 SBus level 5 sparc ipl 9
>> tcx0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,tcx <at> 3,800000
>> tcx0: revision 0, screen 1024x768
>> ledma0 at sbus0: SBus slot 5 0x8400010
>> le0 at ledma0: SBus slot 5 0x8c00000 sparc ipl 6
>> le0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/ledma <at> 5,8400010/le <at> 5,8c00000
>> pseudo-device: fssnap0
>> fssnap0 is /pseudo/fssnap <at> 0
>> sbusmem0 at sbus0: SBus slot 0 0x0
>> sbusmem0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 0,0
>> sbusmem1 at sbus0: SBus slot 1 0x0
>> sbusmem1 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 1,0
>> sbusmem2 at sbus0: SBus slot 2 0x0
>> sbusmem2 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 2,0
>> sbusmem3 at sbus0: SBus slot 3 0x0
>> sbusmem3 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 3,0
>> sbusmem4 at sbus0: SBus slot 4 0x0
>> sbusmem4 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 4,0
>> sbusmem5 at sbus0: SBus slot 5 0x0
>> sbusmem5 is /iommu <at> 0,10000000/sbus <at> 0,10001000/sbusmem <at> 5,0
>> pseudo-device: ramdisk1024
>> ramdisk1024 is /pseudo/ramdisk <at> 1024
>> pseudo-device: winlock0
>> winlock0 is /pseudo/winlock <at> 0
>> pseudo-device: lockstat0
>> lockstat0 is /pseudo/lockstat <at> 0
>> pseudo-device: llc10
>> llc10 is /pseudo/llc1 <at> 0
>> pseudo-device: lofi0
>> lofi0 is /pseudo/lofi <at> 0
>> pseudo-device: fcp0
>> fcp0 is /pseudo/fcp <at> 0
>> NOTICE: Couldn't set value
>> (../../sun/io/audio/sada/drv/audiocs/audio_4231.c, Line #1759 0x00 0x88)
>> audio may not work correctly until it is stopped and restarted
>> audiocs0 at sbus0: SBus slot 4 0xc000000 SBus level 5 sparc ipl 9
>> audiocs0 is /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,CS4231 <at> 4,c000000
>>
>> Not having anything to compare to, are the tcx0 and sbusmem entries
>> correct?
>
> Oh that's interesting - I always thought that the hangs were being caused by
> OpenBIOS reporting 4 CPUs by default whilst QEMU only provides 1.

Where does it report 4 CPUs? I see only one in the device tree.

> But this
> trace strongly points towards the audio driver being the culprit instead.

To be honest I doubt it. I'd rather suspect networking problem with le
(aka pcnet), which might be improperly initialized either in qemu or
in OpenBIOS. OBP under qemu tries netboot first, so it initializes the
le card before Solaris gets it. So the fact that the card is properly
initialised under OBP may be just a co-incidence.

Anyway it should be easy to check - just kick the audio out of the
device tree. No recompilation of OpenBIOS should be necessary,
something like

cd /iommu <at> 0,10000000/sbus <at> 0,10001000/SUNW,CS4231 <at> 4,c000000
" name" delete-property
device-end
boot cdrom:d -vs

should do it.
Nathan, can you check?

Artyom
--

-- 
Regards,
Artyom Tarasenko

solaris/sparc under qemu blog: http://tyom.blogspot.com/


Gmane