Bug 13646

Summary: warn_on tty_io.c, broken bluetooth
Product: Drivers Reporter: Rafael J. Wysocki (rjw)
Component: BluetoothAssignee: drivers_bluetooth (drivers_bluetooth)
Status: CLOSED INSUFFICIENT_DATA    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.30 Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 13070    

Description Rafael J. Wysocki 2009-06-28 21:21:11 UTC 
Subject    : 2.6.30-rc6 -> final regression: warn_on tty_io.c, broken bluetooth
Submitter  : Pavel Machek <pavel@ucw.cz>
Date       : 2009-06-19 17:05
References : http://lkml.org/lkml/2009/6/19/187

This entry is being used for tracking a regression from 2.6.29.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Rafael J. Wysocki 2009-08-29 12:28:45 UTC 
On Saturday 29 August 2009, Pavel Machek wrote:
> On Wed 2009-08-26 09:14:02, Pekka Enberg wrote:
> > On Wed, Aug 26, 2009 at 12:05 AM, Rafael J. Wysocki<rjw@sisk.pl> wrote:
> > > This message has been generated automatically as a part of a report
> > > of regressions introduced between 2.6.29 and 2.6.30.
> > >
> > > The following bug entry is on the current list of known regressions
> > > introduced between 2.6.29 and 2.6.30. ?Please verify if it still should
> > > be listed and let me know (either way).
> > >
> > >
> > > Bug-Entry ? ? ? : http://bugzilla.kernel.org/show_bug.cgi?id=13646
> > > Subject ? ? ? ? : warn_on tty_io.c, broken bluetooth
> > > Submitter ? ? ? : Pavel Machek <pavel@ucw.cz>
> > > Date ? ? ? ? ? ?: 2009-06-19 17:05 (68 days old)
> > > References ? ? ?: http://lkml.org/lkml/2009/6/19/187
> > 
> > Pavel, is this still an open issue? Plenty tty fixes went into 2.6.31
> > so maybe we need to backport some of them to -stable?
> 
> It seems to be interminent, and depends on timing/usage patterns. (Try
> to start bluetooth when it is already starting). It
> is possible that it was there before. Perhaps it can be just closed as
> 'bug but not regression'.
Comment 2 Rafael J. Wysocki 2009-08-29 12:29:28 UTC 
Closing as "insufficient data".