similar to: nouveau: kernel rejected pushbuf: Invalid argument

Thanks for your response. I am able to capture a few more lines of the dump (see console-output.txt). dmesg output attached. My bitmap is 720x512. Below is the library versions, and amount of vram. Any feedback is appreciated. Thanks. Steve [steve at localhost ~]$ lspci -nn -d 10de: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 01:00.1

If you (or Java, behind your back) is using an indirect draw, that could explain the failures - I only got those "fully" right fairly recently. These, and a few other matters, should be fixed with a more recent mesa version - 11.2.1 was just released, I'd recommend trying with that. Another simple explanation is if your application is multithreaded and is drawing concurrently from

On Thu, Apr 21, 2016 at 11:17 AM, Li, Stephen <Steve.Li at imaginecommunications.com> wrote: > Hi, > > > > I am getting a crash in nouveau in my application. It’s basically a java > application, and I am loading a bitmap into an opengl texture and showing it > in a panel. Below is a snippet of the console output. Sometimes I will get a > lock up instead of a crash. My

Hello, I am kernel engineer working on PV-OPS kernel trying to get it work in Dom0 with an NVidia (NV30 right now) card. But there are issues, such as that the pv-ops kernel has a different understanding of memory (for details check out: http://wiki.xensource.com/xenwiki/XenPVOPSDRM). I've fleshed out most of them (like GART had the wrong phys addresses, ouch!), but the one that I am

Can anyone work out why my callerid doesn't work on my isdn4Linux with asterisk (or without asterisk for that matter)... This used to work fine, and I am quite confident that the telco is sending callerid information (because they always do on all ISDN lines standard, only extra cost on POTS lines). This is the information from dmesg, whether asterisk is running or not: isdn_net: Incoming

https://bugs.freedesktop.org/show_bug.cgi?id=68488 Priority: medium Bug ID: 68488 Assignee: nouveau at lists.freedesktop.org Summary: Lockup and reboot on T61 with nouveau driver/exa QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: All Reporter: a9016009 at gmx.de

https://bugs.freedesktop.org/show_bug.cgi?id=79823 Priority: medium Bug ID: 79823 Assignee: nouveau at lists.freedesktop.org Summary: Mozilla apps freeze on startup with nouveau-dri-10.2.1 libs on dual-screen Severity: normal Classification: Unclassified OS: Linux (All) Reporter: natrio at

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #8 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I desactivated kscreenlocker which resolve the reactivate problem. But the problem of corrupt screen when starting different programs remains and is worst since the last zypper dup. I found this error still related to nouveau when the two screen got corrupted ov

https://bugs.freedesktop.org/show_bug.cgi?id=92438 Bug ID: 92438 Summary: Segfault in pushbuf_kref when running the android emulator (qemu) on nv50 Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Hello, Could someone briefly describe (or point me to the documentation) what can be a reason for getting NV_PFIFO_INTR_DMA_PUSHER status (nouveau_fifo_irq_handler). This started happening immediately after I set the nouveau_vram_pushbuf flag to TRUE ,it's 100% repetitive and causes fences not to be signaled. Below is the debug log from moment of creation of fifo 1 to some point in time

Hi list, on my workstation I've a md raid (mirror) for / on md1. This raid has 2 ssd as members (each corsair GT force 120GB MLC). This disks are ~ 5 years old. Today I've checked my ssds smart status and I get: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 050 Pre-fail Always -

https://bugs.freedesktop.org/show_bug.cgi?id=107963 Bug ID: 107963 Summary: kernel rejected pushbuf: Invalid argument Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Hi List, I've been getting the following EDAC memory errors EDAC MC0: CE page 0xeb0dd, offset 0x0, grain 4096, syndrome 0x45, row 3, channel 0, label "": i82875p CE and from this seeing that these errors have been corrected. Checking cat /sys/devices/system/edac/mc/mc0/csrow3/ch0_ce_count gives me a count of 4 thus I now know that csrow3 - ch0 is the problem My question is, how

https://bugs.freedesktop.org/show_bug.cgi?id=96952 Bug ID: 96952 Summary: Noveau driver doesn't working well when in Kdenlive Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee:

http://bugs.freedesktop.org/show_bug.cgi?id=11868 Summary: Starting X for the second time fails (without reloading drm modules) Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hello, These are error messages I get when I try to call a number over CAPI channel. -- Executing SetCallerID("SIP/xlite1-3b80", "0") in new stack -- Executing Dial("SIP/xlite1-3b80", "CAPI/hfcpci/b17") in new stack > data = hfcpci/b17 > capi request for interface 'hfcpci' == hfcpci: Call CAPI/hfcpci/b17-1 (pres=0x00,

I'm trying to use an hfc based pci card with asterisk but every call fails falling in the congestion extension. exten => _0.,1,Dial(${TRUNK}:${EXTEN:${TRUNKMSD}}||tr) exten => _0.,2,Congestion Looking in the syslog i can see: isdn: HiSax,ch0 cause: E001B it seems that this is a terrible error when arrives... hard to tell what is the cause. Also terrible is finding a lot of material

Local APIC timer may stop at deep C state (C3/C4...) entry/exit. this patch add the logic that use platform timer (HPET) to reenable local APIC timer at C state entry/exit. Signed-off-by: Wei Gang <gang.wei@intel.com> Signed-off-by: Yu Ke <ke.yu@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Dear Sirs. It seems to me a never ending story. We run a box with a TYAN Thunder 2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise 1600 RAID adapter and additional Intel 1000/Pro server type (64 bit) GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this state was really hard! It is a story similar to that what happend when we changed towards FreeBSD

As far as i see, we reserve the bo in the gem pushbuf ioctl, and unreserve after the pushbuf and the fence have been emitted. This assumption holds if bo moves happen on the same channel or if a cpu copy happens and we're waiting on fences. But for nv50 it is very common for the bo move to happen on the kernel fifo, which does not guarantee anything. Is there any safety i missed? Maarten.