isdn-card loads but doesn't work in dom != 0

isdn-card loads but doesn't work in dom != 0

[Patrick Scharrenberg]

Hi!

I've got two hfc-chipset based isdn-cards in my pc. My intention was to
capsule them in a seperate xen-domain with restricted  network access.
The cards work fine in domain-0.

I hid them from domain-0 and assigned them to my isdn-domain.
There lspci shows them and drivers load and find the cards correctly.

The problem is, that they nevertheless don't work in this domain. When I
try to establish a connection nothing happens and after a while a
timeout occours.
I'm using mISDN stack and the same xen0-kernel for dom0 (where it works)
and isdn-domain.

Maybe it has something to do with shared interrupts?
lspci -v shows me that all(!) pci-devices share interrupts 5 and 11 when
working with xen.
When booting a normal linux-kernel without xen the system uses more than
these two irqs :-)

I use an asus "A7N8X Deluxe" motherboard which has a NVidia NForce2 chipset
(see   http://www.asus.com.tw/prog/spec.asp?m=A7N8X   for more
information about the motherboard and chipset)

so what might be the problem?

thanks and greets
Patrick

xm dmesg:

 Xen version 2.0.5 (root@) (gcc version 3.3.5 (Debian 1:3.3.5-8)) Tue
Mar 15 15:20:51 UTC 2005
 Latest ChangeSet: information unavailable

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009f800 (usable)
(XEN)  000000000009f800 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000000fff0000 (usable)
(XEN)  000000000fff0000 - 000000000fff3000 (ACPI NVS)
(XEN)  000000000fff3000 - 0000000010000000 (ACPI data)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffff0000 - 0000000100000000 (reserved)
(XEN) System RAM: 255MB (261692kB)
(XEN) Xen heap: 10MB (10788kB)
(XEN) CPU0: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2
(XEN) CPU caps: 0383fbff c1c3fbff 00000000 00000000
(XEN) ACPI: RSDP (v000 Nvidia                                    ) @
0x000f75e0
(XEN) ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x0fff3000
(XEN) ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x0fff3040
(XEN) ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
0x0fff74c0
(XEN) ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium(tm) Pro APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 1597.613 MHz processor.
(XEN) Found and enabled local APIC!
(XEN) CPU0: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2
(XEN) CPU caps: 0383fbff c1c3fbff 00000000 00000000
(XEN) CPU0 booted
(XEN) SMP motherboard not detected.
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 1597.6200 MHz.
(XEN) ..... Bus speed is 266.2699 MHz.
(XEN) ..... bus_scale = 0x000110B3
(XEN) Time init:
(XEN) .... System Time: 11926489ns
(XEN) .... cpu_freq:    00000000:5F39A594
(XEN) .... scale:       00000001:407A5F95
(XEN) .... Wall Clock:  1110903013s 30000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfb490, last bus=3
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Using IRQ router default [10de/01e0] at 00:00.0
(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->00f08e60
(XEN)  Initrd image:  00000000->00000000
(XEN)  Dom0 alloc.:   01000000->09000000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c0438504
(XEN)  Init. ramdisk: c0439000->c0439000
(XEN)  Phys-Mach map: c0439000->c0459000
(XEN)  Page tables:   c0459000->c045c000
(XEN)  Start info:    c045c000->c045d000
(XEN)  Boot stack:    c045d000->c045e000
(XEN)  TOTAL:         c0000000->c0800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ..done.
(XEN) Hiding PCI device 01:09.0 from DOM0
(XEN) Hiding PCI device 01:0a.0 from DOM0
(XEN) Scrubbing Free RAM: ...done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) spurious 8259A interrupt: IRQ7.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

RE: isdn-card loads but doesn't work in dom != 0

[Ian Pratt]

 
It does indeed sound like the interrupt routing is stuffed. Not sure
why. 

There's going to be a major change to the code that does IRQ assignment
real soon now (I've been saying this for months, but things are actually
moving forwards now). The code is moving out of Xen and into domain 0.

I'd suggest waiting a couple of weeks and keeping your fingers crossed,
unless you fancy doing a bit of bug hunting. If you let dom0 see the
cards, can it use them OK? What does the interrupt assignment look like
-- same as native?

Ian


> I've got two hfc-chipset based isdn-cards in my pc. My 
> intention was to
> capsule them in a seperate xen-domain with restricted  network access.
> The cards work fine in domain-0.
> 
> I hid them from domain-0 and assigned them to my isdn-domain.
> There lspci shows them and drivers load and find the cards correctly.
> 
> The problem is, that they nevertheless don't work in this 
> domain. When I
> try to establish a connection nothing happens and after a while a
> timeout occours.
> I'm using mISDN stack and the same xen0-kernel for dom0 
> (where it works)
> and isdn-domain.
> 
> Maybe it has something to do with shared interrupts?
> lspci -v shows me that all(!) pci-devices share interrupts 5 
> and 11 when
> working with xen.
> When booting a normal linux-kernel without xen the system 
> uses more than
> these two irqs :-)
> 
> I use an asus "A7N8X Deluxe" motherboard which has a NVidia 
> NForce2 chipset
> (see   http://www.asus.com.tw/prog/spec.asp?m=A7N8X   for more
> information about the motherboard and chipset)
> 
> so what might be the problem?
> 
> thanks and greets
> Patrick
> 
> xm dmesg:
> 
>  Xen version 2.0.5 (root@) (gcc version 3.3.5 (Debian 1:3.3.5-8)) Tue
> Mar 15 15:20:51 UTC 2005
>  Latest ChangeSet: information unavailable
> 
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009f800 (usable)
> (XEN)  000000000009f800 - 00000000000a0000 (reserved)
> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000000fff0000 (usable)
> (XEN)  000000000fff0000 - 000000000fff3000 (ACPI NVS)
> (XEN)  000000000fff3000 - 0000000010000000 (ACPI data)
> (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> (XEN)  00000000ffff0000 - 0000000100000000 (reserved)
> (XEN) System RAM: 255MB (261692kB)
> (XEN) Xen heap: 10MB (10788kB)
> (XEN) CPU0: Before vendor init, caps: 0383fbff c1c3fbff 
> 00000000, vendor = 2
> (XEN) CPU caps: 0383fbff c1c3fbff 00000000 00000000
> (XEN) ACPI: RSDP (v000 Nvidia                                    ) @
> 0x000f75e0
> (XEN) ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
> 0x0fff3000
> (XEN) ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
> 0x0fff3040
> (XEN) ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
> 0x0fff74c0
> (XEN) ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @
> 0x00000000
> (XEN) ACPI: Local APIC address 0xfee00000
> (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> (XEN) Processor #0 Pentium(tm) Pro APIC version 16
> (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> (XEN) Initializing CPU#0
> (XEN) Detected 1597.613 MHz processor.
> (XEN) Found and enabled local APIC!
> (XEN) CPU0: Before vendor init, caps: 0383fbff c1c3fbff 
> 00000000, vendor = 2
> (XEN) CPU caps: 0383fbff c1c3fbff 00000000 00000000
> (XEN) CPU0 booted
> (XEN) SMP motherboard not detected.
> (XEN) enabled ExtINT on CPU#0
> (XEN) ESR value before enabling vector: 00000000
> (XEN) ESR value after enabling vector: 00000000
> (XEN) Using local APIC timer interrupts.
> (XEN) Calibrating APIC timer for CPU0...
> (XEN) ..... CPU speed is 1597.6200 MHz.
> (XEN) ..... Bus speed is 266.2699 MHz.
> (XEN) ..... bus_scale = 0x000110B3
> (XEN) Time init:
> (XEN) .... System Time: 11926489ns
> (XEN) .... cpu_freq:    00000000:5F39A594
> (XEN) .... scale:       00000001:407A5F95
> (XEN) .... Wall Clock:  1110903013s 30000us
> (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfb490, last bus=3
> (XEN) PCI: Using configuration type 1
> (XEN) PCI: Probing PCI hardware
> (XEN) PCI: Probing PCI hardware (bus 00)
> (XEN) PCI: Using IRQ router default [10de/01e0] at 00:00.0
> (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->00f08e60
> (XEN)  Initrd image:  00000000->00000000
> (XEN)  Dom0 alloc.:   01000000->09000000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: c0100000->c0438504
> (XEN)  Init. ramdisk: c0439000->c0439000
> (XEN)  Phys-Mach map: c0439000->c0459000
> (XEN)  Page tables:   c0459000->c045c000
> (XEN)  Start info:    c045c000->c045d000
> (XEN)  Boot stack:    c045d000->c045e000
> (XEN)  TOTAL:         c0000000->c0800000
> (XEN)  ENTRY ADDRESS: c0100000
> (XEN) Scrubbing DOM0 RAM: ..done.
> (XEN) Hiding PCI device 01:09.0 from DOM0
> (XEN) Hiding PCI device 01:0a.0 from DOM0
> (XEN) Scrubbing Free RAM: ...done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen).
> (XEN) spurious 8259A interrupt: IRQ7.
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click

Re: isdn-card loads but doesn't work in dom != 0

[Mark Hurenkamp]

Hi,


> Maybe it has something to do with shared interrupts?
> lspci -v shows me that all(!) pci-devices share interrupts 5 and 11 when
> working with xen.
> When booting a normal linux-kernel without xen the system uses more than
> these two irqs :-)
Not sure if it is related, but on of my systems I noticed that Xen does not
route IRQ's well if I have the 'plug and play OS' option enabled in the
Bios. I had similar problems untill I switched it off.

On my server (Gigabyte GA-7S748-L/Sis748 with Fritz!PCIv2 ISDN card),
ISDN is working fine in a non-0 domain, but I'm using capi (not mISDN)
to run a voice and fax mail box. I don't use it regularly for internet
connection, but after installation that worked fine as well (I'm on a
ADSL line so don't really need it for that).


Hope it helps,

Mark.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click