Re: [Qemu-devel] Sparc guest
On 8/19/07, Nigel Horne [EMAIL PROTECTED] 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
Am 20.08.2007 um 21:26 schrieb Blue Swirl: On 8/19/07, Nigel Horne [EMAIL PROTECTED] 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?
[Qemu-devel] Sparc guest
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 - SCSI
Am 03.08.2007 um 13:52 schrieb Aurelien Jarno: The problem appears when one interrupt on the SCSI controller is triggered twice by the interrupt controller, the second interrupt disturb the driver. I have fixed one problem like that a few months ago in the CVS, so it happens less often, but there is still a problem somewhere. Do you know under which circumstances this happens? And is there any way to avoid it? Andreas
Re: [Qemu-devel] Sparc guest - SCSI
Am 03.08.2007 um 12:42 schrieb Nigel Horne: Andreas Färber wrote: Am 03.08.2007 um 10:45 schrieb Nigel Horne: Guest: Linux/sparc Host: Linux/x86 From time to time I am getting SCSI errors from the guest using the latest CVS: scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting command esp0: dumping state esp0: dma -- cond_rega4000211 addrf292b000 esp0: SW [sreg00 sstep04 ireg18] esp0: HW reread [sreg03 sstep00 ireg10] esp0: current command [tgt00 lun00 pphaseDATAOUT cphaseDATAOUT] esp0: disconnected SCSI host 0 abort (pid 50803) timed out - resetting SCSI bus is being reset for host 0 channel 0. esp0: Resetting scsi bus esp0: SCSI bus reset interrupt As far as I can tell the guest recovers fine, but it may be worth investigating. I reported similar errors recently (OS X ppc host) - for me it panics afterwards and does not recover fine. I got the impression that it happens later if I disable the lance NIC. I have the lance NIC enabled in the guest. So what? I usually have it enabled, too. :)
Re: [Qemu-devel] Sparc guest - SCSI
Am 03.08.2007 um 16:54 schrieb Aurelien Jarno:
I suggest to read the description of the problem from last time:
http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html
I guess there is still one case when this can happen. The only
solution
I see to avoid that is to fix the bug (the problem doesn't occurs on
real hardware, so the emulation is buggy).
I tried that patch before ever posting to this list. Like I reported
earlier, if applied I don't get a kernel panic any more but instead
qemu crashes and is gone. So sadly it didn't fix the issue for me
as is.
Which version are you using?
At the time both 0.9.0 and CVS HEAD, today CVS HEAD.
This patch is supposed to be in the CVS
already.
Negative, this is the excerpt from today's hw/slavio_intctl.c around
line 293:
static void slavio_set_irq(void *opaque, int irq, int level)
{
SLAVIO_INTCTLState *s = opaque;
uint32_t mask = 1 irq;
uint32_t pil = s-intbit_to_level[irq];
DPRINTF(Set cpu %d irq %d - pil %d level %d\n, s-target_cpu,
irq, pil,
level);
if (pil 0) {
if (level) {
s-intregm_pending |= mask;
s-intreg_pending[s-target_cpu] |= 1 pil;
} else {
s-intregm_pending = ~mask;
s-intreg_pending[s-target_cpu] = ~(1 pil);
}
slavio_check_interrupts(s);
}
}
Your referenced patch moves slavio_check_interrupts(s); four lines up
so is not in CVS.
Andreas
[Qemu-devel] Sparc guest - SCSI
Guest: Linux/sparc Host: Linux/x86 From time to time I am getting SCSI errors from the guest using the latest CVS: scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting command esp0: dumping state esp0: dma -- cond_rega4000211 addrf292b000 esp0: SW [sreg00 sstep04 ireg18] esp0: HW reread [sreg03 sstep00 ireg10] esp0: current command [tgt00 lun00 pphaseDATAOUT cphaseDATAOUT] esp0: disconnected SCSI host 0 abort (pid 50803) timed out - resetting SCSI bus is being reset for host 0 channel 0. esp0: Resetting scsi bus esp0: SCSI bus reset interrupt As far as I can tell the guest recovers fine, but it may be worth investigating. -Nigel begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music adr:Pogmoor;;28 Wharfedale Road;Barnsley;South Yorkshire;S75 2LJ;UK email;internet:[EMAIL PROTECTED] tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE url:http://www.bandsman.co.uk version:2.1 end:vcard
Re: [Qemu-devel] Sparc guest - SCSI
Am 03.08.2007 um 14:02 schrieb Nigel Horne: Guest: Linux/sparc Host: Linux/x86 From time to time I am getting SCSI errors from the guest using the latest CVS: scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting command esp0: dumping state esp0: dma -- cond_rega4000211 addrf292b000 esp0: SW [sreg00 sstep04 ireg18] esp0: HW reread [sreg03 sstep00 ireg10] esp0: current command [tgt00 lun00 pphaseDATAOUT cphaseDATAOUT] esp0: disconnected SCSI host 0 abort (pid 50803) timed out - resetting SCSI bus is being reset for host 0 channel 0. esp0: Resetting scsi bus esp0: SCSI bus reset interrupt As far as I can tell the guest recovers fine, but it may be worth investigating. I reported similar errors recently (OS X ppc host) - for me it panics afterwards and does not recover fine. I got the impression that it happens later if I disable the lance NIC. I have the lance NIC enabled in the guest. So what? I usually have it enabled, too. :) No need to be so rude/agressive, I just thought I'd add the information in case some one found it helpful. Hey, asking what you meant and a smiley are most certainly not rude or aggressive. You replied to my suggestion with a one-liner that was about as helpful as replying with your screen resolution, as it happens with and without NIC. So I wanted to know what you wanted to imply with that. Apparently nothing - question answered, thank you. But on the subject of being rude, I reported this a month ago in your sparc guest thread and it was ignored by everyone, you said nothing of esp0 issues back then and now it's suddenly a new issue... http://lists.gnu.org/archive/html/qemu-devel/2007-06/msg00481.html Andreas
Re: [Qemu-devel] Sparc guest - SCSI
Am 03.08.2007 um 16:15 schrieb Aurelien Jarno: Andreas Färber a écrit : Am 03.08.2007 um 13:52 schrieb Aurelien Jarno: The problem appears when one interrupt on the SCSI controller is triggered twice by the interrupt controller, the second interrupt disturb the driver. I have fixed one problem like that a few months ago in the CVS, so it happens less often, but there is still a problem somewhere. Do you know under which circumstances this happens? And is there any way to avoid it? I suggest to read the description of the problem from last time: http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html I guess there is still one case when this can happen. The only solution I see to avoid that is to fix the bug (the problem doesn't occurs on real hardware, so the emulation is buggy). I tried that patch before ever posting to this list. Like I reported earlier, if applied I don't get a kernel panic any more but instead qemu crashes and is gone. So sadly it didn't fix the issue for me as is. And without knowing about interrupt controllers it is hard to fix a bug no-one knows what or where exactly it is and how it should be fixed... :( Andreas http://lists.gnu.org/archive/html/qemu-devel/2007-06/msg00086.html
Re: [Qemu-devel] Sparc guest - SCSI
Andreas Färber wrote: Am 03.08.2007 um 10:45 schrieb Nigel Horne: Guest: Linux/sparc Host: Linux/x86 From time to time I am getting SCSI errors from the guest using the latest CVS: scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting command esp0: dumping state esp0: dma -- cond_rega4000211 addrf292b000 esp0: SW [sreg00 sstep04 ireg18] esp0: HW reread [sreg03 sstep00 ireg10] esp0: current command [tgt00 lun00 pphaseDATAOUT cphaseDATAOUT] esp0: disconnected SCSI host 0 abort (pid 50803) timed out - resetting SCSI bus is being reset for host 0 channel 0. esp0: Resetting scsi bus esp0: SCSI bus reset interrupt As far as I can tell the guest recovers fine, but it may be worth investigating. I reported similar errors recently (OS X ppc host) - for me it panics afterwards and does not recover fine. I got the impression that it happens later if I disable the lance NIC. I have the lance NIC enabled in the guest. Andreas -- Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 [EMAIL PROTECTED] http://www.bandsman.co.uk begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music adr:Pogmoor;;28 Wharfedale Road;Barnsley;South Yorkshire;S75 2LJ;UK email;internet:[EMAIL PROTECTED] tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE url:http://www.bandsman.co.uk version:2.1 end:vcard
Re: [Qemu-devel] Sparc guest - SCSI
Andreas Färber a écrit : Am 03.08.2007 um 10:45 schrieb Nigel Horne: Guest: Linux/sparc Host: Linux/x86 From time to time I am getting SCSI errors from the guest using the latest CVS: scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting command esp0: dumping state esp0: dma -- cond_rega4000211 addrf292b000 esp0: SW [sreg00 sstep04 ireg18] esp0: HW reread [sreg03 sstep00 ireg10] esp0: current command [tgt00 lun00 pphaseDATAOUT cphaseDATAOUT] esp0: disconnected SCSI host 0 abort (pid 50803) timed out - resetting SCSI bus is being reset for host 0 channel 0. esp0: Resetting scsi bus esp0: SCSI bus reset interrupt As far as I can tell the guest recovers fine, but it may be worth investigating. I reported similar errors recently (OS X ppc host) - for me it panics afterwards and does not recover fine. I got the impression that it happens later if I disable the lance NIC. The problem appears when one interrupt on the SCSI controller is triggered twice by the interrupt controller, the second interrupt disturb the driver. I have fixed one problem like that a few months ago in the CVS, so it happens less often, but there is still a problem somewhere. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net
RE: [Qemu-devel] Sparc guest - SCSI
Am 03.08.2007 um 12:42 schrieb Nigel Horne: Andreas Färber wrote: Am 03.08.2007 um 10:45 schrieb Nigel Horne: Guest: Linux/sparc Host: Linux/x86 From time to time I am getting SCSI errors from the guest using the latest CVS: scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting command esp0: dumping state esp0: dma -- cond_rega4000211 addrf292b000 esp0: SW [sreg00 sstep04 ireg18] esp0: HW reread [sreg03 sstep00 ireg10] esp0: current command [tgt00 lun00 pphaseDATAOUT cphaseDATAOUT] esp0: disconnected SCSI host 0 abort (pid 50803) timed out - resetting SCSI bus is being reset for host 0 channel 0. esp0: Resetting scsi bus esp0: SCSI bus reset interrupt As far as I can tell the guest recovers fine, but it may be worth investigating. I reported similar errors recently (OS X ppc host) - for me it panics afterwards and does not recover fine. I got the impression that it happens later if I disable the lance NIC. I have the lance NIC enabled in the guest. So what? I usually have it enabled, too. :) No need to be so rude/agressive, I just thought I'd add the information in case some one found it helpful.
Re: [Qemu-devel] Sparc guest - SCSI
Andreas Färber a écrit : Am 03.08.2007 um 13:52 schrieb Aurelien Jarno: The problem appears when one interrupt on the SCSI controller is triggered twice by the interrupt controller, the second interrupt disturb the driver. I have fixed one problem like that a few months ago in the CVS, so it happens less often, but there is still a problem somewhere. Do you know under which circumstances this happens? And is there any way to avoid it? I suggest to read the description of the problem from last time: http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html I guess there is still one case when this can happen. The only solution I see to avoid that is to fix the bug (the problem doesn't occurs on real hardware, so the emulation is buggy). -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net
Re: [Qemu-devel] Sparc guest - SCSI
Andreas Färber a écrit : Am 03.08.2007 um 16:15 schrieb Aurelien Jarno: Andreas Färber a écrit : Am 03.08.2007 um 13:52 schrieb Aurelien Jarno: The problem appears when one interrupt on the SCSI controller is triggered twice by the interrupt controller, the second interrupt disturb the driver. I have fixed one problem like that a few months ago in the CVS, so it happens less often, but there is still a problem somewhere. Do you know under which circumstances this happens? And is there any way to avoid it? I suggest to read the description of the problem from last time: http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html I guess there is still one case when this can happen. The only solution I see to avoid that is to fix the bug (the problem doesn't occurs on real hardware, so the emulation is buggy). I tried that patch before ever posting to this list. Like I reported earlier, if applied I don't get a kernel panic any more but instead qemu crashes and is gone. So sadly it didn't fix the issue for me as is. Which version are you using? This patch is supposed to be in the CVS already. -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net
Re: [Qemu-devel] Sparc guest - SCSI
I seem to have reverted the patch here:
http://cvs.savannah.gnu.org/viewvc/qemu/qemu/hw/slavio_intctl.c?r1=1.15r2=1.16
But I still get SCSI errors when using e2fsck with this change.
On 8/3/07, Andreas Färber [EMAIL PROTECTED] wrote:
Am 03.08.2007 um 16:54 schrieb Aurelien Jarno:
I suggest to read the description of the problem from last time:
http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html
I guess there is still one case when this can happen. The only
solution
I see to avoid that is to fix the bug (the problem doesn't occurs on
real hardware, so the emulation is buggy).
I tried that patch before ever posting to this list. Like I reported
earlier, if applied I don't get a kernel panic any more but instead
qemu crashes and is gone. So sadly it didn't fix the issue for me
as is.
Which version are you using?
At the time both 0.9.0 and CVS HEAD, today CVS HEAD.
This patch is supposed to be in the CVS
already.
Negative, this is the excerpt from today's hw/slavio_intctl.c around
line 293:
static void slavio_set_irq(void *opaque, int irq, int level)
{
SLAVIO_INTCTLState *s = opaque;
uint32_t mask = 1 irq;
uint32_t pil = s-intbit_to_level[irq];
DPRINTF(Set cpu %d irq %d - pil %d level %d\n, s-target_cpu,
irq, pil,
level);
if (pil 0) {
if (level) {
s-intregm_pending |= mask;
s-intreg_pending[s-target_cpu] |= 1 pil;
} else {
s-intregm_pending = ~mask;
s-intreg_pending[s-target_cpu] = ~(1 pil);
}
slavio_check_interrupts(s);
}
}
Your referenced patch moves slavio_check_interrupts(s); four lines up
so is not in CVS.
Andreas
Re: [Qemu-devel] sparc guest
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 inline: Q Screenshot 1.png
Re: [Qemu-devel] sparc guest
Once I got an infinite loop of esp0 timeout messages during boot (not reproducable). Just got it again, it's: esp0: Data transfer overrun.
Re: [Qemu-devel] sparc guest
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 [EMAIL PROTECTED] http://www.bandsman.co.uk begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music email;internet:[EMAIL PROTECTED] tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE version:2.1 end:vcard
Re: [Qemu-devel] sparc guest
Am 27.06.2007 um 22:43 schrieb Blue Swirl: On 6/27/07, Nigel Horne [EMAIL PROTECTED] wrote: Thiemo Seufer wrote: Blue Swirl wrote: On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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= 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
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 [EMAIL PROTECTED] 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
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
Thiemo Seufer wrote: Blue Swirl wrote: On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://www.bandsman.co.uk begin:vcard fn:Nigel Horne n:Horne;Nigel org:NJH Music email;internet:[EMAIL PROTECTED] tel;fax:+44 870 705 9334 note:Skype: nigelhorne x-mozilla-html:FALSE version:2.1 end:vcard
Re: [Qemu-devel] sparc guest
On 6/27/07, Nigel Horne [EMAIL PROTECTED] wrote: Thiemo Seufer wrote: Blue Swirl wrote: On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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
Blue Swirl wrote: On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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
[Qemu-devel] sparc guest
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
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
On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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
Blue Swirl wrote: On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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
Am 25.06.2007 um 22:07 schrieb Nigel Horne: Blue Swirl wrote: On 6/25/07, Thiemo Seufer [EMAIL PROTECTED] 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
