WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] RE: Xen-users Digest, Vol 18, Issue 13

To: "'xen-users@xxxxxxxxxxxxxxxxxxx'" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] RE: Xen-users Digest, Vol 18, Issue 13
From: Max E Baro <MEB@xxxxxxxxxxxxxxxxx>
Date: Wed, 9 Aug 2006 16:18:45 -0400
Delivery-date: Wed, 09 Aug 2006 13:19:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I had to recompile the module for the QLA controller specifying the xen kernel version I had and plugging it into my initrd image to get the module to load.

...max

-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of
xen-users-request@xxxxxxxxxxxxxxxxxxx
Sent: Thursday, August 03, 2006 7:55 AM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Xen-users Digest, Vol 18, Issue 13


Send Xen-users mailing list submissions to
        xen-users@xxxxxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users
or, via email, send a message with subject or body 'help' to
        xen-users-request@xxxxxxxxxxxxxxxxxxx

You can reach the person managing the list at
        xen-users-owner@xxxxxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."


Today's Topics:

   1. qla2xxx Memory Alllocation Failed -rlc on Xen + SLES10
      (Gladys Hoffmann)


----------------------------------------------------------------------

Message: 1
Date: Thu, 03 Aug 2006 11:01:36 +0200
From: Gladys Hoffmann <ghoffmann@xxxxxxxxxxxxx>
Subject: [Xen-users] qla2xxx Memory Alllocation Failed -rlc on Xen +
        SLES10
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <44D1BB70.9080009@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed

Hi,

are there any new conclusions for this subjet?
I've got the same problem while booting Dom-0 with SLES 10 and the
qla2310 - HBAs.
Here are some more informations.

Regards
Gladys

- SLES 10 with XEN out of the box but with a new initrd to load the
gdth-modul first and the qla2xxx later
- output from xm info
release                : 2.6.16.21-0.8-xenpae
version                : #1 SMP Mon Jul 3 18:25:39 UTC 2006
machine                : i686
nr_cpus                : 4
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 1
threads_per_core       : 2
cpu_mhz                : 3000
hw_caps                : bfebfbff:20100000:00000000:00000180:0000641d
total_memory           : 8191
free_memory            : 143
max_free_memory        : 7905
xen_major              : 3
xen_minor              : 0
xen_extra              : .2_09749-0.4
xen_caps               : xen-3.0-x86_32p
platform_params        : virt_start=0xf5800000
xen_changeset          : 09749
cc_compiler            : gcc version 4.1.0 (SUSE Linux)
cc_compile_by          : abuild
cc_compile_domain      : suse.de
cc_compile_date        : Mon Jul  3 19:19:21 UTC 2006

output from xm dmesg

 \ \/ /___ _ __
  \  // _ \ '_ \
  /  \  __/ | | |
 /_/\_\___|_| |_|

  _____  ___   ____      ___   ___ _____ _  _   ___      ___  _  _
 |___ / / _ \ |___ \    / _ \ / _ \___  | || | / _ \    / _ \| || |
   |_ \| | | |  __) |  | | | | (_) | / /| || || (_) |__| | | | || |_
  ___) | |_| | / __/   | |_| |\__, |/ / |__   _\__, |__| |_| |__   _|
 |____(_)___(_)_____|___\___/   /_//_/     |_|   /_/    \___(_) |_|
                   |_____|
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0.2_09749-0.4 (abuild@xxxxxxx) (gcc version 4.1.0 (SUSE
Linux)) Mon Jul  3 19:19:21 UTC 2006
 Latest ChangeSet: 09749

(XEN) Command line: /xen-pae.gz
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009a000 (usable)
(XEN)  000000000009a000 - 00000000000a0000 (reserved)
(XEN)  00000000000ca000 - 00000000000d0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cff70000 (usable)
(XEN)  00000000cff70000 - 00000000cff78000 (ACPI data)
(XEN)  00000000cff78000 - 00000000cff80000 (ACPI NVS)
(XEN)  00000000cff80000 - 00000000d0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ff800000 - 00000000ffc00000 (reserved)
(XEN)  00000000fffffc00 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000230000000 (usable)
(XEN) System RAM: 8191MB (8387624kB)
(XEN) Xen heap: 10MB (10272kB)
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) PAE enabled, limit: 16 GB
(XEN) found SMP MP-table at 000f5b20
(XEN) DMI present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 PTLTD                                 ) @ 0x000f5b80
(XEN) ACPI: RSDT (v001 PTLTD    RSDT   0x06040000  LTP 0x00000000) @
0xcff73c28
(XEN) ACPI: FADT (v001 INTEL  LINDHRST 0x06040000 PTL  0x00000003) @
0xcff77e20
(XEN) ACPI: MADT (v001 PTLTD     APIC   0x06040000  LTP 0x00000000) @
0xcff77e94
(XEN) ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06040000  LTP 0x00000001) @
0xcff77f48
(XEN) ACPI: SPCR (v001 PTLTD  $UCRTBL$ 0x06040000 PTL  0x00000001) @
0xcff77f70
(XEN) ACPI: MCFG (v001 PTLTD     MCFG   0x06040000  LTP 0x00000000) @
0xcff77fc0
(XEN) ACPI: SSDT (v001  PmRef    CpuPm 0x00003000 INTL 0x20030224) @
0xcff73c64
(XEN) ACPI: DSDT (v001  Intel LINDHRST 0x06040000 MSFT 0x0100000e) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x03] address[0xfec81000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec81000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x04] address[0xfec81400] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 4, version 32, address 0xfec81400, GSI 48-71
(XEN) ACPI: IOAPIC (id[0x05] address[0xfec82000] gsi_base[72])
(XEN) IOAPIC[3]: apic_id 5, version 32, address 0xfec82000, GSI 72-95
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec82400] gsi_base[96])
(XEN) IOAPIC[4]: apic_id 8, version 32, address 0xfec82400, GSI 96-119
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 5 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 3000.255 MHz processor.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU0: Thermal monitoring enabled
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 1/6 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU1: Thermal monitoring enabled
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 2/1 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#2.
(XEN) CPU2: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU2: Thermal monitoring enabled
(XEN) CPU2: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#3.
(XEN) CPU3: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU3: Thermal monitoring enabled
(XEN) CPU3: Intel(R) Xeon(TM) CPU 3.00GHz stepping 01
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000006000000->0000000008000000 (2032975 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c040bed4
(XEN)  Init. ramdisk: c040c000->c0ab0e00
(XEN)  Phys-Mach map: c0ab1000->c127a53c
(XEN)  Start info:    c127b000->c127c000
(XEN)  Page tables:   c127c000->c128b000
(XEN)  Boot stack:    c128b000->c128c000
(XEN)  TOTAL:         c0000000->c1400000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Initrd len 0x6a4e00, start at 0xc040c000
(XEN) Scrubbing Free RAM:
..........................................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) microcode: CPU0 already at revision 0x12 (current=0x12)
(XEN) microcode: CPU1 already at revision 0x12 (current=0x12)
(XEN) microcode: CPU2 already at revision 0x12 (current=0x12)
(XEN) microcode: CPU3 already at revision 0x12 (current=0x12)
(XEN) microcode: No new microcode data for CPU2
(XEN) microcode: No new microcode data for CPU1
(XEN) microcode: No new microcode data for CPU3
(XEN) microcode: No new microcode data for CPU0




> >On 7/20/06, john little <jslittl@xxxxxxxxxxxxx> wrote:
> >Hi all,
>
> >When booting into SLES 10 with the XEN kernel that ships with it (XEN
> 3.0.2) I
> >get the following error message: qla2xxx 0000:02:01.0: Memory Allocation
> >failed - rlc
>
> >The card comes up ok when booting into the stock kernel.
>
> Maybe you tell what kind of card you are trying run, and if you try to
> run it in domU or dom0, then it's a bit easier to help you. Most
> people here have not much time for guessing your environment.
>
> You can try to build and install xen from stable/testing/unstable
> sources (in that order) and see if your hardware runs better then.
>
> Henning
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users





------------------------------

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


End of Xen-users Digest, Vol 18, Issue 13
*****************************************

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] RE: Xen-users Digest, Vol 18, Issue 13, Max E Baro <=