From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: James Stevenson <james@stev.org>
Cc: pd dd <parviz_kernel@yahoo.com>,
"M. Soltysiak" <msoltysiak@hotmail.com>,
ML-linux-kernel <linux-kernel@vger.kernel.org>,
William Stearns <wstearns@pobox.com>
Subject: Re: Linux BUG: Memory Leak
Date: 13 Mar 2003 15:45:34 +0000 [thread overview]
Message-ID: <1047570333.25944.42.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <01f801c2e96c$980b4390$0cfea8c0@ezdsp.com>
On Thu, 2003-03-13 at 14:26, James Stevenson wrote:
> this isnt a serious problem then ?
There were problems with the XFree 4.3 DRM if you mixed it with
certain other ingredients like rmap. I don't know what Slackware
ships but that may be the problem.
With a base kernel + XFree 4.3 DRM port the only problems I'm now
hitting are serious breakages in the DRM code causing memory
corruption on Radeon 9x00 and the fact 4.3 broke SiS DRM support.
next prev parent reply other threads:[~2003-03-13 14:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 6:49 M. Soltysiak
2003-03-12 7:19 ` David Shirley
2003-03-12 10:04 ` Maciej Soltysiak
2003-03-12 18:38 ` James Stevenson
2003-03-12 19:25 ` Elladan
2003-03-12 7:22 ` Mike Galbraith
2003-03-12 7:30 ` William Stearns
2003-03-13 7:13 ` William Stearns
2003-03-13 9:13 ` pd dd
2003-03-13 14:26 ` James Stevenson
2003-03-13 15:45 ` Alan Cox [this message]
2003-03-13 15:05 ` Tomas Szepe
2003-03-13 15:33 ` Damian Kołkowski
2003-03-13 16:29 ` venom
2003-03-13 14:26 ` James Stevenson
2003-03-13 14:42 ` Richard B. Johnson
2003-03-13 15:10 ` Mark Mielke
2003-03-13 15:13 ` Richard B. Johnson
2003-03-13 18:54 ` Alan Cox
2003-03-13 15:06 ` Martin Schlemmer
2003-03-13 14:27 ` James Stevenson
2003-03-13 15:43 ` Alan Cox
2003-03-12 16:49 ` Disconnect
2003-03-12 19:24 Felipe Alfaro Solana
2003-03-12 20:58 ` James Stevenson
2003-03-12 22:23 Felipe Alfaro Solana
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=1047570333.25944.42.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=james@stev.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msoltysiak@hotmail.com \
--cc=parviz_kernel@yahoo.com \
--cc=wstearns@pobox.com \
/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
all inboxes | Powered by JetHome®