From: Bill Davidsen <davidsen@tmr.com>
To: linux@horizon.com
Cc: neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: Interesting RAID checking observations
Date: Mon, 04 Sep 2006 13:16:05 -0400 [thread overview]
Message-ID: <44FC5F55.6000008@tmr.com> (raw)
In-Reply-To: <20060828131552.5776.qmail@science.horizon.com>
linux@horizon.com wrote:
>>I don't think the processor is saturating. I've seen reports of this
>>sort of thing before and until recently had no idea what was happening,
>>couldn't reproduce it, and couldn't think of any more useful data to
>>collect.
>>
>>
>
>Well I can reproduce it easily enough. It's a production server, but
>I can do low-risk experiments after hours.
>
>I'd like to note that the symptoms include not even being
>able to *type* at the console, which I thought was all in-kernel
>code, not subject to being swapped out. But whatever.
>
Really? Or is it just that you can type but the characters don't get
echoed. The type part is in the kernel, but the display involves X
unless you run a direct console.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-09-04 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 6:46 Interesting RAID checking observations linux
2006-08-27 11:18 ` Justin Piszcz
2006-08-28 13:00 ` linux
2006-08-28 1:04 ` Neil Brown
2006-08-28 13:15 ` linux
2006-09-04 17:16 ` Bill Davidsen [this message]
2006-09-04 21:15 ` linux
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 6:58 linux
2006-09-21 18:48 ` linux
2006-09-21 18:55 ` Rob Bray
2006-09-22 2:13 ` linux
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=44FC5F55.6000008@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux@horizon.com \
--cc=neilb@suse.de \
/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).