[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread Kai Kasurinen
** Bug 64972 has been marked a duplicate of this bug ** Bug 64970 has been marked a duplicate of this bug -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listi

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread Kai Kasurinen
** Bug 65228 has been marked a duplicate of this bug -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread BenjaminOtto
Ahh, got the new kernel and it seems to work fine again now. Thanks a lot. -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread Soren Hansen
On Tue, Oct 10, 2006 at 08:39:29PM -, BenjaminOtto wrote: > How long will it take for a new binary kernel with this fix being > released? It shouldn't be more than a few hours at most. Cheers. -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- de

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread BenjaminOtto
How long will it take for a new binary kernel with this fix being released? -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread David Nielsen
** Bug 65143 has been marked a duplicate of this bug -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread BenjaminOtto
** Bug 65098 has been marked a duplicate of this bug -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread Ben Collins
Got some local debug in there. Uploaded a fixed source. ** Changed in: linux-source-2.6.17 (Ubuntu) Status: Confirmed => Fix Committed -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com ht

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread Soren Hansen
It's not a compiz nor beryl issue. They just suffer from the issue as well since they rely DRI to work. Anyone trying to run tuxracer, GL based screensavers or anything else requiring DRI will also have problems. -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread BenjaminOtto
** Tags added: 2.6.17-10-generic beryl compiz i915 kernel -- System Logs fill up with i915 errors (1GB per 20 min.) https://launchpad.net/bugs/65000 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 65000] Re: System Logs fill up with i915 errors (1GB per 20 min.)

2006-10-10 Thread BenjaminOtto
I am using the compiz packages from http://gandalfn.wordpress.com/ (made from the official compiz-tree) so i should in fact be an issue with i945 and compiz/beryl. ** Bug 65041 has been marked a duplicate of this bug ** Bug 65039 has been marked a duplicate of this bug ** Bug 65043 has been mark