From: Andrew Morton <akpm@digeo.com>
To: Steven Cole <elenstev@mesatop.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hard lockups running X with 2.5.38-bk4, -bk5 and -mm3
Date: Thu, 26 Sep 2002 15:55:30 -0700 [thread overview]
Message-ID: <3D939062.9C44B2B8@digeo.com> (raw)
In-Reply-To: 1033078474.1306.43.camel@spc9.esa.lanl.gov
Steven Cole wrote:
>
> I only recently started testing 2.5.x kernels with X, and have
> immediately run into problems.
>
> My new test system is a Dell GX110 single PIII, IDE (Intel 82801AA IDE),
> 256MB memory. The 2.5.38-bk4,5 and -mm3 kernels were SMP (due to
> not having Rusty's cpu_possible fix), non-PREEMPT.
>
> Running XFree86 4.2.1, I get a hard lockup with the box not responsive
> to pings. Ssh sessions don't respond and the pointer does not respond
> to mouse movements. This occurs very soon (2-3 minutes) after starting
> X with 2.5.38-bk4 and -bk5. I was able to run 2.5.38-mm3 for about 30
> minutes under load (kernel compiles) before a freeze occurred. I ran
> 2.5.38-mm3 again for about 20 minutes with X and under load before a
> second lockup occurred. Sorry, nothing logged, and when the freezes
> occur, there is no response to SYSRQ-H,S or B. SYSRQ-H works as
> expected before the freeze.
>
> Without running X on this system, no freezes have been observed with any
> of these kernels with the system loaded by running kernel compiles and
> dbench with up to 40 clients.
>
Me too. deadlocks on tasklist_lock. Some fixes went into Linus's
tree a few hours ago, so please retest.
next prev parent reply other threads:[~2002-09-26 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 22:14 Hard lockups running X with 2.5.38-bk4, -bk5 and -mm3 Steven Cole
2002-09-26 22:55 ` Andrew Morton [this message]
2002-09-30 15:37 ` Steven Cole
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=3D939062.9C44B2B8@digeo.com \
--to=akpm@digeo.com \
--cc=elenstev@mesatop.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).