Subject: Re: [BUG] rfcomm]
From: Marcel Holtmann <marcel@holtmann.org>
To: Alon Bar-Lev <alon.barlev@gmail.com>
Cc: linux-kernel@vger.kernel.org, bluez-devel@lists.sourceforge.net
In-Reply-To: <200710231950.31313.alon.barlev@gmail.com>
References: <200710231950.31313.alon.barlev@gmail.com>
Content-Type: text/plain
Date: Tue, 23 Oct 2007 19:55:06 +0200
Message-Id: <1193162106.6184.208.camel@violet>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 842
Lines: 26

Hi Alon,

> I have this issue for long time (At least from linux-2.6.18).
> I think it is about time I report this... :)
> 
> When coming out of suspend (uswsusp or suspend2) if rfcomm was
> active it creates this dump.
> 
> If you need any more info I will be glad to provide.

first of all, please check if this still happens with 2.6.23, because we
had some patches in the area of the RFCOMM TTY code that might have
fixed this. Second, can you try without uswsusp or suspend2. Both of
them are not upstream and I can't tell how much these would effect this
kind of behavior.

Regards

Marcel


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/