similar to: Cannot VGA Passthrough Intel HD Graphics 4600 IGD

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

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

+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

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

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

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

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

Package: linux-2.6 Version: 2.6.32-26~bpo50+1 Severity: important --- Please enter the report below this line. --- I've installed the following packages an lenny, which are working well on other maschines. # dpkg -l | grep xen | grep bpo ii libxenstore3.0 4.0.1-1~bpo50+1 Xenstore communications library for Xen ii linux-image-2.6.32-bpo.5-xen-686 2.6.32-26~bpo50+1 Linux 2.6.32 for modern

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

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.

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

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!

Hi Brian, From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. You can check PCI bus whether support MSI like: cat /sys/bus/pci/devices/00:0e.0/msi_bus Other, do you call pci_enable_device() before pci_enable_msi() ? On

Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the

On 2014/7/4 10:45, Brian Becker wrote: > Yijing, > > cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting > that it supports MSI. However, this "00:0e.0 PCI bridge: PLX > Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" > is a component of the addin card. Wouldn't the lack of support for MSI > by the chipset "00:00.0

On 2014/7/4 10:43, Ilia Mirkin wrote: > On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote: >> Hi Brian, >> From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this >> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >>

Hi [1.] One line summary of the problem: rsync segfaulting and the kernel oops'ing while synchronizing two smbfs's [2.] Full description of the problem/report: I am implementing file synchronization between two Windows NT 4 machines through two smbfs mounts. Rsync runs for about half an hour; then the kernel gives an oops and rsync segfaults. Hereafter the smbfs file system is

Hi, It would seem like it (attachments are from 4.9-rc1, btw), but it doesn't look like there is any support in the Xorg driver. How can I help with that? Best regards, Sune Mølgaard Translucent ApS On 2016-04-22 09:33, Pierre Moreau wrote: > Hello, > > A patch was merged yesterday to recognise GM108 (see >