From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: Pavel Machek In-Reply-To: <20061223235501.GA1740@elf.ucw.cz> References: <20061223234305.GA1809@elf.ucw.cz> <20061223235501.GA1740@elf.ucw.cz> Date: Sun, 24 Dec 2006 15:39:23 +0100 Message-Id: <1166971163.15485.21.camel@violet> Mime-Version: 1.0 Cc: Andrew Morton , bluez-devel@lists.sf.net, kernel list , maxk@qualcomm.com Subject: Re: [Bluez-devel] bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752100AbWLXPDv (ORCPT ); Sun, 24 Dec 2006 10:03:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752113AbWLXPDv (ORCPT ); Sun, 24 Dec 2006 10:03:51 -0500 Received: from coyote.holtmann.net ([217.160.111.169]:53111 "EHLO mail.holtmann.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752100AbWLXPDu (ORCPT ); Sun, 24 Dec 2006 10:03:50 -0500 X-Greylist: delayed 1424 seconds by postgrey-1.27 at vger.kernel.org; Sun, 24 Dec 2006 10:03:50 EST Subject: Re: bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) From: Marcel Holtmann To: Pavel Machek Cc: Andrew Morton , kernel list , maxk@qualcomm.com, bluez-devel@lists.sourceforge.net In-Reply-To: <20061223235501.GA1740@elf.ucw.cz> References: <20061223234305.GA1809@elf.ucw.cz> <20061223235501.GA1740@elf.ucw.cz> Content-Type: text/plain Date: Sun, 24 Dec 2006 15:39:23 +0100 Message-Id: <1166971163.15485.21.camel@violet> Mime-Version: 1.0 X-Mailer: Evolution 2.9.4 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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