Thomas Schwinge
2010-Apr-08 11:34 UTC
[Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello!
This was originally reported to the Debian BTS,
<http://bugs.debian.org/576877>, but Ian Campbell suggested to forward it
to xen-devel.
To get the Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 kernel to
boot, I need to supply mem=4G. This was not necessary with the 2.6.32-10
kernel.
I only changed the kernel, no further changes.
2.6.32-11 is ``based on commit f64df18aae5ab07b44bdcc2334cf0044ef46320c
of
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git.''''
--
according to debian/patches/features/all/xen/pvops.patch.
commit f64df18aae5ab07b44bdcc2334cf0044ef46320c
Merge: d945b01 d69a8da
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Thu Mar 25 17:00:21 2010 -0700
Merge commit ''d69a8da4f6f2bb1815d2bc2f49afed3f3ee4f07d''
into xen/stable-2.6.32.x
* commit ''d69a8da4f6f2bb1815d2bc2f49afed3f3ee4f07d'':
xen/apic: Don''t register GSI in pre-setup
xen/apic: Map physical interrupt before setting up GSI
xen/apic: Control-flow cleanup in xen_register_gsi
The noreboot and nopat options that Ian suggested in
<http://bugs.debian.org/576877#10> have no effect. (I always have
noreboot specified.)
2.6.32-10:
(XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@debian.org) (gcc version
4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010
(XEN) Command line:
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009e000 (usable)
(XEN) 000000000009e000 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000ddee0000 (usable)
(XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data)
(XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS)
(XEN) 00000000ddf00000 - 00000000e0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000fff00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000120000000 (usable)
(XEN) System RAM: 4062MB (4159992kB)
2.6.32-11: resets the machine immediatelly, no log messages visible
(don''t have serial console set-up).
2.6.32-11, with mem=4G:
(XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@debian.org) (gcc version
4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010
(XEN) Command line: mem=4G
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Truncating RAM from 4718592kB to 4194304kB
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009e000 (usable)
(XEN) 000000000009e000 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000ddee0000 (usable)
(XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data)
(XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS)
(XEN) 00000000ddf00000 - 00000000e0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000fff00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3550MB (3635704kB)
/proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 47
model name : AMD Sempron(tm) Processor 3000+
stepping : 2
cpu MHz : 1800.085
cache size : 128 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu de tsc msr pae cx8 apic mtrr cmov clflush mmx fxsr sse
sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up rep_good pni hypervisor
lahf_lm
bogomips : 3600.17
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc
-- Package-specific info:
** Version:
Linux version 2.6.32-4-xen-amd64 (Debian 2.6.32-11) (maks@debian.org) (gcc
version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Mon Apr 5 23:19:15 UTC 2010
** Command line:
root=/dev/mapper/vg0-boole--root ro console=tty0
** Tainted: W (512)
* Taint on warning.
** Kernel log:
[ 3.594644] sr 0:0:0:0: Attached scsi CD-ROM sr0
[ 3.595448] usbcore: registered new interface driver hiddev
[ 3.599715] sd 2:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0
GB/74.5 GiB)
[ 3.599855] sd 2:0:0:0: [sda] Write Protect is off
[ 3.599893] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.599938] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn''t support DPO or FUA
[ 3.600295] sda:
[ 3.603437] input: Logitech USB-PS/2 Optical Mouse as
/devices/pci0000:00/0000:00:03.0/usb2/2-3/2-3:1.0/input/input4
[ 3.603627] generic-usb 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10
Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:03.0-3/input0
[ 3.603717] usbcore: registered new interface driver usbhid
[ 3.603755] usbhid: v2.6:USB HID core driver
[ 3.613586] sr 0:0:0:0: Attached scsi generic sg0 type 5
[ 3.614071] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 3.625464] sda1
[ 3.626452] sd 2:0:0:0: [sda] Attached SCSI disk
[ 5.544048] floppy0: no floppy controllers found
[ 5.611207] device-mapper: uevent: version 1.0.3
[ 5.612270] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-devel@redhat.com
[ 5.876201] PM: Starting manual resume from disk
[ 5.876242] PM: Resume from partition 254:1
[ 5.876244] PM: Checking hibernation image.
[ 5.876535] PM: Error -22 checking image file
[ 5.876538] PM: Resume from disk failed.
[ 5.929409] kjournald starting. Commit interval 5 seconds
[ 5.929471] EXT3-fs: mounted filesystem with ordered data mode.
[ 7.388166] udev: starting version 151
[ 7.941584] processor LNXCPU:00: registered as cooling_device0
[ 8.258516] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 8.273361] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 8.552543] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 8.568814] EDAC MC: Ver: 2.1.0 Apr 5 2010
[ 8.582764] parport_pc 00:08: reported by Plug and Play ACPI
[ 8.582899] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[ 8.675567] EDAC amd64_edac: Ver: 3.2.0 Apr 5 2010
[ 8.675964] EDAC amd64: ECC is enabled by BIOS.
[ 8.676454] EDAC MC: Rev E or earlier detected
[ 8.677722] EDAC MC0: Giving out device to ''amd64_edac''
''RevF'': DEV 0000:00:18.2
[ 8.678852] EDAC PCI0: Giving out device to module
''amd64_edac'' controller ''EDAC PCI
controller'': DEV ''0000:00:18.2'' (POLLED)
[ 8.839689] Error: Driver ''pcspkr'' is already registered,
aborting...
[ 8.989920] xen: registering gsi 18 triggering 0 polarity 1
[ 8.989933] alloc irq_desc for 18 on node 0
[ 8.989937] alloc kstat_irqs on node 0
[ 8.989947] xen: --> irq=18
[ 8.989958] Intel ICH 0000:00:02.7: PCI INT C -> GSI 18 (level, low) ->
IRQ 18
[ 9.312097] intel8x0_measure_ac97_clock: measured 53952 usecs (2596 samples)
[ 9.312140] intel8x0: clocking to 48000
[ 11.580049] floppy0: no floppy controllers found
[ 12.959737] EXT3 FS on dm-0, internal journal
[ 13.297799] Adding 974840k swap on /dev/mapper/vg0-boole--swap. Priority:-1
extents:1 across:974840k
[ 13.506263] kjournald starting. Commit interval 5 seconds
[ 13.506564] EXT3 FS on dm-2, internal journal
[ 13.506633] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.984105] loop: module loaded
[ 14.288494] Bridge firewalling registered
[ 14.333916] device eth0 entered promiscuous mode
[ 14.337838] r8169: eth0: link up
[ 14.345691] br0: port 1(eth0) entering learning state
[ 24.588013] br0: no IPv6 routers present
[ 24.992008] eth0: no IPv6 routers present
[ 29.344014] br0: port 1(eth0) entering forwarding state
[ 44.728065] RPC: Registered udp transport module.
[ 44.728112] RPC: Registered tcp transport module.
[ 44.728147] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 44.810238] Slow work thread pool: Starting up
[ 44.810370] Slow work thread pool: Ready
[ 44.810504] FS-Cache: Loaded
[ 44.862639] FS-Cache: Netfs ''nfs'' registered for caching
[ 44.896796] svc: failed to register lockdv1 RPC service (errno 97).
[ 45.430933] fuse init (API version 7.13)
[ 46.057971] Event-channel device installed.
[ 46.255770] alloc irq_desc for 502 on node 0
[ 46.255776] alloc kstat_irqs on node 0
[ 46.255853] xenbus_probe wake_waiting
[ 46.255920] xenbus_probe wake_waiting
[ 46.255975] alloc irq_desc for 501 on node 0
[ 46.255979] alloc kstat_irqs on node 0
[ 46.257009] XENBUS: Unable to read cpu state
[ 46.257711] xenbus_probe_devices backend
[ 46.258085] xenbus_probe_devices failed xenbus_directory
[ 46.258128] backend_probe_and_watch devices probed ok
[ 46.258386] backend_probe_and_watch watch add ok ok
[ 46.258425] backend_probe_and_watch all done
[ 46.258460] xenbus_probe_devices device
[ 46.258667] xenbus_probe_devices failed xenbus_directory
[ 46.258705] frontend_probe_and_watch devices probed ok
[ 46.258883] frontend_probe_and_watch watch add ok ok
[ 46.258920] frontend_probe_and_watch all done
[ 54.348904] Bluetooth: Core ver 2.15
[ 54.349059] NET: Registered protocol family 31
[ 54.349096] Bluetooth: HCI device and connection manager initialized
[ 54.349134] Bluetooth: HCI socket layer initialized
[ 54.465496] Bluetooth: L2CAP ver 2.14
[ 54.465541] Bluetooth: L2CAP socket layer initialized
[ 54.495468] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 54.495515] Bluetooth: BNEP filters: protocol multicast
[ 54.498713] Bluetooth: RFCOMM TTY layer initialized
[ 54.498765] Bluetooth: RFCOMM socket layer initialized
[ 54.498802] Bluetooth: RFCOMM ver 1.11
[ 54.532711] Bluetooth: SCO (Voice Link) ver 0.6
[ 54.532757] Bluetooth: SCO socket layer initialized
** Model information
sys_vendor: FUJITSU SIEMENS
product_name: D2264-A1
product_version:
chassis_vendor: FUJITSU SIEMENS
chassis_version:
bios_vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
bios_version: 5.00 R1.07-01.2264.A1
board_vendor: FUJITSU SIEMENS
board_name: D2264-A1
board_version: S26361-D2264-A1
** Loaded modules:
Module Size Used by
sco 7209 2
bnep 9411 2
rfcomm 29565 0
l2cap 24704 4 bnep,rfcomm
crc16 1319 1 l2cap
bluetooth 41795 6 sco,bnep,rfcomm,l2cap
rfkill 13012 2 bluetooth
xen_evtchn 4259 1
xenfs 9472 1
fuse 50126 1
nfs 240554 1
lockd 57539 1 nfs
fscache 29818 1 nfs
nfs_acl 2031 1 nfs
auth_rpcgss 33460 1 nfs
sunrpc 161159 11 nfs,lockd,nfs_acl,auth_rpcgss
bridge 39598 0
stp 1440 1 bridge
loop 11783 0
snd_intel8x0 24122 0
snd_ac97_codec 99186 1 snd_intel8x0
ac97_bus 1086 1 snd_ac97_codec
amd64_edac_mod 13630 0
snd_pcm 60503 2 snd_intel8x0,snd_ac97_codec
parport_pc 18855 0
psmouse 49521 0
parport 27938 1 parport_pc
snd_timer 15502 1 snd_pcm
edac_core 29245 3 amd64_edac_mod
shpchp 26264 0
edac_mce_amd 6369 1 amd64_edac_mod
pcspkr 1699 0
serio_raw 3752 0
k8temp 3139 0
pci_hotplug 21171 1 shpchp
snd 46350 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 4598 1 snd
snd_page_alloc 6217 2 snd_intel8x0,snd_pcm
evdev 7336 11
container 2389 0
processor 30247 0
ext3 106502 2
jbd 37053 1 ext3
mbcache 4970 1 ext3
dm_mod 53674 18
sg 18744 0
sd_mod 29689 2
crc_t10dif 1276 1 sd_mod
usbhid 33244 0
sr_mod 12602 0
hid 62793 1 usbhid
cdrom 29399 1 sr_mod
sata_sis 3730 1
ata_generic 2983 0
ohci_hcd 19212 0
pata_sis 9623 1 sata_sis
ehci_hcd 30802 0
r8169 28877 0
mii 3210 1 r8169
libata 132183 3 sata_sis,ata_generic,pata_sis
button 4634 0
usbcore 121815 4 usbhid,ohci_hcd,ehci_hcd
nls_base 6377 1 usbcore
scsi_mod 121925 4 sg,sd_mod,sr_mod,libata
thermal 11674 0
fan 3346 0
thermal_sys 11878 3 processor,thermal,fan
** PCI devices:
00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 761/M761 Host
[1039:0761] (rev 01)
Subsystem: Fujitsu Technology Solutions D2030-A1 Motherboard [1734:1099]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort+ >SERR- <PERR- INTx-
Latency: 64
Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=32M]
Capabilities: <access denied>
00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SG86C202 [1039:0002]
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
I/O behind bridge: 00002000-00002fff
Memory behind bridge: fa100000-fa1fffff
Prefetchable memory behind bridge: f0000000-f7ffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS965 [MuTIOL Media
IO] [1039:0965] (rev 48)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort+ >SERR- <PERR- INTx-
Latency: 0
00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE]
[1039:5513] (rev 01) (prog-if 80 [Master])
Subsystem: Fujitsu Technology Solutions D2030-A1 Motherboard [1734:1095]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 128
Interrupt: pin ? routed to IRQ 16
Region 0: I/O ports at 01f0 [size=8]
Region 1: I/O ports at 03f4 [size=1]
Region 2: I/O ports at 0170 [size=8]
Region 3: I/O ports at 0374 [size=1]
Region 4: I/O ports at 1c80 [size=16]
Capabilities: <access denied>
Kernel driver in use: pata_sis
00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS]
AC''97 Sound Controller [1039:7012] (rev a0)
Subsystem: Fujitsu Technology Solutions Device [1734:109c]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 173 (13000ns min, 2750ns max)
Interrupt: pin C routed to IRQ 18
Region 0: I/O ports at 1400 [size=256]
Region 1: I/O ports at 1000 [size=128]
Capabilities: <access denied>
Kernel driver in use: Intel ICH
00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1
Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI])
Subsystem: Fujitsu Technology Solutions D2030-A1 Motherboard [1734:1095]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64 (20000ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1
Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI])
Subsystem: Fujitsu Technology Solutions D2030-A1 Motherboard [1734:1095]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64 (20000ns max)
Interrupt: pin B routed to IRQ 21
Region 0: Memory at fa001000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1
Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI])
Subsystem: Fujitsu Technology Solutions D2030-A1 Motherboard [1734:1095]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64 (20000ns max)
Interrupt: pin C routed to IRQ 22
Region 0: Memory at fa002000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd
00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0
Controller [1039:7002] (prog-if 20 [EHCI])
Subsystem: Fujitsu Technology Solutions D2030-A1 [1734:1095]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64 (20000ns max)
Interrupt: pin D routed to IRQ 23
Region 0: Memory at fa003000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
00:05.0 IDE interface [0101]: Silicon Integrated Systems [SiS] 182 SATA/RAID
Controller [1039:0182] (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Fujitsu Technology Solutions D2030-A1 [1734:1095]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 1cb0 [size=8]
Region 1: I/O ports at 1ca4 [size=4]
Region 2: I/O ports at 1ca8 [size=8]
Region 3: I/O ports at 1ca0 [size=4]
Region 4: I/O ports at 1c90 [size=16]
Region 5: I/O ports at 1c00 [size=128]
Capabilities: <access denied>
Kernel driver in use: sata_sis
00:06.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
[1039:000a] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
00:09.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet [10ec:8169] (rev 10)
Subsystem: Fujitsu Technology Solutions D2030-A1 [1734:1091]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at 1800 [size=256]
Region 1: Memory at fa004000 (32-bit, non-prefetchable) [size=256]
Capabilities: <access denied>
Kernel driver in use: r8169
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration [1022:1100]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Capabilities: <access denied>
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map [1022:1101]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller [1022:1102]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Kernel driver in use: amd64_edac
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control [1022:1103]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Kernel driver in use: k8temp
00:1f.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
[1039:0004] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort+ <SERR- <PERR-
BridgeCtl: Parity+ SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport
01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems [SiS]
661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] (rev 03)
(prog-if 00 [VGA controller])
Subsystem: Fujitsu Technology Solutions D2030-A1 [1734:1099]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 11
BIST result: 00
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at fa100000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at 2000 [size=128]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
** USB devices:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel
Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (900, ''testing''), (800,
''unstable'')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-4-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-4-xen-amd64 depends on:
ii debconf [debconf-2.0] 1.5.30 Debian configuration management sy
ii initramfs-tools 0.93.4 tools for generating an initramfs
ii linux-base 2.6.32-11 Linux image base package
ii module-init-tools 3.12~pre2-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-4-xen-amd64 recommends:
ii firmware-linux-free 2.6.32-9 Binary firmware for various driver
Versions of packages linux-image-2.6.32-4-xen-amd64 suggests:
pn grub <none> (no description available)
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-4-xen-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
ii xen-hypervisor-3.4-amd64 [xe 3.4.3~rc3-1 The Xen Hypervisor on AMD64
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.32-4-xen-amd64/prerm/would-invalidate-boot-loader-2.6.32-4-xen-amd64:
true
linux-image-2.6.32-4-xen-amd64/postinst/bootloader-test-error-2.6.32-4-xen-amd64:
linux-image-2.6.32-4-xen-amd64/postinst/missing-firmware-2.6.32-4-xen-amd64:
linux-image-2.6.32-4-xen-amd64/postinst/depmod-error-initrd-2.6.32-4-xen-amd64:
false
linux-image-2.6.32-4-xen-amd64/postinst/bootloader-error-2.6.32-4-xen-amd64:
linux-image-2.6.32-4-xen-amd64/prerm/removing-running-kernel-2.6.32-4-xen-amd64:
true
Regards,
Thomas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Apr-08 13:38 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On Thu, Apr 08, 2010 at 01:34:22PM +0200, Thomas Schwinge wrote:> Hello! > > This was originally reported to the Debian BTS, > <http://bugs.debian.org/576877>, but Ian Campbell suggested to forward it > to xen-devel.Nice writeup. I like how you included all the details that I would have thought of to ask. Is this the normal Debian bug reporting procedure ?> > > To get the Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 kernel to > boot, I need to supply mem=4G. This was not necessary with the 2.6.32-10 > kernel. > > I only changed the kernel, no further changes. > > 2.6.32-11 is ``based on commit f64df18aae5ab07b44bdcc2334cf0044ef46320c > of git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git.'''' -- > according to debian/patches/features/all/xen/pvops.patch. > > commit f64df18aae5ab07b44bdcc2334cf0044ef46320c > Merge: d945b01 d69a8da > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > Date: Thu Mar 25 17:00:21 2010 -0700 > > Merge commit ''d69a8da4f6f2bb1815d2bc2f49afed3f3ee4f07d'' into xen/stable-2.6.32.x > > * commit ''d69a8da4f6f2bb1815d2bc2f49afed3f3ee4f07d'': > xen/apic: Don''t register GSI in pre-setup > xen/apic: Map physical interrupt before setting up GSI > xen/apic: Control-flow cleanup in xen_register_gsi > > > The noreboot and nopat options that Ian suggested in > <http://bugs.debian.org/576877#10> have no effect. (I always have > noreboot specified.)OK. Then the next thing that comes in my mind is ACPI GSI. For that thought we will need ...> > > 2.6.32-10: > (XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@debian.org) (gcc version 4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010 > (XEN) Command line: > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009e000 (usable) > (XEN) 000000000009e000 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000ddee0000 (usable) > (XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data) > (XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS) > (XEN) 00000000ddf00000 - 00000000e0000000 (reserved) > (XEN) 00000000fec00000 - 00000000fec10000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000fff00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000120000000 (usable) > (XEN) System RAM: 4062MB (4159992kB) > > 2.6.32-11: resets the machine immediatelly, no log messages visible > (don''t have serial console set-up)... we need to see more of what Xen and Linux prints during bootup which can be done by adding these in the Xen command line: "loglvl=all guest_loglvl=all sync_console console_to_ring apic=debug apic_verbosity=debug" (the kitchensink of all the debug options on) and this in the Linux kernel line: "console=hvc0 earlyprintk=xen debug initcall_debug acpi.debug_level=0xffffffff acpi.debug_layer=0x2" You might get away without a serial console and see the output on the display. But it would be much much better to get the serial console working. Pasi wrote an excellent Wiki page explaining how to do this: http://wiki.xensource.com/xenwiki/XenSerialConsole Please e-mail back the full serial console or the last thing you see on the VGA screen. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2010-Apr-08 13:42 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On Thu, 2010-04-08 at 09:38 -0400, Konrad Rzeszutek Wilk wrote:> On Thu, Apr 08, 2010 at 01:34:22PM +0200, Thomas Schwinge wrote: > > Hello! > > > > This was originally reported to the Debian BTS, > > <http://bugs.debian.org/576877>, but Ian Campbell suggested to forward it > > to xen-devel. > > Nice writeup. I like how you included all the details that I would have > thought of to ask. Is this the normal Debian bug reporting procedure ?The Debian "reportbug" tool supports per-package plugins and the kernel packages install a plugin which collect all this stuff. Ian. -- Ian Campbell Current Noise: Strapping Young Lad - Cod Metal Thing Don''t get to bragging. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Schwinge
2010-Apr-08 22:19 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello!
OK. You really tricked me into doing that: soldering iron, D-Sub 9
sockets, null modem cable, and all that... :-)
But here we go:
(XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@debian.org) (gcc version
4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010
(XEN) Console output is synchronous.
(XEN) Command line: com1=38400,8n1 console=com1 loglvl=all guest_loglvl=all
sync_console console_to_ring apic=debug apic_verbosity=debug
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009e000 (usable)
(XEN) 000000000009e000 - 00000000000a0000 (reserved)
(XEN) 00000000000e4000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000ddee0000 (usable)
(XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data)
(XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS)
(XEN) 00000000ddf00000 - 00000000e0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000fff00000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000120000000 (usable)
(XEN) System RAM: 4062MB (4159992kB)
(XEN) ACPI: RSDP 000F7350, 0024 (r2 PTLTD )
(XEN) ACPI: XSDT DDEEB7E4, 004C (r1 PTLTD XSDT 50000 LTP 0)
(XEN) ACPI: FACP DDEEB8A4, 00F4 (r3 FSC �PZ- 50000 F4240)
(XEN) ACPI: DSDT DDEEB998, 34FB (r1 FSC D2030 50000 MSFT 2000002)
(XEN) ACPI: FACS DDEEFFC0, 0040
(XEN) ACPI: SSDT DDEEEE93, 00B5 (r1 PTLTD POWERNOW 50000 LTP 1)
(XEN) ACPI: APIC DDEEEF48, 0050 (r1 PTLTD APIC 50000 LTP 0)
(XEN) ACPI: MCFG DDEEEF98, 0040 (r1 PTLTD MCFG 50000 LTP 0)
(XEN) ACPI: BOOT DDEEEFD8, 0028 (r1 PTLTD $SBFTBL$ 50000 LTP 1)
(XEN) NUMA turned off
(XEN) Faking a node at 0000000000000000-0000000120000000
(XEN) Domain heap initialised
(XEN) found SMP MP-table at 000f73b0
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: PM-Timer IO Port: 0xf008
(XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[f004,0], pm1x_evt[f000,0]
(XEN) ACPI: wakeup_vec[ddeeffcc], vec_size[20]
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:15 APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 1, version 20, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) mapped APIC to ffff828bffffe000 (fee00000)
(XEN) mapped IOAPIC to ffff828bffffd000 (fec00000)
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 1800.104 MHz processor.
(XEN) CPU0: AMD Flush Filter disabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 128K (64 bytes/line)
(XEN) CPU0: AMD K8 machine check reporting enabled.
(XEN) CPU0: AMD Sempron(tm) Processor 3000+ stepping 02
(XEN) Getting VERSION: 50010
(XEN) Getting VERSION: 50010
(XEN) Getting ID: 0
(XEN) Getting LVT0: 10000
(XEN) Getting LVT1: 10000
(XEN) masked ExtINT on CPU#0
(XEN) Total of 1 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) init IO_APIC IRQs
(XEN) IO-APIC (apicid-pin) 1-0, 1-16, 1-17, 1-18, 1-19, 1-20, 1-21, 1-22,
1-23 not connected.
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
(XEN) number of MP IRQ sources: 15.
(XEN) number of IO-APIC #1 registers: 24.
(XEN) testing the IO APIC.......................
(XEN) IO APIC #1......
(XEN) .... register #00: 01000000
(XEN) ....... : physical APIC id: 01
(XEN) ....... : Delivery Type: 0
(XEN) ....... : LTS : 0
(XEN) .... register #01: 00178014
(XEN) ....... : max redirection entries: 0017
(XEN) ....... : PRQ implemented: 1
(XEN) ....... : IO APIC version: 0014
(XEN) .... register #02: 01000000
(XEN) ....... : arbitration: 01
(XEN) .... IRQ redirection table:
(XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
(XEN) 00 000 00 1 0 0 0 0 0 0 00
(XEN) 01 001 01 0 0 0 0 0 1 1 20
(XEN) 02 001 01 0 0 0 0 0 1 1 F0
(XEN) 03 001 01 0 0 0 0 0 1 1 28
(XEN) 04 001 01 0 0 0 0 0 1 1 F1
(XEN) 05 001 01 0 0 0 0 0 1 1 30
(XEN) 06 001 01 0 0 0 0 0 1 1 38
(XEN) 07 001 01 0 0 0 0 0 1 1 40
(XEN) 08 001 01 0 0 0 0 0 1 1 48
(XEN) 09 001 01 0 0 0 0 0 1 1 50
(XEN) 0a 001 01 0 0 0 0 0 1 1 58
(XEN) 0b 001 01 0 0 0 0 0 1 1 60
(XEN) 0c 001 01 0 0 0 0 0 1 1 68
(XEN) 0d 001 01 0 0 0 0 0 1 1 70
(XEN) 0e 001 01 0 0 0 0 0 1 1 78
(XEN) 0f 001 01 0 0 0 0 0 1 1 88
(XEN) 10 000 00 1 0 0 0 0 0 0 00
(XEN) 11 000 00 1 0 0 0 0 0 0 00
(XEN) 12 000 00 1 0 0 0 0 0 0 00
(XEN) 13 000 00 1 0 0 0 0 0 0 00
(XEN) 14 000 00 1 0 0 0 0 0 0 00
(XEN) 15 000 00 1 0 0 0 0 0 0 00
(XEN) 16 000 00 1 0 0 0 0 0 0 00
(XEN) 17 000 00 1 0 0 0 0 0 0 00
(XEN) Using vector-based indexing
(XEN) IRQ to pin mappings:
(XEN) IRQ240 -> 0:2
(XEN) IRQ32 -> 0:1
(XEN) IRQ40 -> 0:3
(XEN) IRQ241 -> 0:4
(XEN) IRQ48 -> 0:5
(XEN) IRQ56 -> 0:6
(XEN) IRQ64 -> 0:7
(XEN) IRQ72 -> 0:8
(XEN) IRQ80 -> 0:9
(XEN) IRQ88 -> 0:10
(XEN) IRQ96 -> 0:11
(XEN) IRQ104 -> 0:12
(XEN) IRQ112 -> 0:13
(XEN) IRQ120 -> 0:14
(XEN) IRQ136 -> 0:15
(XEN) .................................... done.
(XEN) Using local APIC timer interrupts.
(XEN) calibrating APIC timer ...
(XEN) ..... CPU clock speed is 1800.0912 MHz.
(XEN) ..... host bus clock speed is 200.0099 MHz.
(XEN) ..... bus_scale = 0x0000CCD7
(XEN) Platform timer is 3.579MHz ACPI PM Timer
�(XEN) Brought up 1 CPUs
(XEN) I/O virtualisation disabled
(XEN) CPUIDLE: disabled due to no HPET. Force enable with
''cpuidle''.
(XEN) ACPI sleep modes: S3
(XEN) mcheck_poll: Machine check polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16b3000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000118000000->000000011c000000 (976900 pages to
be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff816b3000
(XEN) Init. ramdisk: ffffffff816b3000->ffffffff82fdc800
(XEN) Phys-Mach map: ffffffff82fdd000->ffffffff83771020
(XEN) Start info: ffffffff83772000->ffffffff837724b4
(XEN) Page tables: ffffffff83773000->ffffffff83794000
(XEN) Boot stack: ffffffff83794000->ffffffff83795000
(XEN) TOTAL: ffffffff80000000->ffffffff83c00000
(XEN) ENTRY ADDRESS: ffffffff814f6200
(XEN) Dom0 has maximum 1 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) **********************************************
(XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
(XEN) ******* This option is intended to aid debugging of Xen by ensuring
(XEN) ******* that all output is synchronously delivered on the serial line.
(XEN) ******* However it can introduce SIGNIFICANT latencies and affect
(XEN) ******* timekeeping. It is NOT recommended for production use!
(XEN) **********************************************
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three
times to switch input to Xen)
(XEN) Freed 132kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
(XEN) d0:v0: unhandled page fault (ec=0000)
(XEN) Pagetable walk from ffff80000420f878:
(XEN) L4[0x100] = 000000011fdfc067 5555555555555555
(XEN) L3[0x000] = 000000011fdfa067 5555555555555555
(XEN) L2[0x021] = 0000000000000000 ffffffffffffffff
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.4 x86_64 debug=n Tainted: C ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff814f8d88>]
(XEN) RFLAGS: 0000000000000286 EM: 1 CONTEXT: pv guest
(XEN) rax: ffff80000420f878 rbx: 00000000000f2813 rcx: 0000000000000000
(XEN) rdx: 0000000000841f0f rsi: ffffffffffffffff rdi: 0000000000000013
(XEN) rbp: 00000000000e0000 rsp: ffffffff81435df0 r8: 0000000000000002
(XEN) r9: ffffffff813b441d r10: 0000000000000000 r11: 0000000000000009
(XEN) r12: 00000000000fec00 r13: 0000000000012804 r14: 0000000000000000
(XEN) r15: ffffffff81435e38 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 0000000119001000 cr2: ffff80000420f878
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff81435df0:
(XEN) 0000000000000000 0000000000000009 0000000000000000 ffffffff814f8d88
(XEN) 000000010000e030 0000000000010086 ffffffff81435e38 000000000000e02b
(XEN) ffffffff814f8d3d ffffffff81435e60 0000000000000001 0000000000000000
(XEN) 0000000000007ff0 0000000002fdd000 0000000000841f0f 0000014081435f98
(XEN) ffffffff815a93ac 0000000000000007 0000000000000000 ffffffff81435f98
(XEN) 0000000000000000 0000000000000000 ffffffff814f8f85 000000010000000b
(XEN) ffffffff8152d2d0 0000000000000000 0000000000000000 ffffffffffffffff
(XEN) ffffffff814fb5fb 0000000000000000 ffffffff814fa249 ffffffff813f5136
(XEN) ffffffff813b441d ffffffff81435f90 ffffffff811ff14f ffffffff8100e361
(XEN) ffffffff8100e343 00000000bbacb60c 00000000effea900 ffffffff813b441d
(XEN) ffffffff813f5136 0000000000000000 faa662c854df1257 0000000000000000
(XEN) 0000000000000000 0000000000000000 ffffffffffffffff ffffffff8152c7b0
(XEN) 0000000000000000 0000000000000000 ffffffff814f69d0 0000000001692cd4
(XEN) faa662c854df1257 0000000000000000 ffffffff81001000 0000000000000000
(XEN) 0000000000000000 0000000000000000 ffffffff814f8aca 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000001
(XEN) 0000000000000000 0000000000000000 ffffffff82fdd000 ffffffff82fde000
(XEN) ffffffff82fdf000 ffffffff82fe0000 ffffffff82fe1000 ffffffff82fe2000
(XEN) ffffffff82fe3000 ffffffff82fe4000 ffffffff82fe5000 ffffffff82fe6000
(XEN) ffffffff82fe7000 ffffffff82fe8000 ffffffff82fe9000 ffffffff82fea000
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
Regards,
Thomas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-08 22:51 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/08/2010 03:19 PM, Thomas Schwinge wrote:> Hello! > > OK. You really tricked me into doing that: soldering iron, D-Sub 9 > sockets, null modem cable, and all that... :-) > > But here we go: > > (XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@debian.org) (gcc version 4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010 > (XEN) Console output is synchronous. > (XEN) Command line: com1=38400,8n1 console=com1 loglvl=all guest_loglvl=all sync_console console_to_ring apic=debug apic_verbosity=debug > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009e000 (usable) > (XEN) 000000000009e000 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000ddee0000 (usable) > (XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data) > (XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS) > (XEN) 00000000ddf00000 - 00000000e0000000 (reserved) > (XEN) 00000000fec00000 - 00000000fec10000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000fff00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000120000000 (usable) > (XEN) System RAM: 4062MB (4159992kB) > (XEN) ACPI: RSDP 000F7350, 0024 (r2 PTLTD ) > (XEN) ACPI: XSDT DDEEB7E4, 004C (r1 PTLTD XSDT 50000 LTP 0) > (XEN) ACPI: FACP DDEEB8A4, 00F4 (r3 FSC �PZ- 50000 F4240) > (XEN) ACPI: DSDT DDEEB998, 34FB (r1 FSC D2030 50000 MSFT 2000002) > (XEN) ACPI: FACS DDEEFFC0, 0040 > (XEN) ACPI: SSDT DDEEEE93, 00B5 (r1 PTLTD POWERNOW 50000 LTP 1) > (XEN) ACPI: APIC DDEEEF48, 0050 (r1 PTLTD APIC 50000 LTP 0) > (XEN) ACPI: MCFG DDEEEF98, 0040 (r1 PTLTD MCFG 50000 LTP 0) > (XEN) ACPI: BOOT DDEEEFD8, 0028 (r1 PTLTD $SBFTBL$ 50000 LTP 1) > (XEN) NUMA turned off > (XEN) Faking a node at 0000000000000000-0000000120000000 > (XEN) Domain heap initialised > (XEN) found SMP MP-table at 000f73b0 > (XEN) DMI present. > (XEN) Using APIC driver default > (XEN) ACPI: PM-Timer IO Port: 0xf008 > (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[f004,0], pm1x_evt[f000,0] > (XEN) ACPI: wakeup_vec[ddeeffcc], vec_size[20] > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > (XEN) Processor #0 15:15 APIC version 16 > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) > (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) > (XEN) IOAPIC[0]: apic_id 1, version 20, address 0xfec00000, GSI 0-23 > (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) > (XEN) ACPI: IRQ0 used by override. > (XEN) ACPI: IRQ2 used by override. > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Using ACPI (MADT) for SMP configuration information > (XEN) mapped APIC to ffff828bffffe000 (fee00000) > (XEN) mapped IOAPIC to ffff828bffffd000 (fec00000) > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Initializing CPU#0 > (XEN) Detected 1800.104 MHz processor. > (XEN) CPU0: AMD Flush Filter disabled > (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > (XEN) CPU: L2 Cache: 128K (64 bytes/line) > (XEN) CPU0: AMD K8 machine check reporting enabled. > (XEN) CPU0: AMD Sempron(tm) Processor 3000+ stepping 02 > (XEN) Getting VERSION: 50010 > (XEN) Getting VERSION: 50010 > (XEN) Getting ID: 0 > (XEN) Getting LVT0: 10000 > (XEN) Getting LVT1: 10000 > (XEN) masked ExtINT on CPU#0 > (XEN) Total of 1 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) init IO_APIC IRQs > (XEN) IO-APIC (apicid-pin) 1-0, 1-16, 1-17, 1-18, 1-19, 1-20, 1-21, 1-22, 1-23 not connected. > (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 > (XEN) number of MP IRQ sources: 15. > (XEN) number of IO-APIC #1 registers: 24. > (XEN) testing the IO APIC....................... > (XEN) IO APIC #1...... > (XEN) .... register #00: 01000000 > (XEN) ....... : physical APIC id: 01 > (XEN) ....... : Delivery Type: 0 > (XEN) ....... : LTS : 0 > (XEN) .... register #01: 00178014 > (XEN) ....... : max redirection entries: 0017 > (XEN) ....... : PRQ implemented: 1 > (XEN) ....... : IO APIC version: 0014 > (XEN) .... register #02: 01000000 > (XEN) ....... : arbitration: 01 > (XEN) .... IRQ redirection table: > (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > (XEN) 00 000 00 1 0 0 0 0 0 0 00 > (XEN) 01 001 01 0 0 0 0 0 1 1 20 > (XEN) 02 001 01 0 0 0 0 0 1 1 F0 > (XEN) 03 001 01 0 0 0 0 0 1 1 28 > (XEN) 04 001 01 0 0 0 0 0 1 1 F1 > (XEN) 05 001 01 0 0 0 0 0 1 1 30 > (XEN) 06 001 01 0 0 0 0 0 1 1 38 > (XEN) 07 001 01 0 0 0 0 0 1 1 40 > (XEN) 08 001 01 0 0 0 0 0 1 1 48 > (XEN) 09 001 01 0 0 0 0 0 1 1 50 > (XEN) 0a 001 01 0 0 0 0 0 1 1 58 > (XEN) 0b 001 01 0 0 0 0 0 1 1 60 > (XEN) 0c 001 01 0 0 0 0 0 1 1 68 > (XEN) 0d 001 01 0 0 0 0 0 1 1 70 > (XEN) 0e 001 01 0 0 0 0 0 1 1 78 > (XEN) 0f 001 01 0 0 0 0 0 1 1 88 > (XEN) 10 000 00 1 0 0 0 0 0 0 00 > (XEN) 11 000 00 1 0 0 0 0 0 0 00 > (XEN) 12 000 00 1 0 0 0 0 0 0 00 > (XEN) 13 000 00 1 0 0 0 0 0 0 00 > (XEN) 14 000 00 1 0 0 0 0 0 0 00 > (XEN) 15 000 00 1 0 0 0 0 0 0 00 > (XEN) 16 000 00 1 0 0 0 0 0 0 00 > (XEN) 17 000 00 1 0 0 0 0 0 0 00 > (XEN) Using vector-based indexing > (XEN) IRQ to pin mappings: > (XEN) IRQ240 -> 0:2 > (XEN) IRQ32 -> 0:1 > (XEN) IRQ40 -> 0:3 > (XEN) IRQ241 -> 0:4 > (XEN) IRQ48 -> 0:5 > (XEN) IRQ56 -> 0:6 > (XEN) IRQ64 -> 0:7 > (XEN) IRQ72 -> 0:8 > (XEN) IRQ80 -> 0:9 > (XEN) IRQ88 -> 0:10 > (XEN) IRQ96 -> 0:11 > (XEN) IRQ104 -> 0:12 > (XEN) IRQ112 -> 0:13 > (XEN) IRQ120 -> 0:14 > (XEN) IRQ136 -> 0:15 > (XEN) .................................... done. > (XEN) Using local APIC timer interrupts. > (XEN) calibrating APIC timer ... > (XEN) ..... CPU clock speed is 1800.0912 MHz. > (XEN) ..... host bus clock speed is 200.0099 MHz. > (XEN) ..... bus_scale = 0x0000CCD7 > (XEN) Platform timer is 3.579MHz ACPI PM Timer > �(XEN) Brought up 1 CPUs > (XEN) I/O virtualisation disabled > (XEN) CPUIDLE: disabled due to no HPET. Force enable with ''cpuidle''. > (XEN) ACPI sleep modes: S3 > (XEN) mcheck_poll: Machine check polling timer started. > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16b3000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000118000000->000000011c000000 (976900 pages to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff816b3000 > (XEN) Init. ramdisk: ffffffff816b3000->ffffffff82fdc800 > (XEN) Phys-Mach map: ffffffff82fdd000->ffffffff83771020 > (XEN) Start info: ffffffff83772000->ffffffff837724b4 > (XEN) Page tables: ffffffff83773000->ffffffff83794000 > (XEN) Boot stack: ffffffff83794000->ffffffff83795000 > (XEN) TOTAL: ffffffff80000000->ffffffff83c00000 > (XEN) ENTRY ADDRESS: ffffffff814f6200 > (XEN) Dom0 has maximum 1 VCPUs > (XEN) Scrubbing Free RAM: .done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) ********************************************** > (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS > (XEN) ******* This option is intended to aid debugging of Xen by ensuring > (XEN) ******* that all output is synchronously delivered on the serial line. > (XEN) ******* However it can introduce SIGNIFICANT latencies and affect > (XEN) ******* timekeeping. It is NOT recommended for production use! > (XEN) ********************************************** > (XEN) 3... 2... 1... > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) > (XEN) Freed 132kB init memory. > mapping kernel into physical memory > Xen: setup ISA identity maps > about to get started... > (XEN) d0:v0: unhandled page fault (ec=0000) > (XEN) Pagetable walk from ffff80000420f878: > (XEN) L4[0x100] = 000000011fdfc067 5555555555555555 > (XEN) L3[0x000] = 000000011fdfa067 5555555555555555 > (XEN) L2[0x021] = 0000000000000000 ffffffffffffffff > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: > (XEN) ----[ Xen-3.4 x86_64 debug=n Tainted: C ]---- > (XEN) CPU: 0 > (XEN) RIP: e033:[<ffffffff814f8d88>] >Looks like it crashed very early. Do you have symbol information for this kernel? If so, could you resolve this to a function?> (XEN) RFLAGS: 0000000000000286 EM: 1 CONTEXT: pv guest > (XEN) rax: ffff80000420f878 rbx: 00000000000f2813 rcx: 0000000000000000 > (XEN) rdx: 0000000000841f0f rsi: ffffffffffffffff rdi: 0000000000000013 > (XEN) rbp: 00000000000e0000 rsp: ffffffff81435df0 r8: 0000000000000002 > (XEN) r9: ffffffff813b441d r10: 0000000000000000 r11: 0000000000000009 > (XEN) r12: 00000000000fec00 r13: 0000000000012804 r14: 0000000000000000 > (XEN) r15: ffffffff81435e38 cr0: 000000008005003b cr4: 00000000000006f0 > (XEN) cr3: 0000000119001000 cr2: ffff80000420f878 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff81435df0: > (XEN) 0000000000000000 0000000000000009 0000000000000000 ffffffff814f8d88 > (XEN) 000000010000e030 0000000000010086 ffffffff81435e38 000000000000e02b > (XEN) >ffffffff814f8d3d ffffffff81435e60 0000000000000001 0000000000000000 > (XEN) 0000000000007ff0 0000000002fdd000 0000000000841f0f 0000014081435f98 > (XEN) >ffffffff815a93ac 0000000000000007 0000000000000000 ffffffff81435f98 > (XEN) 0000000000000000 0000000000000000>ffffffff814f8f85 000000010000000b > (XEN) >ffffffff8152d2d0 0000000000000000 0000000000000000 ffffffffffffffff > (XEN) >ffffffff814fb5fb 0000000000000000>ffffffff814fa249>ffffffff813f5136 > (XEN) >ffffffff813b441d ffffffff81435f90 ffffffff811ff14f>ffffffff8100e361 > (XEN) >ffffffff8100e343 00000000bbacb60c 00000000effea900>ffffffff813b441d > (XEN) >ffffffff813f5136 0000000000000000 faa662c854df1257 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffffffffffff>ffffffff8152c7b0 > (XEN) 0000000000000000 0000000000000000>ffffffff814f69d0 0000000001692cd4 >And the addresses I marked with ''>'' as well? [ If you have a vmlinux, you can do this with: $ gdb vmlinux (gdb) x/i 0xXXXXXX < show faulting instruction (gdb) list *0xXXXXXX < get line info ] Thanks, J> (XEN) faa662c854df1257 0000000000000000 ffffffff81001000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 ffffffff814f8aca 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000001 > (XEN) 0000000000000000 0000000000000000 ffffffff82fdd000 ffffffff82fde000 > (XEN) ffffffff82fdf000 ffffffff82fe0000 ffffffff82fe1000 ffffffff82fe2000 > (XEN) ffffffff82fe3000 ffffffff82fe4000 ffffffff82fe5000 ffffffff82fe6000 > (XEN) ffffffff82fe7000 ffffffff82fe8000 ffffffff82fe9000 ffffffff82fea000 > (XEN) Domain 0 crashed: rebooting machine in 5 seconds. > > > Regards, > Thomas > > > > _______________________________________________ > 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
Thomas Schwinge
2010-Apr-09 18:00 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello! Before we get to the backtrace, one further detail: this kernel *does* boot if one of the following has happened before: the BIOS memchecker has run, memtest86+ has run, some other kernel has run (though it doesn''t always boot in this latter case). Thus, I wildly guess that some uninitialized data structure (in memory) is dereferenced -- that happens to be in a sane state after memtest86+ et al. On Thu, Apr 08, 2010 at 03:51:30PM -0700, Jeremy Fitzhardinge wrote:> Looks like it crashed very early. Do you have symbol information for > this kernel? If so, could you resolve this to a function?According to Bastian Blank, there are no debugging files available for the Debian kernels, which seems odd to me, but oh well. I re-built the kernel myself, reproduced the crash, and here we go.> [ If you have a vmlinux, you can do this with: > $ gdb vmlinux > (gdb) x/i 0xXXXXXX < show faulting instruction > (gdb) list *0xXXXXXX < get line info > ]Hrm, GDB doesn''t like the vmlinux file that the Debian kernel build process generates: $ gdb -q debian/build/build_amd64_xen_amd64/vmlinux Reading symbols from /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/build_amd64_xen_amd64/vmlinux...(no debugging symbols found)...done. (gdb) x/i ffffffff814f6d88 No symbol table is loaded. Use the "file" command. Do I have to pass some special options to the Debian build machinery? I just ran: $ fakeroot make -j 6 -f debian/rules.gen binary-arch_amd64_xen addr2line can at least partly decode the bits of debugging information that are present; see below. Here is the complete log again: as I had to rebuild the kernel, some values are different. (XEN) Xen version 3.4 (Debian 3.4.3~rc3-1) (waldi@debian.org) (gcc version 4.4.3 (Debian 4.4.3-2) ) Mon Mar 1 21:16:18 UTC 2010 (XEN) Console output is synchronous. (XEN) Command line: com1=38400,8n1 console=com1 loglvl=all guest_loglvl=all sync_console console_to_ring apic=debug apic_verbosity=debug (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009e000 (usable) (XEN) 000000000009e000 - 00000000000a0000 (reserved) (XEN) 00000000000e4000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000ddee0000 (usable) (XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data) (XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS) (XEN) 00000000ddf00000 - 00000000e0000000 (reserved) (XEN) 00000000fec00000 - 00000000fec10000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000fff00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000120000000 (usable) (XEN) System RAM: 4062MB (4159992kB) (XEN) ACPI: RSDP 000F7350, 0024 (r2 PTLTD ) (XEN) ACPI: XSDT DDEEB7E4, 004C (r1 PTLTD XSDT 50000 LTP 0) (XEN) ACPI: FACP DDEEB8A4, 00F4 (r3 FSC �P- 50000 F4240) (XEN) ACPI: DSDT DDEEB998, 34FB (r1 FSC D2030 50000 MSFT 2000002) (XEN) ACPI: FACS DDEEFFC0, 0040 (XEN) ACPI: SSDT DDEEEE93, 00B5 (r1 PTLTD POWERNOW 50000 LTP 1) (XEN) ACPI: APIC DDEEEF48, 0050 (r1 PTLTD APIC 50000 LTP 0) (XEN) ACPI: MCFG DDEEEF98, 0040 (r1 PTLTD MCFG 50000 LTP 0) (XEN) ACPI: BOOT DDEEEFD8, 0028 (r1 PTLTD $SBFTBL$ 50000 LTP 1) (XEN) NUMA turned off (XEN) Faking a node at 0000000000000000-0000000120000000 (XEN) Domain heap initialised (XEN) found SMP MP-table at 000f73b0 (XEN) DMI present. (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0xf008 (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[f004,0], pm1x_evt[f000,0] (XEN) ACPI: wakeup_vec[ddeeffcc], vec_size[20] (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 15:15 APIC version 16 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) (XEN) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 1, version 20, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) mapped APIC to ffff828bffffe000 (fee00000) (XEN) mapped IOAPIC to ffff828bffffd000 (fec00000) (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 1800.076 MHz processor. (XEN) CPU0: AMD Flush Filter disabled (XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) (XEN) CPU: L2 Cache: 128K (64 bytes/line) (XEN) CPU0: AMD K8 machine check reporting enabled. (XEN) CPU0: AMD Sempron(tm) Processor 3000+ stepping 02 (XEN) Getting VERSION: 50010 (XEN) Getting VERSION: 50010 (XEN) Getting ID: 0 (XEN) Getting LVT0: 10000 (XEN) Getting LVT1: 10000 (XEN) masked ExtINT on CPU#0 (XEN) Total of 1 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) init IO_APIC IRQs (XEN) IO-APIC (apicid-pin) 1-0, 1-16, 1-17, 1-18, 1-19, 1-20, 1-21, 1-22, 1-23 not connected. (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0 (XEN) number of MP IRQ sources: 15. (XEN) number of IO-APIC #1 registers: 24. (XEN) testing the IO APIC....................... (XEN) IO APIC #1...... (XEN) .... register #00: 01000000 (XEN) ....... : physical APIC id: 01 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 00178014 (XEN) ....... : max redirection entries: 0017 (XEN) ....... : PRQ implemented: 1 (XEN) ....... : IO APIC version: 0014 (XEN) .... register #02: 01000000 (XEN) ....... : arbitration: 01 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 001 01 0 0 0 0 0 1 1 20 (XEN) 02 001 01 0 0 0 0 0 1 1 F0 (XEN) 03 001 01 0 0 0 0 0 1 1 28 (XEN) 04 001 01 0 0 0 0 0 1 1 F1 (XEN) 05 001 01 0 0 0 0 0 1 1 30 (XEN) 06 001 01 0 0 0 0 0 1 1 38 (XEN) 07 001 01 0 0 0 0 0 1 1 40 (XEN) 08 001 01 0 0 0 0 0 1 1 48 (XEN) 09 001 01 0 0 0 0 0 1 1 50 (XEN) 0a 001 01 0 0 0 0 0 1 1 58 (XEN) 0b 001 01 0 0 0 0 0 1 1 60 (XEN) 0c 001 01 0 0 0 0 0 1 1 68 (XEN) 0d 001 01 0 0 0 0 0 1 1 70 (XEN) 0e 001 01 0 0 0 0 0 1 1 78 (XEN) 0f 001 01 0 0 0 0 0 1 1 88 (XEN) 10 000 00 1 0 0 0 0 0 0 00 (XEN) 11 000 00 1 0 0 0 0 0 0 00 (XEN) 12 000 00 1 0 0 0 0 0 0 00 (XEN) 13 000 00 1 0 0 0 0 0 0 00 (XEN) 14 000 00 1 0 0 0 0 0 0 00 (XEN) 15 000 00 1 0 0 0 0 0 0 00 (XEN) 16 000 00 1 0 0 0 0 0 0 00 (XEN) 17 000 00 1 0 0 0 0 0 0 00 (XEN) Using vector-based indexing (XEN) IRQ to pin mappings: (XEN) IRQ240 -> 0:2 (XEN) IRQ32 -> 0:1 (XEN) IRQ40 -> 0:3 (XEN) IRQ241 -> 0:4 (XEN) IRQ48 -> 0:5 (XEN) IRQ56 -> 0:6 (XEN) IRQ64 -> 0:7 (XEN) IRQ72 -> 0:8 (XEN) IRQ80 -> 0:9 (XEN) IRQ88 -> 0:10 (XEN) IRQ96 -> 0:11 (XEN) IRQ104 -> 0:12 (XEN) IRQ112 -> 0:13 (XEN) IRQ120 -> 0:14 (XEN) IRQ136 -> 0:15 (XEN) .................................... done. (XEN) Using local APIC timer interrupts. (XEN) calibrating APIC timer ... (XEN) ..... CPU clock speed is 1800.0759 MHz. (XEN) ..... host bus clock speed is 200.0082 MHz. (XEN) ..... bus_scale = 0x0000CCD7 (XEN) Platform timer is 3.579MHz ACPI PM Timer �(XEN) Brought up 1 CPUs (XEN) I/O virtualisation disabled (XEN) CPUIDLE: disabled due to no HPET. Force enable with ''cpuidle''. (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x16b1000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000118000000->000000011c000000 (976900 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff816b1000 (XEN) Init. ramdisk: ffffffff816b1000->ffffffff82fd8600 (XEN) Phys-Mach map: ffffffff82fd9000->ffffffff8376d020 (XEN) Start info: ffffffff8376e000->ffffffff8376e4b4 (XEN) Page tables: ffffffff8376f000->ffffffff83790000 (XEN) Boot stack: ffffffff83790000->ffffffff83791000 (XEN) TOTAL: ffffffff80000000->ffffffff83c00000 (XEN) ENTRY ADDRESS: ffffffff814f4200 (XEN) Dom0 has maximum 1 VCPUs (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) ********************************************** (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) ******* This option is intended to aid debugging of Xen by ensuring (XEN) ******* that all output is synchronously delivered on the serial line. (XEN) ******* However it can introduce SIGNIFICANT latencies and affect (XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) (XEN) Freed 132kB init memory. mapping kernel into physical memory Xen: setup ISA identity maps about to get started... (XEN) d0:v0: unhandled page fault (ec=0000) (XEN) Pagetable walk from ffff800002200800: (XEN) L4[0x100] = 000000011fdfc067 5555555555555555 (XEN) L3[0x000] = 000000011fdfa067 5555555555555555 (XEN) L2[0x011] = 0000000000000000 ffffffffffffffff (XEN) domain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.4 x86_64 debug=n Tainted: C ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff814f6d88>] (XEN) RFLAGS: 0000000000000286 EM: 1 CONTEXT: pv guest (XEN) rax: ffff800002200800 rbx: 00000000000f2805 rcx: 0000000000000000 (XEN) rdx: 0000000000440100 rsi: ffffffffffffffff rdi: 0000000000000005 (XEN) rbp: 00000000000e0000 rsp: ffffffff81433df0 r8: 0000000000000002 (XEN) r9: ffffffff813b4119 r10: 0000000000000000 r11: 0000000000000009 (XEN) r12: 00000000000fec00 r13: 0000000000012804 r14: 0000000000000000 (XEN) r15: ffffffff81433e38 cr0: 000000008005003b cr4: 00000000000006f0 (XEN) cr3: 0000000119001000 cr2: ffff800002200800 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff81433df0: (XEN) 0000000000000000 0000000000000009 0000000000000000 ffffffff814f6d88 (XEN) 000000010000e030 0000000000010086 ffffffff81433e38 000000000000e02b (XEN) ffffffff814f6d3d ffffffff81433e60 0000000000000001 0000000000000000 (XEN) 0000000000007ff0 0000000002fd9000 0000000000440100 0000014081433f98 (XEN) ffffffff815a73ac 0000000000000007 0000000000000000 ffffffff81433f98 (XEN) 0000000000000000 0000000000000000 ffffffff814f6f85 000000010000000b (XEN) ffffffff8152b2d0 0000000000000000 0000000000000000 ffffffffffffffff (XEN) ffffffff814f95fb 0000000000000000 ffffffff814f8249 ffffffff813f3f5f (XEN) ffffffff813b4119 ffffffff81433f90 ffffffff811ff14f ffffffff8100e361 (XEN) ffffffff8100e343 00000000bbacb60c 00000000effea900 ffffffff813b4119 (XEN) ffffffff813f3f5f 0000000000000000 0ca584b366de3445 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffffffffffff ffffffff8152a7b0 (XEN) 0000000000000000 0000000000000000 ffffffff814f49d0 0000000001690cd4 (XEN) 0ca584b366de3445 0000000000000000 ffffffff81001000 0000000000000000 (XEN) 0000000000000000 0000000000000000 ffffffff814f6aca 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000001 (XEN) 0000000000000000 0000000000000000 ffffffff82fd9000 ffffffff82fda000 (XEN) ffffffff82fdb000 ffffffff82fdc000 ffffffff82fdd000 ffffffff82fde000 (XEN) ffffffff82fdf000 ffffffff82fe0000 ffffffff82fe1000 ffffffff82fe2000 (XEN) ffffffff82fe3000 ffffffff82fe4000 ffffffff82fe5000 ffffffff82fe6000 (XEN) Domain 0 crashed: rebooting machine in 5 seconds. $ for ip in ffffffff814f6d88 ffffffff81433e38 ffffffff814f6d3d ffffffff81433e60 ffffffff815a73ac ffffffff81433f98 ffffffff814f6f85 ffffffff8152b2d0 ffffffff814f95fb ffffffff814f8249 ffffffff813f3f5f ffffffff813b4119 ffffffff81433f90 ffffffff811ff14f ffffffff8100e361 ffffffff8100e343 ffffffff813b4119 ffffffff813f3f5f ffffffff8152a7b0 ffffffff814f49d0 ffffffff81001000 ffffffff814f6aca; do echo "* $ip:" && addr2line -fie debian/build/build_amd64_xen_amd64/vmlinux "$ip"; done > ~/shared/tmp/tmp * ffffffff814f6d88: xen_release_chunk setup.c:0 * ffffffff81433e38: _sdata ??:0 * ffffffff814f6d3d: xen_release_chunk setup.c:0 * ffffffff81433e60: _sdata ??:0 * ffffffff815a73ac: idt_table ??:0 * ffffffff81433f98: _sdata ??:0 * ffffffff814f6f85: xen_memory_setup ??:0 * ffffffff8152b2d0: ?? ??:0 * ffffffff814f95fb: setup_memory_map ??:0 * ffffffff814f8249: setup_arch ??:0 * ffffffff813f3f5f: kallsyms_token_index ??:0 * ffffffff813b4119: kallsyms_token_index ??:0 * ffffffff81433f90: _sdata ??:0 * ffffffff811ff14f: extract_entropy random.c:0 * ffffffff8100e361: __raw_callee_save_xen_irq_disable irq.c:0 * ffffffff8100e343: __raw_callee_save_xen_restore_fl irq.c:0 * ffffffff813b4119: kallsyms_token_index ??:0 * ffffffff813f3f5f: kallsyms_token_index ??:0 * ffffffff8152a7b0: ?? ??:0 * ffffffff814f49d0: start_kernel ??:0 * ffffffff81001000: init_level4_pgt ??:0 * ffffffff814f6aca: xen_start_kernel ??:0 Reproducing the crash, the boot log shows slightly different values in some processor registers and on some stack addresses, but the general structure doesn''t changes. Likewise, unfortunately, for a successful boot (after memtester86+ has been run): ``(XEN) d0:v0: unhandled page fault (ec=0000)'''' and the following lines are gone, and the kernel boot continues as follows. Of course, relying on running memtester86+ before being able to boot the kernel obviously isn''t a proper solution, and I have not tested whether the thusly-booted kernel survives under real load. [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.32-4-xen-amd64 (Debian 2.6.32-11) (maks@debian.org) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Fri Apr 9 18:06:54 CEST 2010 [ 0.000000] Command line: root=/dev/mapper/vg0-boole--root ro console=hvc0 earlyprintk=xen debug initcall_debug acpi.debug_level=0xffffffff acpi.debug_layer=0x2 [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] xen_release_chunk: looking at area pfn e0000-fec00: 75780 pages freed [ 0.000000] xen_release_chunk: looking at area pfn fec10-fee00: 0 pages freed [ 0.000000] xen_release_chunk: looking at area pfn fee01-fff00: 0 pages freed [ 0.000000] released 75780 pages of unused memory [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000009e000 (usable) [ 0.000000] Xen: 000000000009e000 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 00000000ddee0000 (usable) [ 0.000000] Xen: 00000000ddee0000 - 00000000ddeef000 (ACPI data) [ 0.000000] Xen: 00000000ddeef000 - 00000000ddf00000 (ACPI NVS) [ 0.000000] Xen: 00000000ddf00000 - 00000000e0000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fec10000 (reserved) [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] Xen: 00000000fff00000 - 0000000100000000 (reserved) [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] DMI present. [ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it. [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] last_pfn = 0xddee0 max_arch_pfn = 0x400000000 [ 0.000000] initial memory mapped : 0 - 20000000 [ 0.000000] init_memory_mapping: 0000000000000000-00000000ddee0000 [ 0.000000] 0000000000 - 00ddee0000 page 4k [ 0.000000] kernel direct mapping tables up to ddee0000 @ 100000-7f5000 [ 0.000000] RAMDISK: 016b1000 - 02fd8600 [ 0.000000] ACPI: RSDP 00000000000f7350 00024 (v02 PTLTD ) [ 0.000000] ACPI: XSDT 00000000ddeeb7e4 0004C (v01 PTLTD ? XSDT 00050000 LTP 00000000) [ 0.000000] ACPI: FACP 00000000ddeeb8a4 000F4 (v03 FSC ÷P?-? 00050000 000F4240) [ 0.000000] ACPI: DSDT 00000000ddeeb998 034FB (v01 FSC D2030 00050000 MSFT 02000002) [ 0.000000] ACPI: FACS 00000000ddeeffc0 00040 [ 0.000000] ACPI: SSDT 00000000ddeeee93 000B5 (v01 PTLTD POWERNOW 00050000 LTP 00000001) [ 0.000000] ACPI: APIC 00000000ddeeef48 00050 (v01 PTLTD ? APIC 00050000 LTP 00000000) [ 0.000000] ACPI: MCFG 00000000ddeeef98 00040 (v01 PTLTD MCFG 00050000 LTP 00000000) [ 0.000000] ACPI: BOOT 00000000ddeeefd8 00028 (v01 PTLTD $SBFTBL$ 00050000 LTP 00000001) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] Scanning NUMA topology in Northbridge 24 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-00000000ddee0000 [ 0.000000] Bootmem setup node 0 0000000000000000-00000000ddee0000 [ 0.000000] NODE_DATA [0000000000010000 - 0000000000017fff] [ 0.000000] bootmap [0000000000018000 - 0000000000033bdf] pages 1c [ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 00ddee0000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [000376f000 - 0003790000] XEN PAGETABLES ==> [000376f000 - 0003790000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 0001690cd4] TEXT DATA BSS ==> [0001000000 - 0001690cd4] [ 0.000000] #4 [00016b1000 - 0002fd8600] RAMDISK ==> [00016b1000 - 0002fd8600] [ 0.000000] #5 [0002fd9000 - 000376f000] XEN START INFO ==> [0002fd9000 - 000376f000] [ 0.000000] #6 [0001691000 - 00016911c4] BRK ==> [0001691000 - 00016911c4] [ 0.000000] #7 [0000100000 - 00007d1000] PGTABLE ==> [0000100000 - 00007d1000] [ 0.000000] found SMP MP-table at [ffff8800000f73b0] f73b0 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000010 -> 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: 0x00000010 -> 0x0000009e [ 0.000000] 0: 0x00000100 -> 0x000ddee0 [ 0.000000] On node 0 totalpages: 908910 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 1748 pages reserved [ 0.000000] DMA zone: 2178 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 12373 pages used for memmap [ 0.000000] DMA32 zone: 892555 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0xf008 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-0 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 256 [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 0000000000100000 [ 0.000000] Allocating PCI resources starting at e0000000 (gap: e0000000:1ec00000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 3.4 (preserve-AD) (dom0) [ 0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:1 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff8800037c6000 s89880 r8192 d20712 u118784 [ 0.000000] pcpu-alloc: s89880 r8192 d20712 u118784 alloc=29*4096 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] trying to map vcpu_info 0 at ffff8800037d1020, mfn 11b7d1, offset 32 [ 0.000000] cpu 0 using vcpu_info at ffff8800037d1020 [ 0.000000] Xen: using vcpu_info placement [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 894733 [ 0.000000] Policy zone: DMA32 [ 0.000000] Kernel command line: root=/dev/mapper/vg0-boole--root ro console=hvc0 earlyprintk=xen debug initcall_debug acpi.debug_level=0xffffffff acpi.debug_layer=0x2 [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Initializing CPU#0 [ 0.000000] DMA: Placing 64MB software IO TLB between ffff880006cac000 - ffff88000acac000 [ 0.000000] DMA: software IO TLB at phys 0x6cac000 - 0xacac000 [ 0.000000] xen_swiotlb_fixup: buf=ffff880006cac000 size=67108864 [ 0.000000] xen_swiotlb_fixup: buf=ffff88000ad0c000 size=32768 [ 0.000000] Memory: 3471612k/3636096k available (3098k kernel code, 456k absent, 164028k reserved, 1880k data, 588k init) [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:4352 nr_irqs:512 [ 0.000000] xen: --> irq=0 [ 0.000000] xen: --> irq=1 [ 0.000000] xen: --> irq=2 [ 0.000000] xen: --> irq=3 [ 0.000000] xen: --> irq=4 [ 0.000000] xen: --> irq=5 [ 0.000000] xen: --> irq=6 [ 0.000000] xen: --> irq=7 [ 0.000000] xen: --> irq=8 [ 0.000000] xen: --> irq=9 [ 0.000000] xen: --> irq=10 [ 0.000000] xen: --> irq=11 [ 0.000000] xen: --> irq=12 [ 0.000000] xen: --> irq=13 [ 0.000000] xen: --> irq=14 [ 0.000000] xen: --> irq=15 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [hvc0] enabled, bootconsole disabled [ 0.000000] console [hvc0] enabled, bootconsole disabled [ 0.000000] Xen: using vcpuop timer interface [ 0.000000] installing Xen timer for CPU 0 [ 0.000000] alloc irq_desc for 511 on node 0 [ 0.000000] alloc kstat_irqs on node 0 [ 0.000000] Detected 1800.063 MHz processor. [ 0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 3600.12 BogoMIPS (lpj=7200252) [ 0.004044] Security Framework initialized [ 0.008000] SELinux: Disabled at boot. [ 0.009187] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.015202] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.017097] Mount-cache hash table entries: 256 [ 0.020223] Initializing cgroup subsys ns [ 0.024001] Initializing cgroup subsys cpuacct [ 0.024001] Initializing cgroup subsys devices [ 0.024001] Initializing cgroup subsys freezer [ 0.024001] Initializing cgroup subsys net_cls [ 0.024039] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [ 0.028005] CPU: L2 Cache: 128K (64 bytes/line) [ 0.032001] CPU 0/0x0 -> Node 0 [ 0.032005] tseg: 00ddf00000 [ 0.036005] Performance Events: AMD PMU driver. [ 0.040001] ------------[ cut here ]------------ [ 0.040001] WARNING: at /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/enlighten.c:722 init_hw_perf_events+0x2fe/0x39e() [ 0.040001] Hardware name: D2264-A1 [ 0.040001] Modules linked in: [ 0.040001] Pid: 0, comm: swapper Not tainted 2.6.32-4-xen-amd64 #1 [ 0.040001] Call Trace: [ 0.040001] [<ffffffff814fb9cc>] ? init_hw_perf_events+0x2fe/0x39e [ 0.040001] [<ffffffff814fb9cc>] ? init_hw_perf_events+0x2fe/0x39e [ 0.040001] [<ffffffff8104fb8c>] ? warn_slowpath_common+0x77/0xa3 [ 0.040001] [<ffffffff814fb9cc>] ? init_hw_perf_events+0x2fe/0x39e [ 0.040001] [<ffffffff812fb1fc>] ? identify_cpu+0x2ff/0x308 [ 0.040001] [<ffffffff8100e9ef>] ? xen_restore_fl_direct_end+0x0/0x1 [ 0.040001] [<ffffffff810e7d8e>] ? kmem_cache_alloc+0x8c/0xf0 [ 0.040001] [<ffffffff814fb622>] ? identify_boot_cpu+0x15/0x3e [ 0.040001] [<ffffffff814fb6a9>] ? check_bugs+0x9/0x2e [ 0.040001] [<ffffffff814f4cc2>] ? start_kernel+0x3cd/0x3e8 [ 0.040001] [<ffffffff814f6aca>] ? xen_start_kernel+0x649/0x64f [ 0.040001] ---[ end trace a7919e7f17c0a725 ]--- [ 0.040001] ... version: 0 [ 0.040001] ... bit width: 48 [ 0.040001] ... generic registers: 4 [ 0.040001] ... value mask: 0000ffffffffffff [ 0.040001] ... max period: 00007fffffffffff [ 0.040001] ... fixed-purpose events: 0 [ 0.040001] ... event mask: 000000000000000f [ 0.040001] SMP alternatives: switching to UP code [ 0.040001] Freeing SMP alternatives: 28k freed [ 0.040001] ACPI: Core revision 20090903 [ 0.047018] alloc irq_desc for 510 on node 0 [ 0.048001] alloc kstat_irqs on node 0 [ 0.048018] alloc irq_desc for 509 on node 0 [ 0.052001] alloc kstat_irqs on node 0 [ 0.052019] alloc irq_desc for 508 on node 0 [ 0.056001] alloc kstat_irqs on node 0 [ 0.056001] alloc irq_desc for 507 on node 0 [ 0.056001] alloc kstat_irqs on node 0 [ 0.056013] calling migration_init+0x0/0x4f @ 1 [ 0.060050] initcall migration_init+0x0/0x4f returned 0 after 3906 usecs [ 0.064001] calling spawn_ksoftirqd+0x0/0x4f @ 1 [ 0.064031] initcall spawn_ksoftirqd+0x0/0x4f returned 0 after 3906 usecs [ 0.068001] calling init_call_single_data+0x0/0x7f @ 1 [ 0.068001] initcall init_call_single_data+0x0/0x7f returned 0 after 0 usecs [ 0.068001] calling spawn_softlockup_task+0x0/0x6b @ 1 [ 0.068040] initcall spawn_softlockup_task+0x0/0x6b returned 0 after 3906 usecs [ 0.072001] calling relay_init+0x0/0x14 @ 1 [ 0.072001] initcall relay_init+0x0/0x14 returned 0 after 0 usecs [ 0.072001] calling tracer_alloc_buffers+0x0/0x199 @ 1 [ 0.072001] initcall tracer_alloc_buffers+0x0/0x199 returned 0 after 0 usecs [ 0.072001] calling init_trace_printk+0x0/0xc @ 1 [ 0.072001] initcall init_trace_printk+0x0/0xc returned 0 after 0 usecs [ 0.072001] Brought up 1 CPUs [ 0.072001] CPU0 attaching NULL sched-domain. [ 0.072155] devtmpfs: initialized [ 0.080141] calling init_mmap_min_addr+0x0/0x21 @ 1 [ 0.084001] initcall init_mmap_min_addr+0x0/0x21 returned 0 after 0 usecs [ 0.084001] calling init_cpufreq_transition_notifier_list+0x0/0x1b @ 1 [ 0.084001] initcall init_cpufreq_transition_notifier_list+0x0/0x1b returned 0 after 0 usecs [ 0.084001] calling net_ns_init+0x0/0xf2 @ 1 [ 0.084080] initcall net_ns_init+0x0/0xf2 returned 0 after 3906 usecs [ 0.088001] calling e820_mark_nvs_memory+0x0/0x36 @ 1 [ 0.088001] initcall e820_mark_nvs_memory+0x0/0x36 returned 0 after 0 usecs [ 0.088001] calling cpufreq_tsc+0x0/0x28 @ 1 [ 0.088001] initcall cpufreq_tsc+0x0/0x28 returned 0 after 0 usecs [ 0.088001] calling pci_reboot_init+0x0/0x14 @ 1 [ 0.088001] initcall pci_reboot_init+0x0/0x14 returned 0 after 0 usecs [ 0.088001] calling init_lapic_sysfs+0x0/0x2e @ 1 [ 0.088001] initcall init_lapic_sysfs+0x0/0x2e returned 0 after 0 usecs [ 0.088001] calling alloc_frozen_cpus+0x0/0x3 @ 1 [ 0.088001] initcall alloc_frozen_cpus+0x0/0x3 returned 0 after 0 usecs [ 0.088001] calling sysctl_init+0x0/0x32 @ 1 [ 0.088001] initcall sysctl_init+0x0/0x32 returned 0 after 0 usecs [ 0.088001] calling ksysfs_init+0x0/0xb9 @ 1 [ 0.088001] initcall ksysfs_init+0x0/0xb9 returned 0 after 0 usecs [ 0.088001] calling async_init+0x0/0x56 @ 1 [ 0.088044] initcall async_init+0x0/0x56 returned 0 after 3906 usecs [ 0.092001] calling init_jiffies_clocksource+0x0/0xc @ 1 [ 0.092012] initcall init_jiffies_clocksource+0x0/0xc returned 0 after 3906 usecs [ 0.096001] calling pm_init+0x0/0x60 @ 1 [ 0.096037] initcall pm_init+0x0/0x60 returned 0 after 3906 usecs [ 0.100001] calling pm_disk_init+0x0/0x13 @ 1 [ 0.100001] initcall pm_disk_init+0x0/0x13 returned 0 after 0 usecs [ 0.100001] calling swsusp_header_init+0x0/0x2c @ 1 [ 0.100001] initcall swsusp_header_init+0x0/0x2c returned 0 after 0 usecs [ 0.100001] calling init_zero_pfn+0x0/0x35 @ 1 [ 0.100001] initcall init_zero_pfn+0x0/0x35 returned 0 after 0 usecs [ 0.100001] calling filelock_init+0x0/0x2f @ 1 [ 0.100017] initcall filelock_init+0x0/0x2f returned 0 after 3906 usecs [ 0.104001] calling init_script_binfmt+0x0/0xe @ 1 [ 0.104001] initcall init_script_binfmt+0x0/0xe returned 0 after 0 usecs [ 0.104001] calling init_elf_binfmt+0x0/0xe @ 1 [ 0.104001] initcall init_elf_binfmt+0x0/0xe returned 0 after 0 usecs [ 0.104001] calling init_compat_elf_binfmt+0x0/0xe @ 1 [ 0.104001] initcall init_compat_elf_binfmt+0x0/0xe returned 0 after 0 usecs [ 0.104001] calling debugfs_init+0x0/0x50 @ 1 [ 0.104015] initcall debugfs_init+0x0/0x50 returned 0 after 3906 usecs [ 0.108001] calling securityfs_init+0x0/0x47 @ 1 [ 0.108001] initcall securityfs_init+0x0/0x47 returned 0 after 0 usecs [ 0.108001] calling random32_init+0x0/0xc7 @ 1 [ 0.108001] initcall random32_init+0x0/0xc7 returned 0 after 0 usecs [ 0.108001] calling gnttab_init+0x0/0x177 @ 1 [ 0.108026] Grant table initialized [ 0.112001] initcall gnttab_init+0x0/0x177 returned 0 after 3906 usecs [ 0.112001] calling regulator_init+0x0/0x2e @ 1 [ 0.112001] regulator: core version 0.5 [ 0.112018] initcall regulator_init+0x0/0x2e returned 0 after 3906 usecs [ 0.116001] calling cpufreq_core_init+0x0/0x9f @ 1 [ 0.116001] initcall cpufreq_core_init+0x0/0x9f returned 0 after 0 usecs [ 0.116001] calling cpuidle_init+0x0/0x36 @ 1 [ 0.116001] initcall cpuidle_init+0x0/0x36 returned 0 after 0 usecs [ 0.116001] calling sock_init+0x0/0x5e @ 1 [ 0.116069] initcall sock_init+0x0/0x5e returned 0 after 3906 usecs [ 0.120001] calling net_inuse_init+0x0/0x26 @ 1 [ 0.120001] initcall net_inuse_init+0x0/0x26 returned 0 after 0 usecs [ 0.120001] calling netpoll_init+0x0/0x2c @ 1 [ 0.120001] initcall netpoll_init+0x0/0x2c returned 0 after 0 usecs [ 0.120001] calling netlink_proto_init+0x0/0x130 @ 1 [ 0.120001] NET: Registered protocol family 16 [ 0.120011] initcall netlink_proto_init+0x0/0x130 returned 0 after 3906 usecs [ 0.124001] calling bdi_class_init+0x0/0x42 @ 1 [ 0.124018] initcall bdi_class_init+0x0/0x42 returned 0 after 3906 usecs [ 0.128001] calling kobject_uevent_init+0x0/0x54 @ 1 [ 0.128007] initcall kobject_uevent_init+0x0/0x54 returned 0 after 3906 usecs [ 0.132001] calling pcibus_class_init+0x0/0x13 @ 1 [ 0.132001] initcall pcibus_class_init+0x0/0x13 returned 0 after 0 usecs [ 0.132001] calling pci_driver_init+0x0/0xc @ 1 [ 0.132001] initcall pci_driver_init+0x0/0xc returned 0 after 0 usecs [ 0.132001] calling backlight_class_init+0x0/0x5d @ 1 [ 0.132022] initcall backlight_class_init+0x0/0x5d returned 0 after 3906 usecs [ 0.136001] calling xenbus_probe_init+0x0/0x277 @ 1 [ 0.136008] alloc irq_desc for 506 on node 0 [ 0.140001] alloc kstat_irqs on node 0 [ 0.140072] xenbus_probe_init ok [ 0.144001] initcall xenbus_probe_init+0x0/0x277 returned 0 after 7812 usecs [ 0.144001] calling tty_class_init+0x0/0x38 @ 1 [ 0.144001] initcall tty_class_init+0x0/0x38 returned 0 after 0 usecs [ 0.144001] calling vtconsole_class_init+0x0/0xb8 @ 1 [ 0.144042] initcall vtconsole_class_init+0x0/0xb8 returned 0 after 3906 usecs [ 0.148001] calling register_node_type+0x0/0x74 @ 1 [ 0.148001] initcall register_node_type+0x0/0x74 returned 0 after 0 usecs [ 0.148001] calling spi_init+0x0/0xc2 @ 1 [ 0.148017] initcall spi_init+0x0/0xc2 returned 0 after 3906 usecs [ 0.152001] calling amd_postcore_init+0x0/0x76 @ 1 [ 0.152019] node 0 link 0: io port [0, fffff] [ 0.156008] TOM: 00000000e0000000 aka 3584M [ 0.160007] node 0 link 0: mmio [e0000000, efffffff] [ 0.164011] node 0 link 0: mmio [a0000, bffff] [ 0.168006] node 0 link 0: mmio [e0000000, fe0bffff] [ 0.172005] TOM2: 0000000120000000 aka 4608M [ 0.176001] bus: [00,ff] on node 0 link 0 [ 0.176001] bus: 00 index 0 io port: [0, ffff] [ 0.176001] bus: 00 index 1 mmio: [e0000000, ffffffff] [ 0.176001] bus: 00 index 2 mmio: [a0000, bffff] [ 0.176001] bus: 00 index 3 mmio: [120000000, fcffffffff] [ 0.176001] initcall amd_postcore_init+0x0/0x76 returned 0 after 23437 usecs [ 0.176001] calling arch_kdebugfs_init+0x0/0x24 @ 1 [ 0.176001] initcall arch_kdebugfs_init+0x0/0x24 returned 0 after 0 usecs [ 0.176001] calling mtrr_if_init+0x0/0x63 @ 1 [ 0.176001] initcall mtrr_if_init+0x0/0x63 returned 0 after 0 usecs [ 0.176001] calling ffh_cstate_init+0x0/0x2a @ 1 [ 0.176001] initcall ffh_cstate_init+0x0/0x2a returned -1 after 0 usecs [ 0.176001] initcall ffh_cstate_init+0x0/0x2a returned with error code -1 [ 0.176001] calling acpi_pci_init+0x0/0x5c @ 1 [ 0.176005] ACPI: bus type pci registered [ 0.180001] initcall acpi_pci_init+0x0/0x5c returned 0 after 3906 usecs [ 0.180001] calling register_xen_pci_notifier+0x0/0x1f @ 1 [ 0.180001] initcall register_xen_pci_notifier+0x0/0x1f returned 0 after 0 usecs [ 0.180001] calling setup_vcpu_hotplug_event+0x0/0x22 @ 1 [ 0.180001] initcall setup_vcpu_hotplug_event+0x0/0x22 returned 0 after 0 usecs [ 0.180001] calling dmi_id_init+0x0/0x33f @ 1 [ 0.180001] initcall dmi_id_init+0x0/0x33f returned 0 after 0 usecs [ 0.180001] calling dma_bus_init+0x0/0x3f @ 1 [ 0.180001] initcall dma_bus_init+0x0/0x3f returned 0 after 0 usecs [ 0.180001] calling dma_channel_table_init+0x0/0x108 @ 1 [ 0.180001] initcall dma_channel_table_init+0x0/0x108 returned 0 after 0 usecs [ 0.180001] calling pci_arch_init+0x0/0x56 @ 1 [ 0.180001] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 2 [ 0.180001] PCI: Not using MMCONFIG. [ 0.180001] PCI: Using configuration type 1 for base access [ 0.180001] initcall pci_arch_init+0x0/0x56 returned 0 after 0 usecs [ 0.180001] calling topology_init+0x0/0x8c @ 1 [ 0.180099] initcall topology_init+0x0/0x8c returned 0 after 3906 usecs [ 0.184001] calling mtrr_init_finialize+0x0/0x3d @ 1 [ 0.184001] initcall mtrr_init_finialize+0x0/0x3d returned 0 after 0 usecs [ 0.184001] calling param_sysfs_init+0x0/0x234 @ 1 [ 0.184491] initcall param_sysfs_init+0x0/0x234 returned 0 after 3906 usecs [ 0.188001] calling pm_sysrq_init+0x0/0x19 @ 1 [ 0.188001] initcall pm_sysrq_init+0x0/0x19 returned 0 after 0 usecs [ 0.188001] calling audit_watch_init+0x0/0x2f @ 1 [ 0.188001] initcall audit_watch_init+0x0/0x2f returned 0 after 0 usecs [ 0.188001] calling init_slow_work+0x0/0x37 @ 1 [ 0.188001] initcall init_slow_work+0x0/0x37 returned 0 after 0 usecs [ 0.188001] calling default_bdi_init+0x0/0xa7 @ 1 [ 0.188127] initcall default_bdi_init+0x0/0xa7 returned 0 after 3906 usecs [ 0.192001] calling init_bio+0x0/0xc4 @ 1 [ 0.192066] bio: create slab <bio-0> at 0 [ 0.196023] initcall init_bio+0x0/0xc4 returned 0 after 7812 usecs [ 0.200001] calling fsnotify_init+0x0/0xc @ 1 [ 0.200001] initcall fsnotify_init+0x0/0xc returned 0 after 0 usecs [ 0.200001] calling fsnotify_notification_init+0x0/0xf0 @ 1 [ 0.200011] initcall fsnotify_notification_init+0x0/0xf0 returned 0 after 3906 usecs [ 0.204001] calling cryptomgr_init+0x0/0xc @ 1 [ 0.204001] initcall cryptomgr_init+0x0/0xc returned 0 after 0 usecs [ 0.204001] calling blk_settings_init+0x0/0x25 @ 1 [ 0.204001] initcall blk_settings_init+0x0/0x25 returned 0 after 0 usecs [ 0.204001] calling blk_ioc_init+0x0/0x2a @ 1 [ 0.204007] initcall blk_ioc_init+0x0/0x2a returned 0 after 3906 usecs [ 0.208001] calling blk_softirq_init+0x0/0x6e @ 1 [ 0.208001] initcall blk_softirq_init+0x0/0x6e returned 0 after 0 usecs [ 0.208001] calling blk_iopoll_setup+0x0/0x6e @ 1 [ 0.208001] initcall blk_iopoll_setup+0x0/0x6e returned 0 after 0 usecs [ 0.208001] calling genhd_device_init+0x0/0x71 @ 1 [ 0.208057] initcall genhd_device_init+0x0/0x71 returned 0 after 3906 usecs [ 0.212001] calling blk_dev_integrity_init+0x0/0x2a @ 1 [ 0.212016] initcall blk_dev_integrity_init+0x0/0x2a returned 0 after 3906 usecs [ 0.216001] calling pci_slot_init+0x0/0x47 @ 1 [ 0.216001] initcall pci_slot_init+0x0/0x47 returned 0 after 0 usecs [ 0.216001] calling fbmem_init+0x0/0x98 @ 1 [ 0.216001] initcall fbmem_init+0x0/0x98 returned 0 after 0 usecs [ 0.216001] calling acpi_init+0x0/0x2de @ 1 [ 0.216850] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.220025] ACPI: EC: Look up EC in DSDT [ 0.229062] ACPI: Interpreter enabled [ 0.232001] ACPI: (supports S0 S1 S3 S4 S5) [ 0.232001] ACPI: Using IOAPIC for interrupt routing [ 0.232050] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 2 [ 0.237071] PCI: MCFG area at e0000000 reserved in ACPI motherboard resources [ 0.240462] PCI: Using MMCONFIG at e0000000 - e02fffff [ 0.250159] initcall acpi_init+0x0/0x2de returned 0 after 35156 usecs [ 0.252001] calling dock_init+0x0/0x8d @ 1 [ 0.252001] ACPI: No dock devices found. [ 0.252001] initcall dock_init+0x0/0x8d returned 0 after 0 usecs [ 0.252001] calling acpi_pci_root_init+0x0/0x28 @ 1 [ 0.252224] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 0.256099] pci 0000:00:00.0: reg 10 32bit mmio: [0xf8000000-0xf9ffffff] [ 0.260216] pci 0000:00:02.5: reg 10 io port: [0x1f0-0x1f7] [ 0.264001] pci 0000:00:02.5: reg 14 io port: [0x3f4-0x3f7] [ 0.264001] pci 0000:00:02.5: reg 18 io port: [0x170-0x177] [ 0.264001] pci 0000:00:02.5: reg 1c io port: [0x374-0x377] [ 0.264001] pci 0000:00:02.5: reg 20 io port: [0x1c80-0x1c8f] [ 0.264001] pci 0000:00:02.5: PME# supported from D3cold [ 0.264001] pci 0000:00:02.5: PME# disabled [ 0.264050] pci 0000:00:02.7: reg 10 io port: [0x1400-0x14ff] [ 0.268001] pci 0000:00:02.7: reg 14 io port: [0x1000-0x107f] [ 0.268001] pci 0000:00:02.7: supports D1 D2 [ 0.268001] pci 0000:00:02.7: PME# supported from D3hot D3cold [ 0.268001] pci 0000:00:02.7: PME# disabled [ 0.268031] pci 0000:00:03.0: reg 10 32bit mmio: [0xfa000000-0xfa000fff] [ 0.272031] pci 0000:00:03.1: reg 10 32bit mmio: [0xfa001000-0xfa001fff] [ 0.276031] pci 0000:00:03.2: reg 10 32bit mmio: [0xfa002000-0xfa002fff] [ 0.280046] pci 0000:00:03.3: reg 10 32bit mmio: [0xfa003000-0xfa003fff] [ 0.284001] pci 0000:00:03.3: PME# supported from D0 D3hot D3cold [ 0.284001] pci 0000:00:03.3: PME# disabled [ 0.284059] pci 0000:00:05.0: reg 10 io port: [0x1cb0-0x1cb7] [ 0.288001] pci 0000:00:05.0: reg 14 io port: [0x1ca4-0x1ca7] [ 0.288001] pci 0000:00:05.0: reg 18 io port: [0x1ca8-0x1caf] [ 0.288001] pci 0000:00:05.0: reg 1c io port: [0x1ca0-0x1ca3] [ 0.288001] pci 0000:00:05.0: reg 20 io port: [0x1c90-0x1c9f] [ 0.288001] pci 0000:00:05.0: reg 24 io port: [0x1c00-0x1c7f] [ 0.288001] pci 0000:00:05.0: PME# supported from D3cold [ 0.288001] pci 0000:00:05.0: PME# disabled [ 0.288125] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold [ 0.292001] pci 0000:00:06.0: PME# disabled [ 0.292051] pci 0000:00:09.0: reg 10 io port: [0x1800-0x18ff] [ 0.296001] pci 0000:00:09.0: reg 14 32bit mmio: [0xfa004000-0xfa0040ff] [ 0.296001] pci 0000:00:09.0: supports D1 D2 [ 0.296001] pci 0000:00:09.0: PME# supported from D1 D2 D3hot D3cold [ 0.296001] pci 0000:00:09.0: PME# disabled [ 0.296389] pci 0000:00:1f.0: PME# supported from D0 D3hot D3cold [ 0.300001] pci 0000:00:1f.0: PME# disabled [ 0.300061] pci 0000:01:00.0: reg 10 32bit mmio pref: [0xf0000000-0xf7ffffff] [ 0.304001] pci 0000:01:00.0: reg 14 32bit mmio: [0xfa100000-0xfa11ffff] [ 0.304001] pci 0000:01:00.0: reg 18 io port: [0x2000-0x207f] [ 0.304001] pci 0000:01:00.0: supports D1 D2 [ 0.304068] pci 0000:00:01.0: bridge io port: [0x2000-0x2fff] [ 0.308001] pci 0000:00:01.0: bridge 32bit mmio: [0xfa100000-0xfa1fffff] [ 0.308001] pci 0000:00:01.0: bridge 32bit mmio pref: [0xf0000000-0xf7ffffff] [ 0.308193] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 0.312397] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT] [ 0.316094] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIX._PRT] [ 0.320009] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE0._PRT] (XEN) PCI add device 00:00.0 (XEN) PCI add device 00:01.0 (XEN) PCI add device 00:02.0 (XEN) PCI add device 00:02.5 (XEN) PCI add device 00:02.7 (XEN) PCI add device 00:03.0 (XEN) PCI add device 00:03.1 (XEN) PCI add device 00:03.2 (XEN) PCI add device 00:03.3 (XEN) PCI add device 00:05.0 (XEN) PCI add device 00:06.0 (XEN) PCI add device 00:09.0 (XEN) PCI add device 00:18.0 (XEN) PCI add device 00:18.1 (XEN) PCI add device 00:18.2 (XEN) PCI add device 00:18.3 (XEN) PCI add device 00:1f.0 (XEN) PCI add device 01:00.0 [ 0.396112] initcall acpi_pci_root_init+0x0/0x28 returned 0 after 144531 usecs [ 0.400001] calling acpi_pci_link_init+0x0/0x43 @ 1 [ 0.400142] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 0.404106] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) [ 0.408101] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) [ 0.412101] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 0.416099] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) [ 0.420099] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 0.424115] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 0.428115] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) [ 0.432044] initcall acpi_pci_link_init+0x0/0x43 returned 0 after 35156 usecs [ 0.436001] calling pnp_init+0x0/0xc @ 1 [ 0.436001] initcall pnp_init+0x0/0xc returned 0 after 0 usecs [ 0.436001] calling setup_shutdown_event+0x0/0x14 @ 1 [ 0.436001] initcall setup_shutdown_event+0x0/0x14 returned 0 after 0 usecs [ 0.436001] calling xenbus_probe_backend_init+0x0/0x4f @ 1 [ 0.436001] xenbus_probe_backend_init bus registered ok [ 0.436001] initcall xenbus_probe_backend_init+0x0/0x4f returned 0 after 0 usecs [ 0.436001] calling xenbus_probe_frontend_init+0x0/0x4f @ 1 [ 0.436001] xenbus_probe_frontend_init bus registered ok [ 0.436001] initcall xenbus_probe_frontend_init+0x0/0x4f returned 0 after 0 usecs [ 0.436001] calling balloon_init+0x0/0x200 @ 1 [ 0.436001] xen_balloon: Initialising balloon driver with page order 0. [ 0.436026] initcall balloon_init+0x0/0x200 returned 0 after 3906 usecs [ 0.440001] calling misc_init+0x0/0xad @ 1 [ 0.440019] initcall misc_init+0x0/0xad returned 0 after 3906 usecs [ 0.444001] calling vga_arb_device_init+0x0/0x74 @ 1 [ 0.444068] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none [ 0.448001] vgaarb: loaded [ 0.448001] initcall vga_arb_device_init+0x0/0x74 returned 0 after 3906 usecs [ 0.448001] calling serio_init+0x0/0x84 @ 1 [ 0.448059] initcall serio_init+0x0/0x84 returned 0 after 3906 usecs [ 0.452001] calling input_init+0x0/0x132 @ 1 [ 0.452001] initcall input_init+0x0/0x132 returned 0 after 0 usecs [ 0.452001] calling rtc_init+0x0/0x71 @ 1 [ 0.452001] initcall rtc_init+0x0/0x71 returned 0 after 0 usecs [ 0.452001] calling power_supply_class_init+0x0/0x38 @ 1 [ 0.452001] initcall power_supply_class_init+0x0/0x38 returned 0 after 0 usecs [ 0.452001] calling hwmon_init+0x0/0x106 @ 1 [ 0.452001] initcall hwmon_init+0x0/0x106 returned 0 after 0 usecs [ 0.452001] calling pci_subsys_init+0x0/0x113 @ 1 [ 0.452001] PCI: Using ACPI for IRQ routing [ 0.452001] initcall pci_subsys_init+0x0/0x113 returned 0 after 0 usecs [ 0.452001] calling proto_init+0x0/0xc @ 1 [ 0.452001] initcall proto_init+0x0/0xc returned 0 after 0 usecs [ 0.452001] calling net_dev_init+0x0/0x177 @ 1 [ 0.452121] initcall net_dev_init+0x0/0x177 returned 0 after 3906 usecs [ 0.456001] calling neigh_init+0x0/0x71 @ 1 [ 0.456001] initcall neigh_init+0x0/0x71 returned 0 after 0 usecs [ 0.456001] calling fib_rules_init+0x0/0x9c @ 1 [ 0.456001] initcall fib_rules_init+0x0/0x9c returned 0 after 0 usecs [ 0.456001] calling pktsched_init+0x0/0xd0 @ 1 [ 0.456001] initcall pktsched_init+0x0/0xd0 returned 0 after 0 usecs [ 0.456001] calling tc_filter_init+0x0/0x4c @ 1 [ 0.456001] initcall tc_filter_init+0x0/0x4c returned 0 after 0 usecs [ 0.456001] calling tc_action_init+0x0/0x4c @ 1 [ 0.456001] initcall tc_action_init+0x0/0x4c returned 0 after 0 usecs [ 0.456001] calling genl_init+0x0/0x90 @ 1 [ 0.456015] initcall genl_init+0x0/0x90 returned 0 after 3906 usecs [ 0.460001] calling wireless_nlevent_init+0x0/0xc @ 1 [ 0.460001] initcall wireless_nlevent_init+0x0/0xc returned 0 after 0 usecs [ 0.460001] calling sysctl_init+0x0/0x3f @ 1 [ 0.460001] initcall sysctl_init+0x0/0x3f returned 0 after 0 usecs [ 0.460001] calling print_all_ICs+0x0/0x581 @ 1 [ 0.460001] initcall print_all_ICs+0x0/0x581 returned 0 after 0 usecs [ 0.460001] calling hpet_late_init+0x0/0x1b3 @ 1 [ 0.460001] initcall hpet_late_init+0x0/0x1b3 returned -19 after 0 usecs [ 0.460001] calling clocksource_done_booting+0x0/0x5a @ 1 [ 0.460001] Switching to clocksource xen [ 0.460104] initcall clocksource_done_booting+0x0/0x5a returned 0 after 3937 usecs [ 0.464001] calling rb_init_debugfs+0x0/0x2f @ 1 [ 0.464001] initcall rb_init_debugfs+0x0/0x2f returned 0 after 11 usecs [ 0.464001] calling tracer_init_debugfs+0x0/0x2d0 @ 1 [ 0.532735] initcall tracer_init_debugfs+0x0/0x2d0 returned 0 after 115 usecs [ 0.536650] calling init_trace_printk_function_export+0x0/0x2f @ 1 [ 0.536650] initcall init_trace_printk_function_export+0x0/0x2f returned 0 after 1 usecs [ 0.536650] calling event_trace_init+0x0/0x1f4 @ 1 [ 0.613885] initcall event_trace_init+0x0/0x1f4 returned 0 after 1516 usecs [ 0.616328] calling init_pipe_fs+0x0/0x42 @ 1 [ 0.647996] initcall init_pipe_fs+0x0/0x42 returned 0 after 56 usecs [ 0.651964] calling eventpoll_init+0x0/0xc2 @ 1 [ 0.681198] initcall eventpoll_init+0x0/0xc2 returned 0 after 28 usecs [ 0.685171] calling anon_inode_init+0x0/0x11b @ 1 [ 0.715458] initcall anon_inode_init+0x0/0x11b returned 0 after 16 usecs [ 0.719446] calling blk_scsi_ioctl_init+0x0/0x292 @ 1 [ 0.719446] initcall blk_scsi_ioctl_init+0x0/0x292 returned 0 after 0 usecs [ 0.719446] calling acpi_event_init+0x0/0x52 @ 1 [ 0.786602] initcall acpi_event_init+0x0/0x52 returned 0 after 21 usecs [ 0.790591] calling pnpacpi_init+0x0/0x8c @ 1 [ 0.790591] pnp: PnP ACPI init [ 0.829446] ACPI: bus type pnp registered [ 0.842599] xen: registering gsi 8 triggering 1 polarity 0 [ 0.845807] xen_allocate_pirq: returning irq 8 for gsi 8 [ 0.845807] xen: --> irq=8 [ 0.883165] Already setup the GSI :8 [ 0.894129] xen: registering gsi 13 triggering 1 polarity 0 [ 0.898047] xen_allocate_pirq: returning irq 13 for gsi 13 [ 0.898047] xen: --> irq=13 [ 0.936112] Already setup the GSI :13 [ 0.947410] xen: registering gsi 1 triggering 1 polarity 0 [ 0.951270] xen_allocate_pirq: returning irq 1 for gsi 1 [ 0.951270] xen: --> irq=1 [ 0.988300] Already setup the GSI :1 [ 1.000095] xen: registering gsi 7 triggering 1 polarity 0 [ 1.004009] xen_allocate_pirq: returning irq 7 for gsi 7 [ 1.004009] xen: --> irq=7 [ 1.040646] Already setup the GSI :7 [ 1.051981] xen: registering gsi 4 triggering 1 polarity 0 [ 1.055541] xen_allocate_pirq: returning irq 4 for gsi 4 [ 1.055541] xen: --> irq=4 [ 1.092577] Already setup the GSI :4 [ 1.103900] xen: registering gsi 3 triggering 1 polarity 0 [ 1.107483] xen_allocate_pirq: returning irq 3 for gsi 3 [ 1.107483] xen: --> irq=3 [ 1.144503] Already setup the GSI :3 [ 1.155496] pnp: PnP ACPI: found 10 devices [ 1.168122] ACPI: ACPI bus type pnp unregistered [ 1.172116] initcall pnpacpi_init+0x0/0x8c returned 0 after 353576 usecs [ 1.172116] calling pnp_system_init+0x0/0xc @ 1 [ 1.216426] system 00:01: ioport range 0x480-0x48f has been reserved [ 1.220412] system 00:01: ioport range 0x4d0-0x4d1 has been reserved [ 1.220412] system 00:01: ioport range 0xf000-0xf0fe has been reserved [ 1.220412] system 00:01: ioport range 0xf200-0xf2fe has been reserved [ 1.220412] system 00:01: ioport range 0x800-0x87f has been reserved [ 1.220412] system 00:01: ioport range 0xfe00-0xfe00 has been reserved [ 1.220412] system 00:01: iomem range 0xfec00000-0xfecfffff could not be reserved [ 1.220412] system 00:01: iomem range 0xfee00000-0xfeefffff could not be reserved [ 1.220412] system 00:01: iomem range 0xff780000-0xffefffff has been reserved [ 1.220412] system 00:01: iomem range 0xe0000000-0xefffffff has been reserved [ 1.421536] initcall pnp_system_init+0x0/0xc returned 0 after 200321 usecs [ 1.425515] calling pcistub_init+0x0/0x1ba @ 1 [ 1.456908] initcall pcistub_init+0x0/0x1ba returned 0 after 840 usecs [ 1.460049] calling chr_dev_init+0x0/0xba @ 1 [ 1.489930] initcall chr_dev_init+0x0/0xba returned 0 after 261 usecs [ 1.493701] calling firmware_class_init+0x0/0x6f @ 1 [ 1.493701] initcall firmware_class_init+0x0/0x6f returned 0 after 9 usecs [ 1.493701] calling cpufreq_gov_performance_init+0x0/0xc @ 1 [ 1.493701] initcall cpufreq_gov_performance_init+0x0/0xc returned 0 after 0 usecs [ 1.493701] calling cpufreq_gov_dbs_init+0x0/0xa9 @ 1 [ 1.601173] initcall cpufreq_gov_dbs_init+0x0/0xa9 returned 0 after 125 usecs [ 1.605062] calling init_acpi_pm_clocksource+0x0/0xee @ 1 [ 1.643732] initcall init_acpi_pm_clocksource+0x0/0xee returned 0 after 4417 usecs [ 1.644003] calling pcibios_assign_resources+0x0/0x6a @ 1 [ 1.644003] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 [ 1.644003] pci 0000:00:01.0: IO window: 0x2000-0x2fff [ 1.644003] pci 0000:00:01.0: MEM window: 0xfa100000-0xfa1fffff [ 1.644003] pci 0000:00:01.0: PREFETCH window: 0xf0000000-0xf7ffffff [ 1.644003] pci 0000:00:06.0: PCI bridge, secondary bus 0000:02 [ 1.644003] pci 0000:00:06.0: IO window: disabled [ 1.644003] pci 0000:00:06.0: MEM window: disabled [ 1.644003] pci 0000:00:06.0: PREFETCH window: disabled [ 1.644003] pci 0000:00:1f.0: PCI bridge, secondary bus 0000:03 [ 1.644003] pci 0000:00:1f.0: IO window: disabled [ 1.644003] pci 0000:00:1f.0: MEM window: disabled [ 1.644003] pci 0000:00:1f.0: PREFETCH window: disabled [ 1.644003] pci 0000:00:06.0: setting latency timer to 64 [ 1.644003] pci 0000:00:1f.0: setting latency timer to 64 [ 1.644003] pci_bus 0000:00: resource 0 io: [0x00-0xffff] [ 1.644003] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] [ 1.644003] pci_bus 0000:01: resource 0 io: [0x2000-0x2fff] [ 1.644003] pci_bus 0000:01: resource 1 mem: [0xfa100000-0xfa1fffff] [ 1.644003] pci_bus 0000:01: resource 2 pref mem [0xf0000000-0xf7ffffff] [ 1.644003] initcall pcibios_assign_resources+0x0/0x6a returned 0 after 319469 usecs [ 1.644003] calling sysctl_core_init+0x0/0x37 @ 1 [ 1.644003] initcall sysctl_core_init+0x0/0x37 returned 0 after 23 usecs [ 1.644003] calling inet_init+0x0/0x1ff @ 1 [ 2.081047] NET: Registered protocol family 2 [ 2.094623] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 2.119563] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 2.147984] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 2.168479] TCP: Hash tables configured (established 524288 bind 65536) [ 2.172263] TCP reno registered [ 2.197762] initcall inet_init+0x0/0x1ff returned 0 after 114031 usecs [ 2.201608] calling af_unix_init+0x0/0x4b @ 1 [ 2.230840] NET: Registered protocol family 1 [ 2.244096] initcall af_unix_init+0x0/0x4b returned 0 after 12955 usecs [ 2.248073] calling pci_apply_final_quirks+0x0/0x2b @ 1 [ 3.864018] pci 0000:00:03.3: EHCI: BIOS handoff failed (BIOS bug?) 01010001 [ 3.884865] pci 0000:01:00.0: Boot video device [ 3.888837] initcall pci_apply_final_quirks+0x0/0x2b returned 0 after 1580492 usecs [ 3.888837] calling populate_rootfs+0x0/0x107 @ 1 [ 3.888837] Unpacking initramfs... [ 3.997956] Freeing initrd memory: 25757k freed [ 4.030957] initcall populate_rootfs+0x0/0x107 returned 0 after 92496 usecs [ 4.032015] calling pci_iommu_init+0x0/0x3a @ 1 [ 4.032015] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 4.032015] DMA: Placing 64MB software IO TLB between ffff880006cac000 - ffff88000acac000 [ 4.032015] DMA: software IO TLB at phys 0x6cac000 - 0xacac000 [ 4.032015] initcall pci_iommu_init+0x0/0x3a returned 0 after 60343 usecs [ 4.032015] calling calgary_fixup_tce_spaces+0x0/0xf8 @ 1 [ 4.032015] initcall calgary_fixup_tce_spaces+0x0/0xf8 returned -19 after 0 usecs [ 4.032015] calling i8259A_init_sysfs+0x0/0x23 @ 1 [ 4.201963] initcall i8259A_init_sysfs+0x0/0x23 returned 0 after 125 usecs [ 4.205859] calling vsyscall_init+0x0/0x6c @ 1 [ 4.236442] initcall vsyscall_init+0x0/0x6c returned 0 after 75 usecs [ 4.240388] calling sbf_init+0x0/0xef @ 1 [ 4.240388] Simple Boot Flag at 0x69 set to 0x1 [ 4.240388] initcall sbf_init+0x0/0xef returned 0 after 13442 usecs [ 4.240388] calling i8237A_init_sysfs+0x0/0x23 @ 1 [ 4.240388] initcall i8237A_init_sysfs+0x0/0x23 returned 0 after 16 usecs [ 4.240388] calling add_rtc_cmos+0x0/0xb6 @ 1 [ 4.240388] initcall add_rtc_cmos+0x0/0xb6 returned 0 after 2 usecs [ 4.240388] calling cache_sysfs_init+0x0/0x61 @ 1 [ 4.383634] initcall cache_sysfs_init+0x0/0x61 returned 0 after 308 usecs [ 4.387358] calling mce_init_device+0x0/0xfd @ 1 [ 4.387358] initcall mce_init_device+0x0/0xfd returned -5 after 0 usecs [ 4.387358] initcall mce_init_device+0x0/0xfd returned with error code -5 [ 4.387358] calling threshold_init_device+0x0/0x86 @ 1 [ 4.387358] initcall threshold_init_device+0x0/0x86 returned 0 after 0 usecs [ 4.387358] calling thermal_throttle_init_device+0x0/0x8f @ 1 [ 4.387358] initcall thermal_throttle_init_device+0x0/0x8f returned 0 after 0 usecs [ 4.387358] calling ioapic_init_sysfs+0x0/0xa6 @ 1 [ 4.387358] initcall ioapic_init_sysfs+0x0/0xa6 returned 0 after 18 usecs [ 4.387358] calling add_pcspkr+0x0/0x28 @ 1 [ 4.585093] initcall add_pcspkr+0x0/0x28 returned 0 after 43 usecs [ 4.589060] calling audit_classes_init+0x0/0xaf @ 1 [ 4.618817] initcall audit_classes_init+0x0/0xaf returned 0 after 14 usecs [ 4.622808] calling init_vdso_vars+0x0/0x218 @ 1 [ 4.653875] initcall init_vdso_vars+0x0/0x218 returned 0 after 22 usecs [ 4.657868] calling ia32_binfmt_init+0x0/0x14 @ 1 [ 4.657868] initcall ia32_binfmt_init+0x0/0x14 returned 0 after 10 usecs [ 4.657868] calling sysenter_setup+0x0/0x2c1 @ 1 [ 4.657868] initcall sysenter_setup+0x0/0x2c1 returned 0 after 4 usecs [ 4.657868] calling init_aout_binfmt+0x0/0xe @ 1 [ 4.657868] initcall init_aout_binfmt+0x0/0xe returned 0 after 0 usecs [ 4.657868] calling init_sched_debug_procfs+0x0/0x2d @ 1 [ 4.657868] initcall init_sched_debug_procfs+0x0/0x2d returned 0 after 7 usecs [ 4.657868] calling proc_execdomains_init+0x0/0x22 @ 1 [ 4.657868] initcall proc_execdomains_init+0x0/0x22 returned 0 after 1 usecs [ 4.657868] calling ioresources_init+0x0/0x3c @ 1 [ 4.657868] initcall ioresources_init+0x0/0x3c returned 0 after 2 usecs [ 4.657868] calling uid_cache_init+0x0/0x8f @ 1 [ 4.900518] initcall uid_cache_init+0x0/0x8f returned 0 after 16 usecs [ 4.904502] calling init_posix_timers+0x0/0x18f @ 1 [ 4.935300] initcall init_posix_timers+0x0/0x18f returned 0 after 8 usecs [ 4.939293] calling init_posix_cpu_timers+0x0/0xed @ 1 [ 4.939293] initcall init_posix_cpu_timers+0x0/0xed returned 0 after 0 usecs [ 4.939293] calling nsproxy_cache_init+0x0/0x2d @ 1 [ 5.007997] initcall nsproxy_cache_init+0x0/0x2d returned 0 after 8 usecs [ 5.011989] calling create_proc_profile+0x0/0x267 @ 1 [ 5.011989] initcall create_proc_profile+0x0/0x267 returned 0 after 0 usecs [ 5.011989] calling timekeeping_init_device+0x0/0x24 @ 1 [ 5.011989] initcall timekeeping_init_device+0x0/0x24 returned 0 after 20 usecs [ 5.011989] calling init_clocksource_sysfs+0x0/0x53 @ 1 [ 5.011989] initcall init_clocksource_sysfs+0x0/0x53 returned 0 after 15 usecs [ 5.011989] calling init_timer_list_procfs+0x0/0x2c @ 1 [ 5.011989] initcall init_timer_list_procfs+0x0/0x2c returned 0 after 2 usecs [ 5.011989] calling init_tstats_procfs+0x0/0x2c @ 1 [ 5.011989] initcall init_tstats_procfs+0x0/0x2c returned 0 after 1 usecs [ 5.011989] calling futex_init+0x0/0x9d @ 1 [ 5.227660] initcall futex_init+0x0/0x9d returned 0 after 23 usecs [ 5.231641] calling proc_dma_init+0x0/0x22 @ 1 [ 5.260114] initcall proc_dma_init+0x0/0x22 returned 0 after 23 usecs [ 5.264102] calling proc_modules_init+0x0/0x23 @ 1 [ 5.264102] initcall proc_modules_init+0x0/0x23 returned 0 after 1 usecs [ 5.264102] calling kallsyms_init+0x0/0x25 @ 1 [ 5.264102] initcall kallsyms_init+0x0/0x25 returned 0 after 1 usecs [ 5.264102] calling snapshot_device_init+0x0/0xc @ 1 [ 5.362973] initcall snapshot_device_init+0x0/0xc returned 0 after 66 usecs [ 5.366913] calling crash_save_vmcoreinfo_init+0x0/0x46d @ 1 [ 5.366913] initcall crash_save_vmcoreinfo_init+0x0/0x46d returned 0 after 27 usecs [ 5.366913] calling crash_notes_memory_init+0x0/0x38 @ 1 [ 5.366913] initcall crash_notes_memory_init+0x0/0x38 returned 0 after 4 usecs [ 5.366913] calling pid_namespaces_init+0x0/0x2d @ 1 [ 5.477933] initcall pid_namespaces_init+0x0/0x2d returned 0 after 11 usecs [ 5.481924] calling audit_init+0x0/0x134 @ 1 [ 5.481924] audit: initializing netlink socket (disabled) [ 5.528570] type=2000 audit(1270835115.253:1): initialized [ 5.532557] initcall audit_init+0x0/0x134 returned 0 after 32200 usecs [ 5.532557] calling audit_tree_init+0x0/0x49 @ 1 [ 5.532557] initcall audit_tree_init+0x0/0x49 returned 0 after 1 usecs [ 5.532557] calling hung_task_init+0x0/0x49 @ 1 [ 5.612998] initcall hung_task_init+0x0/0x49 returned 0 after 66 usecs [ 5.616939] calling utsname_sysctl_init+0x0/0x14 @ 1 [ 5.616939] initcall utsname_sysctl_init+0x0/0x14 returned 0 after 23 usecs [ 5.616939] calling init_tracepoints+0x0/0xc @ 1 [ 5.616939] initcall init_tracepoints+0x0/0xc returned 0 after 0 usecs [ 5.616939] calling init_events+0x0/0x61 @ 1 [ 5.716282] initcall init_events+0x0/0x61 returned 0 after 19 usecs [ 5.720264] calling init_sched_switch_trace+0x0/0xc @ 1 [ 5.720264] initcall init_sched_switch_trace+0x0/0xc returned 0 after 1 usecs [ 5.720264] calling init_blk_tracer+0x0/0x57 @ 1 [ 5.787150] initcall init_blk_tracer+0x0/0x57 returned 0 after 7 usecs [ 5.791143] calling perf_event_sysfs_init+0x0/0x13 @ 1 [ 5.791143] initcall perf_event_sysfs_init+0x0/0x13 returned 0 after 8 usecs [ 5.791143] calling init_per_zone_wmark_min+0x0/0x5d @ 1 [ 5.791143] initcall init_per_zone_wmark_min+0x0/0x5d returned 0 after 326 usecs [ 5.791143] calling kswapd_init+0x0/0x6e @ 1 [ 5.896020] initcall kswapd_init+0x0/0x6e returned 0 after 89 usecs [ 5.899954] calling setup_vmstat+0x0/0xc2 @ 1 [ 5.899954] initcall setup_vmstat+0x0/0xc2 returned 0 after 14 usecs [ 5.899954] calling mm_sysfs_init+0x0/0x29 @ 1 [ 5.899954] initcall mm_sysfs_init+0x0/0x29 returned 0 after 8 usecs [ 5.899954] calling proc_vmalloc_init+0x0/0x25 @ 1 [ 5.899954] initcall proc_vmalloc_init+0x0/0x25 returned 0 after 1 usecs [ 5.899954] calling procswaps_init+0x0/0x22 @ 1 [ 5.899954] initcall procswaps_init+0x0/0x22 returned 0 after 1 usecs [ 5.899954] calling hugetlb_init+0x0/0x3c2 @ 1 [ 5.899954] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 5.899954] initcall hugetlb_init+0x0/0x3c2 returned 0 after 18770 usecs [ 5.899954] calling ksm_init+0x0/0x196 @ 1 [ 6.115150] initcall ksm_init+0x0/0x196 returned 0 after 89 usecs [ 6.119059] calling slab_proc_init+0x0/0x25 @ 1 [ 6.119059] initcall slab_proc_init+0x0/0x25 returned 0 after 4 usecs [ 6.119059] calling slab_sysfs_init+0x0/0xe9 @ 1 [ 6.183066] initcall slab_sysfs_init+0x0/0xe9 returned 0 after 1755 usecs [ 6.185312] calling fasync_init+0x0/0x2a @ 1 [ 6.216368] initcall fasync_init+0x0/0x2a returned 0 after 30 usecs [ 6.220345] calling proc_filesystems_init+0x0/0x22 @ 1 [ 6.220345] initcall proc_filesystems_init+0x0/0x22 returned 0 after 9 usecs [ 6.220345] calling dnotify_init+0x0/0x80 @ 1 [ 6.285937] initcall dnotify_init+0x0/0x80 returned 0 after 18 usecs [ 6.289919] calling inotify_setup+0x0/0xd @ 1 [ 6.289919] initcall inotify_setup+0x0/0xd returned 0 after 0 usecs [ 6.289919] calling inotify_user_setup+0x0/0xbe @ 1 [ 6.352689] initcall inotify_user_setup+0x0/0xbe returned 0 after 44 usecs [ 6.356652] calling aio_setup+0x0/0x71 @ 1 [ 6.386216] initcall aio_setup+0x0/0x71 returned 0 after 77 usecs [ 6.390136] calling proc_locks_init+0x0/0x23 @ 1 [ 6.390136] initcall proc_locks_init+0x0/0x23 returned 0 after 4 usecs [ 6.390136] calling init_sys32_ioctl+0x0/0x85 @ 1 [ 6.390136] initcall init_sys32_ioctl+0x0/0x85 returned 0 after 16 usecs [ 6.390136] calling dquot_init+0x0/0x105 @ 1 [ 6.390136] VFS: Disk quotas dquot_6.5.2 [ 6.498671] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 6.518047] initcall dquot_init+0x0/0x105 returned 0 after 30696 usecs [ 6.522030] calling proc_cmdline_init+0x0/0x22 @ 1 [ 6.552574] initcall proc_cmdline_init+0x0/0x22 returned 0 after 13 usecs [ 6.556561] calling proc_cpuinfo_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_cpuinfo_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_devices_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_devices_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_interrupts_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_interrupts_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_loadavg_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_loadavg_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_meminfo_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_meminfo_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_stat_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_stat_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_uptime_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_uptime_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_version_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_version_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_softirqs_init+0x0/0x22 @ 1 [ 6.556561] initcall proc_softirqs_init+0x0/0x22 returned 0 after 1 usecs [ 6.556561] calling proc_kcore_init+0x0/0xb5 @ 1 [ 6.556561] initcall proc_kcore_init+0x0/0xb5 returned 0 after 6 usecs [ 6.556561] calling proc_kmsg_init+0x0/0x25 @ 1 [ 6.556561] initcall proc_kmsg_init+0x0/0x25 returned 0 after 1 usecs [ 6.556561] calling proc_page_init+0x0/0x42 @ 1 [ 6.556561] initcall proc_page_init+0x0/0x42 returned 0 after 2 usecs [ 6.556561] calling init_devpts_fs+0x0/0x42 @ 1 [ 7.003589] initcall init_devpts_fs+0x0/0x42 returned 0 after 49 usecs [ 7.007550] calling init_ramfs_fs+0x0/0xc @ 1 [ 7.007550] initcall init_ramfs_fs+0x0/0xc returned 0 after 0 usecs [ 7.007550] calling init_hugetlbfs_fs+0x0/0x8e @ 1 [ 7.070599] initcall init_hugetlbfs_fs+0x0/0x8e returned 0 after 73 usecs [ 7.074529] calling ipc_init+0x0/0x2f @ 1 [ 7.074529] msgmni has been set to 6830 [ 7.074529] initcall ipc_init+0x0/0x2f returned 0 after 11413 usecs [ 7.074529] calling ipc_sysctl_init+0x0/0x14 @ 1 [ 7.074529] initcall ipc_sysctl_init+0x0/0x14 returned 0 after 34 usecs [ 7.074529] calling init_mqueue_fs+0x0/0xaa @ 1 [ 7.182511] initcall init_mqueue_fs+0x0/0xaa returned 0 after 82 usecs [ 7.186427] calling key_proc_init+0x0/0x59 @ 1 [ 7.186427] initcall key_proc_init+0x0/0x59 returned 0 after 5 usecs [ 7.186427] calling selinux_nf_ip_init+0x0/0x61 @ 1 [ 7.186427] initcall selinux_nf_ip_init+0x0/0x61 returned 0 after 0 usecs [ 7.186427] calling init_sel_fs+0x0/0x5e @ 1 [ 7.186427] initcall init_sel_fs+0x0/0x5e returned 0 after 0 usecs [ 7.186427] calling selnl_init+0x0/0x4d @ 1 [ 7.315633] initcall selnl_init+0x0/0x4d returned 0 after 17 usecs [ 7.319624] calling sel_netif_init+0x0/0x66 @ 1 [ 7.319624] initcall sel_netif_init+0x0/0x66 returned 0 after 0 usecs [ 7.319624] calling sel_netnode_init+0x0/0x73 @ 1 [ 7.319624] initcall sel_netnode_init+0x0/0x73 returned 0 after 0 usecs [ 7.319624] calling sel_netport_init+0x0/0x73 @ 1 [ 7.319624] initcall sel_netport_init+0x0/0x73 returned 0 after 0 usecs [ 7.319624] calling aurule_init+0x0/0x37 @ 1 [ 7.319624] initcall aurule_init+0x0/0x37 returned 0 after 0 usecs [ 7.319624] calling crypto_wq_init+0x0/0x2e @ 1 [ 7.482891] initcall crypto_wq_init+0x0/0x2e returned 0 after 71 usecs [ 7.486834] calling crypto_algapi_init+0x0/0xd @ 1 [ 7.486834] initcall crypto_algapi_init+0x0/0xd returned 0 after 12 usecs [ 7.486834] calling skcipher_module_init+0x0/0x35 @ 1 [ 7.486834] initcall skcipher_module_init+0x0/0x35 returned 0 after 0 usecs [ 7.486834] calling chainiv_module_init+0x0/0xc @ 1 [ 7.589546] initcall chainiv_module_init+0x0/0xc returned 0 after 19 usecs [ 7.593528] calling eseqiv_module_init+0x0/0xc @ 1 [ 7.625102] initcall eseqiv_module_init+0x0/0xc returned 0 after 6 usecs [ 7.629095] calling md5_mod_init+0x0/0xc @ 1 [ 7.658680] initcall md5_mod_init+0x0/0xc returned 0 after 89 usecs [ 7.662589] calling krng_mod_init+0x0/0xc @ 1 [ 7.691095] alg: No test for stdrng (krng) [ 7.703523] initcall krng_mod_init+0x0/0xc returned 0 after 12188 usecs [ 7.707506] calling proc_genhd_init+0x0/0x3c @ 1 [ 7.707506] initcall proc_genhd_init+0x0/0x3c returned 0 after 8 usecs [ 7.707506] calling bsg_init+0x0/0x12d @ 1 [ 7.770344] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 7.774231] initcall bsg_init+0x0/0x12d returned 0 after 21804 usecs [ 7.774231] calling noop_init+0x0/0x14 @ 1 [ 7.774231] io scheduler noop registered [ 7.774231] initcall noop_init+0x0/0x14 returned 0 after 11663 usecs [ 7.774231] calling as_init+0x0/0x14 @ 1 [ 7.774231] io scheduler anticipatory registered [ 7.774231] initcall as_init+0x0/0x14 returned 0 after 13690 usecs [ 7.774231] calling deadline_init+0x0/0x14 @ 1 [ 7.774231] io scheduler deadline registered [ 7.774231] initcall deadline_init+0x0/0x14 returned 0 after 12676 usecs [ 7.774231] calling cfq_init+0x0/0x95 @ 1 [ 7.960101] io scheduler cfq registered (default) [ 7.964022] initcall cfq_init+0x0/0x95 returned 0 after 13945 usecs [ 7.964022] calling percpu_counter_startup+0x0/0x38 @ 1 [ 7.964022] initcall percpu_counter_startup+0x0/0x38 returned 0 after 2 usecs [ 7.964022] calling pci_proc_init+0x0/0x60 @ 1 [ 8.044736] initcall pci_proc_init+0x0/0x60 returned 0 after 74 usecs [ 8.048701] calling pcie_portdrv_init+0x0/0x42 @ 1 [ 8.079197] alloc irq_desc for 505 on node 0 [ 8.082956] alloc kstat_irqs on node 0 [ 8.104426] pcieport 0000:00:06.0: setting latency timer to 64 [ 8.122340] alloc irq_desc for 504 on node 0 [ 8.126033] alloc kstat_irqs on node 0 [ 8.147522] pcieport 0000:00:1f.0: setting latency timer to 64 [ 8.165265] initcall pcie_portdrv_init+0x0/0x42 returned 0 after 84306 usecs [ 8.169139] calling aer_service_init+0x0/0x2a @ 1 [ 8.201004] aer 0000:00:06.0:pcie02: AER service couldn''t init device: no _OSC support [ 8.224868] initcall aer_service_init+0x0/0x2a returned 0 after 23349 usecs [ 8.228848] calling pcifront_init+0x0/0x52 @ 1 [ 8.228848] initcall pcifront_init+0x0/0x52 returned 0 after 16 usecs [ 8.228848] calling fb_console_init+0x0/0x11b @ 1 [ 8.293680] initcall fb_console_init+0x0/0x11b returned 0 after 32 usecs [ 8.297654] calling xenfb_init+0x0/0x58 @ 1 [ 8.297654] initcall xenfb_init+0x0/0x58 returned -19 after 0 usecs [ 8.297654] calling vesafb_init+0x0/0x23a @ 1 [ 8.359378] initcall vesafb_init+0x0/0x23a returned 0 after 44 usecs [ 8.363349] calling efifb_init+0x0/0x1de @ 1 [ 8.363349] initcall efifb_init+0x0/0x1de returned -19 after 8 usecs [ 8.363349] calling acpi_reserve_resources+0x0/0xeb @ 1 [ 8.363349] initcall acpi_reserve_resources+0x0/0xeb returned 0 after 4 usecs [ 8.363349] calling irqrouter_init_sysfs+0x0/0x39 @ 1 [ 8.363349] initcall irqrouter_init_sysfs+0x0/0x39 returned 0 after 16 usecs [ 8.363349] calling gntdev_init+0x0/0x33 @ 1 [ 8.498812] initcall gntdev_init+0x0/0x33 returned 0 after 56 usecs [ 8.502760] calling pciback_init+0x0/0x138 @ 1 [ 8.531575] initcall pciback_init+0x0/0x138 returned 0 after 104 usecs [ 8.535488] calling blkif_init+0x0/0x17a @ 1 [ 8.568038] initcall blkif_init+0x0/0x17a returned 0 after 3507 usecs [ 8.572018] calling netback_init+0x0/0x1c9 @ 1 [ 8.602058] registering netback [ 8.611270] initcall netback_init+0x0/0x1c9 returned 0 after 10231 usecs [ 8.615207] calling hypervisor_subsys_init+0x0/0x20 @ 1 [ 8.615207] initcall hypervisor_subsys_init+0x0/0x20 returned 0 after 0 usecs [ 8.615207] calling hyper_sysfs_init+0x0/0xe8 @ 1 [ 8.683659] initcall hyper_sysfs_init+0x0/0xe8 returned 0 after 37 usecs [ 8.687627] calling rand_initialize+0x0/0x2c @ 1 [ 8.687627] initcall rand_initialize+0x0/0x2c returned 0 after 17 usecs [ 8.687627] calling tty_init+0x0/0xf5 @ 1 [ 8.752379] initcall tty_init+0x0/0xf5 returned 0 after 1727 usecs [ 8.756019] calling pty_init+0x0/0x336 @ 1 [ 8.783406] initcall pty_init+0x0/0x336 returned 0 after 90 usecs [ 8.787360] calling sysrq_init+0x0/0x25 @ 1 [ 8.787360] initcall sysrq_init+0x0/0x25 returned 0 after 12 usecs [ 8.787360] calling xen_hvc_init+0x0/0xe2 @ 1 [ 8.846944] alloc irq_desc for 503 on node 0 [ 8.850928] alloc kstat_irqs on node 0 [ 8.872675] initcall xen_hvc_init+0x0/0xe2 returned 0 after 25144 usecs [ 8.876380] calling hpet_init+0x0/0x60 @ 1 [ 8.905195] initcall hpet_init+0x0/0x60 returned 0 after 110 usecs [ 8.909092] calling agp_init+0x0/0x26 @ 1 [ 8.909092] Linux agpgart interface v0.103 [ 8.909092] initcall agp_init+0x0/0x26 returned 0 after 12170 usecs [ 8.909092] calling agp_intel_init+0x0/0x24 @ 1 [ 8.981714] initcall agp_intel_init+0x0/0x24 returned 0 after 41 usecs [ 8.985698] calling agp_sis_init+0x0/0x24 @ 1 [ 9.014933] initcall agp_sis_init+0x0/0x24 returned 0 after 27 usecs [ 9.018906] calling agp_via_init+0x0/0x24 @ 1 [ 9.018906] initcall agp_via_init+0x0/0x24 returned 0 after 14 usecs [ 9.018906] calling serial8250_init+0x0/0x141 @ 1 [ 9.018906] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 9.100544] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 9.118645] initcall serial8250_init+0x0/0x141 returned 0 after 36399 usecs [ 9.122505] calling serial8250_pnp_init+0x0/0xc @ 1 [ 9.154924] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 9.171521] initcall serial8250_pnp_init+0x0/0xc returned 0 after 16535 usecs [ 9.175473] calling serial8250_pci_init+0x0/0x15 @ 1 [ 9.175473] initcall serial8250_pci_init+0x0/0x15 returned 0 after 35 usecs [ 9.175473] calling topology_sysfs_init+0x0/0x5c @ 1 [ 9.175473] initcall topology_sysfs_init+0x0/0x5c returned 0 after 8 usecs [ 9.175473] calling mac_hid_init+0x0/0x84 @ 1 [ 9.279042] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [ 9.282962] initcall mac_hid_init+0x0/0x84 returned 0 after 22839 usecs [ 9.282962] calling net_olddevs_init+0x0/0x96 @ 1 [ 9.282962] initcall net_olddevs_init+0x0/0x96 returned 0 after 5 usecs [ 9.282962] calling i8042_init+0x0/0x3a8 @ 1 [ 9.370133] PNP: PS/2 Controller [PNP0303:KEYB] at 0x60,0x64 irq 1 [ 9.374089] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp [ 9.418451] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 9.433106] initcall i8042_init+0x0/0x3a8 returned 0 after 61547 usecs [ 9.437034] calling mousedev_init+0x0/0x83 @ 1 [ 9.466671] mice: PS/2 mouse device common for all mice [ 9.470524] initcall mousedev_init+0x0/0x83 returned 0 after 15466 usecs [ 9.470524] calling atkbd_init+0x0/0x27 @ 1 [ 9.515660] initcall atkbd_init+0x0/0x27 returned 0 after 69 usecs [ 9.519600] calling xenkbd_init+0x0/0x57 @ 1 [ 9.519600] initcall xenkbd_init+0x0/0x57 returned -19 after 0 usecs [ 9.519600] calling cmos_init+0x0/0x63 @ 1 [ 9.579513] rtc_cmos 00:03: RTC can wake from S4 [ 9.593569] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 9.611975] rtc0: alarms up to one year, y3k, 114 bytes nvram [ 9.629339] initcall cmos_init+0x0/0x63 returned 0 after 48710 usecs [ 9.633309] calling init_ladder+0x0/0xc @ 1 [ 9.633309] cpuidle: using governor ladder [ 9.633309] initcall init_ladder+0x0/0xc returned 0 after 12171 usecs [ 9.633309] calling init_menu+0x0/0xc @ 1 [ 9.633309] cpuidle: using governor menu [ 9.633309] initcall init_menu+0x0/0xc returned 0 after 11662 usecs [ 9.633309] calling ledtrig_ide_init+0x0/0x1b @ 1 [...] Regards, Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-09 18:20 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/09/2010 11:00 AM, Thomas Schwinge wrote:> Before we get to the backtrace, one further detail: this kernel *does* > boot if one of the following has happened before: the BIOS memchecker has > run, memtest86+ has run, some other kernel has run (though it doesn''t > always boot in this latter case). Thus, I wildly guess that some > uninitialized data structure (in memory) is dereferenced -- that happens > to be in a sane state after memtest86+ et al. >OK, I think I see what''s happening here...> $ for ip in ffffffff814f6d88 ffffffff81433e38 ffffffff814f6d3d ffffffff81433e60 ffffffff815a73ac ffffffff81433f98 ffffffff814f6f85 ffffffff8152b2d0 ffffffff814f95fb ffffffff814f8249 ffffffff813f3f5f ffffffff813b4119 ffffffff81433f90 ffffffff811ff14f ffffffff8100e361 ffffffff8100e343 ffffffff813b4119 ffffffff813f3f5f ffffffff8152a7b0 ffffffff814f49d0 ffffffff81001000 ffffffff814f6aca; do echo "* $ip:" && addr2line -fie debian/build/build_amd64_xen_amd64/vmlinux "$ip"; done > ~/shared/tmp/tmp > * ffffffff814f6d88: > xen_release_chunk >This is the code which goes through the gaps between the E820 table entries looking for pages which Xen has assigned the kernel, but the kernel can''t use (because they''re not covered by E820). It does this with: for(pfn = start; pfn < end; pfn++) { unsigned long mfn = pfn_to_mfn(pfn); /* Make sure pfn exists to start with */ if (mfn == INVALID_P2M_ENTRY || mfn_to_pfn(mfn) != pfn) continue; ... So in theory we''re poking at the p2m and m2p tables for random pages which may or may not be valid. So if we do a pfn_to_mfn on a pfn which is within the range of valid pfns, but not actually a valid pfn for our domain, then the resulting mfn is undefined (and may depend on random memory contents, which is why it is affected by what you''ve previously booted). We then pass that mfn back to mfn_to_pfn to see if it really does belong to us (because it will return the same pfn back). But it could be random garbage, which mfn_to_pfn uses to index an array. Normally that would be OK, because it uses: __get_user(pfn, &machine_to_phys_mapping[mfn]); to dereference the array. But at this early stage, none of the kernel''s exception handlers have been set up, so this will just fault into Xen. It would be interesting to confirm this by building your kernel with CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting instruction is actually this line. Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-Apr-09 18:52 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
> $ gdb -q debian/build/build_amd64_xen_amd64/vmlinux > Reading symbols from /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/build_amd64_xen_amd64/vmlinux...(no debugging symbols found)...done. > (gdb) x/i ffffffff814f6d88You need to prefix it with ''0x'', so: (gdb) x/i 0xffffffff814f6d88 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Schwinge
2010-Apr-10 22:13 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello! On Fri, Apr 09, 2010 at 11:20:52AM -0700, Jeremy Fitzhardinge wrote:> On 04/09/2010 11:00 AM, Thomas Schwinge wrote: > > Before we get to the backtrace, one further detail: this kernel *does* > > boot if one of the following has happened before: the BIOS memchecker has > > run, memtest86+ has run, some other kernel has run (though it doesn''t > > always boot in this latter case). Thus, I wildly guess that some > > uninitialized data structure (in memory) is dereferenced -- that happens > > to be in a sane state after memtest86+ et al. > > > > OK, I think I see what''s happening here... > > > $ for ip in ffffffff814f6d88 ffffffff81433e38 ffffffff814f6d3d ffffffff81433e60 ffffffff815a73ac ffffffff81433f98 ffffffff814f6f85 ffffffff8152b2d0 ffffffff814f95fb ffffffff814f8249 ffffffff813f3f5f ffffffff813b4119 ffffffff81433f90 ffffffff811ff14f ffffffff8100e361 ffffffff8100e343 ffffffff813b4119 ffffffff813f3f5f ffffffff8152a7b0 ffffffff814f49d0 ffffffff81001000 ffffffff814f6aca; do echo "* $ip:" && addr2line -fie debian/build/build_amd64_xen_amd64/vmlinux "$ip"; done > ~/shared/tmp/tmp > > * ffffffff814f6d88: > > xen_release_chunk > > > > This is the code which goes through the gaps between the E820 table > entries looking for pages which Xen has assigned the kernel, but the > kernel can''t use (because they''re not covered by E820). It does this with: > > for(pfn = start; pfn < end; pfn++) { > unsigned long mfn = pfn_to_mfn(pfn); > > /* Make sure pfn exists to start with */ > if (mfn == INVALID_P2M_ENTRY || mfn_to_pfn(mfn) != pfn) > continue; > ... > > > So in theory we''re poking at the p2m and m2p tables for random pages > which may or may not be valid. So if we do a pfn_to_mfn on a pfn which > is within the range of valid pfns, but not actually a valid pfn for our > domain, then the resulting mfn is undefined (and may depend on random > memory contents, which is why it is affected by what you''ve previously > booted). > > We then pass that mfn back to mfn_to_pfn to see if it really does belong > to us (because it will return the same pfn back). But it could be > random garbage, which mfn_to_pfn uses to index an array. > > Normally that would be OK, because it uses: > > __get_user(pfn, &machine_to_phys_mapping[mfn]); > > to dereference the array. But at this early stage, none of the kernel''s > exception handlers have been set up, so this will just fault into Xen. > > It would be interesting to confirm this by building your kernel with > CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting > instruction is actually this line.Bingo! $ for ip in ffffffff814f6d88 ffffffff81433e38 ffffffff814f6d3d ffffffff81433e60 ffffffff815a73ac ffffffff81433f98 ffffffff814f6f85 ffffffff8152b2d0 ffffffff814f95fb ffffffff814f8249 ffffffff813f3f5f ffffffff813b4119 ffffffff81433f90 ffffffff811ff14f ffffffff8100e361 ffffffff8100e343 ffffffff813b4119 ffffffff813f3f5f ffffffff8152a7b0 ffffffff814f49d0 ffffffff81001000 ffffffff814f6aca ffffffff82fdb000; do echo "* $ip:" && addr2line -fie debian/build/build_amd64_xen_amd64/vmlinux "$ip" && gdb -q --batch --eval-command="x/i 0x$ip" --eval-command="list *0x$ip" debian/build/build_amd64_xen_amd64/vmlinux; done * ffffffff814f6d88: mfn_to_pfn /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/include/asm/xen/page.h:77 xen_release_chunk /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/setup.c:63 0xffffffff814f6d88 <xen_release_chunk+193>: mov (%rax),%rdx 0xffffffff814f6d88 is in xen_release_chunk (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/include/asm/xen/page.h:77). 72 /* 73 * The array access can fail (e.g., device space beyond end of RAM). 74 * In such cases it doesn''t matter what we return (we return garbage), 75 * but we must handle the fault without crashing! 76 */ 77 __get_user(pfn, &machine_to_phys_mapping[mfn]); 78 79 return pfn; 80 } 81 * ffffffff81433e38: _sdata ??:0 0xffffffff81433e38: add %al,(%rax) No source file for address 0xffffffff81433e38. * ffffffff814f6d3d: pfn_to_mfn /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/include/asm/xen/page.h:50 xen_release_chunk /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/setup.c:60 0xffffffff814f6d3d <xen_release_chunk+118>: mov %rax,%rdx 0xffffffff814f6d3d is in xen_release_chunk (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/include/asm/xen/page.h:50). 45 static inline unsigned long pfn_to_mfn(unsigned long pfn) 46 { 47 if (xen_feature(XENFEAT_auto_translated_physmap)) 48 return pfn; 49 50 return get_phys_to_machine(pfn) & ~FOREIGN_FRAME_BIT; 51 } 52 53 static inline int phys_to_machine_mapping_valid(unsigned long pfn) 54 { * ffffffff81433e60: _sdata ??:0 0xffffffff81433e60: add %al,(%rax) No source file for address 0xffffffff81433e60. * ffffffff815a73ac: idt_table ??:0 0xffffffff815a73ac: add %al,(%rax) No source file for address 0xffffffff815a73ac. * ffffffff81433f98: _sdata ??:0 0xffffffff81433f98: add %al,(%rax) No source file for address 0xffffffff81433f98. * ffffffff814f6f85: xen_return_unused_memory /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/setup.c:91 xen_memory_setup /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/setup.c:173 0xffffffff814f6f85 <xen_memory_setup+366>: mov 0x8(%rbx),%rdi 0xffffffff814f6f85 is in xen_memory_setup (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/setup.c:91). 86 unsigned long released = 0; 87 int i; 88 89 for (i = 0; i < e820->nr_map; i++) { 90 released += xen_release_chunk(last_end, e820->map[i].addr); 91 last_end = e820->map[i].addr + e820->map[i].size; 92 } 93 94 released += xen_release_chunk(last_end, PFN_PHYS(xen_start_info->nr_pages)); 95 * ffffffff8152b2d0: ?? ??:0 0xffffffff8152b2d0: add %al,(%rax) No source file for address 0xffffffff8152b2d0. * ffffffff814f95fb: setup_memory_map /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/kernel/e820.c:1463 0xffffffff814f95fb <setup_memory_map+7>: mov $0xffffffff815a8c40,%rdi 0xffffffff814f95fb is in setup_memory_map (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/kernel/e820.c:1463). 1458 void __init setup_memory_map(void) 1459 { 1460 char *who; 1461 1462 who = x86_init.resources.memory_setup(); 1463 memcpy(&e820_saved, &e820, sizeof(struct e820map)); 1464 printk(KERN_INFO "BIOS-provided physical RAM map:\n"); 1465 e820_print_map(who); 1466 } * ffffffff814f8249: setup_arch ??:0 0xffffffff814f8249: cmpw $0x208,0x34e84(%rip) # 0xffffffff8152d0d6 No source file for address 0xffffffff814f8249. * ffffffff813f3f5f: kallsyms_token_index ??:0 0xffffffff813f3f5f: outsb %ds:(%rsi),(%dx) No source file for address 0xffffffff813f3f5f. * ffffffff813b4119: kallsyms_token_index ??:0 0xffffffff813b4119: add %bh,(%rsp,%rsi,1) No source file for address 0xffffffff813b4119. * ffffffff81433f90: _sdata ??:0 0xffffffff81433f90: add %al,(%rax) No source file for address 0xffffffff81433f90. * ffffffff811ff14f: extract_entropy /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/char/random.c:865 0xffffffff811ff14f <extract_entropy+106>: cmpq $0x0,0x38(%rbp) 0xffffffff811ff14f is in extract_entropy (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/drivers/char/random.c:865). 860 nbytes = account(r, nbytes, min, reserved); 861 862 while (nbytes) { 863 extract_buf(r, tmp); 864 865 if (r->last_data) { 866 spin_lock_irqsave(&r->lock, flags); 867 if (!memcmp(tmp, r->last_data, EXTRACT_SIZE)) 868 panic("Hardware RNG duplicated output!\n"); 869 memcpy(r->last_data, tmp, EXTRACT_SIZE); * ffffffff8100e361: __raw_callee_save_xen_irq_disable irq.c:0 0xffffffff8100e361: pop %r11 No source file for address 0xffffffff8100e361. * ffffffff8100e343: __raw_callee_save_xen_restore_fl irq.c:0 0xffffffff8100e343: pop %r11 No source file for address 0xffffffff8100e343. * ffffffff813b4119: kallsyms_token_index ??:0 0xffffffff813b4119: add %bh,(%rsp,%rsi,1) No source file for address 0xffffffff813b4119. * ffffffff813f3f5f: kallsyms_token_index ??:0 0xffffffff813f3f5f: outsb %ds:(%rsi),(%dx) No source file for address 0xffffffff813f3f5f. * ffffffff8152a7b0: ?? ??:0 0xffffffff8152a7b0: add %al,(%rax) No source file for address 0xffffffff8152a7b0. * ffffffff814f49d0: setup_command_line /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/init/main.c:395 start_kernel /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/init/main.c:548 0xffffffff814f49d0 <start_kernel+219>: mov $0xffff880001000000,%rdi 0xffffffff814f49d0 is in start_kernel (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/init/main.c:395). 390 * parsing is performed in place, and we should allow a component to 391 * store reference of name/value for future reference. 392 */ 393 static void __init setup_command_line(char *command_line) 394 { 395 saved_command_line = alloc_bootmem(strlen (boot_command_line)+1); 396 static_command_line = alloc_bootmem(strlen (command_line)+1); 397 strcpy (saved_command_line, boot_command_line); 398 strcpy (static_command_line, command_line); 399 } * ffffffff81001000: init_level4_pgt /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/kernel/head_64.S:272 0xffffffff81001000: movslq (%rax),%esp 0xffffffff81001000 is at /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/kernel/head_64.S:272. 267 ENTRY(stack_start) 268 .quad init_thread_union+THREAD_SIZE-8 269 .word 0 270 271 bad_address: 272 jmp bad_address 273 274 .section ".init.text","ax" 275 #ifdef CONFIG_EARLY_PRINTK 276 .globl early_idt_handlers * ffffffff814f6aca: xen_start_kernel /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/enlighten.c:1267 0xffffffff814f6aca <xen_start_kernel+1609>: add $0x30,%rsp 0xffffffff814f6aca is in xen_start_kernel (/media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/source_amd64_xen/arch/x86/xen/enlighten.c:1267). 1262 #ifdef CONFIG_X86_32 1263 i386_start_kernel(); 1264 #else 1265 x86_64_start_reservations((char *)__pa_symbol(&boot_params)); 1266 #endif 1267 } * ffffffff82fdb000: ?? ??:0 0xffffffff82fdb000: Cannot access memory at address 0xffffffff82fdb000 No source file for address 0xffffffff82fdb000. On Fri, Apr 09, 2010 at 02:52:06PM -0400, Konrad Rzeszutek Wilk wrote:> > $ gdb -q debian/build/build_amd64_xen_amd64/vmlinux > > Reading symbols from /media/data-local/thomas/tmp/linux_xen_/linux-2.6-2.6.32/debian/build/build_amd64_xen_amd64/vmlinux...(no debugging symbols found)...done. > > (gdb) x/i ffffffff814f6d88 > > You need to prefix it with ''0x'', so: > (gdb) x/i 0xffffffff814f6d88Indeed. -- On some days, I should either stay away from the keyboard, or, even better, start to think some more, as well as read what I''ve been typing... Usually, I do know how to operate GDB. ;-) Regards, Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-10 22:52 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/10/2010 03:13 PM, Thomas Schwinge wrote:>> Normally that would be OK, because it uses: >> >> __get_user(pfn, &machine_to_phys_mapping[mfn]); >> >> to dereference the array. But at this early stage, none of the kernel''s >> exception handlers have been set up, so this will just fault into Xen. >> >> It would be interesting to confirm this by building your kernel with >> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting >> instruction is actually this line. >> > Bingo! >Excellent. Now I just need to work out how to do a proper manual limit check on the mfn. (I''ve always been a bit suspicious of this code, because there''s no guarantee that a random invalid mfn *won''t* happen to return the pfn we''re looking for...)> $ for ip in ffffffff814f6d88 ffffffff81433e38 ffffffff814f6d3d ffffffff81433e60 ffffffff815a73ac ffffffff81433f98 ffffffff814f6f85 ffffffff8152b2d0 ffffffff814f95fb ffffffff814f8249 ffffffff813f3f5f ffffffff813b4119 ffffffff81433f90 ffffffff811ff14f ffffffff8100e361 ffffffff8100e343 ffffffff813b4119 ffffffff813f3f5f ffffffff8152a7b0 ffffffff814f49d0 ffffffff81001000 ffffffff814f6aca ffffffff82fdb000; do echo "* $ip:" && addr2line -fie debian/build/build_amd64_xen_amd64/vmlinux "$ip" && gdb -q --batch --eval-command="x/i 0x$ip" --eval-command="list *0x$ip" debian/build/build_amd64_xen_amd64/vmlinux; done >Oooh, nifty. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Goirand
2010-Apr-11 09:49 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Jeremy Fitzhardinge wrote:> On 04/10/2010 03:13 PM, Thomas Schwinge wrote: >>> Normally that would be OK, because it uses: >>> >>> __get_user(pfn, &machine_to_phys_mapping[mfn]); >>> >>> to dereference the array. But at this early stage, none of the kernel''s >>> exception handlers have been set up, so this will just fault into Xen. >>> >>> It would be interesting to confirm this by building your kernel with >>> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting >>> instruction is actually this line. >>> >> Bingo! >> > > Excellent.Could this be also the reason why I had very funky memory management (eg: some RAM missing between "xm list" and "xm info")? Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-12 19:34 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/11/2010 02:49 AM, Thomas Goirand wrote:>> Excellent. >> > Could this be also the reason why I had very funky memory management > (eg: some RAM missing between "xm list" and "xm info")? >I don''t think so. Before I added the "unused memory freeing" code, then you''d see memory assigned to a domain that the domain itself couldn''t use, and so it was effectively wasted. With the memory-freeing in place, the "xm list" and the domain''s internal view of memory should be basically the same. Either way, it shouldn''t have any effect on the global memory accounting shown by xm info. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Goirand
2010-Apr-13 01:20 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Jeremy Fitzhardinge wrote:> On 04/11/2010 02:49 AM, Thomas Goirand wrote: >>> Excellent. >>> >> Could this be also the reason why I had very funky memory management >> (eg: some RAM missing between "xm list" and "xm info")? >> > > I don''t think so. Before I added the "unused memory freeing" code, then > you''d see memory assigned to a domain that the domain itself couldn''t > use, and so it was effectively wasted. With the memory-freeing in > place, the "xm list" and the domain''s internal view of memory should be > basically the same. > > Either way, it shouldn''t have any effect on the global memory accounting > shown by xm info. > > JThen do you have an idea why "xm info" shows a bit more, 900 MB free / 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I''m not talking about just few bytes here, but one third of my RAM gone ... What''s going on? Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-13 06:02 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On Tue, Apr 13, 2010 at 09:20:33AM +0800, Thomas Goirand wrote:> Jeremy Fitzhardinge wrote: > > On 04/11/2010 02:49 AM, Thomas Goirand wrote: > >>> Excellent. > >>> > >> Could this be also the reason why I had very funky memory management > >> (eg: some RAM missing between "xm list" and "xm info")? > >> > > > > I don''t think so. Before I added the "unused memory freeing" code, then > > you''d see memory assigned to a domain that the domain itself couldn''t > > use, and so it was effectively wasted. With the memory-freeing in > > place, the "xm list" and the domain''s internal view of memory should be > > basically the same. > > > > Either way, it shouldn''t have any effect on the global memory accounting > > shown by xm info. > > > > J > > Then do you have an idea why "xm info" shows a bit more, 900 MB free / > 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I''m not > talking about just few bytes here, but one third of my RAM gone ... > What''s going on? >Please paste "xm list" and "xm info" -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Goirand
2010-Apr-13 09:48 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Pasi Kärkkäinen wrote:> Please paste "xm list" and "xm info" > > -- PasiI guess you mean "past AGAIN"? Because I did in this list, and nobody replied to me: http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00031.html This is just one example, sometimes, I got even more (and sometimes less) RAM that is gone in the deepness of the hypervisor. Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-13 09:52 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On Tue, Apr 13, 2010 at 05:48:16PM +0800, Thomas Goirand wrote:> Pasi Kärkkäinen wrote: > > Please paste "xm list" and "xm info" > > > > -- Pasi > > I guess you mean "past AGAIN"? Because I did in this list, and nobody > replied to me: > > http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00031.html > > This is just one example, sometimes, I got even more (and sometimes > less) RAM that is gone in the deepness of the hypervisor. >Seems weird yeah. Please pastebin full "xm dmesg" and full "xm info". -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Goirand
2010-Apr-13 10:08 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Pasi Kärkkäinen wrote: On Tue, Apr 13, 2010 at 05:48:16PM +0800, Thomas Goirand wrote: Pasi Kärkkäinen wrote: Please paste "xm list" and "xm info" -- Pasi I guess you mean "past AGAIN"? Because I did in this list, and nobody replied to me: http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00031.html This is just one example, sometimes, I got even more (and sometimes less) RAM that is gone in the deepness of the hypervisor. Seems weird yeah. Please pastebin full "xm dmesg" and full "xm info". -- Pasi Here you are: http://pastebin.com/vJbPSRjC Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-13 19:50 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/12/2010 06:20 PM, Thomas Goirand wrote:> > Then do you have an idea why "xm info" shows a bit more, 900 MB free / > 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I''m not > talking about just few bytes here, but one third of my RAM gone ... > What''s going on? >Is this immediately after boot, or have you started/shutdown some domains? Also, can you include the xen console output from "xm debug-keys m" as well? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Goirand
2010-Apr-13 22:27 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Jeremy Fitzhardinge wrote:> On 04/12/2010 06:20 PM, Thomas Goirand wrote: >> Then do you have an idea why "xm info" shows a bit more, 900 MB free / >> 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I''m not >> talking about just few bytes here, but one third of my RAM gone ... >> What''s going on? >> > > Is this immediately after boot, or have you started/shutdown some domains? > > Also, can you include the xen console output from "xm debug-keys m" as well? > > JHi Jeremy, Let me explain again. After boot-up situation (running KDE 3.5 and typing this message), xm info shows 3990 RAM (I believe the 4GB is 4096MB, unless Xen counts RAM like HDD vendors...) and 645 MB free, and "xm list" shows that dom0 is using 3286 MB. Already, things are weird because 645 free + 3286 for the dom0 makes 3931 and not 3990, and I never asked that my dom0 takes anything (at boot-up it should take all the available memory). Then I do: xm mem-set Domain-0 2048 and then I get: xm list Domain-0: 2048 xm info Free RAM: 1627 That makes a total of 3675 MB, which is less than the total of what I had at boot time without using xm mem-set. Ever more weirdness: the amount of free RAM after a xm mem-set call does vary randomly each time I boot my laptop (a one year old Lenovo T500). Note that I tried upgrading to the very latest version of Xen and pv_ops kernel from the pkg-xen team, so I tried both kernel 2.6.32-10 / hypervisor 3.4.2-3 and kernel 2.6.32-11 / hypervisor 3.4.2-4. They both had the issue. I''m using them in Lenny (I rebuilt the Debian package from source to create my own backports, which I don''t believe is an issue as the same thing has been uploaded to backports.org). "xm debug-keys m" shows nothing, when exactly should I type it (sorry, I''m not familiar with Xen debugging...). Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mike Viau
2010-Apr-13 23:16 UTC
RE: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
> Wed, 14 Apr 2010 06:27:37 +0800 <thomas@goirand.fr> wrote: > > Jeremy Fitzhardinge wrote: > > On 04/12/2010 06:20 PM, Thomas Goirand wrote: > >> Then do you have an idea why "xm info" shows a bit more, 900 MB free / > >> 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I''m not > >> talking about just few bytes here, but one third of my RAM gone ... > >> What''s going on? > >> > > > > Is this immediately after boot, or have you started/shutdown some domains? > > > > Also, can you include the xen console output from "xm debug-keys m" as well? > > > > J > > Hi Jeremy, > > Let me explain again. > > After boot-up situation (running KDE 3.5 and typing this message), xm > info shows 3990 RAM (I believe the 4GB is 4096MB, unless Xen counts RAM > like HDD vendors...) and 645 MB free, and "xm list" shows that dom0 is > using 3286 MB. Already, things are weird because 645 free + 3286 for the > dom0 makes 3931 and not 3990, and I never asked that my dom0 takes > anything (at boot-up it should take all the available memory). > > Then I do: > > xm mem-set Domain-0 2048 > > and then I get: > xm list Domain-0: 2048 > xm info Free RAM: 1627 > > That makes a total of 3675 MB, which is less than the total of what I > had at boot time without using xm mem-set. Ever more weirdness: the > amount of free RAM after a xm mem-set call does vary randomly each time > I boot my laptop (a one year old Lenovo T500). > > Note that I tried upgrading to the very latest version of Xen and pv_ops > kernel from the pkg-xen team, so I tried both kernel 2.6.32-10 / > hypervisor 3.4.2-3 and kernel 2.6.32-11 / hypervisor 3.4.2-4. They both > had the issue. I''m using them in Lenny (I rebuilt the Debian package > from source to create my own backports, which I don''t believe is an > issue as the same thing has been uploaded to backports.org). > > "xm debug-keys m" shows nothing, when exactly should I type it (sorry, > I''m not familiar with Xen debugging...).The terminal returns nothing for me as well. Then I found this: http://lists.xensource.com/archives/html/xen-changelog/2007-03/msg00137.html Perhaps you could look at the DEBUG entries more closely in your Xen log. Look for the extra injected debug-key events in the logs.> > Thomas > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_________________________________________________________________ Live connected. Get Hotmail & Messenger on your phone. http://go.microsoft.com/?linkid=9724462 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-13 23:59 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/13/2010 03:27 PM, Thomas Goirand wrote:> Jeremy Fitzhardinge wrote: > >> On 04/12/2010 06:20 PM, Thomas Goirand wrote: >> >>> Then do you have an idea why "xm info" shows a bit more, 900 MB free / >>> 3990 MB total, while "xm list" shows only a 2048 dom0 running??? I''m not >>> talking about just few bytes here, but one third of my RAM gone ... >>> What''s going on? >>> >>> >> Is this immediately after boot, or have you started/shutdown some domains? >> >> Also, can you include the xen console output from "xm debug-keys m" as well? >> >> J >> > Hi Jeremy, > > Let me explain again. > > After boot-up situation (running KDE 3.5 and typing this message), xm > info shows 3990 RAM (I believe the 4GB is 4096MB, unless Xen counts RAM > like HDD vendors...)Yes, you system has 3990MB of RAM; the hardware/BIOS is hiding, using or otherwise disabling 106MB of memory.> and 645 MB free, and "xm list" shows that dom0 is > using 3286 MB. Already, things are weird because 645 free + 3286 for the > dom0 makes 3931 and not 3990, and I never asked that my dom0 takes > anything (at boot-up it should take all the available memory). >I would assume that extra 59MB is memory Xen has allocated for its own purposes on behalf of the domain. And Xen won''t give all memory to dom0 at boot; it will always leave some memory free.> Then I do: > > xm mem-set Domain-0 2048 > > and then I get: > xm list Domain-0: 2048 > xm info Free RAM: 1627 > > That makes a total of 3675 MB, which is less than the total of what I > had at boot time without using xm mem-set.So the apparent overhead has grown from 59MB to 315MB?> Ever more weirdness: the > amount of free RAM after a xm mem-set call does vary randomly each time > I boot my laptop (a one year old Lenovo T500). >How much variation? By a few pages? 10s of MB? What happens if you just boot with dom0_mem=2048MB at boot time rather than shrinking it after boot?> Note that I tried upgrading to the very latest version of Xen and pv_ops > kernel from the pkg-xen team, so I tried both kernel 2.6.32-10 / > hypervisor 3.4.2-3 and kernel 2.6.32-11 / hypervisor 3.4.2-4. They both > had the issue. I''m using them in Lenny (I rebuilt the Debian package > from source to create my own backports, which I don''t believe is an > issue as the same thing has been uploaded to backports.org). >This should all be an internal-to-Xen issue, so I wouldn''t expect the kernel to have any effect.> "xm debug-keys m" shows nothing, when exactly should I type it (sorry, > I''m not familiar with Xen debugging...). >The result will appear on the console, so you may need to follow it with "xm dmesg" to see the output. I don''t know all that much about how Xen does its internal memory management, but aside from the ~300MB apparently lost by shrinking dom0 the amounts of memory you''re talking about are small, and well within the sort of range I''d expect for allocator overhead. But even then, looking at "free memory" numbers is notoriously unreliable, because that doesn''t necessarily represent the amount of memory that''s actually available for allocation - it could be higher, because something that''s using memory can be convinced to release it if needed. I did some similar experiments on my system and none of the numbers add up properly for me either. Which suggests to me that the "free" number in xm info is not the whole truth, and that the memory accounting is keeping multiple books... J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Goirand
2010-Apr-14 05:48 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Jeremy Fitzhardinge wrote:> Yes, you system has 3990MB of RAM; the hardware/BIOS is hiding, using or > otherwise disabling 106MB of memory.Possible, yes. Especially video could allocate some RAM anyway.>> and 645 MB free, and "xm list" shows that dom0 is >> using 3286 MB. Already, things are weird because 645 free + 3286 for the >> dom0 makes 3931 and not 3990, and I never asked that my dom0 takes >> anything (at boot-up it should take all the available memory). >> > > I would assume that extra 59MB is memory Xen has allocated for its own > purposes on behalf of the domain. And Xen won''t give all memory to dom0 > at boot; it will always leave some memory free.Quite not. This already allocated RAM that seems to be gone, isn''t always the same amount. Plus 60MB, I never ever saw Xen taking that much.>> Then I do: >> >> xm mem-set Domain-0 2048 >> >> and then I get: >> xm list Domain-0: 2048 >> xm info Free RAM: 1627 >> >> That makes a total of 3675 MB, which is less than the total of what I >> had at boot time without using xm mem-set. > > So the apparent overhead has grown from 59MB to 315MB?No. Apparently, the memory manager of the hypervisor is somehow broken. These values aren''t always the same, this is quite random and weird, even the first amount of "lost RAM" just right after booting is not always the same (10s of MB). Once, I even had up to a gig that was gone.>> Ever more weirdness: the >> amount of free RAM after a xm mem-set call does vary randomly each time >> I boot my laptop (a one year old Lenovo T500). >> > > How much variation? By a few pages? 10s of MB?100s of MB variation.> What happens if you just boot with dom0_mem=2048MB at boot time rather > than shrinking it after boot?If I do that, I can''t even boot, when X starts (KDM), my screen becomes dark and it seems that the video initialization fails to be done correctly! I''d be hard to tell if it''s a driver timing or a Xen issue.> This should all be an internal-to-Xen issue, so I wouldn''t expect the > kernel to have any effect.Agreed with the diagnostic, this is an hypervisor issue.>> "xm debug-keys m" shows nothing, when exactly should I type it (sorry, >> I''m not familiar with Xen debugging...). >> > > The result will appear on the console, so you may need to follow it with > "xm dmesg" to see the output. > > I don''t know all that much about how Xen does its internal memory > management, but aside from the ~300MB apparently lost by shrinking dom0 > the amounts of memory you''re talking about are small, and well within > the sort of range I''d expect for allocator overhead.I''ve been using Xen for YEARS, and no, this is not a normal behavior that I''m seeing here. Having 1GB gone is NOT a normal situation, this is a lot more than just few bytes for the internals of the hypervisor. Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Schwinge
2010-Apr-20 11:18 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello! On Sat, Apr 10, 2010 at 03:52:45PM -0700, Jeremy Fitzhardinge wrote:> On 04/10/2010 03:13 PM, Thomas Schwinge wrote: > >> Normally that would be OK, because it uses: > >> > >> __get_user(pfn, &machine_to_phys_mapping[mfn]); > >> > >> to dereference the array. But at this early stage, none of the kernel''s > >> exception handlers have been set up, so this will just fault into Xen. > >> > >> It would be interesting to confirm this by building your kernel with > >> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting > >> instruction is actually this line. > >> > > Bingo! > > Excellent. Now I just need to work out how to do a proper manual limit > check on the mfn. (I''ve always been a bit suspicious of this code, > because there''s no guarantee that a random invalid mfn *won''t* happen to > return the pfn we''re looking for...)Any news already about this one? Regards, Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-20 18:19 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/20/2010 04:18 AM, Thomas Schwinge wrote:> Hello! > > On Sat, Apr 10, 2010 at 03:52:45PM -0700, Jeremy Fitzhardinge wrote: > >> On 04/10/2010 03:13 PM, Thomas Schwinge wrote: >> >>>> Normally that would be OK, because it uses: >>>> >>>> __get_user(pfn, &machine_to_phys_mapping[mfn]); >>>> >>>> to dereference the array. But at this early stage, none of the kernel''s >>>> exception handlers have been set up, so this will just fault into Xen. >>>> >>>> It would be interesting to confirm this by building your kernel with >>>> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting >>>> instruction is actually this line. >>>> >>>> >>> Bingo! >>> >> Excellent. Now I just need to work out how to do a proper manual limit >> check on the mfn. (I''ve always been a bit suspicious of this code, >> because there''s no guarantee that a random invalid mfn *won''t* happen to >> return the pfn we''re looking for...) >> > Any news already about this one? > >Keir, is there a way to test the validity of an mfn before using it to index into the m2p array? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Apr-28 21:21 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 04/20/2010 04:18 AM, Thomas Schwinge wrote:> Hello! > > On Sat, Apr 10, 2010 at 03:52:45PM -0700, Jeremy Fitzhardinge wrote: > >> On 04/10/2010 03:13 PM, Thomas Schwinge wrote: >> >>>> Normally that would be OK, because it uses: >>>> >>>> __get_user(pfn, &machine_to_phys_mapping[mfn]); >>>> >>>> to dereference the array. But at this early stage, none of the kernel''s >>>> exception handlers have been set up, so this will just fault into Xen. >>>> >>>> It would be interesting to confirm this by building your kernel with >>>> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting >>>> instruction is actually this line. >>>> >>>> >>> Bingo! >>> >> Excellent. Now I just need to work out how to do a proper manual limit >> check on the mfn. (I''ve always been a bit suspicious of this code, >> because there''s no guarantee that a random invalid mfn *won''t* happen to >> return the pfn we''re looking for...) >> > Any news already about this one? >Does this help? J From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Subject: [PATCH] xen/core: don''t bother trying to free pages beyond the ones Xen gave us Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c index 8dc1635..9deb6ba 100644 --- a/arch/x86/xen/setup.c +++ b/arch/x86/xen/setup.c @@ -78,18 +78,24 @@ static unsigned long __init xen_release_chunk(phys_addr_t start_addr, return len; } -static unsigned long __init xen_return_unused_memory(const struct e820map *e820) +static unsigned long __init xen_return_unused_memory(unsigned long max_pfn, + const struct e820map *e820) { + phys_addr_t max_addr = PFN_PHYS(max_pfn); phys_addr_t last_end = 0; unsigned long released = 0; int i; - for (i = 0; i < e820->nr_map; i++) { - released += xen_release_chunk(last_end, e820->map[i].addr); + for (i = 0; i < e820->nr_map && last_end < max_addr; i++) { + phys_addr_t end = e820->map[i].addr; + end = min(max_addr, end); + + released += xen_release_chunk(last_end, end); last_end = e820->map[i].addr + e820->map[i].size; } - released += xen_release_chunk(last_end, PFN_PHYS(xen_start_info->nr_pages)); + if (last_end < max_addr) + released += xen_release_chunk(last_end, max_addr); printk(KERN_INFO "released %ld pages of unused memory\n", released); return released; @@ -129,7 +135,7 @@ char * __init xen_memory_setup(void) sanitize_e820_map(e820.map, ARRAY_SIZE(e820.map), &e820.nr_map); - xen_return_unused_memory(&e820); + xen_return_unused_memory(xen_start_info->nr_pages, &e820); return "Xen"; } _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Schwinge
2010-May-08 15:46 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello! Sorry for the delay in getting back to this. On Wed, Apr 28, 2010 at 02:21:58PM -0700, Jeremy Fitzhardinge wrote:> On 04/20/2010 04:18 AM, Thomas Schwinge wrote: > > On Sat, Apr 10, 2010 at 03:52:45PM -0700, Jeremy Fitzhardinge wrote: > >> On 04/10/2010 03:13 PM, Thomas Schwinge wrote: > >>>> Normally that would be OK, because it uses: > >>>> > >>>> __get_user(pfn, &machine_to_phys_mapping[mfn]); > >>>> > >>>> to dereference the array. But at this early stage, none of the kernel''s > >>>> exception handlers have been set up, so this will just fault into Xen. > >>>> > >>>> It would be interesting to confirm this by building your kernel with > >>>> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting > >>>> instruction is actually this line. > >>>> > >>> Bingo! > >>> > >> Excellent. Now I just need to work out how to do a proper manual limit > >> check on the mfn. (I''ve always been a bit suspicious of this code, > >> because there''s no guarantee that a random invalid mfn *won''t* happen to > >> return the pfn we''re looking for...) > > Does this help?> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > Subject: [PATCH] xen/core: don''t bother trying to free pages beyond the ones Xen gave us > > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>I put this on top of Debian linux-2.6 2.6.32-11, which is based on f64df18aae5ab07b44bdcc2334cf0044ef46320c of git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. Please tell me if I shall put it on top of another version. The patch does mitigate / hide the problem, as the 100000000 to 120000000 pages are now chopped off (which is not what you intended to do, as I understood it): (XEN) Xen version 3.4.3-rc3 (Debian 3.4.3~rc3-2) (waldi@debian.org) (gcc version 4.4.3 (Debian 4.4.3-7) ) Thu Apr 8 14:16:43 UTC 2010 (XEN) Command line: com1=38400,8n1 vga=current,keep console=com1,vga loglvl=all guest_loglvl=all console_to_ring (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009e000 (usable) (XEN) 000000000009e000 - 00000000000a0000 (reserved) (XEN) 00000000000e4000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000ddee0000 (usable) (XEN) 00000000ddee0000 - 00000000ddeef000 (ACPI data) (XEN) 00000000ddeef000 - 00000000ddf00000 (ACPI NVS) (XEN) 00000000ddf00000 - 00000000e0000000 (reserved) (XEN) 00000000fec00000 - 00000000fec10000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000fff00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000120000000 (usable) (XEN) System RAM: 4062MB (4159992kB) [...] [ 0.000000] Linux version 2.6.32-4-xen-amd64 (Debian 2.6.32-11) (maks@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Apr 29 09:32:20 CEST 2010 [ 0.000000] Command line: root=/dev/mapper/vg0-boole--root ro console=hvc0 earlyprintk=xen debug [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] xen_release_chunk: looking at area pfn e0000-f2804: 75780 pages freed [ 0.000000] released 75780 pages of unused memory [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000009e000 (usable) [ 0.000000] Xen: 000000000009e000 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 00000000ddee0000 (usable) [ 0.000000] Xen: 00000000ddee0000 - 00000000ddeef000 (ACPI data) [ 0.000000] Xen: 00000000ddeef000 - 00000000ddf00000 (ACPI NVS) [ 0.000000] Xen: 00000000ddf00000 - 00000000e0000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fec10000 (reserved) [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] Xen: 00000000fff00000 - 0000000100000000 (reserved) [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] DMI present. [ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it. [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] last_pfn = 0xddee0 max_arch_pfn = 0x400000000 [...] Regards, Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-May-08 23:01 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
On 05/08/2010 08:46 AM, Thomas Schwinge wrote:>> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> >> Subject: [PATCH] xen/core: don''t bother trying to free pages beyond the ones Xen gave us >> >> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> >> > I put this on top of Debian linux-2.6 2.6.32-11, which is based on > f64df18aae5ab07b44bdcc2334cf0044ef46320c of > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. Please > tell me if I shall put it on top of another version. > > The patch does mitigate / hide the problem, as the 100000000 to 120000000 > pages are now chopped off (which is not what you intended to do, as I > understood it): >No, it looks like its working as expected, though its perhaps not ideal if you want to give dom0 all host memory. Xen is giving dom0 ~4G of pages, from 0-4G in pseudo-physical space. Unfortunately that overlaps with the PCI window which is somewhere in the 3-4G range. While in theory they''re in distinct address spaces (pseudo-phys vs machine phys), it is too hard to deal with that (it is not a concept that Linux really understands). The hardware avoids the PCI hole by remapping the memory to above 4G, but that''s not visible to dom0. The end result is that some memory Xen gave dom0 in the PCI hole can''t be used, but rather than wasting it we just free it back to Xen. It will get used as soon as you start up a domain (or, in principle, you could balloon it back into dom0, but we don''t currently support that). J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thomas Schwinge
2010-May-10 09:48 UTC
Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn''t boot with > 4 GiB; resets immediatelly, no log messages
Hello! On Sat, May 08, 2010 at 04:01:07PM -0700, Jeremy Fitzhardinge wrote:> On 05/08/2010 08:46 AM, Thomas Schwinge wrote: > >> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> > >> Subject: [PATCH] xen/core: don''t bother trying to free pages beyond the ones Xen gave us > >> > >> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>> it looks like its working as expected, [...]Ah, I understand; thanks for the explanation. $ sudo xm info [...] total_memory : 4062 free_memory : 667 [...] As expected.> though its perhaps not ideal > if you want to give dom0 all host memory.That is not a problem for me in this case. Thanks for taking care about fixing this issue! Regards, Thomas _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel