Displaying 20 results from an estimated 12749 matches for "faulted".
2020 Jun 19
0
[PATCH 08/16] nouveau/hmm: fault one page at a time
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 the hmm_range
default_flags to fix a corner case where the input hmm_pfns array
is
2020 Jul 01
0
[PATCH v3 1/5] nouveau/hmm: fault one page at a time
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 the hmm_range
default_flags to fix a corner case where the input hmm_pfns array
is
2013 Jul 24
11
[Bug 67255] New: black screen after resuming from Hibernate
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
2019 Sep 17
1
[PATCH 1/6] drm/nouveau: fault: Store aperture in fault information
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?
>
>
2018 Apr 24
4
[PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG
On Tue 24-04-18 13:28:49, Mikulas Patocka wrote:
>
>
> On Tue, 24 Apr 2018, Michal Hocko wrote:
>
> > On Tue 24-04-18 13:00:11, Mikulas Patocka wrote:
> > >
> > >
> > > On Tue, 24 Apr 2018, Michal Hocko wrote:
> > >
> > > > On Tue 24-04-18 11:50:30, Mikulas Patocka wrote:
> > > > >
> > > > >
2007 Jul 29
2
Execution Flow when Guest Page Fault
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
2016 Oct 18
4
NVAC "No Signal"
Fixes "No Signal" via HDMI from NVIDIA Corporation ION VGA (rev b1)
Ref.
"drm/nouveau/disp/g94: implement workaround for dvi issue on fx380"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a
The last working Fedora kernel 4.8.0-0.rc0.git3.1.fc25
Patched and tested with:
$ modinfo -n nouveau
2006 Feb 14
1
[LLVMdev] Fault-injector for LLVM
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
be able to do this in a generic
2019 Sep 16
0
[PATCH 1/6] drm/nouveau: fault: Store aperture in fault information
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/engine/fifo/gk104.c | 3 ++-
2011 Oct 24
1
dell: mtpbase: ioc fault state?
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 -
2018 Apr 25
0
[PATCH] fault-injection: reorder config entries
This patch reorders Kconfig entries, so that menuconfig displays proper
indentation.
Signed-off-by: Mikulas Patocka <mpatocka at redhat.com>
---
lib/Kconfig.debug | 36 ++++++++++++++++++------------------
1 file changed, 18 insertions(+), 18 deletions(-)
Index: linux-2.6/lib/Kconfig.debug
===================================================================
---
2004 Sep 23
16
network_alloc_rx_buffers panic
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
2023 Dec 05
1
Meaning of the engines in paramaters of nouveau module
...e 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 faulted 0 chsw 1 save 1 load 1 chid 5*-> chid 6
> [ 1696.780422] nouveau 0000:01:00.0: fifo:000000:07[ ce2]: 00050005: busy 0 faulted 0 chsw 0 save 0 load 0 chid 5 -> chid 5
> [ 1696.780476] nouveau 0000:01:00.0: fifo:000004:04[ ce0]: 00000000: busy 0 faulted 0 chsw 0 save 0 load 0 chid...
2019 Sep 17
1
[PATCH 2/6] drm/nouveau: fault: Widen engine field
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>
> ---
>
2011 Sep 28
8
Getting the page fault count for domU
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-tp4847541p4847541.html
Sent from the Xen - Dev mailing list
2018 Apr 25
7
[PATCH v4] fault-injection: introduce kvmalloc fallback options
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
2018 Apr 25
7
[PATCH v4] fault-injection: introduce kvmalloc fallback options
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
2018 May 28
5
Error IIS
Hi!
My DC is running Samba 4.8.2(Ubuntu 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)
2008 Apr 01
4
Tiger Woods 2004
TW2004 Installation:
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
2023 Dec 03
1
Meaning of the engines in paramaters of nouveau module
..., 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 faulted 0 chsw 1 save 1 load 1 chid 5*-> chid 6
[ 1696.780422] nouveau 0000:01:00.0: fifo:000000:07[ ce2]: 00050005: busy 0 faulted 0 chsw 0 save 0 load 0 chid 5 -> chid 5
[ 1696.780476] nouveau 0000:01:00.0: fifo:000004:04[ ce0]: 00000000: busy 0 faulted 0 chsw 0 save 0 load 0 chid 0 ->...