mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Raymano Garibaldi" <raymano@faunos.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Denys Vlasenko" <vda.linux@googlemail.com>,
	"Kernel development list" <linux-kernel@vger.kernel.org>,
	"USB development list" <linux-usb-devel@lists.sourceforge.net>,
	kirk@faunos.com
Subject: Re: [linux-usb-devel] [BUG] USB_PERSIST
Date: Thu, 29 Nov 2007 04:53:25 -0700	[thread overview]
Message-ID: <1618816c0711290353h3c0e4192we5909725d1aff3e9@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711281711210.3641-100000@iolanthe.rowland.org>

The feature does work as long as the device remains plugged in and
that is what I have said in my previous postings too. What I'm saying
that should work and worked under 2.6.21 and is not working currently
is the ability to unplug and plug back in the device while the
computer is suspended before resuming without losing the mount.

On 11/28/07, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Tue, 27 Nov 2007, Raymano Garibaldi wrote:
>
> > Hi Alan,
> >
> > Here's what I got after compiling kernel with CONFIG_USB_PERSIST and
> > CONFIG_USB_DEBUG both enabled. The attached files are:
> >
> > config - shows the .config file used when compiling kernel 2.6.23.9
> >
> > sysandmount.txt - shows mounts and the state of persist for all usb
> > devices right before suspending.
> >
> > dmesg_attached.txt - dmesg right after resuming when the USB device
> > remained attached while machine was suspend
> >
> > dmesg_detachedandreattached.txt - dmesg right after resuming when the
> > USB device was detached while suspended and then reattached before
> > resuming.
>
> This all looks okay.  Earlier you wrote:
>
> > I have tried this. Simply turning off CONFIG_USB_PERSIST doesn't work.
> > In this case the USB drive file system is unmounted on resume, even if
> > the drive remained plugged in during suspend.
>
> But the logs you just posted show that the filesystem _does_ remain
> mounted after resume, provided you don't unplug the drive.  At least
> that's what it looked like -- it was hard to tell for sure because each
> logfile contained multiple suspend/resume cycles with varying outcomes.
>
> Alan Stern
>
>

  reply	other threads:[~2007-11-29 11:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  4:14 Raymano Garibaldi
2007-11-19  4:37 ` Denys Vlasenko
2007-11-19  6:18   ` Raymano Garibaldi
2007-11-21  0:04     ` Raymano Garibaldi
2007-11-25  6:39       ` Andrew Morton
2007-11-25 16:06         ` [linux-usb-devel] " Alan Stern
2007-11-26  5:17           ` Raymano Garibaldi
2007-11-26 15:16             ` Alan Stern
2007-11-26 18:43               ` Raymano Garibaldi
2007-11-26 22:17                 ` Alan Stern
2007-11-28  6:02                   ` Raymano Garibaldi
2007-11-28 22:14                     ` Alan Stern
2007-11-29 11:53                       ` Raymano Garibaldi [this message]
2007-11-29 16:08                         ` Alan Stern
2007-11-29 19:01                           ` Mark Lord
2007-11-29 19:07                             ` Alan Stern
2007-11-30  4:37                           ` Raymano Garibaldi

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=1618816c0711290353h3c0e4192we5909725d1aff3e9@mail.gmail.com \
    --to=raymano@faunos.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirk@faunos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=vda.linux@googlemail.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

all inboxes | Powered by JetHome®