mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Eric Paris <eparis@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Eric Paris <eparis@parisplace.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"H. Peter Anvin" <hpa@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: memleaks, acpi + ext4 + tty
Date: Mon, 31 Aug 2009 17:31:43 -0700	[thread overview]
Message-ID: <43e72e890908311731h626a5b9bu486653c755cda2fa@mail.gmail.com> (raw)
In-Reply-To: <1251764791.2158.7.camel@dhcp231-106.rdu.redhat.com>

On Mon, Aug 31, 2009 at 5:26 PM, Eric Paris<eparis@redhat.com> wrote:
> On Mon, 2009-08-31 at 16:54 -0700, Luis R. Rodriguez wrote:
>> On Mon, Aug 31, 2009 at 1:02 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>> > On Mon, Aug 31, 2009 at 12:47 PM, John W.
>> > Linville<linville@tuxdriver.com> wrote:
>> >> On Mon, Aug 31, 2009 at 12:43:01PM -0700, Luis R. Rodriguez wrote:
>> >>> On Mon, Aug 31, 2009 at 12:33 PM, John W.
>> >>> Linville<linville@tuxdriver.com> wrote:
>> >>
>> >>> > My guess is that the culprit is between
>> >>> > v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
>> >>>
>> >>> But the issue is *not* in linux-2.6-allstable, it is only present on
>> >>> wireless-testing, and I went as far back as merge-2009-08-28. I was
>> >>> using whatever tag was available prior to you moving to rc8, and that
>> >>> worked.
>> >>
>> >> OK, then I can only guess that something went wrong in your bisection
>> >> (e.g. dirty build, something not marked properly, etc).
>> >
>> > Well so remember I did a clean git clone of wireless-testing and the
>> > issue was still there, but I determined just now it seems rc8 from
>> > Linus does indeed also have the issue. For some reason the issue was
>> > not present on hpa's rc8 on linux-2.6-allstable. Will double check on
>> > that again.
>>
>> OK so hpa's tree just had all of Linus' stuff pulled, not just rc8. It
>> turns out Eric Paris' inotify patches are required to fix 2.6.31-rc8
>> for me.. I tested just one patch and it fixed my bootup lag:
>>
>> http://git.infradead.org/users/eparis/notify.git/commit/b962e7312ae87006aed6f68ceee94bdf8db08338
>>
>> FWIW for that patch:
>>
>> Tested-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>>
>> So -- you if you're like me and had issues with bootup lag on
>> wireless-testing, you can probably fix your wireless-testing by
>> pulling his patches:
>>
>> git pull git://git.infradead.org/users/eparis/notify.git for-linus
>>
>> I saw Linus had some other fixes but I'll wait for rc9 for that as my
>> box seems reasonably stable right now.
>
> Yes, -rc8 broke pretty badly for a number of people.  Linus did pull all
> of the fixes that I know of.  I wouldn't suggest pulling just that one
> commit.  All 3 of the post -rc8 patches in my tree fix -rc8
> regressions   :(

Thanks, the note -- so I guess best is to just pull from Linus ontop
of wireless-testing.

 Luis

  reply	other threads:[~2009-09-01  0:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  5:25 Luis R. Rodriguez
2009-08-28 16:32 ` Catalin Marinas
2009-08-28 16:52   ` Luis R. Rodriguez
2009-08-28 21:50     ` Luis R. Rodriguez
2009-08-28 22:09       ` Luis R. Rodriguez
2009-08-31  8:23         ` Luis R. Rodriguez
2009-08-31 17:50           ` Luis R. Rodriguez
2009-08-31 18:37             ` Luis R. Rodriguez
2009-08-31 19:30               ` Luis R. Rodriguez
2009-08-31 19:33                 ` John W. Linville
2009-08-31 19:43                   ` Luis R. Rodriguez
2009-08-31 19:47                     ` John W. Linville
2009-08-31 20:02                       ` Luis R. Rodriguez
2009-08-31 23:54                         ` Luis R. Rodriguez
2009-09-01  0:26                           ` Eric Paris
2009-09-01  0:31                             ` Luis R. Rodriguez [this message]
2009-09-01  6:33                               ` Zhu Yi
2009-09-01 18:00                                 ` Luis R. Rodriguez
2009-08-31 19:58                     ` Luis R. Rodriguez
2009-09-01 22:10                       ` H. Peter Anvin
2009-08-29 21:41     ` Catalin Marinas
2009-08-30 16:34   ` Aneesh Kumar K.V
2009-08-30 17:17     ` Theodore Tso
2009-08-30 17:29       ` Luis R. Rodriguez
2009-08-30 18:24         ` Theodore Tso
2009-09-01 17:59           ` Luis R. Rodriguez

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=43e72e890908311731h626a5b9bu486653c755cda2fa@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.com \
    --cc=eparis@parisplace.org \
    --cc=eparis@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hpa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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

all inboxes | Powered by JetHome®