https://bugs.freedesktop.org/show_bug.cgi?id=56340
--- Comment #16 from Robert Hancock hancock...@gmail.com ---
It's not really clear that there is a driver issue even though some other
models of graphics cards don't have this problem in these motherboards. It's
quite possible that there is some
https://bugs.freedesktop.org/show_bug.cgi?id=56340
--- Comment #17 from Ilia Mirkin imir...@alum.mit.edu ---
(In reply to comment #15)
(In reply to comment #14)
Again, since this mainboard is a Socket 7 mainboard, I am not able to run
this system on Linux 3.x kernel.
For posterity, I'll
https://bugs.freedesktop.org/show_bug.cgi?id=28152
--- Comment #10 from Ilia Mirkin imir...@alum.mit.edu ---
Naturally I just popped the NV34 out of my system and forgot to test this out.
For next time that it goes in... all I have to run is fvwm? Or is it fvmw2?
fvwm95? Do I need to set up some
https://bugs.freedesktop.org/show_bug.cgi?id=66176
--- Comment #7 from Ilia Mirkin imir...@alum.mit.edu ---
Note that a NV40 reclocking fix just went into the nouveau/linux-2.6 tree:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=dde3164f85035787ce7c63b791ce3c565ff3e3ff
Can you re-test
https://bugs.freedesktop.org/show_bug.cgi?id=62870
Ilia Mirkin imir...@alum.mit.edu changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=51579
Ilia Mirkin imir...@alum.mit.edu changed:
What|Removed |Added
Status|NEEDINFO|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #4 from Ilia Mirkin imir...@alum.mit.edu ---
Can you confirm that this happens with the latest DDX (1.0.9)? If so, we'll
need a bit more information -- please attach both a dmesg + Xorg.0.log for your
system. (Even if there are no
https://bugs.freedesktop.org/show_bug.cgi?id=61069
--- Comment #3 from dave.muel...@gmx.ch ---
What do you mean by latest kernel? If you mean 3.10, the answer is yes.
Is there something in the upcoming 3.11 which may fix this issue?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=51862
Ilia Mirkin imir...@alum.mit.edu changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=61069
--- Comment #4 from Ilia Mirkin imir...@alum.mit.edu ---
I doubt there's anything in 3.11 to fix this, but the fact is that I'm
currently running on top of the nouveau/linux-2.6 tree
(http://cgit.freedesktop.org/nouveau/linux-2.6/), which is
https://bugs.freedesktop.org/show_bug.cgi?id=61069
--- Comment #5 from dave.muel...@gmx.ch ---
Perhaps you have to try with a bigger image (e.g. 4096x4096 pixel) to
compensate for your larger screen resolution.
I didn't played with the compositor so far, just used the standard KDE
settings.
I
https://bugs.freedesktop.org/show_bug.cgi?id=31961
--- Comment #15 from Salah Coronya salah.coro...@gmail.com ---
Yes, it still does (as of 3b56bba6abaa70d629fccdcf8490e087ea3a1ab4 in
mouveau-master) it unles the workaround in Comment 12 (set the resolution an
mnaully disable the phantom ports on
https://bugs.freedesktop.org/show_bug.cgi?id=67277
--- Comment #3 from Salah Coronya salah.coro...@gmail.com ---
Created attachment 84371
-- https://bugs.freedesktop.org/attachment.cgi?id=84371action=edit
lockep splat 3.11-rc6+
I have the same thing in the current nouveau head (
https://bugs.freedesktop.org/show_bug.cgi?id=60772
--- Comment #11 from Honza hkm...@bigfoot.com ---
Mirkin: You might've overlooked it, but there IS patch in the message you
posted reference to. I don't see what other patch might be needed.
Also, the behaviour I'm seeking is behaviour previous
https://bugs.freedesktop.org/show_bug.cgi?id=60772
--- Comment #12 from Honza hkm...@bigfoot.com ---
PS: Oh, and isn't I hate it when things do stuff behind my back argument
AGAINST udev?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #6 from Vincent Lefevre vincent-...@vinc17.net ---
Created attachment 84380
-- https://bugs.freedesktop.org/attachment.cgi?id=84380action=edit
Xorg.0.log (2013-08-21)
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #7 from Vincent Lefevre vincent-...@vinc17.net ---
Created attachment 84381
-- https://bugs.freedesktop.org/attachment.cgi?id=84381action=edit
Shell script to reproduce the bug (needs xterm and base64)
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=49786
Vincent Lefevre vincent-...@vinc17.net changed:
What|Removed |Added
Attachment #84381|0 |1
is
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #9 from Vincent Lefevre vincent-...@vinc17.net ---
(In reply to comment #4)
Can you confirm that this happens with the latest DDX (1.0.9)? If so, we'll
need a bit more information -- please attach both a dmesg + Xorg.0.log for
your
https://bugs.freedesktop.org/show_bug.cgi?id=49786
Vincent Lefevre vincent-...@vinc17.net changed:
What|Removed |Added
Attachment #84379|dmesg output (2013-08-21) |dmesg output -
https://bugs.freedesktop.org/show_bug.cgi?id=49786
Vincent Lefevre vincent-...@vinc17.net changed:
What|Removed |Added
Attachment #84380|Xorg.0.log (2013-08-21) |Xorg.0.log -
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #10 from Vincent Lefevre vincent-...@vinc17.net ---
Some other thing: the dmesg and Xorg.0.log I've attached correspond to the DELL
Latitude E6400. The bug also occurs on a different machine (not with me here);
I'll try to attach
https://bugs.freedesktop.org/show_bug.cgi?id=60772
--- Comment #13 from Emil Velikov emil.l.veli...@gmail.com ---
To put this in another light
(In reply to comment #11)
Mirkin: You might've overlooked it, but there IS patch in the message you
posted reference to. I don't see what other patch
https://bugs.freedesktop.org/show_bug.cgi?id=58556
Pierre Moreau pierre.mor...@free.fr changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #11 from Ilia Mirkin imir...@alum.mit.edu ---
Great repro script! Bug confirmed on my NV96, and disconfirmed on NV18. I see
that your card is a NV98, so this is probably a bug in the nv50 exa logic.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #12 from Vincent Lefevre vincent-...@vinc17.net ---
FYI, the other machine where the bug occurs also has a NV98 chipset. The exact
card is the following:
NVIDIA Corporation G98 [Quadro NVS 295] (rev a1)
according to lspci. The one
https://bugs.freedesktop.org/show_bug.cgi?id=49786
--- Comment #13 from Ilia Mirkin imir...@alum.mit.edu ---
And as I suspected, if you run a compositor, the issue goes away (e.g. with
xcompmgr).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=56474
Ilia Mirkin imir...@alum.mit.edu changed:
What|Removed |Added
Summary|3D app segfaults on NV46|[NV30 gallium]
https://bugs.freedesktop.org/show_bug.cgi?id=67277
--- Comment #4 from Ilia Mirkin imir...@alum.mit.edu ---
There is a patch available at:
http://lists.freedesktop.org/archives/dri-devel/2013-August/043406.html
Which should fix the issue.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=64774
--- Comment #21 from Pasi Kärkkäinen pa...@iki.fi ---
Any comments about this issue?
The patch (linux-3.9.9-gpu-drm-nouveau-warn-on-node-pages.patch) from comment
#9 fixes the reproducible hard kernel crash for me.. should we push this to
https://bugs.freedesktop.org/show_bug.cgi?id=60007
--- Comment #18 from Ilia Mirkin imir...@alum.mit.edu ---
@Cornel: Can you check if your NV98 card (that you originally filed the issue
about) is fine with the latest kernels? Or does it still require Marcin's
patch? If you're having another
https://bugs.freedesktop.org/show_bug.cgi?id=64774
--- Comment #22 from Ilia Mirkin imir...@alum.mit.edu ---
We should figure out why it's getting stuff that it doesn't expect. I had
suggested adding the warn solely to avoid the crash down the line. I guess it's
reasonable for the upstream kernel
https://bugs.freedesktop.org/show_bug.cgi?id=64774
--- Comment #23 from Pasi Kärkkäinen pa...@iki.fi ---
Feel free to post it with your analysis! You can add my reported-by and
tested-by.
I'm able to reproduce the crash with Linux 3.8.x, 3.9.x and 3.10.x, so the
patch is needed at least on the
https://bugs.freedesktop.org/show_bug.cgi?id=68075
--- Comment #7 from Pasi Kärkkäinen pa...@iki.fi ---
Created attachment 84407
-- https://bugs.freedesktop.org/attachment.cgi?id=84407action=edit
nouveau debug Xorg logs
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=68075
Pasi Kärkkäinen pa...@iki.fi changed:
What|Removed |Added
Attachment #84407|text/plain |application/octet-stream
https://bugs.freedesktop.org/show_bug.cgi?id=68075
--- Comment #8 from Pasi Kärkkäinen pa...@iki.fi ---
Xorg logs (also with dmesg and xrandr output) attached.
Summary about each test-case:
01-dvi-not-connected-at-boot-but-is-connected-later:
- DVI monitor is not connected to nouveau at boot
https://bugs.freedesktop.org/show_bug.cgi?id=68402
Priority: medium
Bug ID: 68402
Assignee: nouveau@lists.freedesktop.org
Summary: Some elements are only rendered in top-left area
Severity: normal
Classification: Unclassified
https://bugs.freedesktop.org/show_bug.cgi?id=68402
--- Comment #1 from Ján Mlynek janmlyn...@gmail.com ---
Created attachment 84413
-- https://bugs.freedesktop.org/attachment.cgi?id=84413action=edit
screenshot
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=68402
--- Comment #2 from Emil Velikov emil.l.veli...@gmail.com ---
Thanks for the bisect Ján
Bit short on hardware atm, so can you confirm hunk of the commit causes the
issue? I'm suspecting the last one, although there is a small chance that it's
https://bugs.freedesktop.org/show_bug.cgi?id=68402
--- Comment #3 from Ján Mlynek janmlyn...@gmail.com ---
It's the last hunk that causes the issue:
BEGIN_NVC0(push, NVC0_3D(VIEWPORT_HORIZ(0)), 2);
PUSH_DATA (push, nvc0-framebuffer.width 16);
PUSH_DATA (push, nvc0-framebuffer.height 16);
The code expects non-VRAM mem nodes to have a pages list. If that's not
set, it will do a null deref down the line. Warn on that condition and
return an error.
See https://bugs.freedesktop.org/show_bug.cgi?id=64774
Reported-by: Pasi Kärkkäinen pa...@iki.fi
Tested-by: Pasi Kärkkäinen pa...@iki.fi
https://bugs.freedesktop.org/show_bug.cgi?id=67277
--- Comment #5 from Emil Velikov emil.l.veli...@gmail.com ---
and for prenv50 cards you might also need
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=3b56bba6abaa70d629fccdcf8490e087ea3a1ab4
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #30 from Anonymous Helper anonym...@dodgeit.com ---
As the days went by. I'm wondering what I should do. Or what's the case with
this report.
Is it kind of a problem, that I need to take care myself? E.g. it cannot be
https://bugs.freedesktop.org/show_bug.cgi?id=67382
--- Comment #31 from Emil Velikov emil.l.veli...@gmail.com ---
(In reply to comment #30)
As the days went by. I'm wondering what I should do. Or what's the case with
this report.
Is it kind of a problem, that I need to take care myself? E.g.
44 matches
Mail list logo
