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-devel

Re: [Filtered!] [Xen-devel] Networking problems with xen3

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Filtered!] [Xen-devel] Networking problems with xen3
From: Jody Belka <lists-xen@xxxxxxxx>
Date: Sun, 6 Nov 2005 23:04:11 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Sun, 06 Nov 2005 22:04:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D32E7AA@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D32E7AA@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040523i
On Sun, Nov 06, 2005 at 09:51:22PM -0000, Ian Pratt wrote:
>  > The bios on this board doesn't give any direct control over 
> > interrupt lines. However, by playing about with some of the 
> > configuration options, I was able to shift it over to irq5, 
> > and then irq10. Both failed in exactly the same manner.
> 
> TX watchdog issues are very likely down to some kind of interrupt
> problem.
> 
> I don't think I've ever booted Xen on a machine that doesn't have an
> iopaic, but we do have PIC support to enable Xen to run on vmware/qemu,
> but I doubt its been tested much on real machines.
> 
> Has anyone else had success with via rhine ethernet chips? It's possible
> it's a driver issue.

I'll just note that everything also ran fine on a xen-2/linux-2.6.11.7 combo.
dmesg logs from xen and linux for that attached.


J
-- 
Jody Belka
knew (at) pimb (dot) org
 __  __            ____    ___  
 \ \/ /___ _ __   |___ \  / _ \ 
  \  // _ \ '_ \    __) || | | |
  /  \  __/ | | |  / __/ | |_| |
 /_/\_\___|_| |_| |_____(_)___/ 
                                
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 2.0 (jmb@xxxxxxxxxxxxx) (gcc version 3.3.5 (Debian 
1:3.3.5-8ubuntu2)) Sat Apr  9 00:04:15 CEST 2005
 Latest ChangeSet: information unavailable

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000003fff0000 (usable)
(XEN)  000000003fff0000 - 000000003fff8000 (ACPI data)
(XEN)  000000003fff8000 - 0000000040000000 (ACPI NVS)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000fff80000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1048124kB)
(XEN) Xen heap: 10MB (10764kB)
(XEN) CPU0: Before vendor init, caps: 0383fbff c1cbfbff 00000000, vendor = 2
(XEN) CPU caps: 0383fbff c1cbfbff 00000000 00000000
(XEN) ACPI: RSDP (v000 AMI                                       ) @ 0x000fa910
(XEN) ACPI: RSDT (v001 AMIINT VIA_K7   0x00000010 MSFT 0x00000097) @ 0x3fff0000
(XEN) ACPI: FADT (v001 AMIINT VIA_K7   0x00000011 MSFT 0x00000097) @ 0x3fff0030
(XEN) ACPI: MADT (v001 AMIINT VIA_K7   0x00000009 MSFT 0x00000097) @ 0x3fff00c0
(XEN) ACPI: DSDT (v001    VIA    K7VT4 0x00001000 MSFT 0x0100000d) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium(tm) Pro APIC version 16
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 1499.556 MHz processor.
(XEN) Found and enabled local APIC!
(XEN) CPU0: Before vendor init, caps: 0383fbff c1cbfbff 00000000, vendor = 2
(XEN) CPU caps: 0383fbff c1cbfbff 00000000 00000000
(XEN) CPU0 booted
(XEN) SMP motherboard not detected.
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000080
(XEN) ESR value after enabling vector: 00000000
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 1499.5855 MHz.
(XEN) ..... Bus speed is 333.2411 MHz.
(XEN) ..... bus_scale = 0x00015555
(XEN) Time init:
(XEN) .... System Time: 12656793ns
(XEN) .... cpu_freq:    00000000:596169A4
(XEN) .... scale:       00000001:556F30D2
(XEN) .... Wall Clock:  1131314318s 40000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdae1, last bus=1
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Using IRQ router default [1106/3177] at 00:11.0
(XEN) PCI: Hardcoded IRQ 14 for device 00:11.1
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found: 
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Kernel image:  00c00000->00f3d2bc
(XEN)  Initrd image:  00f3e000->01f3e000
(XEN)  Dom0 alloc.:   02000000->12000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c0483c2c
(XEN)  Init. ramdisk: c0484000->c1484000
(XEN)  Phys-Mach map: c1484000->c14c4000
(XEN)  Page tables:   c14c4000->c14cb000
(XEN)  Start info:    c14cb000->c14cc000
(XEN)  Boot stack:    c14cc000->c14cd000
(XEN)  TOTAL:         c0000000->c1800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ...done.
(XEN) Initrd len 0x1000000, start at 0xc0484000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
Xen).
(XEN) PCI: Hardcoded IRQ 14 for device 00:11.1
(XEN) spurious 8259A interrupt: IRQ7.

Attachment: dmesg.xen2.linux
Description: Binary data

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