search for: rearmed

On my GP107 when I load nouveau after unloading it, for some reason the GPU stopped sending or the CPU stopped receiving interrupts if MSI was enabled. Doing a rearm once before getting any interrupts fixes this. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/subdev/pci/base.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git

On Fri, Nov 24, 2017 at 3:02 PM, Thierry Reding <thierry.reding at gmail.com> wrote: > On Fri, Nov 24, 2017 at 03:56:26AM +0100, Karol Herbst wrote: >> On my GP107 when I load nouveau after unloading it, for some reason the >> GPU stopped sending or the CPU stopped receiving interrupts if MSI was >> enabled. > > I suppose this could happen if the GPU raises an

On Fri, Nov 24, 2017 at 03:56:26AM +0100, Karol Herbst wrote: > On my GP107 when I load nouveau after unloading it, for some reason the > GPU stopped sending or the CPU stopped receiving interrupts if MSI was > enabled. I suppose this could happen if the GPU raises an interrupt after the driver's already called free_irq() on it, and hence the driver can't rearm itself in the

I have made the daring (and possibly idiotic) decision to play BCR on my laptop instead of my desktop computer, as my desktop is single core and therefore runs the game rather sluggishly while my laptop is dual-core. The only problem with this is that my laptop runs Linux. Does anyone knwo what I might have to tweak in order to get it to run? Will I have to disable SecuROM?

Hi, recently we tried to enable MSI interrupts with nouveau. Unfortunately there have been some reports of things failing with certain cards, where it isn't entirely clear if this is a GPU errata or some other component in the PCIe chain failing. Could you perhaps investigate if there are any known Nvidia GPU erratas with regard to MSI interrupts, or maybe tell us the generations of cards

704a6c008b7942bb7f30bb43d2a6bcad7f543662 broke pci msi rearm for g92 GPUs. g92 needs the nv46_pci_msi_rearm, where g94+ gpus used nv40_pci_msi_rearm. Reported-by: Andrew Randrianasulu <randrianasulu at gmail.com> Signed-off-by: Karol Herbst <karolherbst at gmail.com> --- drm/nouveau/include/nvkm/subdev/pci.h | 1 + drm/nouveau/nvkm/engine/device/base.c | 20 +++++++-------

On Fri, Oct 25, 2013 at 7:43 AM, Robert Morell <rmorell at nvidia.com> wrote: > On Mon, Sep 30, 2013 at 10:44:12AM -0700, Lucas Stach wrote: >> Hi, >> >> recently we tried to enable MSI interrupts with nouveau. Unfortunately >> there have been some reports of things failing with certain cards, where >> it isn't entirely clear if this is a GPU errata or

On Mon, Sep 30, 2013 at 10:44:12AM -0700, Lucas Stach wrote: > Hi, > > recently we tried to enable MSI interrupts with nouveau. Unfortunately > there have been some reports of things failing with certain cards, where > it isn't entirely clear if this is a GPU errata or some other component > in the PCIe chain failing. > > Could you perhaps investigate if there are any

See https://bugs.freedesktop.org/show_bug.cgi?id=74492 Reported-by: Ronald <ronald645 at gmail.com> Suggested-by: Marcin Ko?cielnicki <koriakin at 0x04.net> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/Makefile | 1 + drivers/gpu/drm/nouveau/core/engine/device/nv40.c | 10 ++---

System Specs wine version: 1.1.0 OS: Gentoo with Linux 2.6.24 Nvidia Drivers: 169.12 wine configs * tried with virtual desktop * tried with WinXP and Vista I was able to install Bionic Commando: Rearmed. However, wine fails when I attempt to start the game with the output shown below. Code: fixme:ntdll:NtQueryInformationProcess (0xffffffff,info_class=34,0x1c3a3b0,0x00000004,0x1c3a3ac) Unknown information class fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_HANDLE_INFORMATION fixme:ntdl...

On Tue, Jan 19, 2016 at 5:22 AM, Jiri Slaby <jslaby at suse.cz> wrote: > Hi, > > On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: >> I'd like to recommend backporting this commit: >> >> commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 >> Author: Hans de Goede <hdegoede at redhat.com> >> Date: Thu Jul 23 17:20:12 2015 +0200 >> >>

Hello, I'd like to recommend backporting this commit: commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 Author: Hans de Goede <hdegoede at redhat.com> Date: Thu Jul 23 17:20:12 2015 +0200 drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c This disables MSI by default on G72 (NV46) devices where it's apparently a bit buggy. We have a later patch which turns MSI back

On Wed, Jul 13, 2016 at 06:17:47PM +0100, Chris Wilson wrote: > On Tue, Jul 12, 2016 at 06:49:34PM +0200, Peter Wu wrote: > > The FBIOPUT_CON2FBMAP ioctl takes a console_lock(). When this is called > > while nouveau was runtime suspended, a deadlock would occur due to > > nouveau_fbcon_set_suspend also trying to obtain console_lock(). > > > > Fix this by delaying

[PATCH][HVM] fix smp guest hang after restore Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> update the pt irq after restore, otherwise all lapic timer intr are lost diff -r 6b5606877bb4 xen/arch/x86/hvm/vlapic.c --- a/xen/arch/x86/hvm/vlapic.c Fri Sep 15 17:05:38 2006 +0800 +++ b/xen/arch/x86/hvm/vlapic.c Tue Jan 30 18:03:19 2007 +0800 @@ -836,14 +836,16 @@ static int

On Thu, Oct 24, 2013 at 04:03:12PM -0700, Ben Skeggs wrote: > On Fri, Oct 25, 2013 at 7:43 AM, Robert Morell <rmorell at nvidia.com> wrote: > > On Mon, Sep 30, 2013 at 10:44:12AM -0700, Lucas Stach wrote: > >> Hi, > >> > >> recently we tried to enable MSI interrupts with nouveau. Unfortunately > >> there have been some reports of things failing

Several users have, over time, reported issues with MSI on these IGPs. They're old, rarely available, and MSI doesn't provide such huge advantages on them. Just disable. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74492 Fixes: fa8c9ac72fe ("drm/nv4c/mc: nv4x igp's have a different msi rearm register")

Hi, On 01/17/2016, 08:28 PM, Ilia Mirkin wrote: > I'd like to recommend backporting this commit: > > commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7 > Author: Hans de Goede <hdegoede at redhat.com> > Date: Thu Jul 23 17:20:12 2015 +0200 > > drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c > > This disables MSI by default on G72 (NV46)

In preparation to enabling -Wvla, remove VLA. In this particular case directly use macro NVKM_MSGQUEUE_CMDLINE_SIZE instead of local variable cmdline_size. Also, remove cmdline_size as it is not actually useful anymore. The use of stack Variable Length Arrays needs to be avoided, as they can be a vector for stack exhaustion, which can be both a runtime bug or a security flaw. Also, in general, as

In preparation to enabling -Wvla, remove VLA. In this particular case directly use macro NVKM_MSGQUEUE_CMDLINE_SIZE instead of local variable cmdline_size. Also, remove cmdline_size as it is not actually useful anymore. The use of stack Variable Length Arrays needs to be avoided, as they can be a vector for stack exhaustion, which can be both a runtime bug or a security flaw. Also, in general, as

Just re-tried this, and it doesn't seem to fire getmail on access for me. My incrontab is as follows: /home/user/Maildir/cur/ IN_ALL_EVENTS,IN_ONESHOT /home/user/bin/mvmail.sh The incrontab rule does work, but only if I make a physical change in /home/user/Maildir/cur/ e.g. by moving a mail from another folder in there. Just accessing the particular inbox doesn't seem to trigger