Xen devel - Jun 2007 - Xen doesnt recognize my root fs, while native kernel can ???

Hello,

I am in a strange situation: I am compiling Xen 3.1 for my machine
with SATA. Xen cannot recognize the root filesystem, and stopped with
a message like "Cannot mount /dev/sda2,....".

Usually, that means Dom0 has no suitable drivers, and I could always
solve the same problem before by choosing the correct drivers for Dom0
kernel.

However, it is different this time: I tried everything I can, but that
problem stands.

I even tried to compile the native kernel 2.6.18, and boot with that
kernel (ie. no Xen). It boots well. Then I copied the same option to
Dom0''s .config, and recompile Dom0. But it doesnt help!!!

So I am wondering what is a good reason why Dom0 cannot recognize my
root filesystem, why native kernel can? That doesnt make any sense to
me at all.

Below is the diff of Dom0''s .config, and native 2.6.18 .config. You
can see that the difference betweem these configurations has nothing
to do with drivers at all.

Any suggestion is appreciated!

Thanks,
Jun



@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don''t edit
-# Linux kernel version: 2.6.18-xen0
-# Wed Jun 13 12:29:14 2007
+# Linux kernel version: 2.6.18
+# Tue Jun 12 14:55:18 2007
 #
 CONFIG_X86_64=y
 CONFIG_64BIT=y
@@ -105,39 +105,57 @@ CONFIG_X86_PC=y
 # CONFIG_MK8 is not set
 CONFIG_MPSC=y
 # CONFIG_GENERIC_CPU is not set
-CONFIG_X86_64_XEN=y
-CONFIG_X86_NO_TSS=y
-CONFIG_X86_NO_IDT=y
 CONFIG_X86_L1_CACHE_BYTES=128
 CONFIG_X86_L1_CACHE_SHIFT=7
 CONFIG_X86_INTERNODE_CACHE_BYTES=128
+CONFIG_X86_TSC=y
 CONFIG_X86_GOOD_APIC=y
 # CONFIG_MICROCODE is not set
 # CONFIG_X86_MSR is not set
 # CONFIG_X86_CPUID is not set
+CONFIG_X86_HT=y
 CONFIG_X86_IO_APIC=y
-CONFIG_X86_XEN_GENAPIC=y
 CONFIG_X86_LOCAL_APIC=y
 # CONFIG_MTRR is not set
 CONFIG_SMP=y
+# CONFIG_SCHED_SMT is not set
+CONFIG_SCHED_MC=y
 # CONFIG_PREEMPT_NONE is not set
 CONFIG_PREEMPT_VOLUNTARY=y
 # CONFIG_PREEMPT is not set
 CONFIG_PREEMPT_BKL=y
-CONFIG_ARCH_FLATMEM_ENABLE=y
+CONFIG_NUMA=y
+# CONFIG_K8_NUMA is not set
+CONFIG_NODES_SHIFT=6
+CONFIG_X86_64_ACPI_NUMA=y
+# CONFIG_NUMA_EMU is not set
+CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
+CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
+CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_SELECT_MEMORY_MODEL=y
-CONFIG_FLATMEM_MANUAL=y
-# CONFIG_DISCONTIGMEM_MANUAL is not set
+# CONFIG_FLATMEM_MANUAL is not set
+CONFIG_DISCONTIGMEM_MANUAL=y
 # CONFIG_SPARSEMEM_MANUAL is not set
-CONFIG_FLATMEM=y
+CONFIG_DISCONTIGMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
+CONFIG_NEED_MULTIPLE_NODES=y
 # CONFIG_SPARSEMEM_STATIC is not set
-CONFIG_SPLIT_PTLOCK_CPUS=4096
+CONFIG_SPLIT_PTLOCK_CPUS=4
+# CONFIG_MIGRATION is not set
 CONFIG_RESOURCES_64BIT=y
+CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
+CONFIG_OUT_OF_LINE_PFN_TO_PAGE=y
 CONFIG_NR_CPUS=8
 CONFIG_HOTPLUG_CPU=y
 CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
+CONFIG_HPET_TIMER=y
+# CONFIG_HPET_EMULATE_RTC is not set
+CONFIG_IOMMU=y
+# CONFIG_CALGARY_IOMMU is not set
 CONFIG_SWIOTLB=y
+CONFIG_X86_MCE=y
+# CONFIG_X86_MCE_INTEL is not set
+# CONFIG_X86_MCE_AMD is not set
 # CONFIG_KEXEC is not set
 # CONFIG_CRASH_DUMP is not set
 CONFIG_PHYSICAL_START=0x200000
@@ -157,36 +175,71 @@ CONFIG_GENERIC_PENDING_IRQ=y
 # Power management options
 #
 CONFIG_PM=y
+CONFIG_PM_LEGACY=y
+CONFIG_PM_DEBUG=y
+CONFIG_SOFTWARE_SUSPEND=y
+CONFIG_PM_STD_PARTITION=""
+CONFIG_SUSPEND_SMP=y

 #
 # ACPI (Advanced Configuration and Power Interface) Support
 #
 CONFIG_ACPI=y
-CONFIG_ACPI_AC=y
-CONFIG_ACPI_BATTERY=y
-CONFIG_ACPI_BUTTON=y
-# CONFIG_ACPI_VIDEO is not set
+CONFIG_ACPI_SLEEP=y
+CONFIG_ACPI_SLEEP_PROC_FS=y
+CONFIG_ACPI_SLEEP_PROC_SLEEP=y
+CONFIG_ACPI_AC=m
+CONFIG_ACPI_BATTERY=m
+CONFIG_ACPI_BUTTON=m
+CONFIG_ACPI_VIDEO=m
 # CONFIG_ACPI_HOTKEY is not set
-CONFIG_ACPI_FAN=y
-# CONFIG_ACPI_DOCK is not set
-CONFIG_ACPI_PROCESSOR=y
+CONFIG_ACPI_FAN=m
+CONFIG_ACPI_DOCK=m
+CONFIG_ACPI_PROCESSOR=m
 CONFIG_ACPI_HOTPLUG_CPU=y
-CONFIG_ACPI_THERMAL=y
-# CONFIG_ACPI_ASUS is not set
-# CONFIG_ACPI_IBM is not set
-# CONFIG_ACPI_TOSHIBA is not set
+CONFIG_ACPI_THERMAL=m
+CONFIG_ACPI_NUMA=y
+CONFIG_ACPI_ASUS=m
+CONFIG_ACPI_IBM=m
+CONFIG_ACPI_TOSHIBA=m
 CONFIG_ACPI_BLACKLIST_YEAR=0
 # CONFIG_ACPI_DEBUG is not set
 CONFIG_ACPI_EC=y
 CONFIG_ACPI_POWER=y
 CONFIG_ACPI_SYSTEM=y
-CONFIG_ACPI_CONTAINER=y
-# CONFIG_ACPI_SBS is not set
+CONFIG_X86_PM_TIMER=y
+CONFIG_ACPI_CONTAINER=m
+CONFIG_ACPI_SBS=m

 #
 # CPU Frequency scaling
 #
-# CONFIG_CPU_FREQ is not set
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_TABLE=m
+# CONFIG_CPU_FREQ_DEBUG is not set
+CONFIG_CPU_FREQ_STAT=m
+CONFIG_CPU_FREQ_STAT_DETAILS=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
+# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
+CONFIG_CPU_FREQ_GOV_POWERSAVE=m
+CONFIG_CPU_FREQ_GOV_USERSPACE=m
+CONFIG_CPU_FREQ_GOV_ONDEMAND=m
+CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m
+
+#
+# CPUFreq processor drivers
+#
+CONFIG_X86_POWERNOW_K8=m
+CONFIG_X86_POWERNOW_K8_ACPI=y
+# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
+CONFIG_X86_ACPI_CPUFREQ=m
+
+#
+# shared options
+#
+# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
+# CONFIG_X86_SPEEDSTEP_LIB is not set

 #
 # Bus options (PCI etc.)
@@ -194,11 +247,10 @@ CONFIG_ACPI_CONTAINER=y
 CONFIG_PCI=y
 CONFIG_PCI_DIRECT=y
 # CONFIG_PCI_MMCONFIG is not set
-CONFIG_XEN_PCIDEV_FRONTEND=y
-# CONFIG_XEN_PCIDEV_FE_DEBUG is not set
 CONFIG_PCIEPORTBUS=y
 CONFIG_HOTPLUG_PCI_PCIE=m
 # CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
+CONFIG_PCI_MSI=y
 # CONFIG_PCI_DEBUG is not set

 #
@@ -211,7 +263,8 @@ CONFIG_HOTPLUG_PCI_PCIE=m
 #
 CONFIG_HOTPLUG_PCI=m
 CONFIG_HOTPLUG_PCI_FAKE=m
-# CONFIG_HOTPLUG_PCI_ACPI is not set
+CONFIG_HOTPLUG_PCI_ACPI=m
+CONFIG_HOTPLUG_PCI_ACPI_IBM=m
 CONFIG_HOTPLUG_PCI_CPCI=y
 CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
 CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
@@ -501,7 +554,13 @@ CONFIG_FW_LOADER=y
 #
 # Plug and Play support
 #
-# CONFIG_PNP is not set
+CONFIG_PNP=y
+# CONFIG_PNP_DEBUG is not set
+
+#
+# Protocols
+#
+CONFIG_PNPACPI=y

 #
 # Block devices
@@ -549,6 +608,7 @@ CONFIG_BLK_DEV_IDESCSI=m
 #
 CONFIG_IDE_GENERIC=y
 # CONFIG_BLK_DEV_CMD640 is not set
+# CONFIG_BLK_DEV_IDEPNP is not set
 CONFIG_BLK_DEV_IDEPCI=y
 CONFIG_IDEPCI_SHARE_IRQ=y
 # CONFIG_BLK_DEV_OFFBOARD is not set
@@ -700,6 +760,7 @@ CONFIG_NETDEVICES=y
 # CONFIG_BONDING is not set
 # CONFIG_EQUALIZER is not set
 CONFIG_TUN=m
+# CONFIG_NET_SB1000 is not set

 #
 # ARCnet devices
@@ -855,8 +916,10 @@ CONFIG_STALDRV=y
 #
 # Serial drivers
 #
-CONFIG_SERIAL_8250=m
-CONFIG_SERIAL_8250_PCI=m
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_PCI=y
+CONFIG_SERIAL_8250_PNP=y
 CONFIG_SERIAL_8250_NR_UARTS=48
 CONFIG_SERIAL_8250_RUNTIME_UARTS=4
 CONFIG_SERIAL_8250_EXTENDED=y
@@ -868,7 +931,8 @@ CONFIG_SERIAL_8250_RSA=y
 #
 # Non-8250 serial port support
 #
-CONFIG_SERIAL_CORE=m
+CONFIG_SERIAL_CORE=y
+CONFIG_SERIAL_CORE_CONSOLE=y
 CONFIG_SERIAL_JSM=m
 CONFIG_UNIX98_PTYS=y
 CONFIG_LEGACY_PTYS=y
@@ -960,15 +1024,19 @@ CONFIG_PC8736x_GPIO=m
 CONFIG_NSC_GPIO=m
 CONFIG_RAW_DRIVER=m
 CONFIG_MAX_RAW_DEVS=256
-# CONFIG_HPET is not set
+CONFIG_HPET=y
+# CONFIG_HPET_RTC_IRQ is not set
+CONFIG_HPET_MMAP=y
 CONFIG_HANGCHECK_TIMER=m

 #
 # TPM devices
 #
 CONFIG_TCG_TPM=m
+CONFIG_TCG_TIS=m
+CONFIG_TCG_NSC=m
 CONFIG_TCG_ATMEL=m
-# CONFIG_TCG_XEN is not set
+CONFIG_TCG_INFINEON=m
 CONFIG_TELCLOCK=m

 #
@@ -1145,6 +1213,7 @@ CONFIG_FIRMWARE_EDID=y
 #
 CONFIG_VGA_CONSOLE=y
 # CONFIG_VGACON_SOFT_SCROLLBACK is not set
+CONFIG_VIDEO_SELECT=y
 CONFIG_DUMMY_CONSOLE=y
 CONFIG_BACKLIGHT_LCD_SUPPORT=y
 CONFIG_BACKLIGHT_CLASS_DEVICE=y
@@ -1172,7 +1241,7 @@ CONFIG_USB=m
 CONFIG_USB_DEVICEFS=y
 # CONFIG_USB_BANDWIDTH is not set
 # CONFIG_USB_DYNAMIC_MINORS is not set
-# CONFIG_USB_SUSPEND is not set
+CONFIG_USB_SUSPEND=y
 # CONFIG_USB_OTG is not set

 #
@@ -1330,6 +1399,7 @@ CONFIG_USB_NET_ZAURUS=m
 # InfiniBand support
 #
 # CONFIG_INFINIBAND is not set
+# CONFIG_IPATH_CORE is not set

 #
 # EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
@@ -1386,6 +1456,7 @@ CONFIG_INTEL_IOATDMA=m
 #
 # Firmware Drivers
 #
+# CONFIG_EDD is not set
 CONFIG_DELL_RBU=m
 CONFIG_DCDBAS=m

@@ -1444,6 +1515,7 @@ CONFIG_PROC_FS=y
 CONFIG_PROC_KCORE=y
 CONFIG_SYSFS=y
 CONFIG_TMPFS=y
+# CONFIG_HUGETLBFS is not set
 # CONFIG_HUGETLB_PAGE is not set
 CONFIG_RAMFS=y
 CONFIG_CONFIGFS_FS=m
@@ -1568,6 +1640,7 @@ CONFIG_DEBUG_FS=y
 # CONFIG_FORCED_INLINING is not set
 # CONFIG_RCU_TORTURE_TEST is not set
 # CONFIG_DEBUG_RODATA is not set
+# CONFIG_IOMMU_DEBUG is not set
 # CONFIG_DEBUG_STACKOVERFLOW is not set
 # CONFIG_DEBUG_STACK_USAGE is not set

@@ -1610,40 +1683,6 @@ CONFIG_CRYPTO_TEST=m
 #
 # Hardware crypto devices
 #
-CONFIG_XEN=y
-CONFIG_XEN_INTERFACE_VERSION=0x00030205
-
-#
-# XEN
-#
-CONFIG_XEN_PRIVILEGED_GUEST=y
-# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
-CONFIG_XEN_PRIVCMD=y
-CONFIG_XEN_XENBUS_DEV=y
-CONFIG_XEN_BACKEND=y
-CONFIG_XEN_BLKDEV_BACKEND=y
-CONFIG_XEN_BLKDEV_TAP=y
-CONFIG_XEN_NETDEV_BACKEND=y
-# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
-CONFIG_XEN_NETDEV_LOOPBACK=y
-CONFIG_XEN_PCIDEV_BACKEND=y
-CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
-# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
-# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
-# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
-# CONFIG_XEN_TPMDEV_BACKEND is not set
-# CONFIG_XEN_BLKDEV_FRONTEND is not set
-# CONFIG_XEN_NETDEV_FRONTEND is not set
-CONFIG_XEN_SCRUB_PAGES=y
-CONFIG_XEN_DISABLE_SERIAL=y
-CONFIG_XEN_SYSFS=y
-CONFIG_XEN_COMPAT_030002_AND_LATER=y
-# CONFIG_XEN_COMPAT_030004_AND_LATER is not set
-# CONFIG_XEN_COMPAT_LATEST_ONLY is not set
-CONFIG_XEN_COMPAT=0x030002
-CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
-CONFIG_NO_IDLE_HZ=y
-CONFIG_XEN_SMPBOOT=y

 #
 # Library routines

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 13/6/07 07:31, "Jun Koi" <junkoi2004@gmail.com> wrote:
> Below is the diff of Dom0''s .config, and native 2.6.18 .config.
You
> can see that the difference betweem these configurations has nothing
> to do with drivers at all.
> 
> Any suggestion is appreciated!
Please post output from native boot (dmesg), XenLinux boot (dmesg), and
Xen''s boot output (xm dmesg). Run Xen with boot option
''loglvl=all'' to make
sure you actually get all of Xen''s output.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi Keir,

On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
wrote:
>
>
>
> On 13/6/07 07:31, "Jun Koi" <junkoi2004@gmail.com> wrote:
>
> > Below is the diff of Dom0''s .config, and native 2.6.18
.config. You
> > can see that the difference betweem these configurations has nothing
> > to do with drivers at all.
> >
> > Any suggestion is appreciated!
>
> Please post output from native boot (dmesg), XenLinux boot (dmesg), and
> Xen''s boot output (xm dmesg). Run Xen with boot option
''loglvl=all'' to make
> sure you actually get all of Xen''s output.
>
The point is that Xen doesnt boot in the first place, so I cannot
provide xm dmesg!

Below is the output from dmesg (native kernel) and Dom0''s .config.
Anything else do you need?

Thank you,
Jun

dmesg
--------
Bootdata ok (command line is root=/dev/sda2 ro)
Linux version 2.6.18 (root@mpc) (gcc version 4.1.2 (Ubuntu
4.1.2-0ubuntu4)) #4 SMP Tue Jun 12 14:57:00 JST 2007
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000008f000 (usable)
 BIOS-e820: 000000000008f000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000007d554000 (usable)
 BIOS-e820: 000000007d554000 - 000000007dd55000 (ACPI NVS)
 BIOS-e820: 000000007dd55000 - 000000007e594000 (usable)
 BIOS-e820: 000000007e594000 - 000000007e5a1000 (reserved)
 BIOS-e820: 000000007e5a1000 - 000000007e66f000 (usable)
 BIOS-e820: 000000007e66f000 - 000000007e6a3000 (ACPI NVS)
 BIOS-e820: 000000007e6a3000 - 000000007e6a7000 (ACPI data)
 BIOS-e820: 000000007e6a7000 - 000000007e6f0000 (ACPI NVS)
 BIOS-e820: 000000007e6f0000 - 000000007e6f1000 (ACPI data)
 BIOS-e820: 000000007e6f1000 - 000000007e6f2000 (usable)
 BIOS-e820: 000000007e6f2000 - 000000007e6ff000 (ACPI data)
 BIOS-e820: 000000007e6ff000 - 000000007e700000 (usable)
 BIOS-e820: 000000007e700000 - 000000007f000000 (reserved)
 BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
DMI 2.4 present.
ACPI: RSDP (v000 INTEL                                 ) @ 0x00000000000fe020
ACPI: RSDT (v001 INTEL  DG965CO  0x00001575      0x01000013) @
0x000000007e6fd038
ACPI: FADT (v001 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x000000007e6fc000
ACPI: MADT (v001 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x000000007e6f6000
ACPI: WDDT (v001 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x000000007e6f5000
ACPI: MCFG (v001 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x000000007e6f4000
ACPI: ASF! (v032 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x000000007e6f3000
ACPI: HPET (v001 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x000000007e6f2000
ACPI: SSDT (v001 INTEL     CpuPm 0x00001575 MSFT 0x01000013) @
0x000000007e6f0000
ACPI: SSDT (v001 INTEL   Cpu0Ist 0x00001575 MSFT 0x01000013) @
0x000000007e6a6000
ACPI: SSDT (v001 INTEL   Cpu1Ist 0x00001575 MSFT 0x01000013) @
0x000000007e6a5000
ACPI: SSDT (v001 INTEL   Cpu2Ist 0x00001575 MSFT 0x01000013) @
0x000000007e6a4000
ACPI: SSDT (v001 INTEL   Cpu3Ist 0x00001575 MSFT 0x01000013) @
0x000000007e6a3000
ACPI: TCPA (v001 INTEL  TIANO    0x00000002 MSFT 0x01000013) @
0x000000007e66f000
ACPI: DSDT (v001 INTEL  DG965CO  0x00001575 MSFT 0x01000013) @
0x0000000000000000
No NUMA configuration found
Faking a node at 0000000000000000-000000007e700000
Bootmem setup node 0 0000000000000000-000000007e700000
On node 0 totalpages: 507470
  DMA zone: 2907 pages, LIFO batch:0
  DMA32 zone: 504563 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to physical flat
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 80000000 (gap: 7f000000:80e00000)
SMP: Allowing 4 CPUs, 2 hotplug CPUs
Built 1 zonelists.  Total pages: 507470
Kernel command line: root=/dev/sda2 ro
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer.
time.c: Detected 2664.012 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Checking aperture...
Memory: 2026568k/2071552k available (2110k kernel code, 35712k
reserved, 1158k data, 180k init)
Calibrating delay using timer specific routine.. 5332.49 BogoMIPS (lpj=10664987)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
Using local APIC timer interrupts.
result 16650066
Detected 16.650 MHz APIC timer.
SMP alternatives: switching to SMP code
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 5328.08 BogoMIPS (lpj=10656160)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Intel(R) Core(TM)2 CPU          6700  @ 2.66GHz stepping 06
Brought up 2 CPUs
testing NMI watchdog ... OK.
migration_cost=17
PM: Adding info for No Bus:platform
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
PM: Adding info for acpi:acpi
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PM: Adding info for No Bus:pci0000:00
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:00:02.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
PM: Adding info for pci:0000:00:00.0
PM: Adding info for pci:0000:00:02.0
PM: Adding info for pci:0000:00:02.1
PM: Adding info for pci:0000:00:03.0
PM: Adding info for pci:0000:00:03.2
PM: Adding info for pci:0000:00:03.3
PM: Adding info for pci:0000:00:19.0
PM: Adding info for pci:0000:00:1a.0
PM: Adding info for pci:0000:00:1a.1
PM: Adding info for pci:0000:00:1a.7
PM: Adding info for pci:0000:00:1b.0
PM: Adding info for pci:0000:00:1c.0
PM: Adding info for pci:0000:00:1c.1
PM: Adding info for pci:0000:00:1c.2
PM: Adding info for pci:0000:00:1c.3
PM: Adding info for pci:0000:00:1c.4
PM: Adding info for pci:0000:00:1d.0
PM: Adding info for pci:0000:00:1d.1
PM: Adding info for pci:0000:00:1d.2
PM: Adding info for pci:0000:00:1d.7
PM: Adding info for pci:0000:00:1e.0
PM: Adding info for pci:0000:00:1f.0
PM: Adding info for pci:0000:00:1f.2
PM: Adding info for pci:0000:00:1f.3
PM: Adding info for pci:0000:00:1f.5
PM: Adding info for pci:0000:02:00.0
PM: Adding info for pci:0000:06:03.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
PM: Adding info for No Bus:pnp0
PM: Adding info for pnp:00:00
PM: Adding info for pnp:00:01
PM: Adding info for pnp:00:02
PM: Adding info for pnp:00:03
PM: Adding info for pnp:00:04
PM: Adding info for pnp:00:05
PM: Adding info for pnp:00:06
PM: Adding info for pnp:00:07
PM: Adding info for pnp:00:08
PM: Adding info for pnp:00:09
PM: Adding info for pnp:00:0a
PM: Adding info for pnp:00:0b
pnp: PnP ACPI: found 12 devices
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn''t work, try "pci=routeirq".  If it
helps, post a report
hpet0: at MMIO 0xfed00000 (virtual 0xffffffffff5fe000), IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
PCI-GART: No AMD northbridge found.
pnp: 00:06: ioport range 0x500-0x53f has been reserved
pnp: 00:06: ioport range 0x400-0x47f could not be reserved
pnp: 00:06: ioport range 0x680-0x6ff has been reserved
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: 90500000-905fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.1
  IO window: 1000-1fff
  MEM window: 90100000-901fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.2
  IO window: disabled.
  MEM window: 90600000-906fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.3
  IO window: disabled.
  MEM window: 90700000-907fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.4
  IO window: disabled.
  MEM window: 90800000-908fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: 90000000-900fffff
  PREFETCH window: disabled.
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1c.0 to 64
GSI 17 sharing vector 0xB1 and IRQ 17
ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 16 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1c.1 to 64
GSI 18 sharing vector 0xB9 and IRQ 18
ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:1c.2 to 64
GSI 19 sharing vector 0xC1 and IRQ 19
ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:1c.3 to 64
ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 17 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1c.4 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
PM: Adding info for pci_express:0000:00:1c.0:pcie00
Allocate Port Service[0000:00:1c.0:pcie02]
PM: Adding info for pci_express:0000:00:1c.0:pcie02
PCI: Setting latency timer of device 0000:00:1c.1 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.1:pcie00]
PM: Adding info for pci_express:0000:00:1c.1:pcie00
Allocate Port Service[0000:00:1c.1:pcie02]
PM: Adding info for pci_express:0000:00:1c.1:pcie02
PCI: Setting latency timer of device 0000:00:1c.2 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.2:pcie00]
PM: Adding info for pci_express:0000:00:1c.2:pcie00
Allocate Port Service[0000:00:1c.2:pcie02]
PM: Adding info for pci_express:0000:00:1c.2:pcie02
PCI: Setting latency timer of device 0000:00:1c.3 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.3:pcie00]
PM: Adding info for pci_express:0000:00:1c.3:pcie00
Allocate Port Service[0000:00:1c.3:pcie02]
PM: Adding info for pci_express:0000:00:1c.3:pcie02
PCI: Setting latency timer of device 0000:00:1c.4 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.4:pcie00]
PM: Adding info for pci_express:0000:00:1c.4:pcie00
Allocate Port Service[0000:00:1c.4:pcie02]
PM: Adding info for pci_express:0000:00:1c.4:pcie02
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Linux agpgart interface v0.101 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
PM: Adding info for platform:serial8250
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt 0000:00:03.3[B] -> GSI 17 (level, low) -> IRQ 169
0000:00:03.3: ttyS1 at I/O 0x2150 (irq = 169) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
GSI 20 sharing vector 0x3A and IRQ 20
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 58
PCI: Setting latency timer of device 0000:00:19.0 to 64
e1000: 0000:00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4)
00:16:76:df:9d:3f
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 19 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x2148 ctl 0x217E bmdma 0x2110 irq 193
ata2: SATA max UDMA/133 cmd 0x2140 ctl 0x217A bmdma 0x2118 irq 193
scsi0 : ata_piix
PM: Adding info for No Bus:host0
ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : ata_piix
PM: Adding info for No Bus:host1
ATA: abnormal status 0x7F on port 0x2147
PM: Adding info for No Bus:target0:0:0
  Vendor: ATA       Model: HDT722525DLA380   Rev: V44O
  Type:   Direct-Access                      ANSI SCSI revision: 05
PM: Adding info for scsi:0:0:0:0
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt 0000:00:1f.5[A] -> GSI 19 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:1f.5 to 64
ata3: SATA max UDMA/133 cmd 0x2138 ctl 0x2176 bmdma 0x20F0 irq 193
ata4: SATA max UDMA/133 cmd 0x2130 ctl 0x2172 bmdma 0x20F8 irq 193
scsi2 : ata_piix
PM: Adding info for No Bus:host2
ATA: abnormal status 0x7F on port 0x213F
scsi3 : ata_piix
PM: Adding info for No Bus:host3
ATA: abnormal status 0x7F on port 0x2137
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
PNP: No PS/2 controller found. Probing ports directly.
PM: Adding info for platform:i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio0
PM: Adding info for serio:serio1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
ACPI: (supports S0 S3 S4 S5)
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 180k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ACPI: PCI Interrupt 0000:00:1a.7[C] -> GSI 18 (level, low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:1a.7 to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1a.7
ehci_hcd 0000:00:1a.7: irq 185, io mem 0x90426400
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
PM: Adding info for usb:usb1
PM: Adding info for No Bus:usbdev1.1_ep00
usb usb1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-0:1.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v3.0
Intel 82802 RNG detected
sd 0:0:0:0: Attached scsi generic sg0 type 0
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
PM: Adding info for No Bus:usbdev1.1_ep81
GSI 21 sharing vector 0x4A and IRQ 21
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 74
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 74, io mem 0x90426000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
PM: Adding info for usb:usb2
PM: Adding info for No Bus:usbdev2.1_ep00
usb usb2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-0:1.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
PM: Adding info for No Bus:usbdev2.1_ep81
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 16 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1a.0 to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 177, io base 0x000020a0
PM: Adding info for usb:usb3
PM: Adding info for No Bus:usbdev3.1_ep00
usb usb3: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-0:1.0
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev3.1_ep81
GSI 22 sharing vector 0x52 and IRQ 22
ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 82
PCI: Setting latency timer of device 0000:00:1a.1 to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 82, io base 0x00002080
PM: Adding info for usb:usb4
PM: Adding info for No Bus:usbdev4.1_ep00
usb usb4: configuration #1 chosen from 1 choice
PM: Adding info for usb:4-0:1.0
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev4.1_ep81
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 74
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.0: irq 74, io base 0x00002060
PM: Adding info for usb:usb5
PM: Adding info for No Bus:usbdev5.1_ep00
usb usb5: configuration #1 chosen from 1 choice
PM: Adding info for usb:5-0:1.0
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev5.1_ep81
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.1: irq 193, io base 0x00002040
PM: Adding info for usb:usb6
PM: Adding info for No Bus:usbdev6.1_ep00
usb usb6: configuration #1 chosen from 1 choice
PM: Adding info for usb:6-0:1.0
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev6.1_ep81
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 185
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.2: irq 185, io base 0x00002020
PM: Adding info for usb:usb7
PM: Adding info for No Bus:usbdev7.1_ep00
usb usb7: configuration #1 chosen from 1 choice
PM: Adding info for usb:7-0:1.0
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
usb 3-1: new low speed USB device using uhci_hcd and address 2
PM: Adding info for No Bus:usbdev7.1_ep81
NET: Registered protocol family 17
PM: Adding info for usb:3-1
PM: Adding info for No Bus:usbdev3.2_ep00
usb 3-1: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-1:1.0
PM: Adding info for No Bus:usbdev3.2_ep81
fuse init (API version 7.7)
Adding 3903752k swap on
/dev/disk/by-uuid/0595b6ff-22f6-410a-be76-dbcf7e430cda.  Priority:-1
extents:1 across:3903752k
EXT3 FS on sda2, internal journal
usb 4-2: new full speed USB device using uhci_hcd and address 2
PM: Adding info for usb:4-2
PM: Adding info for No Bus:usbdev4.2_ep00
usb 4-2: configuration #1 chosen from 1 choice
PM: Adding info for usb:4-2:1.0
hub 4-2:1.0: USB hub found
hub 4-2:1.0: 3 ports detected
PM: Adding info for No Bus:usbdev4.2_ep81
input: Microsoft Microsoft IntelliMouse(r) Explorer as /class/input/input0
input: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse(r)
Explorer] on usb-0000:00:1a.0-1
usb 4-2.3: new full speed USB device using uhci_hcd and address 3
PM: Adding info for usb:4-2.3
PM: Adding info for No Bus:usbdev4.3_ep00
usb 4-2.3: configuration #1 chosen from 1 choice
PM: Adding info for usb:4-2.3:1.0
PM: Adding info for No Bus:usbdev4.3_ep81
PM: Adding info for usb:4-2.3:1.1
PM: Adding info for No Bus:usbdev4.3_ep82
PM: Adding info for usb:4-2.3:1.2
PM: Adding info for No Bus:usbdev4.3_ep83
input: HID 070a:0007 as /class/input/input1
input: USB HID v1.00 Keyboard [HID 070a:0007] on usb-0000:00:1a.1-2.3
toshiba_acpi: Unknown parameter `hotkeys_over_acpi''
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device
is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x3
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device
is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x4
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ibm_acpi: ec object not found
drivers/usb/input/hid-core.c: usb_submit_urb(ctrl) failed
drivers/usb/input/hid-core.c: timeout initializing reports
input: HID 070a:0007 as /class/input/input2
input: USB HID v1.00 Device [HID 070a:0007] on usb-0000:00:1a.1-2.3
input: HID 070a:0007 as /class/input/input3
input: USB HID v1.00 Mouse [HID 070a:0007] on usb-0000:00:1a.1-2.3
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
Losing some ticks... checking if CPU frequency changed.
warning: many lost ticks.
Your time source seems to be instable or some driver is hogging interupts
rip _spin_unlock_irqrestore+0x8/0x9
Falling back to HPET
------



.config (Dom0)
---------
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_AUDIT_ARCH=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_CPUSETS=y
CONFIG_RELAY=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y

#
# Block layer
#
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VSMP is not set
# CONFIG_MK8 is not set
CONFIG_MPSC=y
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_64_XEN=y
CONFIG_X86_NO_TSS=y
CONFIG_X86_NO_IDT=y
CONFIG_X86_L1_CACHE_BYTES=128
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_INTERNODE_CACHE_BYTES=128
CONFIG_X86_GOOD_APIC=y
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_X86_IO_APIC=y
CONFIG_X86_XEN_GENAPIC=y
CONFIG_X86_LOCAL_APIC=y
# CONFIG_MTRR is not set
CONFIG_SMP=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4096
CONFIG_RESOURCES_64BIT=y
CONFIG_NR_CPUS=8
CONFIG_HOTPLUG_CPU=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_SWIOTLB=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x200000
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_REORDER=y
CONFIG_K8_NB=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_PENDING_IRQ=y

#
# Power management options
#
CONFIG_PM=y

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_MMCONFIG is not set
CONFIG_XEN_PCIDEV_FRONTEND=y
# CONFIG_XEN_PCIDEV_FE_DEBUG is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=m
# CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE is not set
# CONFIG_PCI_DEBUG is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=m
CONFIG_HOTPLUG_PCI_FAKE=m
# CONFIG_HOTPLUG_PCI_ACPI is not set
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m
# CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NETDEBUG is not set
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
CONFIG_NET_KEY=m
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_BIC=y

#
# IP: Virtual Server Configuration
#
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
# CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
# CONFIG_NETFILTER_XT_TARGET_NOTRACK is not set
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=m
# CONFIG_IP_NF_CONNTRACK is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
# CONFIG_IP_NF_MATCH_DSCP is not set
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
# CONFIG_IP_NF_TARGET_DSCP is not set
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m

#
# DCCP Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y

#
# TIPC Configuration (EXPERIMENTAL)
#
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
# CONFIG_ATM is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
# CONFIG_DECNET is not set
CONFIG_LLC=m
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
CONFIG_NET_CLS_ROUTE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_IEEE80211 is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
CONFIG_BLK_DEV_RAM_BLOCKSIZE=1024
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
CONFIG_BLK_DEV_IDE_SATA=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_RAID_ATTRS=m
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
CONFIG_CHR_DEV_SCH=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m

#
# SCSI low-level drivers
#
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_AHCI=y
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_ATA_PIIX=y
CONFIG_SCSI_SATA_MV=y
# CONFIG_SCSI_SATA_NV is not set
# CONFIG_SCSI_PDC_ADMA is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIL24 is not set
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Network device support
#
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# PHY device support
#

#
# Ethernet (10 or 100Mbit)
#
# CONFIG_NET_ETHERNET is not set
CONFIG_MII=m

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
CONFIG_E1000=y
CONFIG_E1000_NAPI=y
# CONFIG_E1000_DISABLE_PACKET_SPLIT is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_CHELSIO_T1 is not set
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
# CONFIG_MYRI10GE is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
CONFIG_INPUT_EVBUG=m

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_SUNKBD=m
CONFIG_KEYBOARD_LKKBD=m
CONFIG_KEYBOARD_XTKBD=m
CONFIG_KEYBOARD_NEWTON=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_VSXXXAA=m
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
CONFIG_GAMEPORT_L4=m
CONFIG_GAMEPORT_EMU10K1=m
CONFIG_GAMEPORT_FM801=m

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_COMPUTONE=m
CONFIG_ROCKETPORT=m
CONFIG_CYCLADES=m
# CONFIG_CYZ_INTR is not set
CONFIG_DIGIEPCA=m
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_N_HDLC is not set
# CONFIG_SPECIALIX is not set
CONFIG_SX=m
# CONFIG_RIO is not set
CONFIG_STALDRV=y

#
# Serial drivers
#
CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_PCI=m
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_SERIAL_JSM=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_NOWAYOUT is not set

#
# Watchdog Device Drivers
#
CONFIG_SOFT_WATCHDOG=m
CONFIG_ACQUIRE_WDT=m
CONFIG_ADVANTECH_WDT=m
CONFIG_ALIM1535_WDT=m
CONFIG_ALIM7101_WDT=m
CONFIG_SC520_WDT=m
CONFIG_EUROTECH_WDT=m
CONFIG_IB700_WDT=m
CONFIG_IBMASR=m
CONFIG_WAFER_WDT=m
CONFIG_I6300ESB_WDT=m
CONFIG_I8XX_TCO=m
CONFIG_SC1200_WDT=m
CONFIG_60XX_WDT=m
CONFIG_SBC8360_WDT=m
CONFIG_CPU5_WDT=m
CONFIG_W83627HF_WDT=m
CONFIG_W83877F_WDT=m
CONFIG_W83977F_WDT=m
CONFIG_MACHZ_WDT=m
CONFIG_SBC_EPX_C3_WATCHDOG=m

#
# PCI-based Watchdog Cards
#
CONFIG_PCIPCWATCHDOG=m
CONFIG_WDTPCI=m
CONFIG_WDT_501_PCI=y

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=m
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_INTEL=m
CONFIG_HW_RANDOM_AMD=m
CONFIG_HW_RANDOM_GEODE=m
CONFIG_NVRAM=m
CONFIG_RTC=y
CONFIG_DTLK=m
CONFIG_R3964=m
CONFIG_APPLICOM=m

#
# Ftape, the floppy tape device driver
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=m
CONFIG_AGP_SIS=m
CONFIG_AGP_VIA=m
CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m
CONFIG_MWAVE=m
CONFIG_PC8736x_GPIO=m
CONFIG_NSC_GPIO=m
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HPET is not set
CONFIG_HANGCHECK_TIMER=m

#
# TPM devices
#
CONFIG_TCG_TPM=m
CONFIG_TCG_ATMEL=m
# CONFIG_TCG_XEN is not set
CONFIG_TELCLOCK=m

#
# I2C support
#
CONFIG_I2C=m
# CONFIG_I2C_CHARDEV is not set

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
# CONFIG_I2C_ALGOPCF is not set
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas''s 1-wire bus
#

#
# Hardware Monitoring support
#
# CONFIG_HWMON is not set
# CONFIG_HWMON_VID is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y

#
# Video Capture Adapters
#

#
# Video Capture Adapters
#
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CX88 is not set

#
# Encoders and Decoders
#
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_TLV320AIC23B=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_CX2341X=m
CONFIG_VIDEO_CX25840=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m

#
# V4L USB devices
#
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_24XXX=y
CONFIG_VIDEO_PVRUSB2_SYSFS=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_USBVIDEO=m
CONFIG_USB_VICAM=m
CONFIG_USB_IBMCAM=m
CONFIG_USB_KONICAWC=m
CONFIG_USB_QUICKCAM_MESSENGER=m
CONFIG_USB_ET61X251=m
CONFIG_VIDEO_OVCAMCHIP=m
CONFIG_USB_W9968CF=m
# CONFIG_USB_OV511 is not set
CONFIG_USB_SE401=m
CONFIG_USB_SN9C102=m
CONFIG_USB_STV680=m
CONFIG_USB_ZC0301=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set

#
# Radio Adapters
#
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_USB_DSBR is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_BUF=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
# CONFIG_USB_DABUSB is not set

#
# Graphics support
#
CONFIG_FIRMWARE_EDID=y
# CONFIG_FB is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_DEVICE=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_DEVICE=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_SL811_HCD=m

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# NOTE: USB_STORAGE enables SCSI, and ''SCSI disk support''
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set

#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_ACECAD is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_TOUCHSCREEN is not set
# CONFIG_USB_YEALINK is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
# CONFIG_USB_ATI_REMOTE2 is not set
# CONFIG_USB_KEYSPAN_REMOTE is not set
# CONFIG_USB_APPLETOUCH is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m
CONFIG_USB_NET_CDCETHER=m
CONFIG_USB_NET_GL620A=m
CONFIG_USB_NET_NET1080=m
CONFIG_USB_NET_PLUSB=m
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET=m
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_NET_ZAURUS=m
# CONFIG_USB_MON is not set

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#
# CONFIG_EDAC is not set

#
# Real Time Clock
#
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
CONFIG_RTC_INTF_DEV_UIE_EMUL=y

#
# RTC drivers
#
CONFIG_RTC_DRV_X1205=m
CONFIG_RTC_DRV_DS1307=m
CONFIG_RTC_DRV_DS1553=m
CONFIG_RTC_DRV_ISL1208=m
CONFIG_RTC_DRV_DS1672=m
CONFIG_RTC_DRV_DS1742=m
CONFIG_RTC_DRV_PCF8563=m
# CONFIG_RTC_DRV_PCF8583 is not set
CONFIG_RTC_DRV_RS5C372=m
CONFIG_RTC_DRV_M48T86=m
CONFIG_RTC_DRV_TEST=m
CONFIG_RTC_DRV_V3020=m

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
CONFIG_INTEL_IOATDMA=m

#
# Firmware Drivers
#
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m

#
# File systems
#
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=y
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS is not set
# CONFIG_CIFS_WEAK_PW_HASH is not set
# CONFIG_CIFS_XATTR is not set
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
# CONFIG_9P_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="cp437"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m

#
# Instrumentation Support
#
# CONFIG_PROFILING is not set
# CONFIG_KPROBES is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_FS=y
# CONFIG_DEBUG_VM is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_UNWIND_INFO is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=m
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=m
CONFIG_CRYPTO_TEST=m

#
# Hardware crypto devices
#
CONFIG_XEN=y
CONFIG_XEN_INTERFACE_VERSION=0x00030205

#
# XEN
#
CONFIG_XEN_PRIVILEGED_GUEST=y
# CONFIG_XEN_UNPRIVILEGED_GUEST is not set
CONFIG_XEN_PRIVCMD=y
CONFIG_XEN_XENBUS_DEV=y
CONFIG_XEN_BACKEND=y
CONFIG_XEN_BLKDEV_BACKEND=y
CONFIG_XEN_BLKDEV_TAP=y
CONFIG_XEN_NETDEV_BACKEND=y
# CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
CONFIG_XEN_NETDEV_LOOPBACK=y
CONFIG_XEN_PCIDEV_BACKEND=y
CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
# CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
# CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
# CONFIG_XEN_PCIDEV_BE_DEBUG is not set
# CONFIG_XEN_TPMDEV_BACKEND is not set
# CONFIG_XEN_BLKDEV_FRONTEND is not set
# CONFIG_XEN_NETDEV_FRONTEND is not set
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DISABLE_SERIAL=y
CONFIG_XEN_SYSFS=y
CONFIG_XEN_COMPAT_030002_AND_LATER=y
# CONFIG_XEN_COMPAT_030004_AND_LATER is not set
# CONFIG_XEN_COMPAT_LATEST_ONLY is not set
CONFIG_XEN_COMPAT=0x030002
CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
CONFIG_NO_IDLE_HZ=y
CONFIG_XEN_SMPBOOT=y

#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 13/6/07 08:40, "Jun Koi" <junkoi2004@gmail.com> wrote:
>> Please post output from native boot (dmesg), XenLinux boot (dmesg), and
>> Xen''s boot output (xm dmesg). Run Xen with boot option
''loglvl=all'' to make
>> sure you actually get all of Xen''s output.
>> 
> 
> The point is that Xen doesnt boot in the first place, so I cannot
> provide xm dmesg!
> 
> Below is the output from dmesg (native kernel) and Dom0''s .config.
> Anything else do you need?
Can you get a serial line on the machine?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
wrote:
> On 13/6/07 08:40, "Jun Koi" <junkoi2004@gmail.com> wrote:
>
> >> Please post output from native boot (dmesg), XenLinux boot
(dmesg), and
> >> Xen''s boot output (xm dmesg). Run Xen with boot option
''loglvl=all'' to make
> >> sure you actually get all of Xen''s output.
> >>
> >
> > The point is that Xen doesnt boot in the first place, so I cannot
> > provide xm dmesg!
> >
> > Below is the output from dmesg (native kernel) and Dom0''s
.config.
> > Anything else do you need?
>
> Can you get a serial line on the machine?
>

Opps, that is compicated, as I dont have a cable to do that.

So if you have no suggestion, perhaps I must try this way. But perhaps
it take more than a week, as I am away in few days.


Thanks,
Jun

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 13/6/07 08:49, "Jun Koi" <junkoi2004@gmail.com> wrote:
>>> The point is that Xen doesnt boot in the first place, so I cannot
>>> provide xm dmesg!
>>> 
>>> Below is the output from dmesg (native kernel) and Dom0''s
.config.
>>> Anything else do you need?
>> 
>> Can you get a serial line on the machine?
> 
> Opps, that is compicated, as I dont have a cable to do that.
> 
> So if you have no suggestion, perhaps I must try this way. But perhaps
> it take more than a week, as I am away in few days.
There''s a decent chance that comparing the two dmesg outputs will show
some
important deviation in the case of running on Xen that is causing the boot
failure. Without the failing output it''s hard to know where to start
looking.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
wrote:
> On 13/6/07 08:49, "Jun Koi" <junkoi2004@gmail.com> wrote:
>
> >>> The point is that Xen doesnt boot in the first place, so I
cannot
> >>> provide xm dmesg!
> >>>
> >>> Below is the output from dmesg (native kernel) and
Dom0''s .config.
> >>> Anything else do you need?
> >>
> >> Can you get a serial line on the machine?
> >
> > Opps, that is compicated, as I dont have a cable to do that.
> >
> > So if you have no suggestion, perhaps I must try this way. But perhaps
> > it take more than a week, as I am away in few days.
>
> There''s a decent chance that comparing the two dmesg outputs will
show some
> important deviation in the case of running on Xen that is causing the boot
> failure. Without the failing output it''s hard to know where to
start
> looking.
>
I see, but can you imagine some reasons why that happens?  It makes
absolute no sense to me.

I have found that my machine has no serial port, so perhaps I must buy
a serial card to debug this problem. Wonder if there is another way to
avoid that (?)

Thanks,
Jun

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jun Koi
> Sent: 13 June 2007 09:54
> To: Keir Fraser
> Cc: xen-devel
> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs, 
> while native kernel can ???
> 
> On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> > On 13/6/07 08:49, "Jun Koi" <junkoi2004@gmail.com>
wrote:
> >
> > >>> The point is that Xen doesnt boot in the first place, 
> so I cannot
> > >>> provide xm dmesg!
> > >>>
> > >>> Below is the output from dmesg (native kernel) and 
> Dom0''s .config.
> > >>> Anything else do you need?
> > >>
> > >> Can you get a serial line on the machine?
> > >
> > > Opps, that is compicated, as I dont have a cable to do that.
> > >
> > > So if you have no suggestion, perhaps I must try this 
> way. But perhaps
> > > it take more than a week, as I am away in few days.
> >
> > There''s a decent chance that comparing the two dmesg 
> outputs will show some
> > important deviation in the case of running on Xen that is 
> causing the boot
> > failure. Without the failing output it''s hard to know where
to start
> > looking.
> >
> 
> I see, but can you imagine some reasons why that happens?  It makes
> absolute no sense to me.
There are lots of possible reasons. The most likely is that your kernel
in the native has drivers that are not part of the Xen default
configuration. 

The other very common problem is that you don''t have those necessary
drivers in the "initrd" for your Xen. This is a problem that is posted
about three times a week (at least) on the Xen Users mailing list [where
this problem probably should be discussed - but I think since it''s
started here, we''ll keep it here]. 
> 
> I have found that my machine has no serial port, so perhaps I must buy
> a serial card to debug this problem. Wonder if there is another way to
> avoid that (?)
If you have a digital camera and you add "noreboot" to the commandline
of "xen.gz" in your grub configuration, maybe you can upload (to some
photo-web-site or such) a screen-shot of the final few lines of the boot
and send a link to the list - that may not give all clues, but at least
it will indicate what''s going on. 

--
Mats
> 
> Thanks,
> Jun
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi Mats,

On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com>
wrote:
>
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jun Koi
> > Sent: 13 June 2007 09:54
> > To: Keir Fraser
> > Cc: xen-devel
> > Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> > while native kernel can ???
> >
> > On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> > > On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > >
> > > >>> The point is that Xen doesnt boot in the first
place,
> > so I cannot
> > > >>> provide xm dmesg!
> > > >>>
> > > >>> Below is the output from dmesg (native kernel) and
> > Dom0''s .config.
> > > >>> Anything else do you need?
> > > >>
> > > >> Can you get a serial line on the machine?
> > > >
> > > > Opps, that is compicated, as I dont have a cable to do that.
> > > >
> > > > So if you have no suggestion, perhaps I must try this
> > way. But perhaps
> > > > it take more than a week, as I am away in few days.
> > >
> > > There''s a decent chance that comparing the two dmesg
> > outputs will show some
> > > important deviation in the case of running on Xen that is
> > causing the boot
> > > failure. Without the failing output it''s hard to know
where to start
> > > looking.
> > >
> >
> > I see, but can you imagine some reasons why that happens?  It makes
> > absolute no sense to me.
>
> There are lots of possible reasons. The most likely is that your kernel
> in the native has drivers that are not part of the Xen default
> configuration.
>
> The other very common problem is that you don''t have those
necessary
> drivers in the "initrd" for your Xen. This is a problem that is
posted
> about three times a week (at least) on the Xen Users mailing list [where
> this problem probably should be discussed - but I think since it''s
> started here, we''ll keep it here].
>
No, that is not a reason in my case. I did it this way:
- Native kernel (2.6.18) is compiled with all the necessary drivers
built-in. That means I dont need initrd to boot my machine with this
kernel. And it boots well.
- I copied the .config of native kernel above to Dom0, and compile
Dom0 with this option. (Of course before compiling, I enabled Xen
option, as you can see in the .config of Dom0 I sent in the last
mail). Again this time I dont need initrd.

So it is logical that Dom0 must boot, but it fails actually. That is
why I find the situation very strange.

> > I have found that my machine has no serial port, so perhaps I must buy
> > a serial card to debug this problem. Wonder if there is another way to
> > avoid that (?)
> If you have a digital camera and you add "noreboot" to the
commandline
> of "xen.gz" in your grub configuration, maybe you can upload (to
some
> photo-web-site or such) a screen-shot of the final few lines of the boot
> and send a link to the list - that may not give all clues, but at least
> it will indicate what''s going on.
OK, I will do that, as it is not desired to buy a serial card :-)

Thanks,
Jun

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

[This email is either empty or too large to be displayed at this time]

> -----Original Message-----
> From: Jun Koi [mailto:junkoi2004@gmail.com] 
> Sent: 13 June 2007 10:22
> To: Petersson, Mats
> Cc: Keir Fraser; xen-devel
> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs, 
> while native kernel can ???
> 
> Here is the screenshot taken with a digital camera. I hope the screen
> is clear enough for you to see.
It seems like it''s loading the driver for that disk and recognising it,
which leaves two possible likely options:
1. You don''t have the filesystem driver for the fs on the /dev/sda2
2. You don''t have "/dev/sda2" although the driver for it is
loaded
[maybe you need something like udev installed to create the device?]

--
Mats
> 
> Thanks,
> Jun
> 
[snip old portions]. 



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 6/13/07, Jun Koi  wrote:
[snip]
> > The other very common problem is that you don''t have those
necessary
> > drivers in the "initrd" for your Xen. This is a problem that
is posted
> > about three times a week (at least) on the Xen Users mailing list
[where
> > this problem probably should be discussed - but I think since
it''s
> > started here, we''ll keep it here].
> >
>
> No, that is not a reason in my case. I did it this way:
> - Native kernel (2.6.18) is compiled with all the necessary drivers
> built-in. That means I dont need initrd to boot my machine with this
> kernel. And it boots well.
> - I copied the .config of native kernel above to Dom0, and compile
> Dom0 with this option. (Of course before compiling, I enabled Xen
> option, as you can see in the .config of Dom0 I sent in the last
> mail). Again this time I dont need initrd.
With my personal experiences with numerous attempts to install Xen
from src, i suggest make an initramfs/initrd image. That is pretty
much useful at times.
Take more care to include your root fs type to be built statically in
the kernel and not as a module. Can yo check on this?
Also same goes for your /boot fs type(if you have a separate /boot
partition though).

And yes, what about your scsi and SATA drivers?
Are they built into the kernel or not?

Hope this helped somehow.

Thanks
- --psr
>
> So it is logical that Dom0 must boot, but it fails actually. That is
> why I find the situation very strange.
- --
- ---
pradeep singh rautela

"Genius is 1% inspiration, and 99% perspiration" - not me :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGb7l2ky6Gd9lpXlERAjKpAJ9dl0lreL8Z7wLjO6UzSnjE0Gne0QCeIlUG
WYRl9jVeaU7dqOAsKlA4wH8=5YwI
-----END PGP SIGNATURE-----

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com>
wrote:
>
>
> > -----Original Message-----
> > From: Jun Koi [mailto:junkoi2004@gmail.com]
> > Sent: 13 June 2007 10:22
> > To: Petersson, Mats
> > Cc: Keir Fraser; xen-devel
> > Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> > while native kernel can ???
> >
> > Here is the screenshot taken with a digital camera. I hope the screen
> > is clear enough for you to see.
>
> It seems like it''s loading the driver for that disk and
recognising it,
> which leaves two possible likely options:
> 1. You don''t have the filesystem driver for the fs on the
/dev/sda2
> 2. You don''t have "/dev/sda2" although the driver for it
is loaded
> [maybe you need something like udev installed to create the device?]
>
OK, but why the same kernel option with native kernel boots my machine
well? It detects the same /dev/sda2.

Do you see my point?

Thanks,
Jun

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 6/13/07, pradeep singh rautela <rautelap@gmail.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 6/13/07, Jun Koi  wrote:
> [snip]
> > > The other very common problem is that you don''t have
those necessary
> > > drivers in the "initrd" for your Xen. This is a problem
that is posted
> > > about three times a week (at least) on the Xen Users mailing list
[where
> > > this problem probably should be discussed - but I think since
it''s
> > > started here, we''ll keep it here].
> > >
> >
> > No, that is not a reason in my case. I did it this way:
> > - Native kernel (2.6.18) is compiled with all the necessary drivers
> > built-in. That means I dont need initrd to boot my machine with this
> > kernel. And it boots well.
> > - I copied the .config of native kernel above to Dom0, and compile
> > Dom0 with this option. (Of course before compiling, I enabled Xen
> > option, as you can see in the .config of Dom0 I sent in the last
> > mail). Again this time I dont need initrd.
> With my personal experiences with numerous attempts to install Xen
> from src, i suggest make an initramfs/initrd image. That is pretty
> much useful at times.
> Take more care to include your root fs type to be built statically in
> the kernel and not as a module. Can yo check on this?
> Also same goes for your /boot fs type(if you have a separate /boot
> partition though).
>
> And yes, what about your scsi and SATA drivers?
Everything is built-in, so I dont see why I need initrd. Actually I
never use initrd, and it is always fine for me, except this time. The
problem like this never happens with me before.


Thanks,
Jun

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

That''s fine. My conclusion is that this is user error: you are trying
to
mount /boot/sda2 and you actually mean /dev/sda2.

 -- Keir

On 13/6/07 10:21, "Jun Koi" <junkoi2004@gmail.com> wrote:
> Here is the screenshot taken with a digital camera. I hope the screen
> is clear enough for you to see.
> 
> Thanks,
> Jun
> 
> 
> 
> On 6/13/07, Jun Koi <junkoi2004@gmail.com> wrote:
>> Hi Mats,
>> 
>> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: xen-devel-bounces@lists.xensource.com
>>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jun
Koi
>>>> Sent: 13 June 2007 09:54
>>>> To: Keir Fraser
>>>> Cc: xen-devel
>>>> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
>>>> while native kernel can ???
>>>> 
>>>> On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>>>>> On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
>>>>> 
>>>>>>>> The point is that Xen doesnt boot in the first
place,
>>>> so I cannot
>>>>>>>> provide xm dmesg!
>>>>>>>> 
>>>>>>>> Below is the output from dmesg (native kernel)
and
>>>> Dom0''s .config.
>>>>>>>> Anything else do you need?
>>>>>>> 
>>>>>>> Can you get a serial line on the machine?
>>>>>> 
>>>>>> Opps, that is compicated, as I dont have a cable to do
that.
>>>>>> 
>>>>>> So if you have no suggestion, perhaps I must try this
>>>> way. But perhaps
>>>>>> it take more than a week, as I am away in few days.
>>>>> 
>>>>> There''s a decent chance that comparing the two
dmesg
>>>> outputs will show some
>>>>> important deviation in the case of running on Xen that is
>>>> causing the boot
>>>>> failure. Without the failing output it''s hard to
know where to start
>>>>> looking.
>>>>> 
>>>> 
>>>> I see, but can you imagine some reasons why that happens?  It
makes
>>>> absolute no sense to me.
>>> 
>>> There are lots of possible reasons. The most likely is that your
kernel
>>> in the native has drivers that are not part of the Xen default
>>> configuration.
>>> 
>>> The other very common problem is that you don''t have those
necessary
>>> drivers in the "initrd" for your Xen. This is a problem
that is posted
>>> about three times a week (at least) on the Xen Users mailing list
[where
>>> this problem probably should be discussed - but I think since
it''s
>>> started here, we''ll keep it here].
>>> 
>> 
>> No, that is not a reason in my case. I did it this way:
>> - Native kernel (2.6.18) is compiled with all the necessary drivers
>> built-in. That means I dont need initrd to boot my machine with this
>> kernel. And it boots well.
>> - I copied the .config of native kernel above to Dom0, and compile
>> Dom0 with this option. (Of course before compiling, I enabled Xen
>> option, as you can see in the .config of Dom0 I sent in the last
>> mail). Again this time I dont need initrd.
>> 
>> So it is logical that Dom0 must boot, but it fails actually. That is
>> why I find the situation very strange.
>> 
>> 
>>>> I have found that my machine has no serial port, so perhaps I
must buy
>>>> a serial card to debug this problem. Wonder if there is another
way to
>>>> avoid that (?)
>>> If you have a digital camera and you add "noreboot" to
the commandline
>>> of "xen.gz" in your grub configuration, maybe you can
upload (to some
>>> photo-web-site or such) a screen-shot of the final few lines of the
boot
>>> and send a link to the list - that may not give all clues, but at
least
>>> it will indicate what''s going on.
>> 
>> OK, I will do that, as it is not desired to buy a serial card :-)
>> 
>> Thanks,
>> Jun
>> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> -----Original Message-----
> From: Keir Fraser [mailto:keir@xensource.com] 
> Sent: 13 June 2007 10:45
> To: Jun Koi; Petersson, Mats
> Cc: xen-devel
> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs, 
> while native kernel can ???
> 
> 
> That''s fine. My conclusion is that this is user error: you 
> are trying to
> mount /boot/sda2 and you actually mean /dev/sda2.
Well spotted. I just expected it to say "/dev/" rather than
"/boot/".

--
Mats
> 
>  -- Keir
> 
> On 13/6/07 10:21, "Jun Koi" <junkoi2004@gmail.com> wrote:
> 
> > Here is the screenshot taken with a digital camera. I hope 
> the screen
> > is clear enough for you to see.
> > 
> > Thanks,
> > Jun
> > 
> > 
> > 
> > On 6/13/07, Jun Koi <junkoi2004@gmail.com> wrote:
> >> Hi Mats,
> >> 
> >> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
> >>> 
> >>> 
> >>>> -----Original Message-----
> >>>> From: xen-devel-bounces@lists.xensource.com
> >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf 
> Of Jun Koi
> >>>> Sent: 13 June 2007 09:54
> >>>> To: Keir Fraser
> >>>> Cc: xen-devel
> >>>> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> >>>> while native kernel can ???
> >>>> 
> >>>> On 6/13/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
wrote:
> >>>>> On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> >>>>> 
> >>>>>>>> The point is that Xen doesnt boot in the
first place,
> >>>> so I cannot
> >>>>>>>> provide xm dmesg!
> >>>>>>>> 
> >>>>>>>> Below is the output from dmesg (native
kernel) and
> >>>> Dom0''s .config.
> >>>>>>>> Anything else do you need?
> >>>>>>> 
> >>>>>>> Can you get a serial line on the machine?
> >>>>>> 
> >>>>>> Opps, that is compicated, as I dont have a cable
to do that.
> >>>>>> 
> >>>>>> So if you have no suggestion, perhaps I must try
this
> >>>> way. But perhaps
> >>>>>> it take more than a week, as I am away in few
days.
> >>>>> 
> >>>>> There''s a decent chance that comparing the
two dmesg
> >>>> outputs will show some
> >>>>> important deviation in the case of running on Xen that
is
> >>>> causing the boot
> >>>>> failure. Without the failing output it''s hard
to know
> where to start
> >>>>> looking.
> >>>>> 
> >>>> 
> >>>> I see, but can you imagine some reasons why that 
> happens?  It makes
> >>>> absolute no sense to me.
> >>> 
> >>> There are lots of possible reasons. The most likely is 
> that your kernel
> >>> in the native has drivers that are not part of the Xen default
> >>> configuration.
> >>> 
> >>> The other very common problem is that you don''t have 
> those necessary
> >>> drivers in the "initrd" for your Xen. This is a
problem
> that is posted
> >>> about three times a week (at least) on the Xen Users 
> mailing list [where
> >>> this problem probably should be discussed - but I think since
it''s
> >>> started here, we''ll keep it here].
> >>> 
> >> 
> >> No, that is not a reason in my case. I did it this way:
> >> - Native kernel (2.6.18) is compiled with all the necessary
drivers
> >> built-in. That means I dont need initrd to boot my machine 
> with this
> >> kernel. And it boots well.
> >> - I copied the .config of native kernel above to Dom0, and compile
> >> Dom0 with this option. (Of course before compiling, I enabled Xen
> >> option, as you can see in the .config of Dom0 I sent in the last
> >> mail). Again this time I dont need initrd.
> >> 
> >> So it is logical that Dom0 must boot, but it fails 
> actually. That is
> >> why I find the situation very strange.
> >> 
> >> 
> >>>> I have found that my machine has no serial port, so 
> perhaps I must buy
> >>>> a serial card to debug this problem. Wonder if there is 
> another way to
> >>>> avoid that (?)
> >>> If you have a digital camera and you add "noreboot"
to
> the commandline
> >>> of "xen.gz" in your grub configuration, maybe you
can
> upload (to some
> >>> photo-web-site or such) a screen-shot of the final few 
> lines of the boot
> >>> and send a link to the list - that may not give all 
> clues, but at least
> >>> it will indicate what''s going on.
> >> 
> >> OK, I will do that, as it is not desired to buy a serial card :-)
> >> 
> >> Thanks,
> >> Jun
> >> 
> 
> 
> 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> -----Original Message-----
> From: Jun Koi [mailto:junkoi2004@gmail.com] 
> Sent: 13 June 2007 10:37
> To: Petersson, Mats
> Cc: Keir Fraser; xen-devel
> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs, 
> while native kernel can ???
> 
> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
> >
> >
> > > -----Original Message-----
> > > From: Jun Koi [mailto:junkoi2004@gmail.com]
> > > Sent: 13 June 2007 10:22
> > > To: Petersson, Mats
> > > Cc: Keir Fraser; xen-devel
> > > Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> > > while native kernel can ???
> > >
> > > Here is the screenshot taken with a digital camera. I 
> hope the screen
> > > is clear enough for you to see.
> >
> > It seems like it''s loading the driver for that disk and 
> recognising it,
> > which leaves two possible likely options:
> 
> > 1. You don''t have the filesystem driver for the fs on the
/dev/sda2
> > 2. You don''t have "/dev/sda2" although the driver
for it is loaded
> > [maybe you need something like udev installed to create the device?]
> >
> 
> OK, but why the same kernel option with native kernel boots my machine
> well? It detects the same /dev/sda2.
> 
> Do you see my point?
I do see your point. I''m just following the evidence on your screen -
which of course may be misleading, but without further information of
some sort, that''s what the current evidence shows. I just realized that
Keir has spotted the REAL problem in this case tho''. 

Note that different distributions have different add-ons (extra patches
to the kernel itself) in the kernel that they distribute. Xen uses the
standard kernel.org kernel, and there is sometimes a difference in that.

As a side not (in regards to the comments about using initrd), I have
found that there''s less problems with that approach than using
"kernel
builtin", simply for the reason that I don''t have to figure out
which
parts I need to compile in on a particular machine to make it work -
instead, I create an initrd on the machine I use Xen, and select
(almost) all different drivers and filesystems as my config. Since
unused modules only take up a bit of disk-space (and I usually have a
large enough disk that a few megabytes doesn''t really matter much), I
don''t have to select just the right ones.


--
Mats
> 
> Thanks,
> Jun
> 
> 
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

What a shame!!! I think I should go hanging myself!!!

Good bye forever! Best wishes to you and Xen project!!!!!

Jun

On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com>
wrote:
>
>
> > -----Original Message-----
> > From: Keir Fraser [mailto:keir@xensource.com]
> > Sent: 13 June 2007 10:45
> > To: Jun Koi; Petersson, Mats
> > Cc: xen-devel
> > Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> > while native kernel can ???
> >
> >
> > That''s fine. My conclusion is that this is user error: you
> > are trying to
> > mount /boot/sda2 and you actually mean /dev/sda2.
>
> Well spotted. I just expected it to say "/dev/" rather than
"/boot/".
>
> --
> Mats
> >
> >  -- Keir
> >
> > On 13/6/07 10:21, "Jun Koi" <junkoi2004@gmail.com>
wrote:
> >
> > > Here is the screenshot taken with a digital camera. I hope
> > the screen
> > > is clear enough for you to see.
> > >
> > > Thanks,
> > > Jun
> > >
> > >
> > >
> > > On 6/13/07, Jun Koi <junkoi2004@gmail.com> wrote:
> > >> Hi Mats,
> > >>
> > >> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com>
wrote:
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: xen-devel-bounces@lists.xensource.com
> > >>>> [mailto:xen-devel-bounces@lists.xensource.com] On
Behalf
> > Of Jun Koi
> > >>>> Sent: 13 June 2007 09:54
> > >>>> To: Keir Fraser
> > >>>> Cc: xen-devel
> > >>>> Subject: Re: [Xen-devel] Xen doesnt recognize my root
fs,
> > >>>> while native kernel can ???
> > >>>>
> > >>>> On 6/13/07, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> > >>>>> On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > >>>>>
> > >>>>>>>> The point is that Xen doesnt boot in
the first place,
> > >>>> so I cannot
> > >>>>>>>> provide xm dmesg!
> > >>>>>>>>
> > >>>>>>>> Below is the output from dmesg
(native kernel) and
> > >>>> Dom0''s .config.
> > >>>>>>>> Anything else do you need?
> > >>>>>>>
> > >>>>>>> Can you get a serial line on the machine?
> > >>>>>>
> > >>>>>> Opps, that is compicated, as I dont have a
cable to do that.
> > >>>>>>
> > >>>>>> So if you have no suggestion, perhaps I must
try this
> > >>>> way. But perhaps
> > >>>>>> it take more than a week, as I am away in few
days.
> > >>>>>
> > >>>>> There''s a decent chance that comparing
the two dmesg
> > >>>> outputs will show some
> > >>>>> important deviation in the case of running on Xen
that is
> > >>>> causing the boot
> > >>>>> failure. Without the failing output it''s
hard to know
> > where to start
> > >>>>> looking.
> > >>>>>
> > >>>>
> > >>>> I see, but can you imagine some reasons why that
> > happens?  It makes
> > >>>> absolute no sense to me.
> > >>>
> > >>> There are lots of possible reasons. The most likely is
> > that your kernel
> > >>> in the native has drivers that are not part of the Xen
default
> > >>> configuration.
> > >>>
> > >>> The other very common problem is that you don''t
have
> > those necessary
> > >>> drivers in the "initrd" for your Xen. This is a
problem
> > that is posted
> > >>> about three times a week (at least) on the Xen Users
> > mailing list [where
> > >>> this problem probably should be discussed - but I think
since it''s
> > >>> started here, we''ll keep it here].
> > >>>
> > >>
> > >> No, that is not a reason in my case. I did it this way:
> > >> - Native kernel (2.6.18) is compiled with all the necessary
drivers
> > >> built-in. That means I dont need initrd to boot my machine
> > with this
> > >> kernel. And it boots well.
> > >> - I copied the .config of native kernel above to Dom0, and
compile
> > >> Dom0 with this option. (Of course before compiling, I enabled
Xen
> > >> option, as you can see in the .config of Dom0 I sent in the
last
> > >> mail). Again this time I dont need initrd.
> > >>
> > >> So it is logical that Dom0 must boot, but it fails
> > actually. That is
> > >> why I find the situation very strange.
> > >>
> > >>
> > >>>> I have found that my machine has no serial port, so
> > perhaps I must buy
> > >>>> a serial card to debug this problem. Wonder if there
is
> > another way to
> > >>>> avoid that (?)
> > >>> If you have a digital camera and you add
"noreboot" to
> > the commandline
> > >>> of "xen.gz" in your grub configuration, maybe
you can
> > upload (to some
> > >>> photo-web-site or such) a screen-shot of the final few
> > lines of the boot
> > >>> and send a link to the list - that may not give all
> > clues, but at least
> > >>> it will indicate what''s going on.
> > >>
> > >> OK, I will do that, as it is not desired to buy a serial card
:-)
> > >>
> > >> Thanks,
> > >> Jun
> > >>
> >
> >
> >
> >
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

An easy mistake to make, and to overlook.

 K.

On 13/6/07 10:56, "Jun Koi" <junkoi2004@gmail.com> wrote:
> What a shame!!! I think I should go hanging myself!!!
> 
> Good bye forever! Best wishes to you and Xen project!!!!!
> 
> Jun
> 
> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
>> 
>> 
>>> -----Original Message-----
>>> From: Keir Fraser [mailto:keir@xensource.com]
>>> Sent: 13 June 2007 10:45
>>> To: Jun Koi; Petersson, Mats
>>> Cc: xen-devel
>>> Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
>>> while native kernel can ???
>>> 
>>> 
>>> That''s fine. My conclusion is that this is user error: you
>>> are trying to
>>> mount /boot/sda2 and you actually mean /dev/sda2.
>> 
>> Well spotted. I just expected it to say "/dev/" rather than
"/boot/".
>> 
>> --
>> Mats
>>> 
>>>  -- Keir
>>> 
>>> On 13/6/07 10:21, "Jun Koi" <junkoi2004@gmail.com>
wrote:
>>> 
>>>> Here is the screenshot taken with a digital camera. I hope
>>> the screen
>>>> is clear enough for you to see.
>>>> 
>>>> Thanks,
>>>> Jun
>>>> 
>>>> 
>>>> 
>>>> On 6/13/07, Jun Koi <junkoi2004@gmail.com> wrote:
>>>>> Hi Mats,
>>>>> 
>>>>> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com>
wrote:
>>>>>> 
>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: xen-devel-bounces@lists.xensource.com
>>>>>>> [mailto:xen-devel-bounces@lists.xensource.com] On
Behalf
>>> Of Jun Koi
>>>>>>> Sent: 13 June 2007 09:54
>>>>>>> To: Keir Fraser
>>>>>>> Cc: xen-devel
>>>>>>> Subject: Re: [Xen-devel] Xen doesnt recognize my
root fs,
>>>>>>> while native kernel can ???
>>>>>>> 
>>>>>>> On 6/13/07, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
>>>>>>>> On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
>>>>>>>> 
>>>>>>>>>>> The point is that Xen doesnt boot
in the first place,
>>>>>>> so I cannot
>>>>>>>>>>> provide xm dmesg!
>>>>>>>>>>> 
>>>>>>>>>>> Below is the output from dmesg
(native kernel) and
>>>>>>> Dom0''s .config.
>>>>>>>>>>> Anything else do you need?
>>>>>>>>>> 
>>>>>>>>>> Can you get a serial line on the
machine?
>>>>>>>>> 
>>>>>>>>> Opps, that is compicated, as I dont have a
cable to do that.
>>>>>>>>> 
>>>>>>>>> So if you have no suggestion, perhaps I
must try this
>>>>>>> way. But perhaps
>>>>>>>>> it take more than a week, as I am away in
few days.
>>>>>>>> 
>>>>>>>> There''s a decent chance that comparing
the two dmesg
>>>>>>> outputs will show some
>>>>>>>> important deviation in the case of running on
Xen that is
>>>>>>> causing the boot
>>>>>>>> failure. Without the failing output
it''s hard to know
>>> where to start
>>>>>>>> looking.
>>>>>>>> 
>>>>>>> 
>>>>>>> I see, but can you imagine some reasons why that
>>> happens?  It makes
>>>>>>> absolute no sense to me.
>>>>>> 
>>>>>> There are lots of possible reasons. The most likely is
>>> that your kernel
>>>>>> in the native has drivers that are not part of the Xen
default
>>>>>> configuration.
>>>>>> 
>>>>>> The other very common problem is that you
don''t have
>>> those necessary
>>>>>> drivers in the "initrd" for your Xen. This is
a problem
>>> that is posted
>>>>>> about three times a week (at least) on the Xen Users
>>> mailing list [where
>>>>>> this problem probably should be discussed - but I think
since it''s
>>>>>> started here, we''ll keep it here].
>>>>>> 
>>>>> 
>>>>> No, that is not a reason in my case. I did it this way:
>>>>> - Native kernel (2.6.18) is compiled with all the necessary
drivers
>>>>> built-in. That means I dont need initrd to boot my machine
>>> with this
>>>>> kernel. And it boots well.
>>>>> - I copied the .config of native kernel above to Dom0, and
compile
>>>>> Dom0 with this option. (Of course before compiling, I
enabled Xen
>>>>> option, as you can see in the .config of Dom0 I sent in the
last
>>>>> mail). Again this time I dont need initrd.
>>>>> 
>>>>> So it is logical that Dom0 must boot, but it fails
>>> actually. That is
>>>>> why I find the situation very strange.
>>>>> 
>>>>> 
>>>>>>> I have found that my machine has no serial port, so
>>> perhaps I must buy
>>>>>>> a serial card to debug this problem. Wonder if
there is
>>> another way to
>>>>>>> avoid that (?)
>>>>>> If you have a digital camera and you add
"noreboot" to
>>> the commandline
>>>>>> of "xen.gz" in your grub configuration, maybe
you can
>>> upload (to some
>>>>>> photo-web-site or such) a screen-shot of the final few
>>> lines of the boot
>>>>>> and send a link to the list - that may not give all
>>> clues, but at least
>>>>>> it will indicate what''s going on.
>>>>> 
>>>>> OK, I will do that, as it is not desired to buy a serial
card :-)
>>>>> 
>>>>> Thanks,
>>>>> Jun
>>>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> What a shame!!! I think I should go hanging myself!!!
>
> Good bye forever! Best wishes to you and Xen project!!!!!
Don''t worry, I do that sort of thing all the time.

In fact, I''d bet that anybody who does any significant amount of
advanced Xen
development occasionally realises that the reason his cunning new feature 
ain''t working is because he was doing something basic like booting the
wrong
kernel image, passing wrong args, etc.

Good luck with whatever you''re planning for Xen :-)

Cheers,
Mark
>
> Jun
>
> On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
> > > -----Original Message-----
> > > From: Keir Fraser [mailto:keir@xensource.com]
> > > Sent: 13 June 2007 10:45
> > > To: Jun Koi; Petersson, Mats
> > > Cc: xen-devel
> > > Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> > > while native kernel can ???
> > >
> > >
> > > That''s fine. My conclusion is that this is user error:
you
> > > are trying to
> > > mount /boot/sda2 and you actually mean /dev/sda2.
> >
> > Well spotted. I just expected it to say "/dev/" rather than
"/boot/".
> >
> > --
> > Mats
> >
> > >  -- Keir
> > >
> > > On 13/6/07 10:21, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > > > Here is the screenshot taken with a digital camera. I hope
> > >
> > > the screen
> > >
> > > > is clear enough for you to see.
> > > >
> > > > Thanks,
> > > > Jun
> > > >
> > > > On 6/13/07, Jun Koi <junkoi2004@gmail.com> wrote:
> > > >> Hi Mats,
> > > >>
> > > >> On 6/13/07, Petersson, Mats
<Mats.Petersson@amd.com> wrote:
> > > >>>> -----Original Message-----
> > > >>>> From: xen-devel-bounces@lists.xensource.com
> > > >>>> [mailto:xen-devel-bounces@lists.xensource.com]
On Behalf
> > >
> > > Of Jun Koi
> > >
> > > >>>> Sent: 13 June 2007 09:54
> > > >>>> To: Keir Fraser
> > > >>>> Cc: xen-devel
> > > >>>> Subject: Re: [Xen-devel] Xen doesnt recognize my
root fs,
> > > >>>> while native kernel can ???
> > > >>>>
> > > >>>> On 6/13/07, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> > > >>>>> On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > > >>>>>>>> The point is that Xen doesnt
boot in the first place,
> > > >>>>
> > > >>>> so I cannot
> > > >>>>
> > > >>>>>>>> provide xm dmesg!
> > > >>>>>>>>
> > > >>>>>>>> Below is the output from dmesg
(native kernel) and
> > > >>>>
> > > >>>> Dom0''s .config.
> > > >>>>
> > > >>>>>>>> Anything else do you need?
> > > >>>>>>>
> > > >>>>>>> Can you get a serial line on the
machine?
> > > >>>>>>
> > > >>>>>> Opps, that is compicated, as I dont have
a cable to do that.
> > > >>>>>>
> > > >>>>>> So if you have no suggestion, perhaps I
must try this
> > > >>>>
> > > >>>> way. But perhaps
> > > >>>>
> > > >>>>>> it take more than a week, as I am away
in few days.
> > > >>>>>
> > > >>>>> There''s a decent chance that
comparing the two dmesg
> > > >>>>
> > > >>>> outputs will show some
> > > >>>>
> > > >>>>> important deviation in the case of running
on Xen that is
> > > >>>>
> > > >>>> causing the boot
> > > >>>>
> > > >>>>> failure. Without the failing output
it''s hard to know
> > >
> > > where to start
> > >
> > > >>>>> looking.
> > > >>>>
> > > >>>> I see, but can you imagine some reasons why that
> > >
> > > happens?  It makes
> > >
> > > >>>> absolute no sense to me.
> > > >>>
> > > >>> There are lots of possible reasons. The most likely
is
> > >
> > > that your kernel
> > >
> > > >>> in the native has drivers that are not part of the
Xen default
> > > >>> configuration.
> > > >>>
> > > >>> The other very common problem is that you
don''t have
> > >
> > > those necessary
> > >
> > > >>> drivers in the "initrd" for your Xen. This
is a problem
> > >
> > > that is posted
> > >
> > > >>> about three times a week (at least) on the Xen Users
> > >
> > > mailing list [where
> > >
> > > >>> this problem probably should be discussed - but I
think since it''s
> > > >>> started here, we''ll keep it here].
> > > >>
> > > >> No, that is not a reason in my case. I did it this way:
> > > >> - Native kernel (2.6.18) is compiled with all the
necessary drivers
> > > >> built-in. That means I dont need initrd to boot my
machine
> > >
> > > with this
> > >
> > > >> kernel. And it boots well.
> > > >> - I copied the .config of native kernel above to Dom0,
and compile
> > > >> Dom0 with this option. (Of course before compiling, I
enabled Xen
> > > >> option, as you can see in the .config of Dom0 I sent in
the last
> > > >> mail). Again this time I dont need initrd.
> > > >>
> > > >> So it is logical that Dom0 must boot, but it fails
> > >
> > > actually. That is
> > >
> > > >> why I find the situation very strange.
> > > >>
> > > >>>> I have found that my machine has no serial port,
so
> > >
> > > perhaps I must buy
> > >
> > > >>>> a serial card to debug this problem. Wonder if
there is
> > >
> > > another way to
> > >
> > > >>>> avoid that (?)
> > > >>>
> > > >>> If you have a digital camera and you add
"noreboot" to
> > >
> > > the commandline
> > >
> > > >>> of "xen.gz" in your grub configuration,
maybe you can
> > >
> > > upload (to some
> > >
> > > >>> photo-web-site or such) a screen-shot of the final
few
> > >
> > > lines of the boot
> > >
> > > >>> and send a link to the list - that may not give all
> > >
> > > clues, but at least
> > >
> > > >>> it will indicate what''s going on.
> > > >>
> > > >> OK, I will do that, as it is not desired to buy a serial
card :-)
> > > >>
> > > >> Thanks,
> > > >> Jun
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Hi All,

Why am i getting screenshot sent by Jun now after almost more than 24
hours late?

Something wrong somewhere ?

Any help?

thanks
--psr

On 6/13/07, Mark Williamson <mark.williamson@cl.cam.ac.uk>
wrote:
> > What a shame!!! I think I should go hanging myself!!!
> >
> > Good bye forever! Best wishes to you and Xen project!!!!!
>
> Don''t worry, I do that sort of thing all the time.
>
> In fact, I''d bet that anybody who does any significant amount of
advanced Xen
> development occasionally realises that the reason his cunning new feature
> ain''t working is because he was doing something basic like booting
the wrong
> kernel image, passing wrong args, etc.
>
> Good luck with whatever you''re planning for Xen :-)
>
> Cheers,
> Mark
>
> >
> > Jun
> >
> > On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
> > > > -----Original Message-----
> > > > From: Keir Fraser [mailto:keir@xensource.com]
> > > > Sent: 13 June 2007 10:45
> > > > To: Jun Koi; Petersson, Mats
> > > > Cc: xen-devel
> > > > Subject: Re: [Xen-devel] Xen doesnt recognize my root fs,
> > > > while native kernel can ???
> > > >
> > > >
> > > > That''s fine. My conclusion is that this is user
error: you
> > > > are trying to
> > > > mount /boot/sda2 and you actually mean /dev/sda2.
> > >
> > > Well spotted. I just expected it to say "/dev/" rather
than "/boot/".
> > >
> > > --
> > > Mats
> > >
> > > >  -- Keir
> > > >
> > > > On 13/6/07 10:21, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > > > > Here is the screenshot taken with a digital camera. I
hope
> > > >
> > > > the screen
> > > >
> > > > > is clear enough for you to see.
> > > > >
> > > > > Thanks,
> > > > > Jun
> > > > >
> > > > > On 6/13/07, Jun Koi <junkoi2004@gmail.com> wrote:
> > > > >> Hi Mats,
> > > > >>
> > > > >> On 6/13/07, Petersson, Mats
<Mats.Petersson@amd.com> wrote:
> > > > >>>> -----Original Message-----
> > > > >>>> From: xen-devel-bounces@lists.xensource.com
> > > > >>>>
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf
> > > >
> > > > Of Jun Koi
> > > >
> > > > >>>> Sent: 13 June 2007 09:54
> > > > >>>> To: Keir Fraser
> > > > >>>> Cc: xen-devel
> > > > >>>> Subject: Re: [Xen-devel] Xen doesnt
recognize my root fs,
> > > > >>>> while native kernel can ???
> > > > >>>>
> > > > >>>> On 6/13/07, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> > > > >>>>> On 13/6/07 08:49, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > > > >>>>>>>> The point is that Xen
doesnt boot in the first place,
> > > > >>>>
> > > > >>>> so I cannot
> > > > >>>>
> > > > >>>>>>>> provide xm dmesg!
> > > > >>>>>>>>
> > > > >>>>>>>> Below is the output from
dmesg (native kernel) and
> > > > >>>>
> > > > >>>> Dom0''s .config.
> > > > >>>>
> > > > >>>>>>>> Anything else do you need?
> > > > >>>>>>>
> > > > >>>>>>> Can you get a serial line on
the machine?
> > > > >>>>>>
> > > > >>>>>> Opps, that is compicated, as I dont
have a cable to do that.
> > > > >>>>>>
> > > > >>>>>> So if you have no suggestion,
perhaps I must try this
> > > > >>>>
> > > > >>>> way. But perhaps
> > > > >>>>
> > > > >>>>>> it take more than a week, as I am
away in few days.
> > > > >>>>>
> > > > >>>>> There''s a decent chance that
comparing the two dmesg
> > > > >>>>
> > > > >>>> outputs will show some
> > > > >>>>
> > > > >>>>> important deviation in the case of
running on Xen that is
> > > > >>>>
> > > > >>>> causing the boot
> > > > >>>>
> > > > >>>>> failure. Without the failing output
it''s hard to know
> > > >
> > > > where to start
> > > >
> > > > >>>>> looking.
> > > > >>>>
> > > > >>>> I see, but can you imagine some reasons why
that
> > > >
> > > > happens?  It makes
> > > >
> > > > >>>> absolute no sense to me.
> > > > >>>
> > > > >>> There are lots of possible reasons. The most
likely is
> > > >
> > > > that your kernel
> > > >
> > > > >>> in the native has drivers that are not part of
the Xen default
> > > > >>> configuration.
> > > > >>>
> > > > >>> The other very common problem is that you
don''t have
> > > >
> > > > those necessary
> > > >
> > > > >>> drivers in the "initrd" for your Xen.
This is a problem
> > > >
> > > > that is posted
> > > >
> > > > >>> about three times a week (at least) on the Xen
Users
> > > >
> > > > mailing list [where
> > > >
> > > > >>> this problem probably should be discussed - but
I think since it''s
> > > > >>> started here, we''ll keep it here].
> > > > >>
> > > > >> No, that is not a reason in my case. I did it this
way:
> > > > >> - Native kernel (2.6.18) is compiled with all the
necessary drivers
> > > > >> built-in. That means I dont need initrd to boot my
machine
> > > >
> > > > with this
> > > >
> > > > >> kernel. And it boots well.
> > > > >> - I copied the .config of native kernel above to
Dom0, and compile
> > > > >> Dom0 with this option. (Of course before compiling,
I enabled Xen
> > > > >> option, as you can see in the .config of Dom0 I
sent in the last
> > > > >> mail). Again this time I dont need initrd.
> > > > >>
> > > > >> So it is logical that Dom0 must boot, but it fails
> > > >
> > > > actually. That is
> > > >
> > > > >> why I find the situation very strange.
> > > > >>
> > > > >>>> I have found that my machine has no serial
port, so
> > > >
> > > > perhaps I must buy
> > > >
> > > > >>>> a serial card to debug this problem. Wonder
if there is
> > > >
> > > > another way to
> > > >
> > > > >>>> avoid that (?)
> > > > >>>
> > > > >>> If you have a digital camera and you add
"noreboot" to
> > > >
> > > > the commandline
> > > >
> > > > >>> of "xen.gz" in your grub
configuration, maybe you can
> > > >
> > > > upload (to some
> > > >
> > > > >>> photo-web-site or such) a screen-shot of the
final few
> > > >
> > > > lines of the boot
> > > >
> > > > >>> and send a link to the list - that may not give
all
> > > >
> > > > clues, but at least
> > > >
> > > > >>> it will indicate what''s going on.
> > > > >>
> > > > >> OK, I will do that, as it is not desired to buy a
serial card :-)
> > > > >>
> > > > >> Thanks,
> > > > >> Jun
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
>
>
> --
> Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
> Mark: To answer a question with a question: What use is a skateboard?
> Dave: Skateboards have wheels.
> Mark: My wheel has a wheel!
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

-- 
---
pradeep singh rautela

"Genius is 1% inspiration, and 99% perspiration" - not me :)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> Why am i getting screenshot sent by Jun now after almost more than 24
> hours late?
>
> Something wrong somewhere ?
I imagine the mailing list objected to it on the grounds it was large / could 
be spam, and so held it for administrator approval.

Mats replied to it yesterday because he was on the cc list so it went direct 
to him even though it didn''t go straight to the list.

The same thing can happen when non-members post to the list, since they also 
have to be approved by the admin.

Cheers,
Mark
>
> On 6/13/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:
> > > What a shame!!! I think I should go hanging myself!!!
> > >
> > > Good bye forever! Best wishes to you and Xen project!!!!!
> >
> > Don''t worry, I do that sort of thing all the time.
> >
> > In fact, I''d bet that anybody who does any significant amount
of advanced
> > Xen development occasionally realises that the reason his cunning new
> > feature ain''t working is because he was doing something basic
like
> > booting the wrong kernel image, passing wrong args, etc.
> >
> > Good luck with whatever you''re planning for Xen :-)
> >
> > Cheers,
> > Mark
> >
> > > Jun
> > >
> > > On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:
> > > > > -----Original Message-----
> > > > > From: Keir Fraser [mailto:keir@xensource.com]
> > > > > Sent: 13 June 2007 10:45
> > > > > To: Jun Koi; Petersson, Mats
> > > > > Cc: xen-devel
> > > > > Subject: Re: [Xen-devel] Xen doesnt recognize my root
fs,
> > > > > while native kernel can ???
> > > > >
> > > > >
> > > > > That''s fine. My conclusion is that this is
user error: you
> > > > > are trying to
> > > > > mount /boot/sda2 and you actually mean /dev/sda2.
> > > >
> > > > Well spotted. I just expected it to say "/dev/"
rather than "/boot/".
> > > >
> > > > --
> > > > Mats
> > > >
> > > > >  -- Keir
> > > > >
> > > > > On 13/6/07 10:21, "Jun Koi"
<junkoi2004@gmail.com> wrote:
> > > > > > Here is the screenshot taken with a digital
camera. I hope
> > > > >
> > > > > the screen
> > > > >
> > > > > > is clear enough for you to see.
> > > > > >
> > > > > > Thanks,
> > > > > > Jun
> > > > > >
> > > > > > On 6/13/07, Jun Koi <junkoi2004@gmail.com>
wrote:
> > > > > >> Hi Mats,
> > > > > >>
> > > > > >> On 6/13/07, Petersson, Mats
<Mats.Petersson@amd.com> wrote:
> > > > > >>>> -----Original Message-----
> > > > > >>>> From:
xen-devel-bounces@lists.xensource.com
> > > > > >>>>
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf
> > > > >
> > > > > Of Jun Koi
> > > > >
> > > > > >>>> Sent: 13 June 2007 09:54
> > > > > >>>> To: Keir Fraser
> > > > > >>>> Cc: xen-devel
> > > > > >>>> Subject: Re: [Xen-devel] Xen doesnt
recognize my root fs,
> > > > > >>>> while native kernel can ???
> > > > > >>>>
> > > > > >>>> On 6/13/07, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> > > > > >>>>> On 13/6/07 08:49, "Jun
Koi" <junkoi2004@gmail.com> wrote:
> > > > > >>>>>>>> The point is that Xen
doesnt boot in the first place,
> > > > > >>>>
> > > > > >>>> so I cannot
> > > > > >>>>
> > > > > >>>>>>>> provide xm dmesg!
> > > > > >>>>>>>>
> > > > > >>>>>>>> Below is the output
from dmesg (native kernel) and
> > > > > >>>>
> > > > > >>>> Dom0''s .config.
> > > > > >>>>
> > > > > >>>>>>>> Anything else do you
need?
> > > > > >>>>>>>
> > > > > >>>>>>> Can you get a serial line
on the machine?
> > > > > >>>>>>
> > > > > >>>>>> Opps, that is compicated, as I
dont have a cable to do that.
> > > > > >>>>>>
> > > > > >>>>>> So if you have no suggestion,
perhaps I must try this
> > > > > >>>>
> > > > > >>>> way. But perhaps
> > > > > >>>>
> > > > > >>>>>> it take more than a week, as I
am away in few days.
> > > > > >>>>>
> > > > > >>>>> There''s a decent chance
that comparing the two dmesg
> > > > > >>>>
> > > > > >>>> outputs will show some
> > > > > >>>>
> > > > > >>>>> important deviation in the case of
running on Xen that is
> > > > > >>>>
> > > > > >>>> causing the boot
> > > > > >>>>
> > > > > >>>>> failure. Without the failing
output it''s hard to know
> > > > >
> > > > > where to start
> > > > >
> > > > > >>>>> looking.
> > > > > >>>>
> > > > > >>>> I see, but can you imagine some
reasons why that
> > > > >
> > > > > happens?  It makes
> > > > >
> > > > > >>>> absolute no sense to me.
> > > > > >>>
> > > > > >>> There are lots of possible reasons. The
most likely is
> > > > >
> > > > > that your kernel
> > > > >
> > > > > >>> in the native has drivers that are not
part of the Xen default
> > > > > >>> configuration.
> > > > > >>>
> > > > > >>> The other very common problem is that you
don''t have
> > > > >
> > > > > those necessary
> > > > >
> > > > > >>> drivers in the "initrd" for your
Xen. This is a problem
> > > > >
> > > > > that is posted
> > > > >
> > > > > >>> about three times a week (at least) on the
Xen Users
> > > > >
> > > > > mailing list [where
> > > > >
> > > > > >>> this problem probably should be discussed
- but I think since
> > > > > >>> it''s started here, we''ll
keep it here].
> > > > > >>
> > > > > >> No, that is not a reason in my case. I did it
this way:
> > > > > >> - Native kernel (2.6.18) is compiled with all
the necessary
> > > > > >> drivers built-in. That means I dont need
initrd to boot my
> > > > > >> machine
> > > > >
> > > > > with this
> > > > >
> > > > > >> kernel. And it boots well.
> > > > > >> - I copied the .config of native kernel above
to Dom0, and
> > > > > >> compile Dom0 with this option. (Of course
before compiling, I
> > > > > >> enabled Xen option, as you can see in the
.config of Dom0 I sent
> > > > > >> in the last mail). Again this time I dont need
initrd.
> > > > > >>
> > > > > >> So it is logical that Dom0 must boot, but it
fails
> > > > >
> > > > > actually. That is
> > > > >
> > > > > >> why I find the situation very strange.
> > > > > >>
> > > > > >>>> I have found that my machine has no
serial port, so
> > > > >
> > > > > perhaps I must buy
> > > > >
> > > > > >>>> a serial card to debug this problem.
Wonder if there is
> > > > >
> > > > > another way to
> > > > >
> > > > > >>>> avoid that (?)
> > > > > >>>
> > > > > >>> If you have a digital camera and you add
"noreboot" to
> > > > >
> > > > > the commandline
> > > > >
> > > > > >>> of "xen.gz" in your grub
configuration, maybe you can
> > > > >
> > > > > upload (to some
> > > > >
> > > > > >>> photo-web-site or such) a screen-shot of
the final few
> > > > >
> > > > > lines of the boot
> > > > >
> > > > > >>> and send a link to the list - that may not
give all
> > > > >
> > > > > clues, but at least
> > > > >
> > > > > >>> it will indicate what''s going on.
> > > > > >>
> > > > > >> OK, I will do that, as it is not desired to
buy a serial card
> > > > > >> :-)
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Jun
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> >
> > --
> > Dave: Just a question. What use is a unicyle with no seat?  And no
> > pedals! Mark: To answer a question with a question: What use is a
> > skateboard? Dave: Skateboards have wheels.
> > Mark: My wheel has a wheel!
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel


-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 6/14/07, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:
[snip]
>
> I imagine the mailing list objected to it on the grounds it was large /
could
> be spam, and so held it for administrator approval.
>
> Mats replied to it yesterday because he was on the cc list so it went
direct
> to him even though it didn''t go straight to the list.
>
> The same thing can happen when non-members post to the list, since they
also
> have to be approved by the admin.
Ok, thats fine.
thanks Mark
--psr
>
> Cheers,
> Mark
[snip]
> --
> Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
> Mark: To answer a question with a question: What use is a skateboard?
> Dave: Skateboards have wheels.
> Mark: My wheel has a wheel!
>

-- 
---
pradeep singh rautela

"Genius is 1% inspiration, and 99% perspiration" - not me :)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel