From: Dave (Bob) <da...@bo...> - 2013-01-12 09:55:31
|
Maybe someone can help me with this... I have been trying to tie down an issue that I have with "UML Network Related Crashing" so that Richard can reproduce my problem. I am currently trying to use both a 32 bit UML and a 64 bit UML to run Debian root filesystems, 32 bit and 64 bit respectively. I am running on a 64 bit machine, with 64 bit kernel incorporating 32 bit compatibility. The 32 bit environment that I am working in for the compilation of 32 bit UML kernels and running them is a place to which I bind mount /dev, /sys, /proc to their primary locations; chroot to the top of this structure; execute 'linux32'; and then work as though I was on a 32 bit machine. When I try to run the 32 bit UML kernel with the 32 bit Debian root filesystem image, it boots to the login prompt, but I can't type anything at the prompt. The UML kernel is displaying messages: "Couldn't grant pty - errno = -2" I have looked into this and I see that this message comes from 'arch/um/os-Linux/tty.c'; due to a non-zero result from 'initial_thread_cb( ... )', which is in 'arch/um/kernel/process.c'; which calls 'initial_thread_cb_skas( ... )', which is in 'arch/um/os-Linux/skas/process.c'. The structure that contains the original non-zero result is not directly manipulated, so I can see that this result comes from some different thread and the working of this is not evident to the uninitiated like myself. Clearly, the 32 bit UML kernel must work with the 32 bit Debian filesystem image for other people. Therefore there must be something about the environment that I am working in that causes this problem. Is this a result of a UML bug that makes it dependent on something unexpected? Or is it something that I'm doing wrong? What should "Couldn't grant pty - errno = -2" be telling me? Regards, David |
From: Richard W. <ri...@si...> - 2013-01-12 10:24:43
|
Am Sat, 12 Jan 2013 09:55:05 +0000 schrieb "Dave (Bob)" <da...@bo...>: > Maybe someone can help me with this... > > I have been trying to tie down an issue that I have with "UML Network > Related Crashing" so that Richard can reproduce my problem. > > I am currently trying to use both a 32 bit UML and a 64 bit UML to run > Debian root filesystems, 32 bit and 64 bit respectively. > > I am running on a 64 bit machine, with 64 bit kernel incorporating 32 > bit compatibility. > > The 32 bit environment that I am working in for the compilation of 32 > bit UML kernels and running them is a place to which I bind > mount /dev, /sys, /proc to their primary locations; chroot to the top > of this structure; execute 'linux32'; and then work as though I was > on a 32 bit machine. > > When I try to run the 32 bit UML kernel with the 32 bit Debian root > filesystem image, it boots to the login prompt, but I can't type > anything at the prompt. The UML kernel is displaying messages: > > "Couldn't grant pty - errno = -2" Please show us the full boot log. Maybe something else failed. Thanks, //richard |
From: Dave H. (Bob) <da...@bo...> - 2013-01-12 12:07:47
|
On Saturday 12 January 2013 10:58:12 Richard Weinberger wrote: > Am Sat, 12 Jan 2013 09:55:05 +0000 > > schrieb "Dave (Bob)" <da...@bo...>: > > Maybe someone can help me with this... > > > > I have been trying to tie down an issue that I have with "UML Network > > Related Crashing" so that Richard can reproduce my problem. > > > > I am currently trying to use both a 32 bit UML and a 64 bit UML to run > > Debian root filesystems, 32 bit and 64 bit respectively. > > > > I am running on a 64 bit machine, with 64 bit kernel incorporating 32 > > bit compatibility. > > > > The 32 bit environment that I am working in for the compilation of 32 > > bit UML kernels and running them is a place to which I bind > > mount /dev, /sys, /proc to their primary locations; chroot to the top > > of this structure; execute 'linux32'; and then work as though I was > > on a 32 bit machine. > > > > When I try to run the 32 bit UML kernel with the 32 bit Debian root > > filesystem image, it boots to the login prompt, but I can't type > > anything at the prompt. The UML kernel is displaying messages: > > > > "Couldn't grant pty - errno = -2" > > Please show us the full boot log. > Maybe something else failed. > > Thanks, > //richard Richard, Boot log below. 'startup' is: ../vmlinux-3.8.0-rc3-um32-def \ root=/dev/ubda \ eth0=tuntap,tap1 \ eth1=mcast \ ubd0=../Debian-Squeeze-x86-root_fs \ ubd1=swap_fs \ mem=512M \ umid=DEB1 -sh-4.2# ./startup Locating the bottom of the address space ... 0x0 Locating the top of the address space ... 0xffffd000 Core dump limits : soft - 0 hard - NONE Checking that ptrace can change system call numbers...OK Checking syscall emulation patch for ptrace...OK Checking advanced syscall emulation patch for ptrace...OK Checking for tmpfs mount on /dev/shm...OK Checking PROT_EXEC mmap in /dev/shm/...OK Checking for the skas3 patch in the host: - /proc/mm...not found: No such file or directory - PTRACE_FAULTINFO...not found - PTRACE_LDT...not found UML running in SKAS0 mode Adding 32870400 bytes to physical memory to account for exec-shield gap Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.8.0-rc3-um32-def (root@vault01) (gcc version 4.7.2 (GCC) ) #1 Fri Jan 11 09:13:28 UTC 2013 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 138010 Kernel command line: root=/dev/ubda eth0=tuntap,tap1 eth1=mcast ubd0=../Debian-Squeeze-x86-root_fs ubd1=swap_fs mem=512M PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 511712k available NR_IRQS:15 Calibrating delay loop... 7441.61 BogoMIPS (lpj=37208064) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 Initializing cgroup subsys cpuacct Initializing cgroup subsys devices Initializing cgroup subsys freezer Initializing cgroup subsys blkio Checking for host processor cmov support...Yes check_one_sigio failed, errno = 2 check_one_sigio failed, errno = 2 devtmpfs: initialized Using 2.6 host AIO NET: Registered protocol family 16 bio: create slab <bio-0> at 0 Switching to clocksource itimer NET: Registered protocol family 2 TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP: reno registered UDP hash table entries: 512 (order: 1, 8192 bytes) UDP-Lite hash table entries: 512 (order: 1, 8192 bytes) NET: Registered protocol family 1 mconsole (version 2) initialized on /home/root/.uml/DEB1/mconsole Checking host MADV_REMOVE support...OK Host TLS support detected Detected host type: x86_64 (GDT indexes 12 to 15) VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 999 io scheduler noop registered io scheduler deadline registered (default) TCP: cubic registered NET: Registered protocol family 17 Initialized stdio console driver Console initialized on /dev/tty0 console [tty0] enabled Initializing software serial port version 1 Configured mcast device: 239.192.168.1:1102-1 Choosing a random ethernet address for device eth1 Netdevice 1 (2e:79:6e:ed:c9:79) : mcast backend multicast address: 239.192.168.1:1102, TTL:1 console [mc-1] enabled ubda: unknown partition table ubdb: unknown partition table Choosing a random ethernet address for device eth0 Netdevice 0 (fa:06:fd:53:63:53) : TUN/TAP backend - EXT4-fs (ubda): mounting ext3 file system using the ext4 subsystem EXT4-fs (ubda): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext3 filesystem) readonly on device 98:0. devtmpfs: mounted modprobe: FATAL: Could not load /lib/modules/3.8.0-rc3-um32-def/modules.dep: No such file or directory INIT: version 2.88 booting Using makefile-style concurrent boot in runlevel S. Starting the hotplug events dispatcher: udevdudev[273]: starting version 164 . Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...udevd-work[284]: kernel-provided name 'hw_random' and NAME= 'hwrng' disagree, please use SYMLINK+= or change the kernel to provide the proper name done. Activating swap...done. EXT4-fs (ubda): re-mounted. Opts: (null) Cleaning up ifupdown.... Setting up networking.... Loading kernel modules...done. Activating lvm and md swap...done. Checking file systems...fsck from util-linux-ng 2.17.2 done. Mounting local filesystems...failed. Activating swapfile swap...done. Cleaning up temporary files.... Configuring network interfaces...Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/fa:06:fd:53:63:53 Sending on LPF/eth0/fa:06:fd:53:63:53 Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPNAK from 10.0.1.253 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 10.0.1.253 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 10.0.1.253 bound to 10.168.1.45 -- renewal in 109556 seconds. done. Cleaning up temporary files.... Setting kernel variables ...done. INIT: Entering runlevel: 2 Using makefile-style concurrent boot in runlevel 2. Starting enhanced syslogd: rsyslogd. Starting periodic command scheduler: cron. get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts Registering fd 0 twice Irqs : 2, 6 Ids : 0x298a3360, 0x298fbde0 Debian GNU/Linux 6.0 DEB1-32 tty0 DEB1-32 login: get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts get_pty : Couldn't grant pty - errno = -2 open_pts : Failed to open pts INIT: Id "s0" respawning too fast: disabled for 5 minutes |
From: Antoine M. <an...@na...> - 2013-01-12 12:50:56
|
> DEB1-32 login: get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > get_pty : Couldn't grant pty - errno = -2 > open_pts : Failed to open pts > INIT: Id "s0" respawning too fast: disabled for 5 minutes Since I made this root_fs, I guess I need to update the webpage as the this one is supposed to boot ok with UML, without any tty issues. Note however that I rarely use those filesystems with UML anymore, and many distros have repeatedly moved/changed/broken tty initialization in so many undocumented ways that I stopped caring a long time ago. That said, if someone finds the solution, I'll gladly apply it. Cheers Antoine |
From: Richard W. <ri...@si...> - 2013-01-12 14:30:07
|
Am Sat, 12 Jan 2013 19:34:34 +0700 schrieb Antoine Martin <an...@na...>: > > DEB1-32 login: get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > get_pty : Couldn't grant pty - errno = -2 > > open_pts : Failed to open pts > > INIT: Id "s0" respawning too fast: disabled for 5 minutes > Since I made this root_fs, I guess I need to update the webpage as the > this one is supposed to boot ok with UML, without any tty issues. > > Note however that I rarely use those filesystems with UML anymore, and > many distros have repeatedly moved/changed/broken tty initialization > in so many undocumented ways that I stopped caring a long time ago. > That said, if someone finds the solution, I'll gladly apply it. I test most of your filesystems on UML. Mostly the Debian ones on both x86_64 and x86. Bob, what exactly are you doing? I just did: make defconfig ARCH=um SUBARCH=x86 make linux ARCH=um SUBARCH=x86 # Image from http://fs.devloop.org.uk/filesystems/Debian-Squeeze/Debian-Squeeze-x86-root_fs.bz2^C ./linux ubda=Debian-Squeeze-x86-root_fs root=/dev/ubda mem=512M It boots like charm. *confused*, //richard |
From: Dave H. (Bob) <da...@bo...> - 2013-01-12 15:52:08
|
On Saturday 12 January 2013 15:29:47 Richard Weinberger wrote: > Am Sat, 12 Jan 2013 19:34:34 +0700 > > schrieb Antoine Martin <an...@na...>: > > > DEB1-32 login: get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > get_pty : Couldn't grant pty - errno = -2 > > > open_pts : Failed to open pts > > > INIT: Id "s0" respawning too fast: disabled for 5 minutes > > > > Since I made this root_fs, I guess I need to update the webpage as the > > this one is supposed to boot ok with UML, without any tty issues. > > > > Note however that I rarely use those filesystems with UML anymore, and > > many distros have repeatedly moved/changed/broken tty initialization > > in so many undocumented ways that I stopped caring a long time ago. > > That said, if someone finds the solution, I'll gladly apply it. > > I test most of your filesystems on UML. > Mostly the Debian ones on both x86_64 and x86. > > Bob, what exactly are you doing? > I just did: > > make defconfig ARCH=um SUBARCH=x86 > make linux ARCH=um SUBARCH=x86 > # Image from > http://fs.devloop.org.uk/filesystems/Debian-Squeeze/Debian-Squeeze-x86-root_ > fs.bz2^C ./linux ubda=Debian-Squeeze-x86-root_fs root=/dev/ubda mem=512M > > It boots like charm. > > *confused*, > //richard Gentlemen, I have re-tested my side, but this time running the 32 bit UML not in my chroot'ed 32 bit environment, but alongside the 64 bit. It works. The difference in the boot-up log is: Checking for host processor cmov support...Yes Checking that host ptys support output SIGIO...Yes Checking that host ptys support SIGIO on close...No, enabling workaround devtmpfs: initialized as opposed to: Checking for host processor cmov support...Yes check_one_sigio failed, errno = 2 check_one_sigio failed, errno = 2 devtmpfs: initialized Why would this be? I will now push on and attempt to either understand why I am getting my 'Network Related UML Crashing', or show how to reproduce it. However, understanding why this issue with my chroot'ed 32 bit method gives problems would be really advantageous (educational). The 32 bit kernel was built in the chroot'ed environment and is obviously linked with a 32 bit glibc. The default is not to link static, therefore I need the 32 bit glibc installed and working in the 64 world. If I remove the /lib/ld-linux.so.2 then the 32 bit kernel doesn't work (as expected). Regards, David |
From: Richard W. <ri...@si...> - 2013-01-12 16:00:43
|
Am Sat, 12 Jan 2013 16:51:52 +0100 (CET) > The difference in the boot-up log is: > > Checking for host processor cmov support...Yes > Checking that host ptys support output SIGIO...Yes > Checking that host ptys support SIGIO on close...No, enabling > workaround devtmpfs: initialized > > as opposed to: > > Checking for host processor cmov support...Yes > check_one_sigio failed, errno = 2 > check_one_sigio failed, errno = 2 > devtmpfs: initialized > > Why would this be? > > I will now push on and attempt to either understand why I am getting > my 'Network Related UML Crashing', or show how to reproduce it. > > However, understanding why this issue with my chroot'ed 32 bit method > gives problems would be really advantageous (educational). > > The 32 bit kernel was built in the chroot'ed environment and is > obviously linked with a 32 bit glibc. The default is not to link > static, therefore I need the 32 bit glibc installed and working in > the 64 world. If I remove the /lib/ld-linux.so.2 then the 32 bit > kernel doesn't work (as expected). Sounds like your chroot environment is incomplete. Maybe no /dev/ or /dev/pts/. Thanks, //richard |
From: Dave H. (Bob) <da...@bo...> - 2013-01-12 17:05:45
|
On Saturday 12 January 2013 17:00:02 Richard Weinberger wrote: > Am Sat, 12 Jan 2013 16:51:52 +0100 (CET) > > > The difference in the boot-up log is: > > > > Checking for host processor cmov support...Yes > > Checking that host ptys support output SIGIO...Yes > > Checking that host ptys support SIGIO on close...No, enabling > > workaround devtmpfs: initialized > > > > as opposed to: > > > > Checking for host processor cmov support...Yes > > check_one_sigio failed, errno = 2 > > check_one_sigio failed, errno = 2 > > devtmpfs: initialized > > > > Why would this be? > > > > I will now push on and attempt to either understand why I am getting > > my 'Network Related UML Crashing', or show how to reproduce it. > > > > However, understanding why this issue with my chroot'ed 32 bit method > > gives problems would be really advantageous (educational). > > > > The 32 bit kernel was built in the chroot'ed environment and is > > obviously linked with a 32 bit glibc. The default is not to link > > static, therefore I need the 32 bit glibc installed and working in > > the 64 world. If I remove the /lib/ld-linux.so.2 then the 32 bit > > kernel doesn't work (as expected). > > Sounds like your chroot environment is incomplete. Maybe no /dev/ > or /dev/pts/. > > Thanks, > //richard Richard, In the 64 bit environment (with additional 32 bit glibc) that works, I do: (/uml_test is a mount point for a filesystem) mount --bind /dev /<path_to_32_bit_stuff>/dev mount --bind /proc /<path_to_32_bit_stuff>/proc mount --bind /sys /<path_to_32_bit_stuff>/sys mount --bind /uml_test <path_to_32_bit_stuff>/uml_test chroot <path_to_32_bit_stuff> linux32 cd /uml_test/DEB1-32 ./startup Or, I do: cd /uml_test/DEB1-32 ./startup So the actual thing that is running, and the dev, sys, and proc filesystems, are all identical for the two situations. If the reason for this isn't clear to those more knowledgeable than I, then I am encouraged to investigate when I have my other problems out of the way. Regards, David |
From: Richard W. <ri...@si...> - 2013-01-12 22:07:10
|
Am Sat, 12 Jan 2013 18:05:28 +0100 (CET) schrieb "Dave Humphreys (Bob)" <da...@bo...>: > > Richard, > > In the 64 bit environment (with additional 32 bit glibc) that works, > I do: (/uml_test is a mount point for a filesystem) > > mount --bind /dev /<path_to_32_bit_stuff>/dev > mount --bind /proc /<path_to_32_bit_stuff>/proc > mount --bind /sys /<path_to_32_bit_stuff>/sys > mount --bind /uml_test <path_to_32_bit_stuff>/uml_test What about /dev/pts? Why the chroot anyways? Thanks, //richard |
From: Dave (Bob) <da...@bo...> - 2013-01-14 20:42:47
|
On 12/01/2013 22:06, Richard Weinberger wrote: > Am Sat, 12 Jan 2013 18:05:28 +0100 (CET) > schrieb "Dave Humphreys (Bob)" <da...@bo...>: >> Richard, >> >> In the 64 bit environment (with additional 32 bit glibc) that works, >> I do: (/uml_test is a mount point for a filesystem) >> >> mount --bind /dev /<path_to_32_bit_stuff>/dev >> mount --bind /proc /<path_to_32_bit_stuff>/proc >> mount --bind /sys /<path_to_32_bit_stuff>/sys >> mount --bind /uml_test <path_to_32_bit_stuff>/uml_test > What about /dev/pts? > Why the chroot anyways? > > Thanks, > //richard > > Richard, Well, of course, I was thinking that setting up the bind mount of /dev took everything else with it. I probably did know better, but it's my mistake. Explicitly adding: mount --bind /dev/pts /<path_to_32_bit_stuff>/dev/pts Makes everything work. Very sorry guys... Why chroot? I have had problems in the past with mixed environments. I maintain glibc and uclibc systems in various architectures, and find that keeping everything very separate keeps the confusion levels down. David |
From: Dave H. (Bob) <da...@bo...> - 2013-01-12 18:31:37
|
Re: [uml-devel] "Couldn't grant pty" Now that I have been able to run the Debiam 32 bit root_fs, I have returned to the network related crashing. This is by way of a status update, I will do more to tie down what is required to demonstrate the problem as simply as possible. However: root@DEB1-32:~# rsync --archive --progress 10.0.10.30:/var/imap/ /var/imap/ The authenticity of host '10.0.10.30 (10.0.10.30)' can't be established. RSA key fingerprint is ce:e4:0d:88:c0:07:01:8d:10:f8:91:52:b5:4b:e1:53. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '10.0.10.30' (RSA) to the list of known hosts. receiving incremental file list ./ .bash_history 1970 100% 1.88MB/s 0:00:00 (xfer#1, to-check=1005/1007) config/ config/annotations.db 144 100% 0.23kB/s 0:00:00 (xfer#2, to-check=1356/1362) config/deliver.db 0 0% 0.00kB/s 0:00:00 ------------[ cut here ]------------ This is what happened on the Debian 32 bit system with the 3.8.0-rc3 UML kernel. The DEB1 UML is now completely dead and locked up, no further messages escaped after this point. If I try to kick it with uml_mconsole: bash-4.1# uml_mconsole DEB1 (DEB1) halt and nothing more happens. 10.0.10.30 is another 32 bit UML. DEB1-32 is the Debian UML, with an IP address of 10.0.10.31. Networking is via mcast. This behaviour is consistent with what I have found all along. I have seen the same on a 32 bit UML running on a genuinely 32 bit machine that is remote to my current location and which I access via the Internet, so the problem arises using real ethernet (via tun-tap) as well as mcast; and in a genuine 32 bit environment. I will try to characterise this more fully, and simplify the method of causing failure as much as possible. I still believe that there is a real problem here, not just me doing something stupid. Regards, David |
From: Richard W. <ri...@si...> - 2013-01-12 22:11:35
|
Am Sat, 12 Jan 2013 19:31:13 +0100 (CET) schrieb "Dave Humphreys (Bob)" <da...@bo...>: > Re: [uml-devel] "Couldn't grant pty" > > Now that I have been able to run the Debiam 32 bit root_fs, I have > returned to the network related crashing. > > This is by way of a status update, I will do more to tie down what is > required to demonstrate the problem as simply as possible. > > However: > > root@DEB1-32:~# rsync --archive --progress > 10.0.10.30:/var/imap/ /var/imap/ The authenticity of host '10.0.10.30 > (10.0.10.30)' can't be established. RSA key fingerprint is > ce:e4:0d:88:c0:07:01:8d:10:f8:91:52:b5:4b:e1:53. Are you sure you > want to continue connecting (yes/no)? yes Warning: Permanently added > '10.0.10.30' (RSA) to the list of known hosts. receiving incremental > file list ./ > .bash_history > 1970 100% 1.88MB/s 0:00:00 (xfer#1, to-check=1005/1007) > config/ > config/annotations.db > 144 100% 0.23kB/s 0:00:00 (xfer#2, to-check=1356/1362) > config/deliver.db > 0 0% 0.00kB/s 0:00:00 ------------[ cut here > ]------------ > > > This is what happened on the Debian 32 bit system with the 3.8.0-rc3 > UML kernel. > > The DEB1 UML is now completely dead and locked up, no further > messages escaped after this point. > > If I try to kick it with uml_mconsole: > > bash-4.1# uml_mconsole DEB1 > (DEB1) halt > > and nothing more happens. > > 10.0.10.30 is another 32 bit UML. > > DEB1-32 is the Debian UML, with an IP address of 10.0.10.31. > > Networking is via mcast. > > This behaviour is consistent with what I have found all along. > > I have seen the same on a 32 bit UML running on a genuinely 32 bit > machine that is remote to my current location and which I access via > the Internet, so the problem arises using real ethernet (via tun-tap) > as well as mcast; and in a genuine 32 bit environment. > > I will try to characterise this more fully, and simplify the method > of causing failure as much as possible. Thanks a lot for the detailed report. Does UML consume 100% on the host side? Thanks, //richard |