similar to: [PATCH] mmu: ALIGN_DOWN correct variable

Displaying 20 results from an estimated 200 matches similar to: "[PATCH] mmu: ALIGN_DOWN correct variable"

2018 Apr 03
2
nouveau TRAP_M2MF still there on G98
Hi! In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0: > drm/nouveau/mmu: ALIGN_DOWN correct variable > > Commit 7110c89bb8852ff8b0f88ce05b332b3fe22bd11e ("mmu: swap out round > for ALIGN") replaced two calls to round/rounddown with ALIGN/ALIGN_DOWN, > but erroneously applied ALIGN_DOWN to a different variable (addr) and left > intended variable (tail) not
2018 Apr 04
2
nouveau TRAP_M2MF still there on G98
On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: > 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > > have your fix. I don't know about earlier versions -- my newer card went > > into
2018 Apr 04
0
nouveau TRAP_M2MF still there on G98
Hi, Adam. 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > Hi! > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > have your fix. I don't know about earlier versions -- my newer card went > into flames just a few days ago, and I replaced it a brand new 8400GS (G98)
2018 Apr 04
0
nouveau TRAP_M2MF still there on G98
On Wed, Apr 4, 2018 at 6:58 PM, Adam Borowski <kilobyte at angband.pl> wrote: > On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: >> 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: >> > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 >> > >> > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which
2013 Jun 18
1
kernel bug nouveau, total system hang, X crashed
Hi, Using kernel 3.9.4, with openSUSE 12.1 (KDE 4.7.4 I think), I was running fine for a long time with no problems. Today with openSUSE 12.3 (KDE 4.10.3, Xorg 1.13.2, upgraded on Jun. 10), my machine hung completely. I believe the nouveau driver is at fault rather than KDE or X, so chose this list. I think it might have been triggered by the "Clock" ScreenLocker (screen saver). It
2018 Mar 17
0
[Bug 105173] [MCP79][Regression] Unhandled NULL pointer dereference in nvkm_object_unmap since kernel 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #18 from Maris Nartiss <maris.nartiss at gmail.com> --- (In reply to Sérgio M. Basto from comment #17) > I tested https://bugs.freedesktop.org/attachment.cgi?id=137730 on a > kernel-4.15 > but doesn't fixed my boot problem . Then, please, open a different bug and provide full kernel (dmesg) output. Or even better
2013 Sep 15
4
[Bug 69387] New: X hangs on resume/monitor blank with nv50cal_space: -16
https://bugs.freedesktop.org/show_bug.cgi?id=69387 Priority: medium Bug ID: 69387 Assignee: nouveau at lists.freedesktop.org Summary: X hangs on resume/monitor blank with nv50cal_space: -16 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All)
2013 Mar 08
1
[Bug 62035] New: [Regression kernel 3.8.0+] G86 GeForce 8400M GS 3D desktop effects does not work
https://bugs.freedesktop.org/show_bug.cgi?id=62035 Priority: medium Bug ID: 62035 Assignee: nouveau at lists.freedesktop.org Summary: [Regression kernel 3.8.0+] G86 GeForce 8400M GS 3D desktop effects does not work QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified
2018 Mar 01
0
[Bug 105173] [MCP79][Regression] Unhandled NULL pointer dereference in nvkm_object_unmap since kernel 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #11 from Nick Lee <nvlbox at gmail.com> --- (In reply to Pierre Moreau from comment #10) > What exactly is reproducible? The artefacts I would assume, but which error > exactly? The NULL pointer dereference, or the “trapped read at 0080000000 on > channel 1 [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH]
2018 Mar 01
0
[Bug 105173] [MCP79][Regression] Unhandled NULL pointer dereference in nvkm_object_unmap since kernel 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #12 from Nick Lee <nvlbox at gmail.com> --- > The NULL pointer dereference, or the “trapped read at 0080000000 on channel 1 > [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH] subclient 04 [M2M_IN] > reason 00000006 [NULL_DMAOBJ]” one? "NULL pointer dereference" AND "trapped read" after
2014 Nov 11
5
[Bug 86164] New: Dual screen causes KDE crash on NV50 (NV98) in nouveau (bisected)
https://bugs.freedesktop.org/show_bug.cgi?id=86164 Bug ID: 86164 Summary: Dual screen causes KDE crash on NV50 (NV98) in nouveau (bisected) Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:
2018 Mar 18
0
[Bug 105173] [MCP79][Regression] Unhandled NULL pointer dereference in nvkm_object_unmap since kernel 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #19 from Sérgio M. Basto <sergio at serjux.com> --- (In reply to Maris Nartiss from comment #18) > (In reply to Sérgio M. Basto from comment #17) > > I tested https://bugs.freedesktop.org/attachment.cgi?id=137730 on a > > kernel-4.15 > > but doesn't fixed my boot problem . > > Then, please, open
2013 Mar 05
0
[PATCH] drm/nouveau: idle channel before releasing notify object
Unmapping it while it's still in use (e.g. by M2MF) can lead to page faults and a lot of TRAP_M2MF spam in dmesg. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_abi16.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nouveau_abi16.c b/drivers/gpu/drm/nouveau/nouveau_abi16.c index 4124192..3b6dc88 100644
2020 Jul 15
2
[PATCH v4 45/75] x86/sev-es: Adjust #VC IST Stack on entering NMI handler
On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote: > @@ -489,6 +490,9 @@ DEFINE_IDTENTRY_RAW(exc_nmi) > this_cpu_write(nmi_cr2, read_cr2()); > nmi_restart: > > + /* Needs to happen before DR7 is accessed */ > + sev_es_ist_enter(regs); > + > this_cpu_write(nmi_dr7, local_db_save()); > > nmi_enter(); > @@ -502,6 +506,8 @@
2020 Jul 15
2
[PATCH v4 45/75] x86/sev-es: Adjust #VC IST Stack on entering NMI handler
On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote: > @@ -489,6 +490,9 @@ DEFINE_IDTENTRY_RAW(exc_nmi) > this_cpu_write(nmi_cr2, read_cr2()); > nmi_restart: > > + /* Needs to happen before DR7 is accessed */ > + sev_es_ist_enter(regs); > + > this_cpu_write(nmi_dr7, local_db_save()); > > nmi_enter(); > @@ -502,6 +506,8 @@
2020 Jul 15
0
[PATCH v4 45/75] x86/sev-es: Adjust #VC IST Stack on entering NMI handler
On Wed, Jul 15, 2020 at 11:47:02AM +0200, Peter Zijlstra wrote: > On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote: > DECLARE_STATIC_KEY_FALSE(sev_es_enabled_key); > > static __always_inline void sev_es_foo() > { > if (static_branch_unlikely(&sev_es_enabled_key)) > __sev_es_foo(); > } > > So that normal people will only see an extra NOP? Yes,
2020 Aug 31
1
[PATCH v6 48/76] x86/entry/64: Add entry code for #VC handler
On Mon, Aug 24, 2020 at 10:54:43AM +0200, Joerg Roedel wrote: > @@ -446,6 +448,82 @@ _ASM_NOKPROBE(\asmsym) > SYM_CODE_END(\asmsym) > .endm > ifdeffery pls... > +/** > + * idtentry_vc - Macro to generate entry stub for #VC > + * @vector: Vector number > + * @asmsym: ASM symbol for the entry point > + * @cfunc: C function to be called > + * > + * The macro
2018 Sep 17
0
Re: [PATCH nbdkit v2] common: isaligned: Use a macro instead of relying on implicit truncation.
On Mon, Sep 17, 2018 at 11:27 PM Richard W.M. Jones <rjones@redhat.com> wrote: > --- > common/include/isaligned.h | 11 +++++------ > plugins/file/file.c | 4 ++-- > plugins/vddk/vddk.c | 8 ++++---- > 3 files changed, 11 insertions(+), 12 deletions(-) > > diff --git a/common/include/isaligned.h b/common/include/isaligned.h > index e693820..81ce8a7
2011 Mar 31
0
[LLVMdev] More DWARF problems
On Mar 31, 2011, at 12:57 AM, Talin wrote: > On Wed, Mar 30, 2011 at 11:17 AM, Devang Patel <dpatel at apple.com> wrote: > > On Mar 29, 2011, at 7:29 PM, Talin wrote: > >> I've been trying to track down the problem with the DWARF info that is being emitted by my front end, which has been broken for about a month now. Here's what happens when I attempt to use gdb
2020 Jul 14
0
[PATCH v4 45/75] x86/sev-es: Adjust #VC IST Stack on entering NMI handler
From: Joerg Roedel <jroedel at suse.de> When an NMI hits in the #VC handler entry code before it switched to another stack, any subsequent #VC exception in the NMI code-path will overwrite the interrupted #VC handlers stack. Make sure this doesn't happen by explicitly adjusting the #VC IST entry in the NMI handler for the time in can cause #VC exceptions. Signed-off-by: Joerg Roedel