https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #73 from Ronald ---
Assuming it's nouveau specific and not drm:
2705de0 drm/nouveau: fix handling empty channel list in ioctl's
is between 3.8.6 and 3.8.7. However, there are some generic DRM changes as
well:
faec22f KMS: fix EDID
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #72 from Mr-4 ---
Things have been pretty stable with 3.8.1, but it is getting a bit "twitchy"
with 3.8.7 - on two separate occasions I've got the following error on restore:
kernel: nouveau [ DRM] re-enabling device...
kernel:
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #71 from Ronald ---
You should test with a vanilla kernel to exclude distro tampering of the
kernel. Furthermore, maybe test if the above patch introduces this regression?
Whatever you do, I suggest you open a new bug for this to get
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #70 from Mr-4 ---
(In reply to comment #69)
> Is the crash consistent? Does it happen every time? The fix should be
> applied at v3.7.3:
No.
I've downgraded the kernel slightly - from 3.7.9-201 to 3.7.9-101 (both
official releases fr
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #69 from Ronald ---
Whoops, typo in first sentence. What I meant was:
Is the crash consistent? Does it happen every time? The fix should be applied
at v3.7.3:
ronald@Alpha /usr/src/linux :) $ git log --oneline --no-merges v3.7^...v3
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #68 from Ronald ---
Is it consistent, git says 'no':
ronald@Alpha /usr/src/linux :) $ git log --oneline --no-merges v3.7.4...v3.7.9
-- drivers/gpu/drm
330b8ab drm/nouveau: add lockdep annotations
c7fc196 drm/radeon: Calling object_un
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #67 from Mr-4 ---
Here we go again...
After experiencing the joy and the meaning of "stability" and what it feels
like, I decided to upgrade to kernel 3.7.9 (the latest stable) from 3.7.4 and
voila... this bug reared its ugly head ag
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #66 from michael.weira...@gmail.com ---
(In reply to comment #65)
> (In reply to comment #44)
> I am experiencing the same problem on my w520 with Nvidia GF106 [Quadro
> 2000M].. I get the same symptoms / messages. Did you find a fix f
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #65 from Petr Stastny ---
(In reply to comment #44)
I am experiencing the same problem on my w520 with Nvidia GF106 [Quadro
2000M].. I get the same symptoms / messages. Did you find a fix for the
problem?
I noticed that suspend / res
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #64 from Mr-4 ---
(In reply to comment #63)
> Only v3.8 carries the fix.
Nope! My own distro (Fedora, as it turns out) had this patch already in their
main nv tree as of kernel 3.7.4, so there was no need for me to apply it
separately
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #63 from Ronald ---
Did you apply the patch from comment #36?
https://bugs.freedesktop.org/show_bug.cgi?id=50121#c36
Only v3.8 carries the fix.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #62 from francoism ---
Sorry for not replying (for a long time).
I'm still having this issue when resume (gives RGB-stripes/freeze).
The following packages are installed from the Arch Linux repo:
nouveau-dri 9.0.2-1
xf86-video-nouve
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #61 from Mr-4 ---
(In reply to comment #60)
> You can put the following line:
>
> "echo 40 > /sys/class/drm/card0/device/pwm0"
>
> In a file in
>
> /usr/lib/pm-utils/sleep.d/
Thanks Roland, I'll try that, though, ideally, I would h
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #60 from Ronald ---
(In reply to comment #59)
You can put the following line:
"echo 40 > /sys/class/drm/card0/device/pwm0"
In a file in
/usr/lib/pm-utils/sleep.d/
Check out the other files on the format/arguments. Make sure you h
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #59 from Mr-4 ---
(In reply to comment #58)
> Created attachment 73597 [details] [review]
> Backport for 3.5 (and may be 3.6) - fixed again
I have to say, I didn't expect for this to be fixed, but this time it looks as
though this nas
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Herton Krzesinski changed:
What|Removed |Added
Attachment #73488|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #57 from Marcin Slusarz ---
This backported patch will crash on nv10-nv17 - priv->bo is only created for
chipsets >= nv17.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #56 from Ronald ---
Spot on! It worked :)
Just found a small window to test:
- 3.5.7+patch(v2): success! 5 cycles, clean dmesg
- 3.6.9+patch(v2): success! 5 cycles, clean dmesg
Backporting this will make a lot of people happy. Than
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #55 from Ronald ---
I will try to test this weekend, cannot promise anything though.
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouv
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Herton Krzesinski changed:
What|Removed |Added
Attachment #73421|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #53 from Herton Krzesinski ---
Created attachment 73421
--> https://bugs.freedesktop.org/attachment.cgi?id=73421&action=edit
Backport for 3.5 (and may be 3.6)
For who is still using or interested in kernel 3.5 or 3.6, can you try/v
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Marcin Slusarz changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Florian Mickler changed:
What|Removed |Added
CC||flor...@mickler.org
--- Comment #52 fr
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #51 from Mr-4 ---
(In reply to comment #50)
> Maybe you can send a patch to Fedora? Maybe they will happily backport it
> for you. Especially since they try to be bleeding edge and all...
I would have if I knew how to fix it and make
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #50 from Ronald ---
@Mr-4, I assumed that most of the rework went in at v3.5 regarding power
management. But v3.7 had the huge overhaul everyone is talking about. So
therefore I assumed that the patch might work at v3.5 and v3.6 as we
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #49 from Mr-4 ---
(In reply to comment #38)
> This patch is not directly applicable to kernels < 3.7, although porting it
> is trivial.
"Porting" of that patch against 3.6 is far from "trivial" - exercise in
futility more like!
There
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #48 from Mr-4 ---
(In reply to comment #46)
> It will be a while until Fedora ships 3.7+ kernels by default. If you want
> to help test vanilla kernels there is a well maintained repo to do so.
>
> See https://fedoraproject.org/wiki/
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #47 from Marcin Slusarz ---
michael.weirauch: this seems to be another bug
--
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #46 from Lucas Stach ---
(In reply to comment #45)
> I am currently waiting for 3.7 to become mainstream for my distro (I am
> using Fedora) so that I could give it a go, but I don't hold my breath to be
> honest.
>
It will be a whil
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #45 from Mr-4 ---
(In reply to comment #30)
> @Raphaël Droz: What kernel version are you using? And maybe the kernel
> version from Mr-4 might be useful as well. Just to confirm.
Apologies for this late reply, but since I first starte
https://bugs.freedesktop.org/show_bug.cgi?id=50121
michael.weira...@gmail.com changed:
What|Removed |Added
Attachment #65931|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Marcin Slusarz changed:
What|Removed |Added
CC||mr.dash.f...@googlemail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #42 from Raphaël Droz ---
perfect!
the last patch did the trick (tested with vanilla 3.7).
I hibernated several times, even with a running instance of glxgears.
No problem anymore.
On my side the startup time is not especially long.
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #41 from Ronald ---
I'm waiting on filing a bug for the NV4E. It seems that nouveau works properly,
I don't see any delays or errors at all in dmesg. It is whining about the b43
firmware, but even if I unload the driver the resume sti
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #40 from Ronald ---
Marcin, I already filed bug #23223 for the NV4B, I'll update that one. It's
quite old, but I'll continue from there. I'll open a new one for the NV4E.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #39 from Ronald ---
Ok, I will file seperate bugs for these cards.
FYI, the FX5200 survived 11 cycles so far without a hitch. Thanks a lot =)
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #38 from Marcin Slusarz ---
This patch is not directly applicable to kernels < 3.7, although porting it is
trivial.
WRT other bugs: Yes, I would like to see separate bug reports. Suspend/resume
should work for all cards and not take
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #37 from Ronald ---
Reverted the old patch and applied the new one. Did this on the same
v3.8rc1+nouveau kernel tree. It only rebuilded the nouveau specific files.
The FX5200 survived 4 consecutive cycles with this patch. It seems to
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Marcin Slusarz changed:
What|Removed |Added
Attachment #72085|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #35 from Marcin Slusarz ---
Good. Please open new bug reports for the other issues you have with these (4B
& 4E) boxes.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #34 from Ronald ---
Just tested v3.8rc1+nouveau+patch on an NV4E. Suspend and resume works! Though
it takes about 1 minute before it shuts down (hangs somewhere). And maybe 1 or
2 minutes to resume (before screen is restored).
Restar
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #33 from Ronald ---
The FX5200 still functions and survived another cycle.
I went ahead and tested your patch on a 'G73 (NV4B)' as well. Since modeset
became mandatory suspend/resume never worked (anymore). It suspended, but
resumed
https://bugs.freedesktop.org/show_bug.cgi?id=50121
--- Comment #32 from Ronald ---
Seems to have fixed the bug. It has survived three consecutive suspend and
resume cycles in a row. This was not possible after v3.5 without your supplied
fix.
So it seems that the direct symptoms have been resolve
https://bugs.freedesktop.org/show_bug.cgi?id=50121
Ronald changed:
What|Removed |Added
Summary|[Regression] NV34 Fx5200 & |[Regression] Since kernel
|NV
44 matches
Mail list logo