From: Pavel Machek <pavel@ucw.cz>
To: Tom Yan <tom.ty89@gmail.com>, linux-scsi@vger.kernel.org
Cc: kernel list <linux-kernel@vger.kernel.org>,
james harvey <jamespharvey20@gmail.com>,
regressions@leemhuis.info, hdegoede@redhat.com,
Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, Oliver Neukum <oliver@neukum.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Date: Sun, 14 Aug 2016 13:10:34 +0200 [thread overview]
Message-ID: <20160814111034.GA10616@amd> (raw)
In-Reply-To: <CAGnHSEnXo8VRm5Y6S6axpe-hG6an8ceujLajbZmxbGGDnCGh2w@mail.gmail.com>
Hi!
On Sun 2016-08-14 18:17:39, Tom Yan wrote:
> On 14 August 2016 at 18:07, Tom Yan <tom.ty89@gmail.com> wrote:
> > On 14 August 2016 at 18:01, Pavel Machek <pavel@ucw.cz> wrote:
> >>
> >> Since SATA support was merged, certainly since v2.4, and from way
> >> before /dev/disk/by-id existed.
> >
> > I have no idea how "SATA before USB" had been done in the past (if it
> > was ever a thing in the kernel), but that has not been the case since
> > at least v3.0 AFAIR.
It is the case in v4.6. We had change hda->sda for SATA drives long
time ago, it was stable since that.
> > No, but you can always use root=PARTUUID=, that's built into the
> > kernel. (root=UUID= requires udev or so though).
>
> Silly me. root=UUID= has nothing to do with udev, but `blkid` in
> util-linux. At least that's how it's done in Arch/mkinitcpio.
I'd rather not mess with initrd, and initrd was not required in the
past.
kernel-parameters.txt only mentions UUID= in connection with
resume. Is the documentation correct?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-08-14 11:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 19:30 Who reordered my disks (probably v4.8-rc1 problem) Pavel Machek
2016-08-14 9:03 ` james harvey
2016-08-14 9:09 ` Pavel Machek
2016-08-14 21:40 ` james harvey
2016-08-14 12:38 ` Bob Tracy
2016-08-14 9:20 ` Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek
2016-08-14 9:34 ` Tom Yan
2016-08-14 10:01 ` Pavel Machek
2016-08-14 10:07 ` Tom Yan
2016-08-14 10:17 ` Tom Yan
2016-08-14 10:26 ` David Lang
2016-08-14 10:53 ` Tom Yan
2016-08-14 14:14 ` Oliver Neukum
2016-08-14 11:29 ` Greg KH
2016-08-14 12:03 ` Pavel Machek
2016-08-14 14:15 ` Greg KH
2016-08-14 14:56 ` Alan Stern
2016-08-14 16:13 ` Pavel Machek
2016-08-14 11:10 ` Pavel Machek [this message]
2016-08-14 11:41 ` Tom Yan
2016-08-14 16:09 ` One Thousand Gnomes
2016-08-14 10:14 ` Pavel Machek
2016-08-14 16:06 ` Pavel Machek
2016-08-14 17:55 ` Pavel Machek
2016-08-14 18:22 ` Hans de Goede
2016-08-15 15:05 ` Who reordered my disks (probably v4.8-rc1 problem) Austin S. Hemmelgarn
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=20160814111034.GA10616@amd \
--to=pavel@ucw.cz \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jamespharvey20@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=regressions@leemhuis.info \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
--cc=tom.ty89@gmail.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