From: Michael Obster <lkm@obster.org>
To: Greg Schafer <gschafer@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 Nasty Lockup
Date: Tue, 26 Sep 2006 15:56:46 +0200 [thread overview]
Message-ID: <4519319E.6070709@obster.org> (raw)
In-Reply-To: <20060926123640.GA7826@tigers.local>
Hi Greg,
what do you mean with desktop use? X11-System? Then please add also your
used grafic card and the X11 driver. I see this behaviour with lots of
binary only driver like from NVIDIA or ATI (perhaps they have problems
with the new 2.6.18 kernel).
Just to except that this is the cause for your lock ups.
Kind regards,
Michael Obster
Greg Schafer schrieb:
> This is a _hard_ lockup. No oops, no magic sysrq, no nuthin, just a
> completely dead machine with only option the reset button. Usually happens
> within a couple of minutes of desktop use but is 100% reproducible. Problem
> is still there in a fresh checkout of current Linus git tree (post 2.6.18).
>
> Dual Athlon-MP 2200's on a Tyan S2466 Tiger MPX. Config attached.
next prev parent reply other threads:[~2006-09-26 13:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:36 2.6.18 Nasty Lockup Greg Schafer
2006-09-26 13:56 ` Michael Obster [this message]
2006-09-26 15:41 ` Ben Duncan
2006-09-26 18:18 ` john stultz
2006-09-26 20:15 ` john stultz
2006-09-26 22:02 ` Greg Schafer
2006-09-26 22:58 ` john stultz
2006-09-26 21:15 ` S.Çağlar Onur
2006-09-26 22:50 ` john stultz
2006-09-27 9:45 ` S.Çağlar Onur
2006-09-27 19:14 ` john stultz
2006-09-27 20:55 ` Andi Kleen
2006-09-27 21:06 ` S.Çağlar Onur
2006-09-28 11:39 ` S.Çağlar Onur
2006-09-29 8:49 ` S.Çağlar Onur
2006-10-06 22:57 ` john stultz
2006-10-07 15:48 ` S.Çağlar Onur
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=4519319E.6070709@obster.org \
--to=lkm@obster.org \
--cc=gschafer@zip.com.au \
--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