search for: 80000002

...718000 systemd-logind[757]] [ +0.000010] nouveau 0000:01:00.0: gr: GPC1/PROP trap: 00000020 [RT_HEIGHT_OVERRUN] x = 1888, y = 1060, format = 2a, storage type = 0 [ +0.000043] nouveau 0000:01:00.0: gr: TRAP ch 6 [023f718000 systemd-logind[757]] [ +0.000004] nouveau 0000:01:00.0: gr: ROP0 80000000 80000002 [ +0.000004] nouveau 0000:01:00.0: gr: ROP1 80000000 80000002 [ +0.000004] nouveau 0000:01:00.0: gr: ROP2 80000000 80000002 [ +0.000010] nouveau 0000:01:00.0: gr: TRAP ch 6 [023f718000 systemd-logind[757]] [ +0.000004] nouveau 0000:01:00.0: gr: ROP0 80000000 80000002 [ +0.000004] nouveau 0000:...

https://bugs.freedesktop.org/show_bug.cgi?id=93629 Bug ID: 93629 Summary: [NVE6] complete system freeze, PGRAPH engine fault on channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

...arting on pid 0xa First chance exception: page fault on read access to 0x1008002f in 32-bit code ( 0x7bb6b48a). In 32 bit mode. Register dump: CS:0073 SS:007b DS:007b ES:007b FS:ffff GS:0033 EIP:7bb6b48a ESP:7b92fc60 EBP:7b92fc64 EFLAGS:00010212( - 00 - RIA1) EAX:1007ffff EBX:7ac0682c ECX:80000002 EDX:7b92fd5c ESI:80000002 EDI:00000046 Stack dump: 0x7b92fc60: 80000002 7b92fc98 7abf3ced 7c0030e0 0x7b92fc70: b7e6aff4 7c00bcf0 00000046 00000000 0x7b92fc80: 00000000 b7fd4234 00000000 7ac0682c 0x7b92fc90: 7c00bcf0 00000046 7b92fcb8 7abf3e4f 0x7b92fca0: 80000002 7a98b014 00000000 000f003f 0x...

https://bugs.freedesktop.org/show_bug.cgi?id=80901 Priority: medium Bug ID: 80901 Assignee: nouveau at lists.freedesktop.org Summary: [NVCF] PWM fan speed too high under kernel 3.15 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: gianni at rootcube.net Hardware: x86-64 (AMD64)

Hello, I've just been hit by this old bug which is still present in 4.14: https://bugs.freedesktop.org/show_bug.cgi?id=80675 On MCP79 (ION), when stolen memory is set to 32MB in BIOS, console is blank but X11 works. When the stolen memory is increased to 64MB, console works fine. Bisected it to this: 4f6029da58ba9204c98e33f4f3737fe085c87a6f is the first bad commit commit

...ompleted in 67us +nouveau: DRM:00000000:00000002: init completed in 66us nouveau: DRM:00000000:0000826f: init running... nouveau: DRM:00000000:0000826f: init children... -nouveau: DRM:00000000:0000826f: init completed in 171us +nouveau: DRM:00000000:0000826f: init completed in 173us nouveau: DRM:80000002:0000003d: init running... nouveau: DRM:80000002:0000003d: init children... -nouveau: DRM:80000002:0000003d: init completed in 66us +nouveau: DRM:80000002:0000003d: init completed in 67us nouveau: DRM:80000003:0000003d: init running... nouveau: DRM:80000003:0000003d: init children... -nouveau: DR...

...The problem is that the first mapping fails: Mapping memory range 0xc0400000 - 0xc1000000 MINI_OS(file=mm.c, line=68) Allocating new L1 pt frame for pt_pfn=36, mfn=ca8, prev_l_mfn=cad, offset=301 (XEN) .../xen-3.0.4-testing.hg/xen/include/asm/mm.h:184:d1 Error pfn 0: rd=ffbe8100, od=ffbf4100, caf=80000002, taf=e8000002 (XEN) mm.c:456:d1 Could not get page ref for pfn 0 (XEN) mm.c:2225:d1 Could not get page for normal update New PT could not be mapped R/W. Now I am puzzled what these hypervisor errors mean, and what I could have done wrong? The code in question is the following: mmu_updates[0...

...pleted in 5709us Nov 24 18:27:28 zeus kernel: nouveau: DRM:00000000:0000006b: init running... Nov 24 18:27:28 zeus kernel: nouveau: DRM:00000000:0000006b: init children... Nov 24 18:27:28 zeus kernel: nouveau: DRM:00000000:0000006b: init completed in 5665us Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000002:0000003d: init running... Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000002:0000003d: init children... Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000002:0000003d: init completed in 5666us Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000003:0000003d: init running... Nov 24 18:27:28 zeus kernel: nou...

...; Nov 24 18:27:28 zeus kernel: nouveau: DRM:00000000:0000006b: init running... > Nov 24 18:27:28 zeus kernel: nouveau: DRM:00000000:0000006b: init children... > Nov 24 18:27:28 zeus kernel: nouveau: DRM:00000000:0000006b: init completed in 5665us > Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000002:0000003d: init running... > Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000002:0000003d: init children... > Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000002:0000003d: init completed in 5666us > Nov 24 18:27:28 zeus kernel: nouveau: DRM:80000003:0000003d: init running... > Nov 24 18:27...

...producible from Fedora-Workstation-Live-x86_64-Rawhide-20180219.n.0.iso > > Did you reproduce it? I tried running supertuxkart on my MCP79 (9400M), got some artefacts, but it did not freeze; the only error I got was “nouveau 0000:03:00.0: fifo: CACHE_ERROR - ch 1 [DRM] subc 0 mthd 0060 data 80000002”. Which version of Mesa, xf86-video-nouveau (or modesetting) did you have in those tests? For reference, I have: Linux: 4.15.4 Mesa: 17.3.5 xf86-video-nouveau: 1.0.15 xorg-server: some 1.19.6 snapshot -- You are receiving this mail because: You are the assignee for the bug. -------------- next...

...from Nick Lee <nvlbox at gmail.com> --- (In reply to Pierre Moreau from comment #5) > I tried running supertuxkart on my MCP79 (9400M), got some artefacts, but it > did not freeze; the only error I got was “nouveau 0000:03:00.0: fifo: > CACHE_ERROR - ch 1 [DRM] subc 0 mthd 0060 data 80000002”. i got same artefact after launch gtk4-demo and after launch disk-usage-analizer > Which version of Mesa, xf86-video-nouveau (or modesetting) did you have in > those tests? curently fedora: kernel-4.16.0-0.rc2.git0.1 mesa-17.3.5-1 xorg-x11-drv-nouveau-1.0.15-3 xorg-x11-server-Xorg-1.19.6-...

...cted dom 0) (XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no reservation headroom (51072,51200) or provided a bad grant ref (00000000) or is dying (1) (XEN) file=/usr/src/redhat/SOURCES/xen-unstable.hg/xen/include/asm/mm.h, line=203) Error pfn 0: rd=ffbec080, od=ff195080, caf=80000002, taf=f0000002 (XEN) DOM24: (file=mm.c, line=350) Could not get page ref for pfn 0 (XEN) DOM24: (file=mm.c, line=2220) Could not get page for mach->phys update I will archive this changset so if anything additional of value can be provided let me know. Regards, Ted ___________________________...

On 06/17/2013 05:41 PM, Michael Giardino wrote: > Kashyap: I have not tried integrating your guest xml but I will look > over it today when I get a chance. Thank you. > > Martin: Below is the output from /proc/cpuinfo. Let me know if there is > anything else that would be helpful in debugging this. Thank you, > Unfotunately, my guess was wrong. If you could run 'cpuid

...00 00000000 00000000 00000000 0000000a 07300403 00000000 00000000 00000603 0000000b 00000000 00000000 0000006f 00000001 0000000c 00000000 00000000 00000000 00000000 0000000d 00000000 00000000 00000000 00000000 80000000 80000008 00000000 00000000 00000000 80000001 00000000 00000000 00000021 2c100800 80000002 65746e49 2952286c 726f4320 4d542865 80000003 37692029 3737342d 50432030 20402055 80000004 30342e33 007a4847 00000000 00000000 80000005 00000000 00000000 00000000 00000000 80000006 00000000 00000000 01006040 00000000 80000007 00000000 00000000 00000000 00000100 80000008 00003027 00000000 00000000 00...

...0d (XEN) Rangesets belonging to domain 0: (XEN) Interrupts { 0-255 } (XEN) I/O Memory { 0-febff, fec01-fedff, fee01-ffffffff } (XEN) I/O Ports { 0-1f, 22-3f, 44-60, 62-9f, a2-cfb, d00-ffff } (XEN) Memory pages belonging to domain 0: (XEN) DomPage list too long to display (XEN) XenPage 00000bed: caf=80000002, taf=e8000002 (XEN) XenPage 00000bec: caf=80000001, taf=e8000001 (XEN) XenPage 00000beb: caf=80000001, taf=e8000001 (XEN) XenPage 00000bea: caf=80000001, taf=e8000001 (XEN) XenPage 00000be9: caf=80000002, taf=e8000002 (XEN) VCPU information and callbacks for domain 0: (XEN) VCPU0: CPU0 [has=T] flag...

...file "/windows/C/windows/fonts/cubant.FOT" err = 2 fixme:bitblt:X11DRV_BitBlt potential optimization - client-side DIB copy ... fixme:bitblt:X11DRV_BitBlt potential optimization - client-side DIB copy fixme:scroll:ScrollBarWndProc Unimplemented style SBS_SIZEBOX. fixme:reg:RegUnLoadKeyW (80000002,L"PolicyData"): stub fixme:reg:RegUnLoadKeyW (80000002,L"PolicyData"): stub After acknowledging the message window, the following lines appear in the shell: fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS ... fixme:win32:DeviceIoControl Unimplem...

...000000e8 0000002c +0000000b 00000000 00000000 0000006f 0000002c 0000000c 00000000 00000000 00000000 00000000 0000000d 00000000 00000000 00000000 00000000 80000000 80000008 00000000 00000000 00000000 -80000001 00000000 00000000 00000001 2c100000 +80000001 00000000 00000000 00000001 2c100800 80000002 20202020 6e492020 286c6574 58202952 80000003 286e6f65 43202952 45205550 36322d35 80000004 204c3035 20402030 30382e31 007a4847 Could this be enough difference to throw cpu-detection off? Struan >>> Martin >>> >>>> Struan >>>> >>>> On 03/03...

...reports it has "syscall" and in the > first one it doesn't. Since "syscall" is x86_64 instruction used > instead of i386's "int 0x80" (IIRC) it makes sense that it is missing > on 32-bit CPU (when the code is running in 32-bit mode). > >> 80000002 20202020 6e492020 286c6574 58202952 >> 80000003 286e6f65 43202952 45205550 36322d35 >> 80000004 204c3035 20402030 30382e31 007a4847 >> >> Could this be enough difference to throw cpu-detection off? >> > Even one bit is enough if that bit represents a flag whic...

...t;f3> ab a1 e4 ec 3a c0 89 74 24 04 89 04 24 e8 39 dc 04 00 8b 45 Random while updating a package with yum: 14857 kernel: Oops: 0003 [#4] 14857 kernel: SMP 14857 kernel: CPU: 0 14857 kernel: EIP is at pgd_free+0x104/0x140 14857 kernel: eax: 00000000 ebx: 00000000 ecx: 00000400 edx: 80000002 14857 kernel: esi: e8545000 edi: e8545000 ebp: e8c8bd68 esp: e8c8bd48 14857 kernel: ds: 007b es: 007b ss: 0069 14857 kernel: Process yum (pid: 2721, threadinfo=e8c8a000 task=e9f65550) 14857 kernel: Stack: <0>e8545000 00000000 00000003 e854c1d8 e8546018 e8c6f040 e8c6f088 e8c6f040...

Hello, I''m trying to get PDB working in accordance with the instructions at http://www.cl.cam.ac.uk/~sos22/replay.bk/docs/misc/XenDebugger-HOWTO and a message from this list: http://lists.xensource.com/archives/html/xen-devel/2004-08/msg00017.html When I try to build pdb I first get errors because the Makefile is configured to treat warnings as errors, and there are some warnings.