similar to: (XEN) physdev.c:61: dom1: map invalid irq 1251

Hello, guys. First apologize my flaws, I am not a native English speaker and thus am prone to stupid errors. My box is an ASUSTek Notebook with Optimus capability (no, this is NOT about Optimus, I don't try to use Optimus yet, so please don't switch off here) with a running Gentoo. The first GPU is an Haswell-based Intel chip, the second one is a nVidia GeForce GTX 850M, the chip is a

Hi, I have HP DL 180 G6 2U Server loaded with CentOS 5.6. Can someone please suggest any good Hardware Raid Controller Card for the mentioned Hardware and OS. The reason being this server comes with Onboard Sata Controller chipset (HP Smart Array B110i Controller). This server has SATA Harddrive - 4 Nos of 500GB each and the OS doesnot detect it. 00:1f.2 SATA controller: Intel Corporation

Greetings, I am resending this as it doesn't appear in the archives and no one responded...maybe it got routed to /dev/null or something :-) I have asked this question the Scientific Linux mailing list (a few months ago) and got the suggestion I talk to the kernel guys. I pinged a kernel guy I know, and his suggestion was to ask the Nouveau list. So here I am. :-) I have had my work laptop

+cc: ocfs2-devel, sunil Marek, Thanks for the detailed report! Can I trouble you to file a bug at http://oss.oracle.com/bugzilla ... oh, is that your report http://oss.oracle.com/bugzilla/show_bug.cgi?id=1339? This looks like a deadlock of some sort. I don't think your hardware configuration really matters here. We'll keep looking into it. Joel On Tue, Dec 20, 2011 at 08:22:48AM

I''m using xen-unstable, and I''ve successfully made a passthrough of an intel storage controller to an HVM domU, binding with pciback. 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) I can access the array from within Windows by installing Intel Rapide Storage Drivers, and everything works as it should. I only have a

First off, the current state of support for Maxwell (GM107/NV110) is not very useful to end-users. It's especially not useful if it's a 3d accelerator card without outputs (as yours appears to be), since acceleration is not supported in 3.15 out of the box. You'd have to figure out how to extract the context switching firmware from the blob driver and load it in nouveau. I'm told

Ack! This slipped through my email. I am terribly sorry. Thank you so much for responding. On 04/06/2014 08:43 PM, Ilia Mirkin wrote: > On Sun, Apr 6, 2014 at 7:16 PM, ~Stack~ <i.am.stack at gmail.com> wrote: >> Greetings, [snip] >> My working kernel is: 2.6.32-358.23.2.el6.x86_64 (and anything before). >> >> The problem kernel is: 2.6.32-431.1.2.el6.x86_64 and

Yes, you are right - the Intel-chip is connected to the display, it just offloads 3D work to do to the nVidia-chip, which isn't even to tell how to get the EDID. I just wanted to try it out, simply for two reasons: 1. I heard that nouveau now "supports" the chip, and since I got the hardware, I wanted to try it out - just for the fun of it. :) 2. As far as I am informed, a way to

Like others on this list I am trying to employ the VTD-NEO patches in Xen 3.2 unstable to assign the internal graphics device to Dom1/Vista. I have removed the Cirrus Logic emulated device from qemu and replaced the Cirrus Logic vgabios with the the actual vgabios from my GPU. However I am hitting an xen assert and was hoping someone might be able to point me in the right direction. Below

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Today I found I can not ping some of my domU''s. I logged in to dom0, did a "xm list", all domU are there. Then I did a "ifconfig" and surprised to find some of vif''s disappeared! Like for example. "xm list" show dom13 is alive, but "brctl show" shows no vif13.0. If I "xm console 13", there''s some message: WARNING:

Hi, I want my server to be a member of DOM1 but user validation done on DOM2. Can this be done? [global] workgroup = DOM1 netbios name = MYUSERVER security = DOMAIN encrypt passwords = Yes password server = PDC_DOM2,BDC_DOM2 This doesn't work... Any ideas? Thanks, Simon.

From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> This patch handle additional cases for IVRS bugs where special->handle is not correctly initialized for IOAPIC and HPETS due to firmware bugs. Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com> Provide logic in "is_ioapic_overidden()" Signed-off-by: Jan Beulich <JBeulich@suse.com> ---

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)

Hello, I''m having problems with VTD on this board. The board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0)

Under the assumption that in these cases recurring faults aren''t a security issue and it can be expected that the drivers there are going to try to take care of the problem. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/amd/iommu_init.c +++ b/xen/drivers/passthrough/amd/iommu_init.c @@ -625,6 +625,18 @@ static void parse_event_log_entry(struct

Hi Wei, A Debian user has hit this message and reported it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 I think it is the BUG_ON in: struct amd_iommu *find_iommu_for_device(int bdf) { BUG_ON ( bdf >= ivrs_bdf_entries ); return ivrs_mappings[bdf].iommu; } It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug report

Hi Wei, A Debian user has hit this message and reported it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661 I think it is the BUG_ON in: struct amd_iommu *find_iommu_for_device(int bdf) { BUG_ON ( bdf >= ivrs_bdf_entries ); return ivrs_mappings[bdf].iommu; } It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug report

Add commands to automatically prep devices for pass-through The current method for passing through devices requires users to either modify cryptic Linux boot parameters and reboot, or do a lot of manual reads and writes into sysfs nodes. This set of patches introduces commands to make this easier. It expands on the concept of "assignable" (from the list_assignable_devices command).