public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	maxk@qualcomm.com, bluez-devel@lists.sourceforge.net
Subject: Re: bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1)
Date: Sat, 30 Dec 2006 22:52:50 +0100	[thread overview]
Message-ID: <20061230215250.GF20714@stusta.de> (raw)
In-Reply-To: <20061224233647.GB1761@elf.ucw.cz>

On Mon, Dec 25, 2006 at 12:36:47AM +0100, Pavel Machek wrote:
> On Sun 2006-12-24 15:39:23, Marcel Holtmann wrote:
> > Hi Pavel,
> > 
> > > > I got this nasty oops while playing with debugger. Not sure if that is
> > > > related; it also might be something with bluetooth; I already know it
> > > > corrupts memory during suspend, perhaps it corrupts memory in some
> > > > error path?
> > > 
> > > Okay, I spoke too soon. bluetooth & suspend memory corruption was
> > > _way_ harder to reproduce than expected. Took me 5-or-so-suspend
> > > cycles... so it is probably unrelated to the previous crash.
> > 
> > can you try to reproduce this with 2.6.20-rc2 as well.
> 
> Yep, here it is, reproduced on 6-th-or-so suspend.
> 
> bluetooth may need to be actively used in order for this to trigger;
> connecting to the net over my cellphone seems to work okay.
> 
> (Full logs in attachment).

Is this issue also present in 2.6.19 or is it a regression?

> 								Pavel

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-12-30 21:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-23 23:43 ext3-related crash in 2.6.20-rc1 Pavel Machek
2006-12-23 23:55 ` bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Pavel Machek
2006-12-24  0:01   ` Pavel Machek
2006-12-24  0:06     ` not-only-bluetooth memory corruption Pavel Machek
2006-12-24  0:07       ` ptrace() memory corruption? Pavel Machek
2006-12-24  1:14         ` Jiri Slaby
2006-12-24 11:52           ` Jiri Slaby
2006-12-24 12:22             ` Andrew Morton
2006-12-24 13:44               ` Jiri Slaby
2006-12-24  1:18   ` bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Andrew Morton
2006-12-24 23:24     ` Pavel Machek
2006-12-24 14:39   ` Marcel Holtmann
2006-12-24 23:36     ` Pavel Machek
2006-12-30 21:52       ` Adrian Bunk [this message]
2007-01-01 19:01         ` Pavel Machek
2006-12-24 23:43     ` Pavel Machek
2006-12-28  8:42       ` Pavel Machek
2006-12-28 10:40         ` Marcel Holtmann
2006-12-24  1:12 ` ext3-related crash in 2.6.20-rc1 Andrew Morton

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=20061230215250.GF20714@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.com \
    --cc=pavel@ucw.cz \
    /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