From: David Ford <david@linux.com>
To: Shawn Starr <Shawn.Starr@Home.net>
Cc: Jorge Nerin <comandante@zaralinux.com>,
linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: kernel BUG at slab.c:1542!(2.4.1-pre9)
Date: Tue, 23 Jan 2001 03:02:27 +0000 [thread overview]
Message-ID: <3A6CF442.86DE8496@linux.com> (raw)
In-Reply-To: <3A6C5058.C5AA7681@zaralinux.com> <3A6CB620.469A15A9@Home.net>
If it makes the kernel do Bad Things, the kernel needs to be fixed.
-d
Shawn Starr wrote:
> This is not a kernel bug, This is a bug in the XFree86 TrueType rendering
> extention. This has been discussed on the Xpert XFree86 mailing list. There
> is a fix in the works (depends on the TrueType fonts your using).
>
> Unless otherwise, Im using 2.4.1-pre9 with no such faults (XFree86 CVS
> X11R6.5.1 merge sources) not 4.0.2 stable.
--
There is a natural aristocracy among men. The grounds of this are virtue and talents. Thomas Jefferson
The good thing about standards is that there are so many to choose from. Andrew S. Tanenbaum
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-23 3:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 15:23 kernel BUG at slab.c:1542! (2.4.1-pre9) Jorge Nerin
2001-01-22 22:37 ` kernel BUG at slab.c:1542!(2.4.1-pre9) Shawn Starr
2001-01-23 3:02 ` David Ford [this message]
2001-01-24 12:58 ` Daniel Phillips
2001-01-24 13:29 ` Gregory Maxwell
2001-01-24 14:32 ` Daniel Phillips
2001-01-24 15:45 ` Andrew Morton
2001-01-25 1:18 ` Alan Cox
2001-01-24 18:05 ` Tim Fletcher
2001-01-24 17:50 ` Shawn Starr
2001-01-24 18:05 ` Tim Fletcher
2001-01-25 11:49 ` Russell King
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=3A6CF442.86DE8496@linux.com \
--to=david@linux.com \
--cc=Shawn.Starr@Home.net \
--cc=comandante@zaralinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@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