From: Greg KH <greg@kroah.com>
To: rasmit.ranjan@wipro.com
Cc: linux-pm@lists.osdl.org
Subject: Re: problem in swsusp with usb-serial convertor attached
Date: Fri, 20 Jan 2006 10:01:23 -0800 [thread overview]
Message-ID: <20060120180123.GA24266@kroah.com> (raw)
In-Reply-To: <380D9721A8E2114485644D71E87C6AB2014368BB@PNE-HJN-MBX01.wipro.com>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On Fri, Jan 20, 2006 at 12:30:36PM +0530, rasmit.ranjan@wipro.com wrote:
> hi,
> In my system Linux-2.6.13.3 swsusp works properly.
Have you tried 2.6.15? And enabled CONFIG_USB_SUSPEND?
> Now one usb-serial convertor device is attached to my system. I manually
> loaded the driver for the device and attached the device to my system.At
> this stage swsusp works properly. But my device is not in use. So resume
> works properly.
> Now i opened minicom terminal for ttyUSB0 and ttyS0 ( now my device is
> in use ) and suspend my system. My system got suspended but did not get
> resumed and showed the follwing messages on screen.
>
> usb 1-1: USB disconnect,address 4
> usb 1-1: usb_disable_device nuking all URBs
> usb 1-1: unregistering interface 1-1:1.0
> rasmit 1-1:1.0 device disconnected
> usb 1-1:1.0 : hot plug
>
> My device was connected to 1-1:1.0
> The driver for usb-serial convertor does not have suspend/resume
> functions.
Which usb-serial driver are you using for this device?
> Is it happening because of the driver does not handle suspend/resume or
> for any other reason ?
None of the usb-serial drivers handle suspend/resume natively, they rely
on the usb core to do a disconnect and reconnect, which will probably
cause your terminal to be disconnected, like you see.
So, I guess everything is working properly :)
thanks,
greg k-h
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2006-01-20 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 7:00 problem in swsusp with usb-serial convertor attached rasmit.ranjan
2006-01-20 18:01 ` Greg KH [this message]
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=20060120180123.GA24266@kroah.com \
--to=greg@kroah.com \
--cc=linux-pm@lists.osdl.org \
--cc=rasmit.ranjan@wipro.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox