mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: "François Valenduc" <francois.valenduc@tvcablenet.be>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Noticeable slow-down in 2.6.35-rc3
Date: Sun, 13 Jun 2010 22:11:03 +0100	[thread overview]
Message-ID: <201006132211.03744.chris2553@googlemail.com> (raw)
In-Reply-To: <201006132158.09216.chris2553@googlemail.com>

On Sunday 13 June 2010 21:58:09 Chris Clayton wrote:
> On Sunday 13 June 2010 21:35:25 François Valenduc wrote:
> > Le 13/06/10 22:15, Chris Clayton a écrit :
>
> <snip>
>
> > > I've bisected it and arrived at:
> > >
> > > 597a264b1a9c7e36d1728f677c66c5c1f7e3b837 is the first bad commit
> > > commit 597a264b1a9c7e36d1728f677c66c5c1f7e3b837
> > > Author: John Fastabend <john.r.fastabend@intel.com>
> > > Date:   Thu Jun 3 09:30:11 2010 +0000
>
> <snip>
>
> > This commit also makes nfsd hangs at startup on my computer (see
> > https://bugzilla.kernel.org/show_bug.cgi?id=16195). This problem doesn't
> > occur if it's reverted.
>
> I've just found John Fastabend's easy and fast fix
> (http://marc.info/?l=linux-kernel&m=127646140827821) and am about to apply
> it and test the new kernel. back soon!
>

Yes, that's fixed the problem I reported.

Thanks.

Chris

> > François Valenduc



-- 
The more I see, the more I know. The more I know, the less I understand. 
Changing Man - Paul Weller

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 20:15 Chris Clayton
2010-06-13 20:35 ` François Valenduc
2010-06-13 20:58   ` Chris Clayton
2010-06-13 21:11     ` Chris Clayton [this message]
2010-06-13 22:13       ` Gene Heskett
2010-06-14 12:55         ` walt
2010-06-14 15:31           ` Gene Heskett
2010-06-14 16:27           ` Gene Heskett

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=201006132211.03744.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=francois.valenduc@tvcablenet.be \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®