[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1618816c0711290353h3c0e4192we5909725d1aff3e9@mail.gmail.com>
Date: Thu, 29 Nov 2007 04:53:25 -0700
From: "Raymano Garibaldi" <raymano@...nos.com>
To: "Alan Stern" <stern@...land.harvard.edu>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Denys Vlasenko" <vda.linux@...glemail.com>,
"Kernel development list" <linux-kernel@...r.kernel.org>,
"USB development list" <linux-usb-devel@...ts.sourceforge.net>,
kirk@...nos.com
Subject: Re: [linux-usb-devel] [BUG] USB_PERSIST
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@...land.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
>
>
-
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