https://bugs.freedesktop.org/show_bug.cgi?id=59168

--- Comment #10 from Ronald <ronald...@gmail.com> ---
Michael Weirauch,

I noticed your whitty comment on bug #50121 and thought that I should report my
debug findings on issue's like these. I have a comparable bug with my 7300GT
(NV4B) at bug #23223. The card suspends fine, but resume's with a lot of
garbage.

- Altough both cards are not the same, in fact the differences are probably
huge.
- Altough I'm not a developer or expert in any of this.
I'm just sharing my knowledge here so you could hopefully aid the developers on
doing their magic.

First:
- Martin Slusarz mentions in bug #23223 comment 18 a script limiter. Maybe you
can try. I report my results at comment 19 in that same bug. Please note there
is an off by one error mentioned in comment 20 you should take into account if
you start to use it. But it works fine.

This method probably helps you, as "nouveau.config=DEVINIT=NvForcePost=1" also
gave garbage in your case. Which means that these scripts are doing something
wrong or unexpected/unknown.

Do this with the latest git kernel plus the latest nouveau tree.

Second:
- Comment 8 in this bug mentioned that switching to the proprietary driver
fixed his issue. This is not bad news per sé. As this could give hope of
gaining more intel by doing an mmiotrace of a working state:

http://nouveau.freedesktop.org/wiki/MmioTrace

Also check bug #23223 on my findings while doing this. It's best to not use X
or Wayland, but only to enable udev. You have to use mmiotrace across a
suspend/resume cycle. I think without using X is the best way to do it. Try to
compress the resulting file with 'xz --best'. I did that, and was able to
upload it to the bug itself.

Do this with the latest git kernel plus the latest nouveau tree.

Third and final:
- I made a VBIOS dump to aid in debugging, which was also requested by Marcin
Slusarz.

https://bugs.freedesktop.org/show_bug.cgi?id=23223#c14

You have to use a v3.6(.9) kernel to use the mechanism I used since that piece
of infrastructure was not ported to later kernel versions during the big rework
in v3.7. Also I'm not sure, but it is said you can also retrieve a VBIOS from
an MMIOTRACE. But alas, I'm not sure so it might be a good idea to seperately
post it.

Above procedures should keep you occupied on a nice rainy sunday afternoon. If
you are going to do this, please mention that you do this on IRC. Maybe someone
might get interested in this as more information has become available.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

Reply via email to