[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#588509: hang sometimes occurs earlier



Hi,

I'm seeing the same issue (hang at boot of -17 kernel) but the hang is sometimes much earlier in the boot process on my system:

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.32-5-amd64 (Debian 2.6.32-17) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Sun Jul 11 01:44:28 UTC 2010 [ 0.000000] Command line: root=/dev/mapper/vgsilver-root ro console=hvc0 console=tty0
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 0000000080000000 (usable)
[    0.000000] DMI not present or invalid.
[    0.000000] last_pfn = 0x80000 max_arch_pfn = 0x400000000
[    0.000000] init_memory_mapping: 0000000000000000-0000000080000000
[    0.000000] RAMDISK: 016a5000 - 031dc000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at 0000000000000000-0000000080000000
[    0.000000] Bootmem setup node 0 0000000000000000-0000000080000000
[    0.000000]   NODE_DATA [0000000000008000 - 000000000000ffff]
[    0.000000]   bootmap [0000000000010000 -  000000000001ffff] pages 10
[    0.000000] (7 early reservations) ==> bootmem [0000000000 - 0080000000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [00035df000 - 00035fe000] XEN PAGETABLES ==> [00035df000 - 00035fe000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 0001684754] TEXT DATA BSS ==> [0001000000 - 0001684754] [ 0.000000] #4 [00016a5000 - 00031dc000] RAMDISK ==> [00016a5000 - 00031dc000] [ 0.000000] #5 [00031dc000 - 00035df000] XEN START INFO ==> [00031dc000 - 00035df000] [ 0.000000] #6 [0000100000 - 00004e1000] PGTABLE ==> [0000100000 - 00004e1000]
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000000 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   0x00100000 -> 0x00100000
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000000 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x00080000
[    0.000000] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] No local APIC present
[    0.000000] APIC: disable apic facility
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 [ 0.000000] Allocating PCI resources starting at 80000000 (gap: 80000000:80000000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 3.2-1
[    0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff880003634000 s90328 r8192 d24360 u122880

sometimes the boot gets to the "Write protecting the kernel read-only data" as mentioned in the bug report.

The VM was running 2.6.32-15 before without any real issues.

The dom0 runs Xen 3.2

Regards,

Rik



Reply to: