From: david nicol <davidnicol@pay2send.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: X freezing in 2.4.21
Date: 12 Aug 2003 05:49:16 -0500 [thread overview]
Message-ID: <1060685356.1249.21.camel@plaza.davidnicol.com> (raw)
I believe it to be gnome's problem, since I don't get lock-ups
under fvwm.
Anyway how difficult would it be to gracefully handle jump-to-null
and why is that causing a panic instead of just one process expiring?
My guess is it has to do with the DRM support.
reply other threads:[~2003-08-12 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1060685356.1249.21.camel@plaza.davidnicol.com \
--to=davidnicol@pay2send.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
all inboxes | Powered by JetHome®