From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Len Brown <lenb@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: x86 instability with 2.6.1{8,9}
Date: Thu, 25 Jan 2007 23:56:27 +0000 [thread overview]
Message-ID: <20070125235627.GA17168@deepthought> (raw)
In-Reply-To: <20070115162911.GA13198@deepthought>
On Mon, Jan 15, 2007 at 04:29:11PM +0000, Ken Moffat wrote:
>
> Today, I've built 2.6.19.2 without highmem (the box only has 1GB,
> dunno why I'd included that in the original config) and I will
> continue to wait patiently for either a week without problems, or
> something that I can manage to note - although I think at the moment
> that the second coming of the great prophet Zarquon is more likely.
>
Bizarre - it panic'd again last Thursday while I was in X, but I
still didn't manage to log any output. At the weekend, I had the
bright idea of using chattr +j on the syslog to try to journal any
data, since then it has been fine. So, it isn't down to highmem, and
I still can't trigger it reliably, or get any trace. Tried running
as x86_64 this morning (because cold starts on Thursdays seem
particularly problematic, perhaps it's a time/power-supply-noise
problem), then x86 from a cold start this afternoon.
Time to hope it won't bite me too often, and move on to testing
2.6.20-rc6.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2007-01-25 23:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 16:01 x86 instability with 2.6.1{8,9} Ken Moffat
2007-01-01 16:48 ` Alistair John Strachan
2007-01-01 17:07 ` Ken Moffat
2007-01-01 19:13 ` Ken Moffat
2007-01-01 19:45 ` Alistair John Strachan
2007-01-02 17:25 ` Len Brown
2007-01-02 18:04 ` Ken Moffat
2007-01-02 18:42 ` Len Brown
2007-01-02 19:34 ` Ken Moffat
2007-01-06 22:04 ` Randy Dunlap
2007-01-07 14:26 ` Ken Moffat
2007-01-15 16:29 ` Ken Moffat
2007-01-25 23:56 ` Ken Moffat [this message]
2007-01-31 21:36 ` Chuck Ebbert
2007-01-31 23:26 ` Ken Moffat
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=20070125235627.GA17168@deepthought \
--to=zarniwhoop@ntlworld.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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