similar to: Xen Security Advisory 59 (CVE-2013-3495) - Intel VT-d Interrupt Remapping engines can be evaded by native NMI interrupts

I have an Intel e1000e NIC which I put into passthrough for an HVM domain under Xen 4.2. All the corresponding hardware protections are enabled on my system (DMA + Interrupt remapping), however, once in a while I get a SERR NMI in dom0 (NMI - PCI sys error (SERR) in xl dmesg). I am wondering about its exact reason. I am thinking in the following way: [+] Under Intel VT-x, interrupts are

https://bugs.freedesktop.org/show_bug.cgi?id=42672 Bug #: 42672 Summary: NMI SERR with 2 Geforce 310 cards Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

http://bugzilla.mindrot.org/show_bug.cgi?id=540 Summary: sshd [priv] has PPID 1 and is killed by ^C in terminal Product: Portable OpenSSH Version: 3.6p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

Dear, I have a data frame object (FSTc) which is in fact a matrix of class data.frame but created from a txt file using the command FSTc<-read.table("FSTcmatrix.txt", header=T) I would like to transform it in a distance matrix of class dist to use it with the ade4 package. I'm quite sure this is a simple operation but i just don't have the commands. Could anyone help?

+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

Hi, I am trying to VGA passthrough Intel HD Graphics 4600 IGD with Xen-unstable 4.4 changeset 27214 and Linux kernel 3.10.0 but was not successful. Details are as follows: =============================================================================================== teo-en-ming@intel-core-i5-4430-desktop:~$ sudo xl info [sudo] password for teo-en-ming: host :

While doing this on an 80gig ibm ide drive: dd if=/dev/cdrom of=cd.iso I got the following assertian failure Aug 9 14:43:27 budder kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1733: "jh2bh(jh) == bh" Aug 9 14:43:27 budder kernel: kernel BUG at journal.c:1733! Aug 9 14:43:27 budder kernel: invalid operand: 0000 Aug 9 14:43:27 budder kernel: CPU: 0 Aug 9

I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware. Could someone please tell me what these error are and if there is some known way to prevent them? My configuration: - 2 Hitachi SATA 120 GB Harddisks - Intel P4 3GHz - Tyan Tomcat i875p motherboard - 1 GB ECC RAM - 2

Hi, The following error message appeared in syslog while the filesharing client overnet was running and writing to the disk. I first only noticed that suddenly Opera was frozen and no new terminals could be started. Regards W. Pichler syslog Jun 15 13:15:34 pc kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000e Jun 15 13:15:34 pc kernel: printing eip: Jun

I just installed CentOS 5 on a computer. On boot, I get the a error message, related to 2 SATA disks. These errors did NOT appear on version 4.4 with the EXACT same hardware. Despite the error messages, the disks seem to be working with no problems. Could someone please tell me what these error are and if there is some known way to prevent them? I searched the Net for these errors and they seem

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

Several people already reported this at linux-kernel and elsewhere with no answers, I thought perhaps this would be a more adequate forum... [1.] One line summary of the problem: After I/O, journal is aborted and filesystems made read-only. [2.] Full description of the problem/report: One can't anymore write to the affected file systems. Upon investigation, ext3fs journal was aborted

Hi all.. I have found some problems on smbfs module in 2.4.18 kernel. I compiled it by myself (not the very first kernel compilation in my life ;-)) and then I have got it. Looks like it touch smbfs module as when I recompile 2.4.18 modules with smbfs sources changed to sources of smbfs from 2.4.17 problem disappears!! My mainboard is Abit BE6 with Pentium III 450 MHz. I am using SuSE 7.3 with

Hi All, I just had "an issue" with my Linux 2.6.1 kernel. While working, I tried to rf -rf a directory, and was told my filesystem was mounted readonly (which it wasn't). I then shut the machine down, and on shutdown, I got a "kernel BUG at fs/ext3/super.c: 411". Full report below: Mike [1.] One line summary of the problem: Filesystem became readonly, then

Hello, The idea was to use the modesetting DDX instead of Nouveau’s one for Maxwell+ as EXA was [broken][1]. But you can give a try at Ilia’s [patches][2], which fix the Nouveau DDX for GM10x and GM20x (I don’t think it has been tested on a GM108 yet). Best regards, Pierre Moreau [1]: https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=3e2e0faa2ee1cce9c1bb5c7ad80d0592460f3edc

hi, give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with 4.9, so 4.10 is required. Greetings. On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" <smo at translucent.dk> wrote: >Hi again, > >It works :-) > >Reclocking, however, is another kettle of fish. > >Trying #echo 0f > /sys/kernel/debug/dri/0/pstate

We're seeing some strange timeout errors on some new Supermicro X9DRT-HF MB's we here when combined with KINGSTON HyperX 3K SSD's It seems that when connnected to the second channel reads often timeout stalling all IO under 8.3-RELEASE-p3 When this happens we see:- Jul 27 14:35:59 lon059 kernel: ahcich1: Timeout on slot 0 port 0 Jul 27 14:35:59 lon059 kernel: ahcich1: is 00000000 cs

also you can't change the clocks when there is nothing running on the GPU. I have some patches pending for this in another series, but maybe I may be able toe extract those fixes. Changing the clocks while something is running shouldn't cause any troubles. Alternatively if you don't care about power consumption, you can boot with nouveau.runpm=0 so that the gpu is always on.

Hi All, I hope I'm posting this to the appriopriate list, and that cross posting to two lists is OK. (If not, I'm sure I'll hear about it quickly :)) I'm running Asterisk on my (new) VIA EPIA-V motherboard. This seems to be the ideal platform for a home version of asterisk - its small, quiet, low power, and should have plenty of computing horsepower if only it would work!

you can boot with nouveau.config=NvBoost=2 to enable higher clocks, but that won't fill in the difference compared to Intel. For this there are some changes needed on the mesa side regarding scheduling. Also keep in mind, that PCIe is an important bottleneck here, because the GPU can't push frames fast enough through the bus, that's why any "high FPS" benchmark will be in