From: Andy Whitcroft <apw@shadowen.org>
To: Martin Bligh <mbligh@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: sparsemem panic in 2.6.17-rc5-mm1 and -mm2
Date: Wed, 07 Jun 2006 18:41:42 +0100 [thread overview]
Message-ID: <44870FD6.1040405@shadowen.org> (raw)
In-Reply-To: <4484D174.7080902@google.com>
Martin Bligh wrote:
> http://test.kernel.org/abat/34264/debug/console.log
>
> Only seems to happen on the sparsemem runs. Possibly a side-effect
> of the page migration stuff, manifesting itself differently?
> Or maybe not?
>
Ok, this shouldn't be that issue as the sparsemem checks won't tickle
that puppy, not enough swap devices in use. That said, I've just run a
full sweep of sparsemem and its GOOD across the board on swap patch and
2222 deadlock. Sadly this failure is on a machine which has just bitten
the dust and I'm waiting for it to be mended. Not sure how long that
will take.
-apw
next prev parent reply other threads:[~2006-06-07 17:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 0:51 sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Martin Bligh
2006-06-06 3:07 ` Andrew Morton
2006-06-06 5:19 ` KAMEZAWA Hiroyuki
2006-06-06 5:36 ` Yasunori Goto
2006-06-06 7:27 ` Andrew Morton
2006-06-07 0:43 ` KAMEZAWA Hiroyuki
2006-06-07 4:58 ` Andrew Morton
2006-06-07 5:36 ` Rusty Russell
2006-06-07 5:50 ` Andrew Morton
2006-06-07 6:49 ` Rusty Russell
2006-06-07 9:26 ` Andy Whitcroft
2006-06-07 16:29 ` Andrew Morton
2006-06-07 16:35 ` Andrew Morton
2006-06-07 17:50 ` Andy Whitcroft
2006-06-15 12:28 ` [PATCH] zone handle unaligned zone boundaries Andy Whitcroft
2006-06-07 17:22 ` sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Andy Whitcroft
2006-06-06 23:42 ` Andrew Morton
2006-06-07 9:16 ` Mel Gorman
2006-06-07 17:38 ` Andy Whitcroft
2006-06-07 17:41 ` Andy Whitcroft [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 3:50 Chuck Ebbert
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=44870FD6.1040405@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.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 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.