From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm snapshot broken-out-2007-04-25-02-49.tar.gz uploaded
Date: Sun, 29 Apr 2007 09:10:04 -0700 [thread overview]
Message-ID: <4634C35C.8040303@goop.org> (raw)
In-Reply-To: <200704291555.57082.ak@suse.de>
Andi Kleen wrote:
>> s/Friday/Sunday
>>
>> GOOD
>> ignore-stolen-time-in-the-softlockup-watchdog.patch
>> ignore-stolen-time-in-the-softlockup-watchdog-fix.patch
>> BAD
>>
>
> Thanks. I think the patch got dropped anyways. At least I don't have it anymore.
>
Is this the testing failures in the locking tests when these patches are
in place? It's very mysterious, but I don't see how it this patch can
cause the symptoms. It looks like they're tickling a bug in lockdep or
the lock tests, but I don't have any insight into how...
J
next prev parent reply other threads:[~2007-04-29 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 9:52 mm snapshot broken-out-2007-04-25-02-49.tar.gz uploaded akpm
2007-04-25 17:20 ` William Heimbigner
2007-04-25 20:25 ` Andrew Morton
2007-04-25 20:24 ` Michal Piotrowski
2007-04-25 20:42 ` Jeremy Fitzhardinge
2007-04-25 20:48 ` Andi Kleen
2007-04-25 20:55 ` Michal Piotrowski
2007-04-25 20:57 ` Andi Kleen
2007-04-25 21:40 ` Michal Piotrowski
2007-04-25 22:07 ` Andi Kleen
2007-04-25 23:02 ` Michal Piotrowski
2007-04-29 13:36 ` Michal Piotrowski
2007-04-29 13:55 ` Andi Kleen
2007-04-29 16:10 ` Jeremy Fitzhardinge [this message]
2007-04-26 21:21 ` Michal Piotrowski
2007-04-27 0:12 ` Greg KH
2007-04-27 17:38 ` Michal Piotrowski
2007-04-27 17:46 ` Greg KH
2007-04-27 17:48 ` Tejun Heo
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=4634C35C.8040303@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
/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