>From recent additional locking in nouveau, it looks like we see
recursive lock acquisition in 3.8-rc6:
nouveau [ DEVICE][:01:00.0] BOOT0 : 0x0e7150a2
nouveau [ DEVICE][:01:00.0] Chipset: GK107 (NVE7)
nouveau [ DEVICE][:01:00.0] Family : NVE0
nouveau [ VBIOS][:01:00.0] checking PR
https://bugs.freedesktop.org/show_bug.cgi?id=59242
Andrew Randrianasulu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=60007
--- Comment #16 from Cornel Panceac ---
still, there is this pattern that i've seen both on fedora 17 (at kernel crash)
and on fedora 18, while opening some big jpegs in eye of gnome. this suggests
there are some other common issues, not fixed ye
https://bugs.freedesktop.org/show_bug.cgi?id=56461
--- Comment #44 from Marcin Slusarz ---
You can use mmiotrace to trace all register reads and writes and then parse it
with demmio (from envytools) to have names attached to registers.
http://nouveau.freedesktop.org/wiki/Development
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=56461
--- Comment #43 from Chris Paulson-Ellis ---
Created attachment 74152
--> https://bugs.freedesktop.org/attachment.cgi?id=74152&action=edit
console output for fading to black cb75d97e + 3bb076af + 92441b22 + i2c hacks +
gart size fix
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=56461
--- Comment #42 from Chris Paulson-Ellis ---
I found the bug in commit cb75d97e that results in the incorrect GART aperture
and fixed it with this patch:
--- a/drivers/gpu/drm/nouveau/nouveau_compat.c
+++ b/drivers/gpu/drm/nouveau/nouveau_compat
On Sun, Feb 03, 2013 at 09:07:56PM +0100, Marcin Slusarz wrote:
> Current uninitialized sensor detection does not work for me on nv4b and
> sensor returns crazy values (>190°C). It stabilises later, but it's too
> late - therm code shutdowns the machine...
>
> Let's just reset it on init.
>
> Sig
https://bugs.freedesktop.org/show_bug.cgi?id=60007
--- Comment #15 from Marcin Slusarz ---
This is totally different issue - different card generations (nv4x vs nv5x) and
different symptoms (garbage on screen vs kernel crash).
The patch I posted pertains only to nv50/kernel crash issue.
--
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=60007
Marcin Slusarz changed:
What|Removed |Added
Attachment #74114|text/plain |image/jpeg
mime type|
Direct port of commit d1bc38b6673c54af61196056c489383fba8dced8
"nv40/exa: fix shaders on big-endian machines" to nv30.
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=60050
---
src/nv30_exa.c | 272 -
1 file changed, 136 insertions(+), 13
orderly_poweroff cannot be called from atomic context.
Signed-off-by: Marcin Slusarz
---
drivers/gpu/drm/nouveau/core/subdev/therm/temp.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/temp.c
b/drivers/gpu/drm/no
Current uninitialized sensor detection does not work for me on nv4b and
sensor returns crazy values (>190°C). It stabilises later, but it's too
late - therm code shutdowns the machine...
Let's just reset it on init.
Signed-off-by: Marcin Slusarz
---
drivers/gpu/drm/nouveau/core/subdev/therm/nv4
+ the same for shutdown threshold - seems impossible, but shutdown can fail.
Signed-off-by: Marcin Slusarz
---
drivers/gpu/drm/nouveau/core/subdev/therm/temp.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/temp.c
b/driv
13 matches
Mail list logo