All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>, Johan Hovold <jhovold@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	Len Brown <len.brown@intel.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Arjan van de Ven <arjan@linux.intel.com>,
	linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, Andreas Mohr <andi@lisas.de>,
	Daniel Sangorrin <daniel.sangorrin@gmail.com>,
	linux-usb@vger.kernel.org
Subject: BUG, regression. usb-serial adapter broken by PM?
Date: Mon, 29 Nov 2010 20:52:14 -0500	[thread overview]
Message-ID: <4CF458CE.2050603@gmail.com> (raw)

Hello,

Recently, my usb-serial converter has become unusable. Attempts to open
the device always fail with:
open("/dev/ttyUSB0", O_RDONLY)          = -1 EAGAIN (Resource temporarily unavailable)

The device is a:
ID 0c52:2101 Sealevel Systems, Inc. Serial Converter
and uses the ftdi_sio driver.

I've bisected this problem to
commit 1bfee5bc86fdaecc912e06080583eddab7263df2
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Sat Sep 25 23:35:00 2010 +0200

    PM / Runtime: Merge synchronous and async runtime routines

I have other usb-serial converters that use other drivers and that are
unaffected. I have noticed the problem on a x86_64 machine (.config
here: http://pastebin.ca/2006414) and can reproduce it in kvm (with usb
passthrough, .config here: http://pastebin.ca/2006416).

I'll be glad to provide more info or try patches.

Thanks,
-Ben

             reply	other threads:[~2010-11-30  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  1:52 Benjamin Poirier [this message]
2010-11-30  3:26 ` BUG, regression. usb-serial adapter broken by PM? Greg KH
2010-11-30  3:26 ` Greg KH
2010-11-30 15:11   ` Benjamin Poirier
2010-11-30 15:11   ` Benjamin Poirier
  -- strict thread matches above, loose matches on Subject: below --
2010-11-30  1:52 Benjamin Poirier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CF458CE.2050603@gmail.com \
    --to=benjamin.poirier@gmail.com \
    --cc=andi@lisas.de \
    --cc=arjan@linux.intel.com \
    --cc=daniel.sangorrin@gmail.com \
    --cc=gregkh@suse.de \
    --cc=jhovold@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.