qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [BUG] Regression in networking code (SIGSEGV)
Date: Mon, 26 Jan 2009 08:29:19 +0200	[thread overview]
Message-ID: <20090126062919.GD15778@redhat.com> (raw)
In-Reply-To: <497CD9C2.4010305@mail.berlios.de>

On Sun, Jan 25, 2009 at 10:29:38PM +0100, Stefan Weil wrote:
> Aurelien Jarno schrieb:
> > On Sat, Jan 24, 2009 at 10:00:33PM +0100, Stefan Weil wrote:
> >   
> >> Gleb Natapov schrieb:
> >>     
> >>> On Wed, Jan 21, 2009 at 10:17:20PM +0100, Stefan Weil wrote:
> >>>   
> >>>       
> >>>> Hi,
> >>>>
> >>>> the SIGSEGV crash below can be reproduced with Qemu r6391 and "high" net
> >>>> load.
> >>>>
> >>>> I bootet a mips malta kernel from a debian nfs root. While this worked fine,
> >>>> aptitude update hangs during downloads, nfs root is lost and after some time
> >>>> Qemu gets a SIGSEGV.
> >>>>
> >>>> A similar crash occurs with a different mips machine (ar7) and different
> >>>> network hardware (ar7 emac / cpmac), so it is not restricted to pcnet.
> >>>> This second system does not survive the network boot.
> >>>>
> >>>> Up to now, I could not run tests with non-mips systems.
> >>>>
> >>>> I'm fairly sure that 2 weeks ago networking worked without problems in both
> >>>> cases.
> >>>>
> >>>>     
> >>>>         
> >>> What is your host CPU?  How you run qemu (what is your command line)?
> >>>   
> >>>       
> >> Debian amd64 host.
> >>
> >> mipsel-softmmu/qemu-system-mipsel --kernel vmlinux \
> >>     --append "debug nohz=off root=/dev/nfs rw ip=::::malta-le::dhcp" \
> >>     -M malta --net nic --net user -m 256
> >>     
> >
> > The fact that your host system is 64-bit and you are using the user
> > networking is interesting. You could try to look at revisions 6272 and
> > 6288, they are probably the cause of your problem.
> >   
> 
> Yes, you are right. Reverting r6288 results in stable networking again.
> 
> Thank you for this hint.
> 
I also use amd64 host, but I was not able to reproduce this with other
guests. I'll try mips guest. Can you try to reproduce the problem with
different guest (x86 for instance)?


--
			Gleb.

  reply	other threads:[~2009-01-26 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 21:17 [Qemu-devel] [BUG] Regression in networking code (SIGSEGV) Stefan Weil
2009-01-22  7:38 ` Gleb Natapov
2009-01-24 21:00   ` Stefan Weil
2009-01-24 21:53     ` Aurelien Jarno
2009-01-25 21:29       ` Stefan Weil
2009-01-26  6:29         ` Gleb Natapov [this message]
2009-02-01 20:11           ` Stefan Weil
     [not found]             ` <20090202163806.GA29674@redhat.com>
2009-02-04 12:01               ` Stefan Weil
2009-02-05 15:34                 ` Gleb Natapov
2009-02-05 19:24                   ` Stefan Weil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090126062919.GD15778@redhat.com \
    --to=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).