From: Andreas Mohr <andi@lisas.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andreas Mohr <andi@lisas.de>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: USB enumeration post-resume NOT persistent yet "persist" --> swapped devices nodes --> root partition reference broken
Date: Thu, 19 Jul 2012 19:30:57 +0200 [thread overview]
Message-ID: <20120719173057.GA1031@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1207191100520.1764-100000@iolanthe.rowland.org>
Hi,
On Thu, Jul 19, 2012 at 11:11:50AM -0400, Alan Stern wrote:
> On Thu, 19 Jul 2012, Andreas Mohr wrote:
>
> > Hi,
> >
> > Yesterday I was surprised to see that with *another* external USB disk
> > happening to be connected before boot,
> > the system booted with root partition device sdb1 assigned rather than sda1.
> > Not thinking much, I then proceeded putting the system into suspend,
>
> Do you mean "suspend" or "hibernate"?
Doh - S2R. I don't do persistent hibernate here (writing some 1GB of data
to flash-based storage each time possibly isn't all too healthy anyway).
> Can you reproduce the problem?
Will retry soonish.
> > http://lists.linux-foundation.org/pipermail/linux-pm/2009-November/023101.html
> > Netbook Acer Aspire One A110L.
> > Running 3.5.0-rc7+ here (yes ma'am, bleeding edge tester :).
> > Was the first time to attempt resume with an additional device remaining
> > connected, IIRC - that -rc7 thing likely doesn't play much of a role here.
> > A bit hesitant to (dis-)prove the bug's "regression flag" with another version
> > since random possibly succeeding I/O accesses to incompatible devices
> > are not necessarily my thing (or is this safe to attempt again? Any more
> > specific session info one would need?).
>
> Well, the dmesg log would help. If you still think the USB layer is at
> fault then you should enable CONFIG_USB_DEBUG.
Maybe I can get this successfully off the machine next time,
by pre-caching required binaries prior to initiating a non-working resume.
> > So, again, possibly USB persistence is bug-broken?
>
> You don't have any good evidence to suggest that. None of the
> information you provided indicates that any USB device nodes (such as
> /dev/bus/usb/001/002) got mixed up. All you know is that the
> block-layer device nodes (such as /dev/sda2) got changed.
OK - so you're trying in vain to tell dense me that I'm supposed to
take note of the *non-changing* (i.e., correctly "persistent")
USB device ID scheme rather than the roguely changing device nodes.
To which I say that unfortunately I don't have a pre/post comparison
at this moment yet.
> Furthermore, if USB persist were broken then the symptoms would be
> different. Instead of starting with a root partition at sdb1 and then
> finding it at sda1, you would have found it gone completely and there
> would be _new_ devices labelled sdc and sdd.
Ah, yeah - I tend to know *this* other effect, too...
> Alan Stern
Thanks a ton for your reply!
Now I know that there's a tendency to better look on the other side
(block device layer etc.) and analyze things there,
once it's established that USB topology ID numbering in fact did persist.
Andreas Mohr
next prev parent reply other threads:[~2012-07-19 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 4:09 Andreas Mohr
2012-07-19 15:11 ` Alan Stern
2012-07-19 17:30 ` Andreas Mohr [this message]
2012-07-19 19:03 ` Alan Stern
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=20120719173057.GA1031@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®