From: J Sloan <joe@tmsusa.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops in 2.5.64
Date: Thu, 06 Mar 2003 11:53:13 -0800 [thread overview]
Message-ID: <3E67A729.5050403@tmsusa.com> (raw)
In-Reply-To: b487vc$1u6$1@penguin.transmeta.com
Linus Torvalds wrote:
>In article <3E66E782.5010502@tmsusa.com>, J Sloan <joe@tmsusa.com> wrote:
>
>
>>2.5.64 was running well, but after a day
>>or so of uptime, in fairly busy use (squid,
>>postfix, dhcp server, iptables, X desktop)
>>I ssh'd in as root, issued an init 3, then
>>a moment later, init 5. A moment after
>>that, the ssh session froze and all internet
>>access stopped as well.
>>
>>The console was frozen, with an oops -
>>
>>
>
>Are you using DRI? There is some evidence that exiting and restarting X
>will not correctly re-initialize the DRI stuff in the kernel, and
>_massive_ kernel memory corruption can ensure when the new X server
>starts.
>
Yes, of course, I want altlantis to look _good_
>
>At which point you'll get random oopses etc.
>
That does indeed seem to be the scenario - it
was rock solid and busy for a day, but when X
was killed and restarted everything went right
to hell -
>Looks like you at least have the DRI kernel modules there.
>
>Try to see if the problem goes away if you start X without DRI support
>(ie remove the "Load 'dri'" or whatever from the XF86Config file, or
>start up in a mode that DRI doesn't support, like 8bpp).
>
>
OK, I'll try it like that -
Joe
prev parent reply other threads:[~2003-03-06 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 6:15 Oops in 2.5.64 J Sloan
2003-03-06 6:36 ` Andrew Morton
2003-03-06 7:17 ` bert hubert
2003-03-06 7:36 ` J Sloan
2003-03-06 7:46 ` Denis Vlasenko
2003-03-06 8:14 ` Andrew Morton
2003-03-06 11:59 ` Ingo Oeser
2003-03-06 19:36 ` Linus Torvalds
2003-03-06 19:53 ` J Sloan [this message]
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=3E67A729.5050403@tmsusa.com \
--to=joe@tmsusa.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;
as well as URLs for NNTP newsgroup(s).