From: "Erik de Bruijn - BudgetDedicated.com" <Erik@BudgetDedicated.com>
To: xen-devel@lists.sourceforge.net
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Subject: Re: eth interrupts unavailable under xen
Date: Wed, 08 Dec 2004 18:06:20 +0100 [thread overview]
Message-ID: <41B7348C.7000804@BudgetDedicated.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123062@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 4707 bytes --]
Ian Pratt wrote:
>>Everything works with the native linux kernel, but under
>>xen/xenlinux network devices are detected but they can't be used.
>>
>>Extracted from the below it seems that eth0 and eth1 do not
>>show up in /proc/interrupts but do show up in the boot
>>output. I'm able to configure the interfaces but they never
>>send out a packet, let alone recieve anything. In the borked
>>an the working system one NIC chipset is similar. We've never
>>had problems with the NIC's before. XenLinux runs smooth on
>>other hosts.
>>
>>
>
>It sounds like an irq routing issue. Hopefully this will be fixed in a
>few weeks time with 2.1 when this code gets moved back to domain 0.
>
>
Would be great!
>In the meantime, it might be interesting to see what a native 2.4.27
>kernel does on this machine as Xen's current code is closer to this than
>2.6.
>
>
Ok, I'll try to give you an update on this later.
>Has the motherboard got an IOAPIC?
>
>
Concluding from the following XEN output I'd say that it does:
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
...
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
Thanks for the feedback!
--
Kind regards,
Erik de Bruijn
BudgetDedicated
www.BudgetDedicated.com | Tel. +31 492 430559 | Fax. +31 492 663870 | Mob. +31 6 21856715 | Adres: Haagwinde 16 | Zipcode NL-5731 WD Mierlo
(XEN) Initialised 1023MB memory (262128 pages) on a 1023MB machine
(XEN) Xen heap size is 10780KB
(XEN) CPU0: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2
(XEN) CPU caps: 0383fbff c1c3fbff 00000000 00000000
(XEN) found SMP MP-table at 000fb820
(XEN) Memory Reservation 0xfb820, 4096 bytes
(XEN) Memory Reservation 0xf5dd0, 4096 bytes
(XEN) ACPI: RSDP (v000 AMI ) @ 0x000fa4a0
(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 VIA_K7 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 ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.1
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: VIA Product ID: VT5440B APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 3 at 0xFEC00000.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Processors: 1
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 1999.751 MHz processor.
(XEN) CPU0: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2
(XEN) CPU caps: 0383fbff c1c3fbff 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000080
(XEN) ESR value after enabling vector: 00000000
(XEN) Error: only one processor found.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 1999.6765 MHz.
(XEN) ..... Bus speed is 266.6235 MHz.
(XEN) ..... bus_scale = 0x00011111
(XEN) Time init:
(XEN) .... System Time: 12240679ns
(XEN) .... cpu_freq: 00000000:7731C988
(XEN) .... scale: 00000001:00082453
(XEN) .... Wall Clock: 1102528081s 140000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdaf1, 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) *** 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: 02800000->02d8ff78
(XEN) Initrd image: 00000000->00000000
(XEN) Dom0 alloc.: 03000000->0b000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c070b328
(XEN) Init. ramdisk: c070c000->c070c000
(XEN) Phys-Mach map: c070c000->c072c000
(XEN) Page tables: c072c000->c072f000
(XEN) Start info: c072f000->c0730000
(XEN) Boot stack: c0730000->c0731000
(XEN) TOTAL: c0000000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ..done.
(XEN) Scrubbing Free RAM: ...........done.
[-- Attachment #2: Type: text/html, Size: 5579 bytes --]
next prev parent reply other threads:[~2004-12-08 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 16:06 eth interrupts unavailable under xen Ian Pratt
2004-12-08 17:06 ` Erik de Bruijn - BudgetDedicated.com [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 17:21 Ian Pratt
2004-12-08 0:11 Erik de Bruijn - BudgetDedicated.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41B7348C.7000804@BudgetDedicated.com \
--to=erik@budgetdedicated.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.