search for: fault

The SVM page fault handler groups faults into a range of contiguous virtual addresses and requests hmm_range_fault() to populate and return the page frame number of system memory mapped by the CPU. In preparation for supporting large pages to be mapped by the GPU, process faults one page at a time. In addition, use t...

The SVM page fault handler groups faults into a range of contiguous virtual addresses and requests hmm_range_fault() to populate and return the page frame number of system memory mapped by the CPU. In preparation for supporting large pages to be mapped by the GPU, process faults one page at a time. In addition, use t...

https://bugs.freedesktop.org/show_bug.cgi?id=67255 Priority: medium Bug ID: 67255 Assignee: nouveau at lists.freedesktop.org Summary: black screen after resuming from Hibernate QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: michele.cane at

On Tue, 17 Sep 2019 at 01:18, Thierry Reding <thierry.reding at gmail.com> wrote: > > From: Thierry Reding <treding at nvidia.com> > > The fault information register contains data about the aperture that > caused the failure. This can be useful in debugging aperture related > programming bugs. Should this be parsed for fault buffer entries too? > > Signed-off-by: Thierry Reding <treding at nvidia.com> > --- > drive...

...gt; > > > > > > > > I really do not think there is anything DEBUG_SG specific here. Why you > > > > > > simply do not follow should_failslab path or even reuse the function? > > > > > > > > > > CONFIG_DEBUG_SG is enabled by default in RHEL and Fedora debug kernel (if > > > > > you don't like CONFIG_DEBUG_SG, pick any other option that is enabled > > > > > there). > > > > > > > > Are you telling me that you are shaping a debugging functionality basing > > >...

I would like to know approximately the overall execution flow when the guest O/S page fault - how is the page fault transfer to a page fault in the host O/S? Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...nvkm/engine/disp/nv50.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/disp/nv50.c @@ -434,7 +434,8 @@ nv50_disp_dptmds_war(struct nvkm_device *device) case 0x96: case 0x98: case 0xaa: - case 0xac: +/* NVIDIA MCP79/MCP7A "No Signal" */ +/* case 0xac: */ return true; default: break; -- 2.7.4

Hi, I'm a PhD student at UIUC and I am using LLVM to add fault-tolerance capabilities to applications. I would like to evaluate my framework by performing fault-injections (fault-insertions) in the application. Essentially, I want to corrupt an LLVM value at the time of its definition and study the behavior of the program under this condition. I would like to...

From: Thierry Reding <treding at nvidia.com> The fault information register contains data about the aperture that caused the failure. This can be useful in debugging aperture related programming bugs. Signed-off-by: Thierry Reding <treding at nvidia.com> --- drivers/gpu/drm/nouveau/include/nvkm/subdev/fault.h | 1 + drivers/gpu/drm/nouveau/nvkm...

Hi List, Any ideas what is wrong with controller? It is running latest 5.x series of centos and driver spills out following warnings at random times: mptbase: ioc0: WARNING - IOC is in FAULT state (1600h)!!! mptbase: ioc0: WARNING - Issuing HardReset from mpt_fault_reset_work!! mptbase: ioc0: Initiating recovery mptbase: ioc0: WARNING - IOC is in FAULT state!!! mptbase: ioc0: WARNING - FAULT code = 1600h mptbase: ioc0: Recovered from IOC FAULT mptbase: ioc0: WARNING - mpt_fa...

...-16 21:08:36.000000000 +0200 +++ linux-2.6/lib/Kconfig.debug 2018-04-25 15:56:16.000000000 +0200 @@ -1503,6 +1503,10 @@ config NETDEV_NOTIFIER_ERROR_INJECT If unsure, say N. +config FUNCTION_ERROR_INJECTION + def_bool y + depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES + config FAULT_INJECTION bool "Fault-injection framework" depends on DEBUG_KERNEL @@ -1510,10 +1514,6 @@ config FAULT_INJECTION Provide fault-injection framework. For more details, see Documentation/fault-injection/. -config FUNCTION_ERROR_INJECTION - def_bool y - depends on HAVE_FUNCTION_...

Some users are hitting this panic in network_alloc_rx_buffers() when running a big network intensive app: /* Check return status of HYPERVISOR_dom_mem_op(). */ if ( rx_mcl[nr_pfns].args[5] != nr_pfns ) panic("Unable to reduce memory reservation\n"); I''m not clear on what is happening here. Are the domains changing size? Which memory reservation is being

...ms.html > does not seems to have most of these terms. > > I am particularly curious about PCE[0-3]. > But also about CLIENT, that seems different and mysterious. > > I wonder if it is possible to write: > nouveau.debug=info,PDISP=debug > to have the info debug level as the default, but for PDISP have the debug level > > Also, my interest is linked to the state of GPU graph given after a context switch timeout that looks like: > [ 1696.780305] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] > [ 1696.780361] nouveau 0000:01:00.0: fifo:000000:00[ gr]...

On Tue, 17 Sep 2019 at 01:18, Thierry Reding <thierry.reding at gmail.com> wrote: > > From: Thierry Reding <treding at nvidia.com> > > The engine field in the FIFO fault information registers is actually 9 > bits wide. Looks like this is true for fault buffer parsing too. > > Signed-off-by: Thierry Reding <treding at nvidia.com> > --- > drivers/gpu/drm/nouveau/nvkm/subdev/fault/gv100.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-...

Hi How do we get the number of page faults done by a guest in a scheduling epoch? Assuming only one VCPU per guest, can I get it from vcpu_info[]? I hope this is not a vey trivial question :) thanks Chintu -- View this message in context: http://xen.1045712.n5.nabble.com/Getting-the-page-fault-count-for-domU-tp4847541p...

On 04/25/2018 01:02 PM, Mikulas Patocka wrote: > > > From: Mikulas Patocka <mpatocka at redhat.com> > Subject: [PATCH v4] fault-injection: introduce kvmalloc fallback options > > This patch introduces a fault-injection option "kvmalloc_fallback". This > option makes kvmalloc randomly fall back to vmalloc. > > Unfortunatelly, some kernel code has bugs - it uses kvmalloc and then Unfortunately,...

On 04/25/2018 01:02 PM, Mikulas Patocka wrote: > > > From: Mikulas Patocka <mpatocka at redhat.com> > Subject: [PATCH v4] fault-injection: introduce kvmalloc fallback options > > This patch introduces a fault-injection option "kvmalloc_fallback". This > option makes kvmalloc randomly fall back to vmalloc. > > Unfortunatelly, some kernel code has bugs - it uses kvmalloc and then Unfortunately,...

...buntu 16) I have windows 2016(member domain), running IIS... But my site in IIS, use user the DC (in portal), but now dont worked , is much erro in log.samba when autentcation in site with user dc... Any Idea? Regards ---------------------------- [2018/05/28 17:35:52.085263,  0] ../lib/util/fault.c:78(fault_report)   =============================================================== [2018/05/28 17:35:52.086760,  0] ../lib/util/fault.c:79(fault_report)   INTERNAL ERROR: Signal 11 in pid 14753 (4.8.2)   Please read the Trouble-Shooting section of the Samba HOWTO [2018/05/28 17:35:52.091457, ...

...tallation: Code: wine /media/cdrom/setup err:wineboot:pendingRename couldn't get file attributes (2) fixme:spoolsv:serv_main (0 (nil)) err:ole:marshal_object object doesn't expose interface {be6115a1-7de5-48dc-ad2a-25060e00fce2}, failing with error 0x80004002 err:rpc:I_RpcReceive we got fault packet with status 0x80004002 err:ole:ClientIdentity_QueryMultipleInterfaces IRemUnknown_RemQueryInterface failed with error 0x80004002 err:ole:marshal_object object doesn't expose interface {be6115a1-7de5-48dc-ad2a-25060e00fce2}, failing with error 0x80004002 err:rpc:I_RpcReceive we got fault...

...s://nouveau.freedesktop.org/NouveauTerms.html does not seems to have most of these terms. I am particularly curious about PCE[0-3]. But also about CLIENT, that seems different and mysterious. I wonder if it is possible to write: nouveau.debug=info,PDISP=debug to have the info debug level as the default, but for PDISP have the debug level Also, my interest is linked to the state of GPU graph given after a context switch timeout that looks like: [ 1696.780305] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] [ 1696.780361] nouveau 0000:01:00.0: fifo:000000:00[ gr]: 8006e005: busy 1...