From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.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 15:33:45 -0400 [thread overview]
Message-ID: <20090831193345.GG5631@tuxdriver.com> (raw)
In-Reply-To: <43e72e890908311230u28b0642ep7a6bfd9dab82318a@mail.gmail.com>
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...
What is linux-2.6-allstable? My guess is that the culprit is between
v2.6.31-rc8 and whatever is at the head of linux-2.6-allstable.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-08-31 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43e72e890908272225w79ec5bf6kc7ef1160e5a088ae@mail.gmail.com>
[not found] ` <tnxtyzr7vcl.fsf@pc1117.cambridge.arm.com>
[not found] ` <43e72e890908280952j410293fbm47b4b9d566e26c14@mail.gmail.com>
[not found] ` <43e72e890908281450k78cc1a2fmd4fd033ae0f4176f@mail.gmail.com>
[not found] ` <43e72e890908281509o44930348w581b865107ea3e98@mail.gmail.com>
2009-08-31 8:23 ` memleaks, acpi + ext4 + tty 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 [this message]
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
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
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=20090831193345.GG5631@tuxdriver.com \
--to=linville@tuxdriver.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=mcgrof@gmail.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;
as well as URLs for NNTP newsgroup(s).