From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Greg Schafer <gschafer@zip.com.au>
Cc: linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.18 Nasty Lockup
Date: Wed, 27 Sep 2006 00:15:47 +0300 [thread overview]
Message-ID: <200609270015.51465.caglar@pardus.org.tr> (raw)
In-Reply-To: <20060926123640.GA7826@tigers.local>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
26 Eyl 2006 Sal 15:36 tarihinde, Greg Schafer şunları yazmıştı:
> 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).
Same symptoms here and its reproducible after starting the irqbalance (0.12 or
0.13), if i disable irqbalance then everything is going fine.
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-26 21:15 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
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 [this message]
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=200609270015.51465.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=gschafer@zip.com.au \
--cc=johnstul@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.