From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Memory corruption with 2.6.32.10, but not with 2.6.34-rc3
Date: Thu, 1 Apr 2010 18:58:57 +0200 [thread overview]
Message-ID: <20100401165857.GN30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100401165144.GB1138@suse.de>
On Thu, Apr 01, 2010 at 09:51:44AM -0700, Greg KH wrote:
> On Thu, Apr 01, 2010 at 03:21:56PM +0200, Daniel Mack wrote:
> >
> > I can cherry-pick things if anyone pin-points something and run
> > lont-time tests again. Any pointer appreciated.
>
> Oh, how about running 'git bisect' to try to find the solution? Just
> remember to reverse 'good' and 'bad' for when you tell git bisect what
> the results are.
Jep, I thought about that of course. But unfortunately, the platform
got merged mainline in the middle of that time window which makes
bisecting tricky. And worse than that - every test run take around half
a day at least :(
Daniel
next prev parent reply other threads:[~2010-04-01 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 13:21 Memory corruption with 2.6.32.10, but not with 2.6.34-rc3 Daniel Mack
2010-04-01 16:50 ` Greg KH
2010-04-01 17:00 ` Daniel Mack
2010-04-01 16:51 ` Greg KH
2010-04-01 16:58 ` Daniel Mack [this message]
2010-04-05 10:59 ` Uwe Kleine-König
2010-04-01 17:29 ` Anders Grafström
2010-04-01 17:57 ` Daniel Mack
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=20100401165857.GN30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).