From: Marcel Holtmann <marcel@holtmann.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
bluez-devel@lists.sf.net,
kernel list <linux-kernel@vger.kernel.org>,
maxk@qualcomm.com
Subject: Re: [Bluez-devel] bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1)
Date: Sun, 24 Dec 2006 15:39:23 +0100 [thread overview]
Message-ID: <1166971163.15485.21.camel@violet> (raw)
In-Reply-To: <20061223235501.GA1740@elf.ucw.cz>
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.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
kernel list <linux-kernel@vger.kernel.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: Sun, 24 Dec 2006 15:39:23 +0100 [thread overview]
Message-ID: <1166971163.15485.21.camel@violet> (raw)
In-Reply-To: <20061223235501.GA1740@elf.ucw.cz>
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.
Regards
Marcel
next prev parent reply other threads:[~2006-12-24 14:39 UTC|newest]
Thread overview: 22+ 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 [this message]
2006-12-24 14:39 ` Marcel Holtmann
2006-12-24 23:36 ` [Bluez-devel] " Pavel Machek
2006-12-24 23:36 ` Pavel Machek
2006-12-30 21:52 ` Adrian Bunk
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 ` [Bluez-devel] " Marcel Holtmann
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=1166971163.15485.21.camel@violet \
--to=marcel@holtmann.org \
--cc=akpm@osdl.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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.