[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080116230646.GB6715@boogie.lpds.sztaki.hu>
Date: Thu, 17 Jan 2008 00:06:46 +0100
From: Gabor Gombas <gombasg@...aki.hu>
To: Dave Young <hidave.darkstar@...il.com>
Cc: Cornelia Huck <cornelia.huck@...ibm.com>,
Tejun Heo <htejun@...il.com>,
Al Viro <viro@...iv.linux.org.uk>,
linux-kernel@...r.kernel.org, bluez-devel@...ts.sf.net,
kay.sievers@...y.org, Greg KH <greg@...ah.com>,
Marcel Holtmann <marcel@...tmann.org>, davem@...emloft.net
Subject: Re: [Bluez-devel] Oops involving RFCOMM and sysfs
Hi,
On Wed, Jan 16, 2008 at 09:02:05AM +0800, Dave Young wrote:
> The rfcomm tty device will possibly retain even when conn is down,
> and sysfs doesn't support zombie device moving, so this patch
> move the tty device before conn device is destroyed.
>
> Signed-off-by: Dave Young <hidave.darkstar@...il.com>
This seems to work, both the oops and the hang are gone. I get these
messages in syslog when the Bluetooth link hangs and I want to kill pppd
with "poff":
Jan 16 23:55:59 twister kernel: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1
Jan 16 23:56:09 twister kernel: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1
But a "killall -9 pppd" seems to help and then the re-connect (after the
phone got power-cycled) works.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists