From: Davide Libenzi <davidel@xmailserver.org>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Andrew Morton <akpm@digeo.com>, Robert Love <rml@tech9.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
piggin@cyberone.com.au
Subject: Re: 2.5.70-mm8: freeze after starting X
Date: Thu, 12 Jun 2003 10:30:24 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0306121022400.3626@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <1055438377.1058.2.camel@serpentine.internal.keyresearch.com>
On Thu, 12 Jun 2003, Bryan O'Sullivan wrote:
> On Wed, 2003-06-11 at 17:24, Andrew Morton wrote:
>
> > Odd that starting the X server triggers it. Be interesting if your patch
> > fixes things for Brian.
>
> I think Robert and I are seeing different things. For me, -mm6 is fine
> (unlike Robert's case), -mm7 oopses in the PCI init code during early
> boot (somewhere in the radeon init stuff, can't capture the oops
> easily), and -mm8 gives itself a wedgie a few seconds after starting X.
>
> I'm about to try, um, whichever of the umpty-ump patches that went back
> and forth looks most plausible.
I'm having total freezes with 2.5.69 in both my home laptop with a SiS650
chipset and in my machine at work with Intel Corp. 82845G/GL. Using X with
Gnome (RH9) the system will end up to a completely frozen state after a
random amount of time. This happens with almost no activity on the machine
that makes me thing to be not related to some kind of load. IRQ are
disabled and the IDE drive light remains on. I planned to debug the thing
but I didn't have time yet. I set up the NMI oopser and I need to do
something to get the dump since when the NMI trigger I'm in graphic mode.
I was thinking about LKCD. It has never happened in console mode so it
must be X/Gnome+2.5.69
- Davide
prev parent reply other threads:[~2003-06-12 17:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 22:17 Bryan O'Sullivan
2003-06-11 22:36 ` Robert Love
2003-06-11 22:41 ` Andrew Morton
2003-06-11 22:53 ` Bryan O'Sullivan
2003-06-11 23:11 ` Bryan O'Sullivan
2003-06-11 23:34 ` Robert Love
2003-06-12 0:18 ` Robert Love
2003-06-12 0:24 ` Andrew Morton
2003-06-12 1:10 ` [patch] as-iosched divide by zero fix Robert Love
2003-06-12 1:22 ` Andrew Morton
2003-06-12 1:28 ` Robert Love
2003-06-12 1:41 ` Nick Piggin
2003-06-12 1:31 ` Nick Piggin
2003-06-12 2:34 ` John Stoffel
2003-06-12 4:05 ` Nick Piggin
2003-06-12 1:22 ` Nick Piggin
2003-06-12 1:29 ` Robert Love
2003-06-12 1:54 ` Steven Cole
2003-06-12 2:01 ` Robert Love
2003-06-12 17:19 ` 2.5.70-mm8: freeze after starting X Bryan O'Sullivan
2003-06-12 17:29 ` Bryan O'Sullivan
2003-06-12 17:30 ` Davide Libenzi [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=Pine.LNX.4.55.0306121022400.3626@bigblue.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=akpm@digeo.com \
--cc=bos@serpentine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=rml@tech9.net \
/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®