[uml-devel] Re: Panic with slirp transport and gcc 3.3

[Bill A. <all...@ma...>]

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. <bal...@de...>

Imagine a large red swirl here.