From: Bill Allombert <allomber@math.u-bordeaux.fr>
To: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net,
176485@bugs.debian.org
Cc: mdz@debian.org
Subject: [uml-devel] Re: Panic with slirp transport and gcc 3.3
Date: Tue, 13 Jan 2004 16:25:42 +0100 [thread overview]
Message-ID: <20040113152542.GD7072@seventeen> (raw)
In-Reply-To: <20040112183623.GB1436@alcor.net>
On Mon, Jan 12, 2004 at 10:36:23AM -0800, Matt Zimmerman wrote:
> By the way, the original reason why I started building UML with gcc-2.95 was
> because building with 3.x broke the slirp transport like so:
>
> Kernel panic: read of switch_pipe failed, errno = 9
>
> errno 9 is EBADF. I never did find the real cause of that bug, but it has
> resurfaced now that I am building with gcc 3.3 again to fix the other, worse
> bug. I would be interested to know if anyone else has run into it. More
> information is here:
For what it worth with the current Debian UML package I get
$ linux ubd0=uml root=/dev/ubd0 eth0=slirp|& less
...
Netdevice 0 : SLIRP backend - command line: 'slirp'
mconsole (version 2) initialized on /home/bill/.uml/wksNEk/mconsole
Partition check:
ubda: unknown partition table
Initializing stdio console driver
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Kernel panic: Segfault with no mm
Without the eth0=slirp parameter, there are no kernel panic.
So at least the error message has changed.
The host kernel has the skas patch from the Debian package applied.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-01-13 15:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 1:13 [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 17:14 ` Jeff Dike
2003-12-21 0:47 ` Matt Zimmerman
2003-12-21 15:58 ` BlaisorBlade
2003-12-21 22:40 ` Matt Zimmerman
2003-12-21 23:16 ` Matt Zimmerman
2003-12-22 0:25 ` Jeff Dike
2003-12-22 4:08 ` Matt Zimmerman
2003-12-22 5:49 ` Daniel Jacobowitz
2003-12-22 9:08 ` Matt Zimmerman
2004-01-05 17:51 ` Adam Heath
2004-01-05 18:10 ` Matt Zimmerman
2003-12-24 12:48 ` BlaisorBlade
2003-12-21 0:52 ` Matt Zimmerman
2003-12-21 1:06 ` Matt Zimmerman
2003-12-28 9:33 ` Matt Zimmerman
2003-12-28 9:51 ` Matt Zimmerman
2003-12-28 9:52 ` Matt Zimmerman
2004-01-06 2:59 ` Jeff Dike
2003-12-28 10:12 ` Matt Zimmerman
2003-12-28 11:30 ` Matt Zimmerman
2003-12-30 18:43 ` Resolution (Re: [uml-devel] 2.4.22-[67] problems) Matt Zimmerman
2004-01-06 2:58 ` Jeff Dike
2004-01-06 7:41 ` Nuno Silva
2004-01-06 8:02 ` Matt Zimmerman
2004-01-06 8:20 ` Nuno Silva
2004-01-06 8:47 ` Nuno Silva
2004-01-06 9:20 ` Nuno Silva
2004-01-06 17:13 ` Matt Zimmerman
2004-01-09 7:22 ` Nuno Silva
2004-01-08 7:07 ` Matt Zimmerman
2004-01-12 18:36 ` [uml-devel] Panic with slirp transport and gcc 3.3 Matt Zimmerman
2004-01-13 15:25 ` Bill Allombert [this message]
2004-01-13 17:30 ` [uml-devel] " Jeff Dike
2004-01-13 17:44 ` Bill Allombert
2004-01-13 18:51 ` Matt Zimmerman
2004-01-16 2:38 ` Jeff Dike
2004-01-16 2:38 ` Matt Zimmerman
2004-01-16 20:04 ` Jeff Dike
2004-01-16 19:49 ` Matt Zimmerman
2004-01-17 0:42 ` Matt Zimmerman
2003-12-21 1:29 ` [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 19:05 ` Nick Craig-Wood
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=20040113152542.GD7072@seventeen \
--to=allomber@math.u-bordeaux.fr \
--cc=176485@bugs.debian.org \
--cc=jdike@addtoit.com \
--cc=mdz@debian.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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