FATAL PAGE FAULT - xen-3.0.5-rc2 and xen-3.0.5-rc3

FATAL PAGE FAULT - xen-3.0.5-rc2 and xen-3.0.5-rc3

[Teck Choon Giam]

Hi,

I have the following errors:

Panic on CPU0:
FATAL PAGE FAULT
[error_code=0002]
Faulting linear address: fbfb1100

More details in snapshots as below as I don't have serial console
cables thus unable to get full details of the errors which I will try
to get one and send the full error if needed:

http://choon.net/xenerrors/Image000.jpg
http://choon.net/xenerrors/Image001.jpg
http://choon.net/xenerrors/Image002.jpg

I am able to use xen-3.0-unstable from hg to boot with the same
configurations from date 11 Feb 2007 build but unable to get current
xen-3.0-unstable from hg to boot now with the same error as 3.0.5-rc2
and 3.0.5-rc3.

Thanks.

Kindest regards,
Choon

Re: FATAL PAGE FAULT - xen-3.0.5-rc2 and xen-3.0.5-rc3

[Keir Fraser]

On 26/4/07 10:18, "Teck Choon Giam" <giamteckchoon@gmail.com> wrote:

> I have the following errors:
> 
> Panic on CPU0:
> FATAL PAGE FAULT
> [error_code=0002]
> Faulting linear address: fbfb1100
> 
> More details in snapshots as below as I don't have serial console
> cables thus unable to get full details of the errors which I will try
> to get one and send the full error if needed:

It's bizarre that only you have seen this crash. It should be easy to track
down though. If you're happy to modify C code, can you try adding:
 printk("***TICKER_INIT %d %d\n", cpu, spc->ticker.cpu);
To csched_start_tickers() in common/sched_credit.c, immediately after the
line 'spc = ...'.

Alternatively I can send you a patch. The extra message should come out
twice immediately before the crash message and it would be interesting to
know what the messages say.

Also, the xen-syms file that matches the crash-message JPEGs you linked to
would be interesting. Perhaps you could zip that up and send it to me
privately if you still have it.

 -- Keir

Re: FATAL PAGE FAULT - xen-3.0.5-rc2 and xen-3.0.5-rc3

[Teck Choon Giam]

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

On 4/26/07, Keir Fraser <keir@xensource.com> wrote:
> On 26/4/07 10:18, "Teck Choon Giam" <giamteckchoon@gmail.com> wrote:
>
> > I have the following errors:
> >
> > Panic on CPU0:
> > FATAL PAGE FAULT
> > [error_code=0002]
> > Faulting linear address: fbfb1100
> >
> > More details in snapshots as below as I don't have serial console
> > cables thus unable to get full details of the errors which I will try
> > to get one and send the full error if needed:
>
> It's bizarre that only you have seen this crash. It should be easy to track
> down though. If you're happy to modify C code, can you try adding:
>  printk("***TICKER_INIT %d %d\n", cpu, spc->ticker.cpu);
> To csched_start_tickers() in common/sched_credit.c, immediately after the
> line 'spc = ...'.

>From your suggestion make me think it is related to sched=sedf option.
 So with that option I has problem to boot xen but without sched=sedf
option it boot nicely... ...

>
> Alternatively I can send you a patch. The extra message should come out
> twice immediately before the crash message and it would be interesting to
> know what the messages say.

You don't need to send me the patch as I have followed your
instruction to add that line :)

Please see attached txt file for boot messages with and without sched=sedf.

>
> Also, the xen-syms file that matches the crash-message JPEGs you linked to
> would be interesting. Perhaps you could zip that up and send it to me
> privately if you still have it.

Don't need the JPEGs I guess since the crash message can be found in
xen-3.0.5-rc3-with-sched_eq_sedf-crash.txt file attached with the
difference of your suggested below line of course :P

printk("***TICKER_INIT %d %d\n", cpu, spc->ticker.cpu);

>
>  -- Keir

Thanks Keir =)

Kindest regards,
Choon
P.S. Sorry, if anyone won't like to see those files in attachment then
I will take note and won't send in any attachments.  Apology.
>

[-- Attachment #2: xen-3.0.5-rc3-with-sched_eq_sedf-crash.txt --]
[-- Type: text/plain, Size: 4606 bytes --]

Please stand by while rebooting the system...
  Booting 'CentOS (xen 3.0.5-rc3 / 2.6.18-xen0)'

root (hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel /xen-3.0.5-rc3_2.6.18.gz dom0_mem=256M sched=sedf pci=routeirq com1=9600
,8n1
   [Multiboot-elf, <0x100000:0xa1480:0x51b80>, shtab=0x1f3078, entry=0x100000]
module /vmlinuz-2.6.18-xen0 root=/dev/md1 ro console=tty0 #pci=routeirq
   [Multiboot-module @ 0x1f4000, 0x356a94 bytes]
module /initrd-2.6.18-xen0.img
   [Multiboot-module @ 0x54b000, 0x361600 bytes]

 __  __            _____  ___   ____              _____
 \ \/ /___ _ __   |___ / / _ \ | ___|    _ __ ___|___ /
  \  // _ \ '_ \    |_ \| | | ||___ \ __| '__/ __| |_ \
  /  \  __/ | | |  ___) | |_| | ___) |__| | | (__ ___) |
 /_/\_\___|_| |_| |____(_)___(_)____/   |_|  \___|____/

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0.5-rc3 (root@choon.net) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) Thu Apr 26 21:44:15 SGT 2007
 Latest ChangeSet: unavailable

(XEN) Command line: /xen-3.0.5-rc3_2.6.18.gz dom0_mem=256M sched=sedf pci=routeirq com1=9600,8n1
(XEN)  0000000000000000 - 0000000000098000 (usable)
(XEN)  0000000000098000 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 00000000000d0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000003ff70000 (usable)
(XEN)  000000003ff70000 - 000000003ff7b000 (ACPI data)
(XEN)  000000003ff7b000 - 000000003ff80000 (ACPI NVS)
(XEN)  000000003ff80000 - 0000000040000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff800000 - 00000000ffc00000 (reserved)
(XEN)  00000000fffffc00 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1047584kB)
(XEN) Xen heap: 10MB (10256kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #0 15:4 APIC version 20
(XEN) Processor #1 15:4 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec10000, GSI 24-47
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) Detected 3000.210 MHz processor.
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
(XEN) Mapping cpu 0 to node 255
(XEN) Booting processor 1/1 eip 90000
(XEN) Mapping cpu 1 to node 255
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) ----[ Xen-3.0.5-rc3  x86_32p  debug=n  Not tainted ]----
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff1167dc>] set_timer+0x3c/0x130
(XEN) EFLAGS: 00010087   CONTEXT: hypervisor
(XEN) eax: fbfb1100   ebx: ffbfce0c   ecx: ff1a1100   edx: ffbfce10
(XEN) esi: ffbfce0c   edi: ff1a1100   ebp: 00000286   esp: ff1c7ec0
(XEN) cr0: 8005003b   cr4: 000006f0   cr3: 00102000   cr2: fbfb1100
(XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff1c7ec0:
(XEN)    00000000 00000000 023cb763 00000000 02d54de3 00000000 00000000 ffbfce0c
(XEN)    00000000 00000020 ff1a1080 ff18f1db ffbfce0c 02d54de3 00000000 ff1a0130
(XEN)    00000000 00000001 00000000 ff195ee5 00000000 f6802748 00000021 00000000
(XEN)    00000000 00000000 006b8600 00000000 00021a00 00c00000 012b8600 00000000
(XEN)    00000000 ff021a00 0003ff08 00000104 00000104 00000a04 012b8600 00000000
(XEN)    3ff70000 00000000 3ff70000 00000000 0000000d 0000000d 00000000 00000008
(XEN)    0000006e 00000001 00000003 000002f8 0000000d 00000000 00000000 ff02cc80
(XEN)    00053b67 001f1aa0 00067ebc ff10018a ff02cc80 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 ffbf7080
(XEN) Xen call trace:
(XEN)    [<ff1167dc>] set_timer+0x3c/0x130
(XEN)    [<ff18f1db>] csched_start_tickers+0x5b/0x90
(XEN)    [<ff195ee5>] __start_xen+0x9a5/0xed0
(XEN)    [<ff10018a>] no_execute_disable+0x53/0x55
(XEN)
(XEN) Pagetable walk from fbfb1100:
(XEN)  L3[0x003] = 00000000001cb001 55555555
(XEN)  L2[0x1df] = 0000000000000000 ffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0002]
(XEN) Faulting linear address: fbfb1100
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

[-- Attachment #3: xen-3.0.5-rc3-without-sched_eq_sedf-boot.txt --]
[-- Type: text/plain, Size: 18027 bytes --]

  Booting 'CentOS (xen 3.0.5-rc3 / 2.6.18-xen0)'

root (hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel /xen-3.0.5-rc3_2.6.18.gz dom0_mem=256M pci=routeirq com1=9600,8n1
   [Multiboot-elf, <0x100000:0xa1480:0x51b80>, shtab=0x1f3078, entry=0x100000]
module /vmlinuz-2.6.18-xen0 root=/dev/md1 ro console=tty0 #pci=routeirq
   [Multiboot-module @ 0x1f4000, 0x356a94 bytes]
module /initrd-2.6.18-xen0.img
   [Multiboot-module @ 0x54b000, 0x361600 bytes]

 __  __            _____  ___   ____              _____
 \ \/ /___ _ __   |___ / / _ \ | ___|    _ __ ___|___ /
  \  // _ \ '_ \    |_ \| | | ||___ \ __| '__/ __| |_ \
  /  \  __/ | | |  ___) | |_| | ___) |__| | | (__ ___) |
 /_/\_\___|_| |_| |____(_)___(_)____/   |_|  \___|____/

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0.5-rc3 (root@choon.net) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) Thu Apr 26 21:44:15 SGT 2007
 Latest ChangeSet: unavailable

(XEN) Command line: /xen-3.0.5-rc3_2.6.18.gz dom0_mem=256M pci=routeirq com1=9600,8n1
(XEN)  0000000000000000 - 0000000000098000 (usable)
(XEN)  0000000000098000 - 00000000000a0000 (reserved)
(XEN)  00000000000ce000 - 00000000000d0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000003ff70000 (usable)
(XEN)  000000003ff70000 - 000000003ff7b000 (ACPI data)
(XEN)  000000003ff7b000 - 000000003ff80000 (ACPI NVS)
(XEN)  000000003ff80000 - 0000000040000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff800000 - 00000000ffc00000 (reserved)
(XEN)  00000000fffffc00 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1047584kB)
(XEN) Xen heap: 10MB (10256kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #0 15:4 APIC version 20
(XEN) Processor #1 15:4 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec10000, GSI 24-47
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) ***TICKER_INIT 0 0
(XEN) Detected 3000.218 MHz processor.
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
(XEN) Mapping cpu 0 to node 255
(XEN) ***TICKER_INIT 1 0
(XEN) Booting processor 1/1 eip 90000
(XEN) Mapping cpu 1 to node 255
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc04d7bfc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003e000000->000000003f000000 (61440 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c04d7bfc
(XEN)  Init. ramdisk: c04d8000->c0839600
(XEN)  Phys-Mach map: c083a000->c087a000
(XEN)  Start info:    c087a000->c087a46c
(XEN)  Page tables:   c087b000->c0886000
(XEN)  Boot stack:    c0886000->c0887000
(XEN)  TOTAL:         c0000000->c0c00000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x361600, start at 0xc04d8000
(XEN) Scrubbing Free RAM: .......done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen).
Linux version 2.6.18-xen0 (root@xen09.choon.net) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #2 SMP Thu Apr 26 21:48:05 SGT 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
NX (Execute Disable) protection: active
found SMP MP-table at 000f6700
DMI present.
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x03] address[0xfec10000] gsi_base[24])
IOAPIC[1]: apic_id 3, version 32, address 0xfec10000, GSI 24-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Enabling APIC mode:  Flat.  Using 2 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
Detected 3000.389 MHz processor.
Built 1 zonelists.  Total pages: 67584
Kernel command line: root=/dev/md1 ro console=tty0 #pci=routeirq
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Xen reported: 3000.218 MHz processor.
Console: colour VGA+ 80x50
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB enabled:
 Aperture:     2 megabytes
 Kernel range: c088a000 - c0a8a000
 Address size: 24 bits
vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000
Memory: 248892k/270336k available (2319k kernel code, 12952k reserved, 829k data, 204k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 5997.58 BogoMIPS (lpj=11995171)
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 12k freed
ACPI: Core revision 20060707
ENABLING IO-APIC IRQs
Brought up 2 CPUs
Initializing CPU#1
migration_cost=3
checking if image is initramfs... it is
Freeing initrd memory: 3461k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 6 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *10 11 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 6 7 *10 11 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:02.0
  IO window: disabled.
  MEM window: dd100000-dd1fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:03.0
  IO window: disabled.
  MEM window: dd200000-dd2fffff
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.0
  IO window: disabled.
  MEM window: dd300000-dd3fffff
  PREFETCH window: 50000000-500fffff
PCI: Bridge: 0000:00:1e.0
  IO window: 2000-2fff
  MEM window: dd400000-deffffff
  PREFETCH window: 50100000-501fffff
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16
ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 16
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 6, 327680 bytes)
TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Simple Boot Flag at 0x36 set to 0x1
audit: initializing netlink socket (disabled)
audit(1177731029.176:1): initialized
audit: cannot initialize inotify handle
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Processor [CPU1] (supports 8 throttling states)
ACPI: Getting cpuindex for acpiid 0x2
ACPI: Getting cpuindex for acpiid 0x3
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.101 (c) Dave Jones
[drm] Initialized drm 1.0.1 20051102
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 17
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1460-0x1467, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x1468-0x146f, BIOS settings: hdc:pio, hdd:DMA
hdd: CD-224E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdd: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
/usr/src/xen-3.0.5-rc3-src/linux-2.6.18-xen/drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Freeing unused kernel memory: 204k freed
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 16, io base 0x00001400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 18, io base 0x00001420
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 19
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: irq 19, io mem 0xdd000400
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
md: raid1 personality registered for level 1
SCSI subsystem initialized
sata_mv 0000:03:07.0: version 0.7
ACPI: PCI Interrupt 0000:03:07.0[A] -> GSI 26 (level, low) -> IRQ 20
sata_mv 0000:03:07.0: 32 slots 4 ports SCSI mode IRQ via INTx
ata1: SATA max UDMA/133 cmd 0x0 ctl 0xD11A2120 bmdma 0x0 irq 20
ata2: SATA max UDMA/133 cmd 0x0 ctl 0xD11A4120 bmdma 0x0 irq 20
ata3: SATA max UDMA/133 cmd 0x0 ctl 0xD11A6120 bmdma 0x0 irq 20
ata4: SATA max UDMA/133 cmd 0x0 ctl 0xD11A8120 bmdma 0x0 irq 20
scsi0 : sata_mv
ata1.00: ATA-6, max UDMA/100, 625142448 sectors: LBA48
ata1.00: ata1: dev 0 multi count 0
ata1.00: configured for UDMA/100
scsi1 : sata_mv
ata2.00: ATA-6, max UDMA/100, 625142448 sectors: LBA48
ata2.00: ata2: dev 0 multi count 0
ata2.00: configured for UDMA/100
scsi2 : sata_mv
ata3.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi3 : sata_mv
ata4.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
  Vendor: ATA       Model: WDC WD3200JD-00K  Rev: 08.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: Attached scsi disk sda
  Vendor: ATA       Model: WDC WD3200JD-00K  Rev: 08.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB)
sdb: Write Protect is off
SCSI device sdb: drive cache: write back
SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB)
sdb: Write Protect is off
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 >
sd 1:0:0:0: Attached scsi disk sdb
  Vendor: ATA       Model: ST3160811AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
sdc: Write Protect is off
SCSI device sdc: drive cache: write back
SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
sdc: Write Protect is off
SCSI device sdc: drive cache: write back
 sdc:
sd 2:0:0:0: Attached scsi disk sdc
  Vendor: ATA       Model: ST3160811AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdd: 312581808 512-byte hdwr sectors (160042 MB)
sdd: Write Protect is off
SCSI device sdd: drive cache: write back
SCSI device sdd: 312581808 512-byte hdwr sectors (160042 MB)
sdd: Write Protect is off
SCSI device sdd: drive cache: write back
 sdd:
sd 3:0:0:0: Attached scsi disk sdd
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb8 ...
md:  adding sdb8 ...
md: sdb6 has different UUID to sdb8
md: sdb5 has different UUID to sdb8
md: sdb3 has different UUID to sdb8
md: sdb2 has different UUID to sdb8
md: sdb1 has different UUID to sdb8
md:  adding sda8 ...
md: sda6 has different UUID to sdb8
md: sda5 has different UUID to sdb8
md: sda3 has different UUID to sdb8
md: sda2 has different UUID to sdb8
md: sda1 has different UUID to sdb8
md: created md5
md: bind<sda8>
md: bind<sdb8>
md: running: <sdb8><sda8>
raid1: raid set md5 active with 2 out of 2 mirrors
md: considering sdb6 ...
md:  adding sdb6 ...
md: sdb5 has different UUID to sdb6
md: sdb3 has different UUID to sdb6
md: sdb2 has different UUID to sdb6
md: sdb1 has different UUID to sdb6
md:  adding sda6 ...
md: sda5 has different UUID to sdb6
md: sda3 has different UUID to sdb6
md: sda2 has different UUID to sdb6
md: sda1 has different UUID to sdb6
md: created md4
md: bind<sda6>
md: bind<sdb6>
md: running: <sdb6><sda6>
raid1: raid set md4 active with 2 out of 2 mirrors
md: considering sdb5 ...
md:  adding sdb5 ...
md: sdb3 has different UUID to sdb5
md: sdb2 has different UUID to sdb5
md: sdb1 has different UUID to sdb5
md:  adding sda5 ...
md: sda3 has different UUID to sdb5
md: sda2 has different UUID to sdb5
md: sda1 has different UUID to sdb5
md: created md2
md: bind<sda5>
md: bind<sdb5>
md: running: <sdb5><sda5>
raid1: raid set md2 active with 2 out of 2 mirrors
md: considering sdb3 ...
md:  adding sdb3 ...
md: sdb2 has different UUID to sdb3
md: sdb1 has different UUID to sdb3
md:  adding sda3 ...
md: sda2 has different UUID to sdb3
md: sda1 has different UUID to sdb3
md: created md1
md: bind<sda3>
md: bind<sdb3>
md: running: <sdb3><sda3>
raid1: raid set md1 active with 2 out of 2 mirrors
md: considering sdb2 ...
md:  adding sdb2 ...
md: sdb1 has different UUID to sdb2
md:  adding sda2 ...
md: sda1 has different UUID to sdb2
md: created md3
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
raid1: raid set md3 active with 2 out of 2 mirrors
md: considering sdb1 ...
md:  adding sdb1 ...
md:  adding sda1 ...
md: created md0
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.

  ***************************************************************
  ***************************************************************
  ** WARNING: Currently emulating unsupported memory accesses  **
  **          in /lib/tls glibc libraries. The emulation is    **
  **          slow. To ensure full performance you should      **
  **          install a 'xen-friendly' (nosegneg) version of   **
  **          the library, or disable tls support by executing **
  **          the following as root:                           **
  **          mv /lib/tls /lib/tls.disabled                    **
  ** Offending process: modprobe (pid=382)                     **
  ***************************************************************
  ***************************************************************

Continuing...




xen09.choon.net login:

[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

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

Re: FATAL PAGE FAULT - xen-3.0.5-rc2 and xen-3.0.5-rc3

[Keir Fraser]

On 27/4/07 21:00, "Teck Choon Giam" <giamteckchoon@gmail.com> wrote:

>> It's bizarre that only you have seen this crash. It should be easy to track
>> down though. If you're happy to modify C code, can you try adding:
>>  printk("***TICKER_INIT %d %d\n", cpu, spc->ticker.cpu);
>> To csched_start_tickers() in common/sched_credit.c, immediately after the
>> line 'spc = ...'.
> 
>> From your suggestion make me think it is related to sched=sedf option.
>  So with that option I has problem to boot xen but without sched=sedf
> option it boot nicely... ...

Oh, I didn't realise you were using sched=sedf. I can test this for myself
and fix before 3.0.5, so sched=sedf continues to work.

 -- Keir

Re: FATAL PAGE FAULT - xen-3.0.5-rc2 and xen-3.0.5-rc3

[Teck Choon Giam]

On 4/28/07, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:

> Oh, I didn't realise you were using sched=sedf. I can test this for myself
> and fix before 3.0.5, so sched=sedf continues to work.

TIA =)

Kindest regards,
Choon