From: Nick Piggin <nickpiggin@yahoo.com.au>
To: pomac@vapor.com
Cc: Linux-kernel@vger.kernel.org
Subject: Re: [OOPS] related to swap?
Date: Tue, 04 Apr 2006 22:31:52 +1000 [thread overview]
Message-ID: <44326738.1090707@yahoo.com.au> (raw)
In-Reply-To: <1144104593.30036.38.camel@localhost>
Ian Kumlien wrote:
> Yes, i run a tainted kernel! either live with it or ignore this mail =)
> starting swap lead to a deadlock within 15 mins
> I have never had the energy to perform a full memtext86+
It would be useful if you could perform a memtest overnight one night,
then run a non-patched and non-tained 2.6.16.1 kernel, and try to
reproduce the problems.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-04-05 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 22:49 [OOPS] related to swap? Ian Kumlien
2006-04-04 12:31 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-05 8:22 Ian Kumlien
2006-04-05 9:38 ` Nick Piggin
2006-04-06 21:28 ` Ian Kumlien
2006-04-09 19:31 ` Ian Kumlien
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=44326738.1090707@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Linux-kernel@vger.kernel.org \
--cc=pomac@vapor.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