From: Daniel Mack <daniel@caiaq.de>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
AKML <linux-arm-kernel@lists.infradead.org>,
linux-wireless@vger.kernel.org,
Sven Neumann <s.neumann@raumfeld.com>
Subject: Re: Memory corruption with 2.6.32.10, but not with 2.6.34-rc3
Date: Thu, 1 Apr 2010 19:00:04 +0200 [thread overview]
Message-ID: <20100401170004.GO30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100401165056.GA1138@suse.de>
On Thu, Apr 01, 2010 at 09:50:56AM -0700, Greg KH wrote:
> On Thu, Apr 01, 2010 at 03:21:56PM +0200, Daniel Mack wrote:
> > So my current summary is that this is related to WiFi, but OTOH it still
> > only happens when file system traffic is issued.
> >
> > 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't think of any USB specific patches that would be related to this,
> sorry.
Yes, I'd rule out USB anyway. It crashes without any USB function as
well. I just copied you as the maintainer of the stable tree :)
Daniel
WARNING: multiple messages have this Message-ID (diff)
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 19:00:04 +0200 [thread overview]
Message-ID: <20100401170004.GO30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100401165056.GA1138@suse.de>
On Thu, Apr 01, 2010 at 09:50:56AM -0700, Greg KH wrote:
> On Thu, Apr 01, 2010 at 03:21:56PM +0200, Daniel Mack wrote:
> > So my current summary is that this is related to WiFi, but OTOH it still
> > only happens when file system traffic is issued.
> >
> > 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't think of any USB specific patches that would be related to this,
> sorry.
Yes, I'd rule out USB anyway. It crashes without any USB function as
well. I just copied you as the maintainer of the stable tree :)
Daniel
next prev parent reply other threads:[~2010-04-01 17:00 UTC|newest]
Thread overview: 16+ 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 13:21 ` Daniel Mack
2010-04-01 16:50 ` Greg KH
2010-04-01 16:50 ` Greg KH
2010-04-01 17:00 ` Daniel Mack [this message]
2010-04-01 17:00 ` Daniel Mack
2010-04-01 16:51 ` Greg KH
2010-04-01 16:51 ` Greg KH
2010-04-01 16:58 ` Daniel Mack
2010-04-01 16:58 ` Daniel Mack
2010-04-05 10:59 ` Uwe Kleine-König
2010-04-05 10:59 ` Uwe Kleine-König
2010-04-01 17:29 ` Anders Grafström
2010-04-01 17:29 ` Anders Grafström
2010-04-01 17:57 ` Daniel Mack
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=20100401170004.GO30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=gregkh@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.neumann@raumfeld.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.