https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #34 from Raphaël Droz ---
Created attachment 75747
--> https://bugs.freedesktop.org/attachment.cgi?id=75747&action=edit
netconsole log of a NV34 crash when mem > 3GB
Finally I took some time to seriously (netconsole) dig "how" it c
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #33 from Raphaël Droz ---
Created attachment 72253
--> https://bugs.freedesktop.org/attachment.cgi?id=72253&action=edit
nouveau CALL_SUBR_ACTIVE errors unpatched 3.7.0
oops, I spoke too soon. It just happened again with an unpatche
https://bugs.freedesktop.org/show_bug.cgi?id=46557
Marcin Slusarz changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=46557
Marcin Slusarz changed:
What|Removed |Added
Attachment #72201|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #31 from Raphaël Droz ---
I switched to 3.7.0 and I can't reproduce either. All seems stable with 4GB.
I'm confident, but I may need to do longer testing.
Note that I can consistently throw "nouveau: ib channel create, -22" messages
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #30 from Salah Coronya ---
As of kernel 3.7, xorg-1.13, nouveau DDX 1.0.4, mesa-9.0 all the errors related
to ths bug are gone for me - no distortion, no crashes, and no CACHE_ERROR,
even after switching VT and running accelerated pro
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #29 from Marcin Slusarz ---
Created attachment 72201
--> https://bugs.freedesktop.org/attachment.cgi?id=72201&action=edit
limit vm size to 31 bits (nv04-nv40,nv45)
Ok, original Salah's issue seems to be fixed. Xorg crashes and CACH
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #28 from Raphaël Droz ---
I should add that I've no problem with 3GB. Problem arises when I add 1 more
GB.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nou
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #27 from Raphaël Droz ---
Created attachment 70841
--> https://bugs.freedesktop.org/attachment.cgi?id=70841&action=edit
nouveau CALL_SUBR_ACTIVE errors using dma_bits=32 kernel on NV34
I tried your suggestion about setting dma_bits
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #26 from m.b.lankho...@gmail.com ---
Judging from the errors, I'd say it can't look up the handle it created.
Diving into the old dma implementation seems
The handles for vram and gart could not be looked up, so guessing an invalid
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #25 from Raphaël Droz ---
Created attachment 69231
--> https://bugs.freedesktop.org/attachment.cgi?id=69231&action=edit
dmesg|egrep -i 'drm|agp|fb'
I regularly encounter a similar trace as in the first attachment (attachment
57574)
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #24 from Emil Velikov ---
(In reply to comment #23)
> here is the output for nouveau from dmesg
>
> ...
> [1.098755] nouveau :00:05.0: >setting latency timer to 64
> ...
> [ 67.077190] nouveau E[ DRM] fail ttm_validate
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #23 from bal...@email.de ---
here is the output for nouveau from dmesg
[1.098755] nouveau :00:05.0: >setting latency timer to 64
[1.099370] nouveau [ DEVICE][:00:05.0] BOOT0 : 0x04e000a2
[1.099374] nouveau [ D
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #22 from bal...@email.de ---
For my system (reported Bug 54988) it starts up now and works for a RAM size of
3G.
But after logging into the gnome desktop the screen becomes blurry and
and while trying to open any gnome menu, the scre
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #21 from Salah Coronya ---
Created attachment 68024
--> https://bugs.freedesktop.org/attachment.cgi?id=68024&action=edit
dmesg of new kernel
It runs FAR better - the distortion and lockups are gone, and the picture us
substantially
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #20 from Marcin Slusarz ---
I talked to Ben about this bug at XDC2012 and he told me we are using
nv04-style virtual memory interface, because of some then unknown bugs in nv4x
implementation - and this is probably the reason why you
https://bugs.freedesktop.org/show_bug.cgi?id=46557
Marcin Slusarz changed:
What|Removed |Added
CC||bal...@email.de
--- Comment #19 from Ma
https://bugs.freedesktop.org/show_bug.cgi?id=46557
Salah Coronya changed:
What|Removed |Added
Summary|nouveau: NV4E acceleration |nouveau: NV4E acceleration
18 matches
Mail list logo
