[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0711261713280.14778-100000@netrider.rowland.org>
Date: Mon, 26 Nov 2007 17:17:51 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Raymano Garibaldi <raymano@...nos.com>
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>
Subject: Re: [linux-usb-devel] [BUG] USB_PERSIST
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
-
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