From: Alan Stern <stern@rowland.harvard.edu>
To: Raymano Garibaldi <raymano@faunos.com>
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>
Subject: Re: [linux-usb-devel] [BUG] USB_PERSIST
Date: Mon, 26 Nov 2007 17:17:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0711261713280.14778-100000@netrider.rowland.org> (raw)
In-Reply-To: <1618816c0711261043nfa61e63m59d242fbbd6a8d6@mail.gmail.com>
On Mon, 26 Nov 2007, Raymano Garibaldi wrote:
> > Wait a minute. You're saying that USB Persist worked under 2.6.21
> > because it wasn't available? That makes no sense. Besides, if you
> > don't like USB Persist under 2.6.23, you can always eliminate it by
> > turning off CONFIG_USB_PERSIST.
> >
>
> 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.
Something about this doesn't sound right.
When you have CONFIG_USB_PERSIST enabled, do you remember to turn on
the Persist feature for the root fs device by writing a "1" to the
device's power/persist file in sysfs?
Can you try building a kernel with CONFIG_USB_PERSIST and
CONFIG_USB_DEBUG both enabled, and post the dmesg log from immediately
after resuming?
Alan Stern
next prev parent reply other threads:[~2007-11-26 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 4:14 [BUG] USB_PERSIST 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 [this message]
2007-11-28 6:02 ` Raymano Garibaldi
2007-11-28 22:14 ` Alan Stern
2007-11-29 11:53 ` Raymano Garibaldi
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=Pine.LNX.4.44L0.0711261713280.14778-100000@netrider.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=raymano@faunos.com \
--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;
as well as URLs for NNTP newsgroup(s).