mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: 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 12:43:01 -0700	[thread overview]
Message-ID: <43e72e890908311243u50b9323fveda9feaaa4d8efdb@mail.gmail.com> (raw)
In-Reply-To: <20090831193345.GG5631@tuxdriver.com>

On Mon, Aug 31, 2009 at 12:33 PM, John W.
Linville<linville@tuxdriver.com> wrote:
> On Mon, Aug 31, 2009 at 12:30:15PM -0700, Luis R. Rodriguez wrote:
>> On Mon, Aug 31, 2009 at 11:37 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>
>> > OK I tried this, I even 'rm -rf * ; git checkout -f' and ..
>> > merge-2009-08-28 tag yields the same issues, long lag upon bootup with
>> > some kmemleaks I cannot even get to check. So somehow something is
>> > different between merge-2009-08-28 and Linus' rc8. This is just
>> > bizarre so to be even safer I'm just going to do a fresh git clone on
>> > wireless-testing.
>>
>> Hey John so I tested wireless-testing on the merge-2009-08-28 tag on a
>> fresh git pull and verified this is indeed busted for me. Although I
>> had tried hpa's linux-2.6-allstable on HEAD just to be sure I am now
>> building Linus' tree from a fresh git clone on the v2.6.31-rc8 tag
>> just to be double check this was indeed not a 2.6.31-rc8 issue but
>> instead *something* on wireless-testing. What that something is is
>> unclear to me still, I guess after all these tests I'll run a manual
>> diff as git doesn't seem to be picking anything up.
>
> As you determined, there is no difference between merge-2009-08-28
> and v2.6.31-rc8.  If one works and the other doesn't, then the main
> thing not working will be git...

Hm that would suck big time. At any rate, even if it was git
wireless-testing seems to have an issue right now. I'll confirm
shortly with Linus' own tree.

> What is linux-2.6-allstable?

hpa's collection of 2.6 stable kernels, including extraversion stuff.

> 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.

  Luis

  reply	other threads:[~2009-08-31 19:43 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 [this message]
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
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=43e72e890908311243u50b9323fveda9feaaa4d8efdb@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=catalin.marinas@arm.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®