search for: intd

...ng like this: Interface IP Gateway Table Network --------- -- ------- ----- ------- intA ipA gwA tableA netA intB ipB gwB tableB netB intC ipC gwC tableC netC [intD is the LAN interface] intD ipD (private) no gateway global netD This works fine most of the time, except that once in a while (every 5-10 minutes or so) packets going out on (e.g.) intB suddenly start getting NAT''ed to source address ipA (i.e. the address of another inter...

...fc000, event channel 1 (d6) System requested SeaBIOS (d6) CPU speed is 3607 MHz (d6) Relocating guest memory for lowmem MMIO space disabled (d6) PCI-ISA link 0 routed to IRQ5 (d6) PCI-ISA link 1 routed to IRQ10 (d6) PCI-ISA link 2 routed to IRQ11 (d6) PCI-ISA link 3 routed to IRQ5 (d6) pci dev 01:2 INTD->IRQ5 (d6) pci dev 01:3 INTA->IRQ10 (d6) pci dev 02:0 INTA->IRQ11 (d6) pci dev 04:0 INTA->IRQ5 (d6) No RAM in high memory; setting high_mem resource base to 100000000 (d6) pci dev 03:0 bar 10 size 002000000: 0f0000008 (d6) pci dev 02:0 bar 14 size 001000000: 0f2000008 (d6) pci dev 04:0...

...: Dom14 PCI link 1 changed 0 -> 10 (XEN) HVM14: PCI-ISA link 1 routed to IRQ10 (XEN) irq.c:270: Dom14 PCI link 2 changed 0 -> 11 (XEN) HVM14: PCI-ISA link 2 routed to IRQ11 (XEN) irq.c:270: Dom14 PCI link 3 changed 0 -> 5 (XEN) HVM14: PCI-ISA link 3 routed to IRQ5 (XEN) HVM14: pci dev 01:2 INTD->IRQ5 (XEN) HVM14: pci dev 01:3 INTA->IRQ10 (XEN) HVM14: pci dev 03:0 INTA->IRQ5 (XEN) HVM14: pci dev 04:0 INTA->IRQ5 (XEN) HVM14: pci dev 02:0 bar 10 size 02000000: f0000008 (XEN) HVM14: pci dev 03:0 bar 14 size 01000000: f2000008 (XEN) HVM14: pci dev 02:0 bar 14 size 00001000: f300000...

...requested SeaBIOS > (d6) CPU speed is 3607 MHz > (d6) Relocating guest memory for lowmem MMIO space disabled > (d6) PCI-ISA link 0 routed to IRQ5 > (d6) PCI-ISA link 1 routed to IRQ10 > (d6) PCI-ISA link 2 routed to IRQ11 > (d6) PCI-ISA link 3 routed to IRQ5 > (d6) pci dev 01:2 INTD->IRQ5 > (d6) pci dev 01:3 INTA->IRQ10 > (d6) pci dev 02:0 INTA->IRQ11 > (d6) pci dev 04:0 INTA->IRQ5 > (d6) No RAM in high memory; setting high_mem resource base to 100000000 > (d6) pci dev 03:0 bar 10 size 002000000: 0f0000008 > (d6) pci dev 02:0 bar 14 size 001000000...

...q.c:258: Dom1 PCI link 1 changed 0 -> 10 (XEN) HVM1: PCI-ISA link 1 routed to IRQ10 (XEN) irq.c:258: Dom1 PCI link 2 changed 0 -> 11 (XEN) HVM1: PCI-ISA link 2 routed to IRQ11 (XEN) irq.c:258: Dom1 PCI link 3 changed 0 -> 5 (XEN) HVM1: PCI-ISA link 3 routed to IRQ5 (XEN) HVM1: pci dev 01:2 INTD->IRQ5 (XEN) HVM1: pci dev 01:3 INTA->IRQ10 (XEN) HVM1: pci dev 02:0 INTA->IRQ11 (XEN) HVM1: pci dev 03:0 INTC->IRQ10 (XEN) HVM1: pci dev 04:0 INTA->IRQ5 (XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008 (XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008 (XEN) HVM1: pci dev...

...tapci0: <Intel PIIX4 ATA33 controller> port 0x2c00-0x2c0f at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x2c20-0x2c3f at device 15.2 on pci0 pci_cfgintr: can't route an interrupt to 0:15 INTD uhci0: Could not allocate irq device_probe_and_attach: uhci0 attach returned 6 Timecounter "PIIX" frequency 3579545 Hz chip0: <Intel 82371AB Power management controller> port 0x1240-0x124f at device 15.3 on pci0 pcib2: <Intel 82454NX PCI Expander Bridge> at device 18.0 on pci...

Hi there, I'm having some fairly serious asterisk problems, which seem to be spread quite liberally across all asterisk versions, I've tried 1.4.2, 1.6.0.10, 1.6.2beta4 and still had exactly the same problem with static and echo on the line when using the PRI interface. A little background: Server: HP DL145 G3 Dual Opteron 246 with 2GB ram and a brand new OpenVox D110P

...c0f > > at device 15.1 on pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port > > 0x2c20-0x2c3f at device 15.2 on pci0 > > pci_cfgintr: can't route an interrupt to 0:15 INTD > > uhci0: Could not allocate irq > > device_probe_and_attach: uhci0 attach returned 6 > > Timecounter "PIIX" frequency 3579545 Hz > > chip0: <Intel 82371AB Power management controller> port > > 0x1240-0x124f at device 15.3 on pci0 > > pcib2: &lt...

...irq.c:270: Dom17 PCI link 2 changed 0 -> 11 (XEN) [2013-07-17 19:10:12] HVM17: PCI-ISA link 2 routed to IRQ11 (XEN) [2013-07-17 19:10:12] irq.c:270: Dom17 PCI link 3 changed 0 -> 5 (XEN) [2013-07-17 19:10:12] HVM17: PCI-ISA link 3 routed to IRQ5 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 01:2 INTD->IRQ5 [ 560.643890] xen_pciback: vpci: 0000:04:00.0: assign to virtual slot 0 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 01:3 INTA->IRQ10 [ 560.650365] xen_pciback: vpci: 0000:08:00.0: assign to virtual slot 1 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 03:0 INTA->IRQ5 (XEN) [2013-07-17 1...

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)

Thomas, Have spoken to Soren, from my bootlog he believes that the problem is in atapicam causing the system to lock up. He is happy to answer some questions but doesnt have time to delve into atapicam himself. Did you author atapicam, I have seen your name on the sourcecode, can you help me further? Whats next? Thanks Adam. -------------- next part -------------- An embedded message was

...lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe9ff000, size 8, enabled pcib0: allocated type 3 (0xfe9ff000-0xfe9ff0ff) for rid 10 of pci0:0:19:5 pcib0: matched entry for 0.19.INTD pcib0: slot 19 INTD hardwired to IRQ 19 found-> vendor=0x1002, dev=0x4385, revid=0x13 domain=0, bus=0, slot=20, func=0 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0403, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type I/O Por...

...nk 0 routed to IRQ5 (XEN) irq.c:270: Dom2 PCI link 1 changed 0 -> 10 (d2) PCI-ISA link 1 routed to IRQ10 (XEN) irq.c:270: Dom2 PCI link 2 changed 0 -> 11 (d2) PCI-ISA link 2 routed to IRQ11 (XEN) irq.c:270: Dom2 PCI link 3 changed 0 -> 5 (d2) PCI-ISA link 3 routed to IRQ5 (d2) pci dev 01:2 INTD->IRQ5 (d2) pci dev 01:3 INTA->IRQ10 (d2) pci dev 02:0 INTA->IRQ11 (d2) pci dev 03:0 INTA->IRQ5 (d2) pci dev 05:0 INTA->IRQ10 (d2) No RAM in high memory; setting high_mem resource base to 100000000 (d2) pci dev 04:0 bar 10 size 002000000: 0f0000008 (d2) pci dev 02:0 bar 14 size 001000...

I''m afraid this series is rather a grab bag and it is distressingly large at this stage. With this series I can boot an Xgene board until it fails to find its SATA controller. This is a dom0 issue for which patches are pending from APM (/me nudges Anup). As well as the APM specific platform stuff there are also some generic improvements which were either necessary or useful during this

George has release acked all of these. Otherwise mostly minor updates this time around. Summary: A == acked, M == modified A xen: arm64: Add 8250 earlyprintk support A xen: arm64: Add Basic Platform support for APM X-Gene Storm. A xen: arm64: Add APM implementor id to processor implementers. M xen: arm: add a quirk to handle platforms with unusual GIC layout A xen: arm: allow platform

Hello, It looks like upstream linux-2.6.git contains at least the following xen related new features for Linux 2.6.36: - Xen-SWIOTLB support (required for Xen PCI passthru and dom0) - Xen PV-on-HVM drivers - Xen VBD online dynamic resize of guest disks (xvd*) Congratulations! What are the plans for 2.6.37 merge window? I believe at least: - Xen PCI frontend Others? I''m going to

Hi,all I have tried to passthrough GPU card(Nvidia quadro 4000) on the latest Xen unstable version (QEMU is using Qemu-upsteam-unstable, not traditional Qemu). This issue as below: Windows7 64-bit guest will blue screen when GPU passthrough configure 4g memory,blue screen code is 50, and SUSE 11 64-bit guest will always stay at the grub screen. I noticed that it will relocate RAM that

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list