[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200911161447.51651.oliver@neukum.org>
Date: Mon, 16 Nov 2009 14:47:51 +0100
From: Oliver Neukum <oliver@...kum.org>
To: Pavel Machek <pavel@....cz>
Cc: Alan Stern <stern@...land.harvard.edu>,
USB list <linux-usb@...r.kernel.org>,
kernel list <linux-kernel@...r.kernel.org>,
marcel@...tmann.org, linux-bluetooth@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: -rc6: something (probably active usb bluetooth) blocks suspend
Am Samstag, 14. November 2009 12:10:21 schrieb Pavel Machek:
> On Mon 2009-11-16 12:48:29, Oliver Neukum wrote:
> > Am Montag, 16. November 2009 12:22:54 schrieb Pavel Machek:
> >
> > Hi Pavle,
> >
> :-)
> :
> > first the obvious question. Does it work if you down the interface?
> > (not by killswitch)
>
> Well, I'm not sure how repeatable it is. It happens once in two tries
> today.
Ok, so it looks like a race.
> > > usb 5-1: usb suspend
> > > usb 5-1: usb auto-resume
> > > uhci_hcd 0000:00:1d.3: port 1 portsc 0095,01
> > > usb 5-1: finish resume
> > > uhci_hcd 0000:00:1d.3: reserve dev 2 ep81-INT, period 1, phase 0, 23
> > > us
> >
> > Why is the device autoresumed here? Are you using autosuspend?
> > This is odd, as the freezer should block the send path and remote
> > wakeups should be deferred.
>
> I believe I have it enabled in kconfig but not during runtime.
Please check.
> (Another problem is that I need to turn the kill switch on/off to get
> my bt usb after resume. That used not be the case long time ago.)
That is possibly another problem.
Regards
Oliver
--
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