On Wed, Jul 10, 2013 at 10:39:21AM +0200, Mathias Hasselmann wrote: > > Is this failure easy to reproduce ? > > Just setup a RFCOMM tty and then violently break the link, by killing > the rfcomm tool, by plugging the bt adapter, by turning off one > peer, ... As soon as timeouts occur on the still running side you'll get > the panic. Almost 100% reproducible. Hi, yes indeed that's the easiest way to reproduce the issue. I was wondering why so few people hit these bugs since they're so easy to trigger. Did you have a chance to test the two patches I sent? Ciao, Gianluca > > Ciao, > Mathias > -- > Mathias Hasselmann | mathias.hasselmann@xxxxxxxx | Software Engineer > KDAB (Deutschland) GmbH&Co KG, a KDAB Group company > Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090 > KDAB - Qt Experts - Platform-independent software solutions > > -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
