[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2009-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 --- Comment #14 from Stuart Bennett sb...@cam.ac.uk 2009-04-02 17:39:00 PST --- From https://bugzilla.redhat.com/show_bug.cgi?id=492399 can it be assumed this bug is resolved? Also, feel free to open a bug here about your DVI issue (an

[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2009-04-02 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 Bill Nottingham nott...@redhat.com changed: What|Removed |Added Status|NEW |RESOLVED

[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2007-09-25 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 --- Comment #13 from [EMAIL PROTECTED] 2007-09-25 07:44 PST --- Created an attachment (id=11746) -- (http://bugs.freedesktop.org/attachment.cgi?id=11746action=view) log with debugging OK, here's the log with debugging. --

[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2007-09-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 --- Comment #8 from [EMAIL PROTECTED] 2007-09-04 08:50 PST --- I still get a DMA queue hang; the hex is slightly different. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this

[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2007-09-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #10263|0 |1 is obsolete|

[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2007-09-04 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #10264|0 |1 is obsolete|

[Nouveau] [Bug 11240] doesn't start X - DMA Queue hang

2007-06-11 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=11240 --- Comment #4 from [EMAIL PROTECTED] 2007-06-11 18:27 PST --- It would be useful if you could bisect the git tree from the point the last working snapshot was known, to track down exactly what broke it (from the fedora bug: