|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] problem using compiled kernel -- Sisu
On 07/26/2010 10:48 PM, Sisu Xi wrote: Hi, Jeremy: I have retried Linux 2.6.32.16 on Ubuntu 10.04, with Xen 4.0, using your git. the vmlinux and .config file is attached. This time it shows the following error on the serial console: Please try to capture a *full* log output. If you're using "screen" you should be able to save everything to a logfile. [ 0.000000] Xen version: 4.0.1-rc5-pre (preserve-AD) (dom0) [ 0.000000] NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 15 pages/cpu @cb6dc000 s39320 r0 d22120 u65536 [ 0.000000] pcpu-alloc: s39320 r0 d22120 u65536 alloc=16*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Xen: using vcpu_info placement [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 481035 [ 0.000000] Kernel command line: earlyprintk=xen [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Enabling fast FPU save and restore... done. [ 0.000000] Enabling unmasked SIMD FPU exception support... done. [ 0.000000] Initializing CPU#0 [ 0.000000] allocated 9698480 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] DMA: Placing 64MB software IO TLB between cc100000 - d0100000 [ 0.000000] DMA: software IO TLB at phys 0xc100000 - 0x10100000 [ 0.000000] xen_swiotlb_fixup: buf=cc100000 size=67108864 [ 0.000000] xen_swiotlb_fixup: buf=d0160000 size=32768 [ 0.000000] Initializing HighMem for node 0 (0002d1fe:0007663c) [ 0.000000] Memory: 1676984k/1939696k available (4734k kernel code, 261416k reserved, 2167k data, 680k init, 1200376k highmem) [ 0.000000] virtual kernel memory layout: [ 0.000000] fixmap : 0xf571e000 - 0xf57ff000 ( 900 kB) [ 0.000000] pkmap : 0xf5200000 - 0xf5400000 (2048 kB) [ 0.000000] vmalloc : 0xed9fe000 - 0xf51fe000 ( 120 MB) [ 0.000000] lowmem : 0xc0000000 - 0xed1fe000 ( 721 MB) [ 0.000000] .init : 0xc07be000 - 0xc0868000 ( 680 kB) [ 0.000000] .data : 0xc059fa33 - 0xc07bd8e8 (2167 kB) [ 0.000000] .text : 0xc0100000 - 0xc059fa33 (4734 kB) [ 0.000000] SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:2304 nr_irqs:768 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1 [ 0.000000] xen_allocate_pirq: returning irq 9 for gsi 9 [ 0.000000] xen: acpi sci 9 [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [tty0] enabled, bootconsole disabled (XEN) PCI add device 00:00.0 (XEN) PCI add device 00:01.0 (XEN) PCI add device 00:1c.0 (XEN) PCI add device 00:1c.1 (XEN) PCI add device 00:1d.0 (XEN) PCI add device 00:1d.1 (XEN) PCI add device 00:1d.2 (XEN) PCI add device 00:1d.3 (XEN) PCI add device 00:1d.7 (XEN) PCI add device 00:1e.0 (XEN) PCI add device 00:1e.2 (XEN) PCI add device 00:1f.0 (XEN) PCI add device 00:1f.1 (XEN) PCI add device 00:1f.2 (XEN) PCI add device 00:1f.3 (XEN) PCI add device 01:00.0 (XEN) PCI add device 01:00.1 (XEN) PCI add device 02:00.0 (XEN) PCI add device 04:00.0 after that, the serial output stops, and the target machines stops at the: usbhid: v2.6: USB HID core driver Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) -check rootdelay= (did the system wait long enough?) -check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! does not exist. Dropping to a shell! BusyBox built-in shell (ash) (initramfs) Could you help me with this? Not really. This is quite different from the original report of an early oops, which was clearly a kernel problem. This seems to be something wrong with your kernel config (either compile-time or runtime). Make sure you have device drivers enabled for all your devices, that your initrd contains those drivers, and your distros startup scripts are doing the right thing. I'm not familiar with any busybox-using distros, so I can't help in detail. Make sure your console on the kernel command line is "console=hvc0", and "ignore_loglevel" is also useful to make sure all the console output is printed.
Thanks,
J
Thanks very much! Best! Yours, Sisu On Mon, Jul 26, 2010 at 10:08 PM, Sisu Xi<xisisu@xxxxxxxxx> wrote:I download them directly from kernel.org and configured it following the tutorial. I have also tried both the 2.6.32.16 kernel and the 2.6.31.13 kernel from git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git, they all give the same error message thanks very much! Best! Yours, Sisu On Mon, Jul 26, 2010 at 10:05 PM, Jeremy Fitzhardinge<jeremy@xxxxxxxx> wrote:On 07/26/2010 07:15 PM, Sisu Xi wrote:Sorry I forgot to attach the file. Here they are. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |