[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100401175758.GQ30801@buzzloop.caiaq.de>
Date: Thu, 1 Apr 2010 19:57:58 +0200
From: Daniel Mack <daniel@...aq.de>
To: Anders Grafström
<grfstrm@...rs.sourceforge.net>
Cc: linux-wireless@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...e.de>,
Sven Neumann <s.neumann@...mfeld.com>,
LKML <linux-kernel@...r.kernel.org>, stable@...nel.org,
AKML <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Memory corruption with 2.6.32.10, but not with 2.6.34-rc3
On Thu, Apr 01, 2010 at 07:29:59PM +0200, Anders Grafström wrote:
> Daniel Mack wrote:
> > We would like to have a fix for this annoying bug in the stable series
> > (especially 2.6.32.x) as well, but I don't have much ideas about where
> > to search for it. Hence, I would appreciate if maintainers could think
> > about any possible commits in the described time window which haven't
> > reached stable. Does the description ring anyone's bell?
> >
> > I can cherry-pick things if anyone pin-points something and run
> > lont-time tests again. Any pointer appreciated.
>
> You could try this one:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8e4971f2fb2380ce66196136e113d04196b80fcd
Thanks. Unfortunately, that didn't fix it (this time, it crashed after a
few minutes only). But shouldn't we have that in -stable anyway?
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists