From: John McGowan <jmcgowan@inch.com>
To: linux-kernel@vger.kernel.org
Subject: Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
Date: Sat, 25 Dec 2004 14:34:00 -0500 [thread overview]
Message-ID: <20041225193400.GA2700@localhost.localdomain> (raw)
Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
Fedora Core2; xorg 6.8.1 (and 6.7.x); kernel 2.6.9/2.6.10
(other problem in earlier 2.6.x?)
Intel i810(E) driver
As reported for kernel 2.6.9, since rc1 the intel810(E) support seems to be
broken and the driver does not even work half way, as it did in kernel 2.6.7.
As in 2.6.9, the screen (xorg, 6.8.1; intel 810(E)) comes up with junk
(unable to access the memory?). I did not try disabling (2D) acceleration
this time (as was suggested to a user of Fedora Core3 by the Fedora team as
as reported in one of the usenet groups) since that is much too slow and, as
I recall, did not fix the (apparent) memory leak (which also occurs in 2.6.7).
[memory leak in older 2.6.x kernels]
--
In 2.6.7 it seems memory is not freed either. Gimp-Gap (Gimp 2.0.x or 2.2.x).
Use move-path and move something over an image. OK ... one animation
... do it again (moving another item over the image). And again and again
... It appears that others have no problem(?) with, in kernel 2.6.?, xorg 6.8.1
and 6.7.x, the memory used by move-path being freed. With the intel 810(E) driver
(used by so few, admittedly), it is never freed (using "free" to see it use
up system, buffer and then swap memory). It is not even freed when Gimp is closed
down. One has to close X itself to get the 810(E) driver to free the memory
(unless it is a bug in xorg 6.7.x and 6.8.1). Is this similar to the kernel
2.6.8[.1] bug where the kernel would not free certain memory under certain
conditions (most notably breaking audio CD burning)? Is there a similar bug
in the earlier 2.6.x intel810(E) drivers?
So, I am back to kernel 2.6.7 (Fedora Core2) for some things, rebooting to
RH7.2 with a 2.4.x kernel when I want to get some work done in Gimp.
next reply other threads:[~2004-12-25 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 19:34 John McGowan [this message]
2004-12-25 20:17 ` Alan Cox
2004-12-26 5:09 ` John McGowan
2004-12-26 17:44 ` Alan Cox
2004-12-26 21:02 ` John McGowan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041225193400.GA2700@localhost.localdomain \
--to=jmcgowan@inch.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome