[Qemu-devel] sparc guest

[Qemu-devel] sparc guest

[Nigel Horne]

Good news, sparc emulation with -nographic no longer core dumps.

The bad news, networking still fails:

....
SunLance: using auto-carrier-detection.
eth0: LANCE 52:54:00:12:34:56
Skipping already loaded module esp.
Setting up networking...done.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces...Internet Software Consortium DHCP 
Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

LANCE unopened after 100 ticks, csr0=0004.
dcsr=a0061020
SIOCSIFFLAGS: Operation not permitted
Listening on LPF/eth0/52:54:00:12:34:56
Sending on   LPF/eth0/52:54:00:12:34:56
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
receive_packet failed on eth0: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
send_packet: Network is down
....

-Nigel

Re: [Qemu-devel] sparc guest

[Thiemo Seufer]

Nigel Horne wrote:
> Good news, sparc emulation with -nographic no longer core dumps.
> 
> The bad news, networking still fails:

FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
related.


Thiemo

Re: [Qemu-devel] sparc guest

[Blue Swirl]

On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
> Nigel Horne wrote:
> > Good news, sparc emulation with -nographic no longer core dumps.
> >
> > The bad news, networking still fails:
>
> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
> related.

On my test cases the network is still fine. What was the setup again?

Re: [Qemu-devel] sparc guest

[Nigel Horne]

Blue Swirl wrote:
> On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
>> Nigel Horne wrote:
>> > Good news, sparc emulation with -nographic no longer core dumps.
>> >
>> > The bad news, networking still fails:
>>
>> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
>> related.
>
> On my test cases the network is still fine. What was the setup again?
Linux host, Debian/sparc guest. Networking used to work fine, but it 
stopped working a few weeks ago:
Starting thus:
qemu-system-sparc -hda ~njh/qemu/sparc/debian.img -nographic -m 64

-Nigel

Re: [Qemu-devel] sparc guest

[Andreas Färber]

Am 25.06.2007 um 22:07 schrieb Nigel Horne:

> Blue Swirl wrote:
>> On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
>>> Nigel Horne wrote:
>>> > Good news, sparc emulation with -nographic no longer core dumps.
>>> >
>>> > The bad news, networking still fails:
>>>
>>> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
>>> related.
>>
>> On my test cases the network is still fine. What was the setup again?
> Linux host, Debian/sparc guest. Networking used to work fine, but  
> it stopped working a few weeks ago:
> Starting thus:
> qemu-system-sparc -hda ~njh/qemu/sparc/debian.img -nographic -m 64

Similar in my case - see the "Sparc32 network problems" thread which  
in the end brought us a nice fix for tcx endianess issues but not yet  
for the original lance networking issues. ;-)

Andreas

Re: [Qemu-devel] sparc guest

[Thiemo Seufer]

Blue Swirl wrote:
> On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
> >Nigel Horne wrote:
> >> Good news, sparc emulation with -nographic no longer core dumps.
> >>
> >> The bad news, networking still fails:
> >
> >FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
> >related.
> 
> On my test cases the network is still fine. What was the setup again?

What I see is apparently not triggered by a change in Qemu. An older
2.6.16 kernel works with current Qemu, but 2.6.21 breaks networking.

The setup is basically the big endian mips regression test initrd
with a newer kernel.


Thiemo

Re: [Qemu-devel] sparc guest

[Nigel Horne]

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Thiemo Seufer wrote:
> Blue Swirl wrote:
>> On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
>>> Nigel Horne wrote:
>>>> Good news, sparc emulation with -nographic no longer core dumps.
>>>>
>>>> The bad news, networking still fails:
>>> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
>>> related.
>> On my test cases the network is still fine. What was the setup again?
> 
> What I see is apparently not triggered by a change in Qemu. An older
> 2.6.16 kernel works with current Qemu, but 2.6.21 breaks networking.

2.6.16 and 2.6.21 are not involved here. My host is running 2.6.20,
the guest is running 2.6.8.

> 
> The setup is basically the big endian mips regression test initrd
> with a newer kernel.

Sparc?

> 
> Thiemo
> 


-- 
Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter.
NJH Music, Barnsley, UK.  ICQ#20252325
njh@bandsman.co.uk http://www.bandsman.co.uk

[-- Attachment #2: njh.vcf --]
[-- Type: text/x-vcard, Size: 181 bytes --]

begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
email;internet:njh@bandsman.co.uk
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
version:2.1
end:vcard

Re: [Qemu-devel] sparc guest

[Blue Swirl]

On 6/27/07, Nigel Horne <njh@bandsman.co.uk> wrote:
> Thiemo Seufer wrote:
> > Blue Swirl wrote:
> >> On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
> >>> Nigel Horne wrote:
> >>>> Good news, sparc emulation with -nographic no longer core dumps.
> >>>>
> >>>> The bad news, networking still fails:
> >>> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
> >>> related.
> >> On my test cases the network is still fine. What was the setup again?
> >
> > What I see is apparently not triggered by a change in Qemu. An older
> > 2.6.16 kernel works with current Qemu, but 2.6.21 breaks networking.
>
> 2.6.16 and 2.6.21 are not involved here. My host is running 2.6.20,
> the guest is running 2.6.8.

I just updated guest from Debian 3.1r1 to 4.0. After reboot net still
works fine (4Mbytes/s), though the kernel is still 2.4.29. I tried
installing a 2.6 series kernel but something went wrong with the ram
disk creation. Host is 2.6.18.

Re: [Qemu-devel] sparc guest

[Andreas Färber]

Am 27.06.2007 um 22:43 schrieb Blue Swirl:

> On 6/27/07, Nigel Horne <njh@bandsman.co.uk> wrote:
>> Thiemo Seufer wrote:
>> > Blue Swirl wrote:
>> >> On 6/25/07, Thiemo Seufer <ths@networkno.de> wrote:
>> >>> Nigel Horne wrote:
>> >>>> Good news, sparc emulation with -nographic no longer core dumps.
>> >>>>
>> >>>> The bad news, networking still fails:
>> >>> FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe  
>> that's
>> >>> related.
>> >> On my test cases the network is still fine. What was the setup  
>> again?
>> >
>> > What I see is apparently not triggered by a change in Qemu. An  
>> older
>> > 2.6.16 kernel works with current Qemu, but 2.6.21 breaks  
>> networking.
>>
>> 2.6.16 and 2.6.21 are not involved here. My host is running 2.6.20,
>> the guest is running 2.6.8.
>
> I just updated guest from Debian 3.1r1 to 4.0. After reboot net still
> works fine (4Mbytes/s), though the kernel is still 2.4.29. I tried
> installing a 2.6 series kernel but something went wrong with the ram
> disk creation. Host is 2.6.18.

My guest is using 4.0's 2.6.18 and it does not work for me (host OS X  
v10.4.10).

I also sometimes get this:
...
Starting Hardware abstraction layer: hald
floppy driver state
-------------------
now=4294959146 last interrupt=4294937998 diff=21148 last called  
handler=f0120824
timeout_message=lock fdc
last output bytes:
13 80 4294937998
  0 80 4294937998
1a 80 4294937998
  0 80 4294937998
12 80 4294937998
  0 80 4294937998
14 80 4294937998
18 80 4294937998
  8 80 4294937998
12 80 4294958847
  0 80 4294958847
13 80 4294958847
  0 80 4294958847
1a 80 4294958847
  0 80 4294958847
  3 80 4294958847
c1 80 4294958847
11 80 4294958847
  7 80 4294958847
  0 80 4294958847
last result at 4294937998
last redo_fd_request at 4294958843

status=80
fdc_busy=1
do_floppy=f01205ac
cont=f01dd0f8
current_req=00000000
command_status=-1

floppy0: floppy timeout called
.
Starting DHCP D-Bus daemon: dhcdbd.
...

So maybe it's a more general problem with interrupt handling?
Lance complains about timeouts, too, and so did DHCP during  
installation.

Andreas

Re: [Qemu-devel] sparc guest

[Blue Swirl]

I found the problem, it wasn't related to Debian's 2.6 kernel after
all, but pcnet just didn't work on a 32-bit host. I'm committing a
fix.

On 6/28/07, Andreas Färber <andreas.faerber@web.de> wrote:
> So maybe it's a more general problem with interrupt handling?
> Lance complains about timeouts, too, and so did DHCP during
> installation.

I think floppy driver on Sparc Linux is broken.

Re: [Qemu-devel] sparc guest

[Andreas Färber]

Am 28.06.2007 um 17:26 schrieb Blue Swirl:

> I found the problem, it wasn't related to Debian's 2.6 kernel after
> all, but pcnet just didn't work on a 32-bit host. I'm committing a
> fix.

Big thanks for fixing this! Works now. :-)

Andreas

Re: [Qemu-devel] sparc guest

[Nigel Horne]

[-- Attachment #1: Type: text/plain, Size: 521 bytes --]

Andreas Färber wrote:
> 
> Am 28.06.2007 um 17:26 schrieb Blue Swirl:
> 
>> I found the problem, it wasn't related to Debian's 2.6 kernel after
>> all, but pcnet just didn't work on a 32-bit host. I'm committing a
>> fix.
> 
> Big thanks for fixing this! Works now. :-)

And here as well. Well done, thanks.
> 
> Andreas
> 

-Nigel

-- 
Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter.
NJH Music, Barnsley, UK.  ICQ#20252325
njh@bandsman.co.uk http://www.bandsman.co.uk

[-- Attachment #2: njh.vcf --]
[-- Type: text/x-vcard, Size: 181 bytes --]

begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
email;internet:njh@bandsman.co.uk
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
version:2.1
end:vcard

Re: [Qemu-devel] sparc guest

[Andreas Färber]

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

With the lance network fixed being able to do some more now, I am  
seeing a number of other issues:

- When there is a network timeout the console starts  
"scrolling" (text moves up and screen stays blank).
To reproduce, run svn checkout svn://10.0.0.1 (with 10.0.0.1 not  
available). On others systems the screen stays as is and only  
displays a timeout error message in the end.

- Already during initial Debian installation attempt I kept getting  
kernel panics (previous thread).
Now I am getting more of those and they appear to be connected to  
esp0 problems. Once I got an infinite loop of esp0 timeout messages  
during boot (not reproducable). But reproducably I get some esp0  
output and then kernel panic while running Mono 1.2.4's ./configure  
script (see screenshot).

Do you have any idea where those problems might originate? Any  
thoughts how to fix or work around them? ./configure -C does not work  
unfortunately.

Andreas

[-- Attachment #2: Q Screenshot 1.png --]
[-- Type: image/png, Size: 29258 bytes --]

Re: [Qemu-devel] sparc guest

[Andreas Färber]

> Once I got an infinite loop of esp0 timeout messages during boot  
> (not reproducable).

Just got it again, it's:
esp0: Data transfer overrun.

[Qemu-devel] Sparc guest

[Nigel Horne]

On the CVS version, networking has stopped working again with Sparc 
guests running Debian Linux.
It had been working fine for a few weeks, but the latest version is 
broken again, with the device
not being found.

-Nigel

Re: [Qemu-devel] Sparc guest

[Blue Swirl]

On 8/19/07, Nigel Horne <njh@bandsman.co.uk> wrote:
> On the CVS version, networking has stopped working again with Sparc
> guests running Debian Linux.
> It had been working fine for a few weeks, but the latest version is
> broken again, with the device
> not being found.

I cannot reproduce this on either i386 or x86_64 host with Debian
stable guest. Also, none of the recent patches could have caused this
effect. I'll update the guest to see if the problem comes from some
updated Debian package.

Re: [Qemu-devel] Sparc guest

[Andreas Färber]

Am 20.08.2007 um 21:26 schrieb Blue Swirl:

> On 8/19/07, Nigel Horne <njh@bandsman.co.uk> wrote:
>> On the CVS version, networking has stopped working again with Sparc
>> guests running Debian Linux.
>> It had been working fine for a few weeks, but the latest version is
>> broken again, with the device
>> not being found.
>
> I cannot reproduce this on either i386 or x86_64 host with Debian
> stable guest. Also, none of the recent patches could have caused this
> effect. I'll update the guest to see if the problem comes from some
> updated Debian package.

A recent security update was kernel 2.6.18.5 but I have not yet  
noticed problems, just having upgraded.
What exactly were you observing? Was it during boot, or are there any  
specific steps to reproduce?