Xen 3.3 + Vanilla 2.6.28 amd64 + ubuntu = init[1] general protection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When compiling myself a slimline Kernel, Ubuntu doesn't work as domU:
Started domain ubuntu-test
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 1, 8192 bytes)
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
platform rtc_cmos: registered platform RTC device (no PNP device found)
fuse init (API version 7.10)
io scheduler noop registered (default)
Initialising Xen virtual ethernet driver.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
IO APIC resources could be not be allocated.
blkfront: xvda1: barriers enabled
XENBUS: Device with no driver: device/console/0
ReiserFS: xvda1: found reiserfs format "3.6" with standard journal
ReiserFS: xvda1: using ordered data mode
ReiserFS: xvda1: journal params: device xvda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: xvda1: checking transaction log (xvda1)
ReiserFS: xvda1: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem).
Freeing unused kernel memory: 244k freed
init[1] general protection ip:ffffe42f sp:ffea8d04 error:0
Kernel panic - not syncing: Attempted to kill init!
xm dmesg shows:
(XEN) mm.c:676:d62 Non-privileged (62) attempt to map I/O space 000000f0
(XEN) traps.c:2134:d90 Domain attempted WRMSR 00000000c0000081 from e023e008:00000000 to 00230010:00000000.
(XEN) traps.c:2134:d90 Domain attempted WRMSR 00000000c0000082 from ffff8300:cf0bb000 to ffffffff:80210200.
(XEN) traps.c:2134:d90 Domain attempted WRMSR 00000000c0000083 from ffff8300:cf0bb080 to ffffffff:80432a00.
(XEN) traps.c:2134:d90 Domain attempted WRMSR 0000000000000174 from 00000000:00000000 to 00000000:00000010.
(XEN) traps.c:2134:d90 Domain attempted WRMSR 0000000000000176 from 00000000:00000000 to ffffffff:80229410.
(XEN) traps.c:2134:d90 Domain attempted WRMSR 00000000c0000083 from ffff8300:cf0bb080 to ffffffff:802295d0.
(XEN) traps.c:2134:d90 Domain attempted WRMSR 00000000c0000084 from 00000000:00034700 to 00000000:00003700.
(XEN) domain.c:506:d90 Attempt to change CR4 flags 00000660 -> 00000620
A different Kernel does work! (vmlinuz-
Ubuntu is 32Bit. A Gentoo stage1 tarball (32bit and 64bit) does work!
What's wrong here? A bug / wrong compile flag in libc?
kernel .config for the 2.6.28 was:
CONFIG_64BIT=y
CONFIG_AIO=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_AUDIT_ARCH=y
CONFIG_BASE_FULL=y
CONFIG_BASE_SMALL=0
CONFIG_BINFMT_ELF=y
CONFIG_BLK_DEV=y
CONFIG_
CONFIG_BLOCK=y
CONFIG_BOUNCE=y
CONFIG_
CONFIG_BUG=y
CONFIG_CIFS_POSIX=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_COMPAT=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_DMI=y
CONFIG_
CONFIG_
CONFIG_ELF_CORE=y
CONFIG_EPOLL=y
CONFIG_EVENTFD=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_EXT3_FS=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_FS_MBCACHE=y
CONFIG_
CONFIG_FUSE_FS=y
CONFIG_FUTEX=y
CONFIG_FW_LOADER=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_HAS_DMA=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_HAVE_IDE=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_HAVE_KVM=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_HOTPLUG=y
CONFIG_HPET_TIMER=y
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
CONFIG_HW_CONSOLE=y
CONFIG_HZ=250
CONFIG_HZ_250=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_INET_DIAG=y
CONFIG_
CONFIG_
CONFIG_INET=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_INPUT=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_IP_PNP=y
CONFIG_
CONFIG_IPV6_SIT=y
CONFIG_IPV6=y
CONFIG_
CONFIG_JBD=y
CONFIG_KALLSYMS=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_LOCKD_V4=y
CONFIG_LOCKD=y
CONFIG_
CONFIG_MMU=y
CONFIG_
CONFIG_NAMESPACES=y
CONFIG_NETDEVICES=y
CONFIG_
CONFIG_NET=y
CONFIG_
CONFIG_NFS_COMMON=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V3=y
CONFIG_
CONFIG_NLS_UTF8=y
CONFIG_NLS=y
CONFIG_
CONFIG_PACKET=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_PARAVIRT=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_PLIST=y
CONFIG_
CONFIG_PRINTK=y
CONFIG_PROC_FS=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_ROOT_NFS=y
CONFIG_RT_MUTEXES=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_SERIO=y
CONFIG_SHMEM=y
CONFIG_SIGNALFD=y
CONFIG_SLABINFO=y
CONFIG_SLUB_DEBUG=y
CONFIG_SLUB=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_SPARSEMEM=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_STANDALONE=y
CONFIG_SUNRPC=y
CONFIG_
CONFIG_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_
CONFIG_TIMERFD=y
CONFIG_
CONFIG_
CONFIG_UID16=y
CONFIG_
CONFIG_UNIX=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_VT_CONSOLE=y
CONFIG_VT=y
CONFIG_X86_64=y
CONFIG_
CONFIG_X86_CMOV=y
CONFIG_
CONFIG_
CONFIG_X86_CPU=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_X86_PC=y
CONFIG_X86_TSC=y
CONFIG_
CONFIG_X86=y
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_
CONFIG_XEN=y
CONFIG_XFRM=y
CONFIG_ZONE_DMA32=y
CONFIG_
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
4. what version of ubuntu do you use?
Thanks!