- Locating the bottom of the address space ... 0x1000
- Locating the top of the address space ... 0xc0000000
- 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
- Linux version 2.6.33.16 (xchg@smasher) (gcc version 4.4.4 (GCC) ) #2 Fri Jul 15 17:38:36 CEST 2011
- Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
- Kernel command line: ubd0=/dev/sda6 root=98:0
- PID hash table entries: 128 (order: -3, 512 bytes)
- Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
- Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
- Memory: 29888k available
- Hierarchical RCU implementation.
- RCU-based detection of stalled CPUs is enabled.
- NR_IRQS:15
- Calibrating delay loop... 1677.72 BogoMIPS (lpj=8388608)
- Mount-cache hash table entries: 512
- 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
- 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
- IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
- TCP established hash table entries: 1024 (order: 1, 8192 bytes)
- TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
- TCP: Hash tables configured (established 1024 bind 1024)
- TCP reno registered
- UDP hash table entries: 256 (order: 0, 4096 bytes)
- UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
- NET: Registered protocol family 1
- IRQ 9/mconsole: IRQF_DISABLED is not guaranteed on shared IRQs
- mconsole (version 2) initialized on /home/xchg/.uml/tWUeUH/mconsole
- Checking host MADV_REMOVE support...OK
- Host TLS support detected
- Detected host type: i386 (GDT indexes 6 to 9)
- VFS: Disk quotas dquot_6.5.2
- Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
- msgmni has been set to 58
- io scheduler noop registered
- io scheduler deadline registered
- io scheduler cfq 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
- console [mc-1] enabled
- ubda: detected capacity change from 0 to 14221476864
- ubda: unknown partition table
- EXT3-fs (ubda): error: couldn't mount because of unsupported optional features (240)
- EXT2-fs (ubda): error: couldn't mount because of unsupported optional features (240)
- EXT4-fs (ubda): mounted filesystem with ordered data mode
- VFS: Mounted root (ext4 filesystem) readonly on device 98:0.
- IRQ 3/console-write: IRQF_DISABLED is not guaranteed on shared IRQs
- IRQ 2/console: IRQF_DISABLED is not guaranteed on shared IRQs
- IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs
- IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs
- IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs
- INIT: IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs
- version 2.86 bootingIRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs
- IRQ 10/winch: IRQF_DISABLED is not guaranteed on shared IRQs
- proc on /proc type proc (rw)
- sysfs on /sys type sysfs (rw)
- Triggering udev events: /sbin/udevadm trigger --action=add
- Loading fuse module failed!
- Setting system time from the hardware clock (localtime).
- hwclock is unable to get I/O port access: the iopl(3) call failed.
- Testing root filesystem status: read-only filesystem
- Checking root filesystem:
- fsck from util-linux 2.19
- /sbin/e2fsck: No such file or directory while trying to open /dev/sda6
- Possibly non-existent device?
- ***********************************************************
- *** An error occurred during the root filesystem check. ***
- *** You will now be given a chance to log into the ***
- *** system in single-user mode to fix the problem. ***
- *** ***
- *** If you are using the ext2 filesystem, running ***
- *** 'e2fsck -v -y <partition>' might help. ***
- ***********************************************************
- Once you exit the single-user shell, the system will reboot.
- Type control-d to proceed with normal startup,
- (or give root password for system maintenance):