All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: 2.6.35-rc2: GPF while executing libhugetlbfs tests on x86_64
Date: Sun, 13 Jun 2010 12:19:44 +0100	[thread overview]
Message-ID: <20100613111944.GA22015@csn.ul.ie> (raw)
In-Reply-To: <4C11CA71.9010606@in.ibm.com>

On Fri, Jun 11, 2010 at 11:02:33AM +0530, Sachin Sant wrote:
> Mel Gorman wrote:
>> If the problem has gone away since 2.6.35-rc2, the most likely candidate fix
>> patch is commit [386f40: Revert "tty: fix a little bug in scrup, vt.c"] which
>> reverts the patch you previously identified as being a problem.  The commit
>> message also matches roughly what you are seeing with the 0x0720 patterns.
>>
>> Can you retest with 2.6.35-rc2 with commit 386f40 applied and see if it
>> also fixes up your problem please?
>>   
> I could not recreate this problem against 2.6.35-rc2 + commit 386f40.
>

Great, I will consider this bug resolved so. Thanks for testing.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mel@csn.ul.ie>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: 2.6.35-rc2: GPF while executing libhugetlbfs tests on x86_64
Date: Sun, 13 Jun 2010 12:19:44 +0100	[thread overview]
Message-ID: <20100613111944.GA22015@csn.ul.ie> (raw)
In-Reply-To: <4C11CA71.9010606@in.ibm.com>

On Fri, Jun 11, 2010 at 11:02:33AM +0530, Sachin Sant wrote:
> Mel Gorman wrote:
>> If the problem has gone away since 2.6.35-rc2, the most likely candidate fix
>> patch is commit [386f40: Revert "tty: fix a little bug in scrup, vt.c"] which
>> reverts the patch you previously identified as being a problem.  The commit
>> message also matches roughly what you are seeing with the 0x0720 patterns.
>>
>> Can you retest with 2.6.35-rc2 with commit 386f40 applied and see if it
>> also fixes up your problem please?
>>   
> I could not recreate this problem against 2.6.35-rc2 + commit 386f40.
>

Great, I will consider this bug resolved so. Thanks for testing.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-13 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 16:08 2.6.35-rc2: GPF while executing libhugetlbfs tests on x86_64 Sachin Sant
2010-06-06 16:08 ` Sachin Sant
2010-06-08  9:18 ` Mel Gorman
2010-06-08  9:18   ` Mel Gorman
2010-06-08 11:50   ` Sachin Sant
2010-06-08 11:50     ` Sachin Sant
2010-06-08 12:36     ` Mel Gorman
2010-06-08 12:36       ` Mel Gorman
2010-06-11  5:32       ` Sachin Sant
2010-06-11  5:32         ` Sachin Sant
2010-06-13 11:19         ` Mel Gorman [this message]
2010-06-13 11:19           ` Mel Gorman

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=20100613111944.GA22015@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sachinp@in.ibm.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.