Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1461701 > unrolled thread

Who reordered my disks (probably v4.8-rc1 problem)

Started byPavel Machek <pavel@ucw.cz>
First post2016-08-14 10:40 +0200
Last post2016-08-15 17:10 +0200
Articles 6 on this page of 26 — 11 participants

Back to article view | Back to linux.kernel

Contents

  Who reordered my disks (probably v4.8-rc1 problem) Pavel Machek <pavel@ucw.cz> - 2016-08-14 10:40 +0200
    Re: Who reordered my disks (probably v4.8-rc1 problem) james harvey <jamespharvey20@gmail.com> - 2016-08-14 11:10 +0200
      Re: Who reordered my disks (probably v4.8-rc1 problem) Pavel Machek <pavel@ucw.cz> - 2016-08-14 11:10 +0200
        Re: Who reordered my disks (probably v4.8-rc1 problem) james harvey <jamespharvey20@gmail.com> - 2016-08-14 23:50 +0200
      Re: Who reordered my disks (probably v4.8-rc1 problem) Bob Tracy <rct@gherkin.frus.com> - 2016-08-14 15:40 +0200
    Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot.  [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 11:30 +0200
      Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Tom Yan <tom.ty89@gmail.com> - 2016-08-14 11:40 +0200
        Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Tom Yan <tom.ty89@gmail.com> - 2016-08-14 12:10 +0200
          Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Tom Yan <tom.ty89@gmail.com> - 2016-08-14 12:20 +0200
            Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] David Lang <david@lang.hm> - 2016-08-14 12:40 +0200
              Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Tom Yan <tom.ty89@gmail.com> - 2016-08-14 13:00 +0200
                Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Oliver Neukum <oneukum@suse.com> - 2016-08-14 16:20 +0200
              Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Greg KH <gregkh@linuxfoundation.org> - 2016-08-14 14:00 +0200
                Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 14:10 +0200
                  Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Greg KH <gregkh@linuxfoundation.org> - 2016-08-14 16:20 +0200
                  Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Alan Stern <stern@rowland.harvard.edu> - 2016-08-14 17:00 +0200
                    Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 18:20 +0200
            Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 13:20 +0200
              Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Tom Yan <tom.ty89@gmail.com> - 2016-08-14 13:50 +0200
        Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 12:10 +0200
        Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> - 2016-08-14 18:10 +0200
      Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 12:20 +0200
        Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 18:10 +0200
          Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Pavel Machek <pavel@ucw.cz> - 2016-08-14 20:00 +0200
            Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking  boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)] Hans de Goede <hdegoede@redhat.com> - 2016-08-14 20:30 +0200
    Re: Who reordered my disks (probably v4.8-rc1 problem) "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2016-08-15 17:10 +0200

Page 2 of 2 — ← Prev page 1 [2]

#1462163 — Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

FromOne Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Date2016-08-14 18:10 +0200
SubjectRe: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Message-ID<s6693-1O5-7@gated-at.bofh.it>
In reply to#1461753
On Sun, 14 Aug 2016 17:34:18 +0800
Tom Yan <tom.ty89@gmail.com> wrote:

> Since when it is expected that SATA disks will always be probed before
> USB disks? We can't guarantee that even if we make sure all ata
> drivers are loaded before usb-storage/uas. That's why we need
> consistent namings (e.g. /dev/disk/by-id/*).

It hasn't. It isn't even true on older kernels and can depend on all
sorts of things. I have boxes that will put the USB first, and a 10
second google search says I'm not alone

http://serverfault.com/questions/322946/ensure-usb-disk-is-never-sda-even-when-booting-from-it

So your "regression" goes back to at least 2011.

Alan

[toc] | [prev] | [next] | [standalone]

#1461766 — Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

FromPavel Machek <pavel@ucw.cz>
Date2016-08-14 12:20 +0200
SubjectRe: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Message-ID<s60Gl-6CJ-5@gated-at.bofh.it>
In reply to#1461749
On Sun 2016-08-14 11:20:44, Pavel Machek wrote:
> Hi!
> 
> > It seems that in v4.8-rc0, /dev/sdX got reordered, and now USB devices
> > are probed before SATA drivers. That is pretty anti-social. It
> > broke my boot on my primary machine, and unfortunately due to BIOS
> > problems (keyboard does not work when connected through a hub) it is
> > less fun than it should be.
> 
> If you know which commit caused	the reordering, that would be helpful.
> 
> v4.1 seems to be ok: SATA disk is sda, as expected.
> 
> v4.4 seems to be ok: SATA disk is sda, as expected.

v4.6 seems to be ok.

v4.7 SATA disk is sde, behind USB card readers. Not helpful.

Ouch. So we have 'stable' kernel with this. Much more fun :-(.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [prev] | [next] | [standalone]

#1462160 — Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

FromPavel Machek <pavel@ucw.cz>
Date2016-08-14 18:10 +0200
SubjectRe: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Message-ID<s6693-1O5-1@gated-at.bofh.it>
In reply to#1461766
On Sun 2016-08-14 12:14:38, Pavel Machek wrote:
> On Sun 2016-08-14 11:20:44, Pavel Machek wrote:
> > Hi!
> > 
> > > It seems that in v4.8-rc0, /dev/sdX got reordered, and now USB devices
> > > are probed before SATA drivers. That is pretty anti-social. It
> > > broke my boot on my primary machine, and unfortunately due to BIOS
> > > problems (keyboard does not work when connected through a hub) it is
> > > less fun than it should be.
> > 
> > If you know which commit caused	the reordering, that would be helpful.
> > 
> > v4.1 seems to be ok: SATA disk is sda, as expected.
> > 
> > v4.4 seems to be ok: SATA disk is sda, as expected.
> 
> v4.6 seems to be ok.

v4.7-rc1 seems to be ok?! 9956d572
v4.7-rc3 seems still to be ok.
v4.7-rc4: still ok.
v4.7-rc5: ok.
v4.7-rc6: problem

Bisecting now, 8 steps to go. As it was introduced between -rc5 and
-rc6, bisect should not be too scary.

Best regards,
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [prev] | [next] | [standalone]

#1462190 — Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

FromPavel Machek <pavel@ucw.cz>
Date2016-08-14 20:00 +0200
SubjectRe: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Message-ID<s67Rw-2Hd-17@gated-at.bofh.it>
In reply to#1462160
On Sun 2016-08-14 18:06:53, Pavel Machek wrote:
> On Sun 2016-08-14 12:14:38, Pavel Machek wrote:
> > On Sun 2016-08-14 11:20:44, Pavel Machek wrote:
> > > Hi!
> > > 
> > > > It seems that in v4.8-rc0, /dev/sdX got reordered, and now USB devices
> > > > are probed before SATA drivers. That is pretty anti-social. It
> > > > broke my boot on my primary machine, and unfortunately due to BIOS
> > > > problems (keyboard does not work when connected through a hub) it is
> > > > less fun than it should be.
> > > 
> > > If you know which commit caused	the reordering, that would be helpful.
> > > 
> > > v4.1 seems to be ok: SATA disk is sda, as expected.
> > > 
> > > v4.4 seems to be ok: SATA disk is sda, as expected.
> > 
> > v4.6 seems to be ok.
> 
> v4.7-rc1 seems to be ok?! 9956d572
> v4.7-rc3 seems still to be ok.
> v4.7-rc4: still ok.
> v4.7-rc5: ok.
> v4.7-rc6: problem
> 
> Bisecting now, 8 steps to go. As it was introduced between -rc5 and
> -rc6, bisect should not be too scary.

Huh. Scary.

I bisected it to

[ba34a65324259082dc6d2924cb82d562db1c6a6b] drm/i915: Avoid early
timeout during AUX transfers

pavel@amd:/data/l/linux$ git bisect log
# bad: [a99cde438de0c4c0cecc1d1af1a55a75b10bfdef] Linux 4.7-rc6
# good: [a8ef0490c3583c3a83fa52ebe60abb8fd7d3c2a4] Merge commit
'4c2e07c6a29e0129e975727b9f57eede813eea85' into bisect-v4.7
git bisect start 'a99cde438de0c4c0cecc1d1af1a55a75b10bfdef'
'a8ef0490c3583c3a83fa52ebe60abb8fd7d3c2a4'
# good: [4c2e07c6a29e0129e975727b9f57eede813eea85] Linux 4.7-rc5
git bisect good 4c2e07c6a29e0129e975727b9f57eede813eea85
# good: [751ad819b0bf443ad8963eb7bfbd533e6a463973] Merge tag
'mac80211-for-davem-2016-06-29-v2' of
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211
git bisect good 751ad819b0bf443ad8963eb7bfbd533e6a463973
# good: [aa7a6c8e5252ba28f36a8f87b9acd6a726aa3ae5] Merge tag
'iommu-fixes-v4.7-rc5' of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
git bisect good aa7a6c8e5252ba28f36a8f87b9acd6a726aa3ae5
# good: [dbdc3bb74faeec5fd92e28c15c945045d5aab426] Merge tag
'acpi-4.7-rc6' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
git bisect good dbdc3bb74faeec5fd92e28c15c945045d5aab426
# good: [467ce7693f5111c11daeb75e02eba2ab9ee6f334] Merge tag
'spi-fix-v4.7-rc5' of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
git bisect good 467ce7693f5111c11daeb75e02eba2ab9ee6f334
# bad: [88c087109b5fedaf9b61839d08543fdaf9d5ec39] Merge tag
'drm-intel-fixes-2016-06-30' of
git://anongit.freedesktop.org/drm-intel into drm-fixes
git bisect bad 88c087109b5fedaf9b61839d08543fdaf9d5ec39
# bad: [cab103274352721b77fc5923a631fc63350bef8e] drm/i915: Fix
missing unlock on error in i915_ppgtt_info()
git bisect bad cab103274352721b77fc5923a631fc63350bef8e
# good: [fa7c13e5b1e2076b0ec716ed584ab76f9e65b7a6] drm/i915/hsw: Avoid
early timeout during LCPLL disable/restore
git bisect good fa7c13e5b1e2076b0ec716ed584ab76f9e65b7a6
# bad: [42482b4546336ecd93acdd95e435bafd7a4c581c] drm/i915: Add more
Kabylake PCI IDs.
git bisect bad 42482b4546336ecd93acdd95e435bafd7a4c581c
pavel@amd:/data/l/linux$

I reverted ba34a65324259082dc6d2924cb82d562db1c6a6b on top of
4.8-rc1+, and it started booting.

Now the question is... what is going on there...?
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[toc] | [prev] | [next] | [standalone]

#1462291 — Re: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]

FromHans de Goede <hdegoede@redhat.com>
Date2016-08-14 20:30 +0200
SubjectRe: Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks (probably v4.8-rc1 problem)]
Message-ID<s68kx-39m-7@gated-at.bofh.it>
In reply to#1462190
Hi,

On 14-08-16 19:55, Pavel Machek wrote:
> On Sun 2016-08-14 18:06:53, Pavel Machek wrote:
>> On Sun 2016-08-14 12:14:38, Pavel Machek wrote:
>>> On Sun 2016-08-14 11:20:44, Pavel Machek wrote:
>>>> Hi!
>>>>
>>>>> It seems that in v4.8-rc0, /dev/sdX got reordered, and now USB devices
>>>>> are probed before SATA drivers. That is pretty anti-social. It
>>>>> broke my boot on my primary machine, and unfortunately due to BIOS
>>>>> problems (keyboard does not work when connected through a hub) it is
>>>>> less fun than it should be.
>>>>
>>>> If you know which commit caused	the reordering, that would be helpful.
>>>>
>>>> v4.1 seems to be ok: SATA disk is sda, as expected.
>>>>
>>>> v4.4 seems to be ok: SATA disk is sda, as expected.
>>>
>>> v4.6 seems to be ok.
>>
>> v4.7-rc1 seems to be ok?! 9956d572
>> v4.7-rc3 seems still to be ok.
>> v4.7-rc4: still ok.
>> v4.7-rc5: ok.
>> v4.7-rc6: problem
>>
>> Bisecting now, 8 steps to go. As it was introduced between -rc5 and
>> -rc6, bisect should not be too scary.
>
> Huh. Scary.
>
> I bisected it to
>
> [ba34a65324259082dc6d2924cb82d562db1c6a6b] drm/i915: Avoid early
> timeout during AUX transfers
>
> pavel@amd:/data/l/linux$ git bisect log
> # bad: [a99cde438de0c4c0cecc1d1af1a55a75b10bfdef] Linux 4.7-rc6
> # good: [a8ef0490c3583c3a83fa52ebe60abb8fd7d3c2a4] Merge commit
> '4c2e07c6a29e0129e975727b9f57eede813eea85' into bisect-v4.7
> git bisect start 'a99cde438de0c4c0cecc1d1af1a55a75b10bfdef'
> 'a8ef0490c3583c3a83fa52ebe60abb8fd7d3c2a4'
> # good: [4c2e07c6a29e0129e975727b9f57eede813eea85] Linux 4.7-rc5
> git bisect good 4c2e07c6a29e0129e975727b9f57eede813eea85
> # good: [751ad819b0bf443ad8963eb7bfbd533e6a463973] Merge tag
> 'mac80211-for-davem-2016-06-29-v2' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211
> git bisect good 751ad819b0bf443ad8963eb7bfbd533e6a463973
> # good: [aa7a6c8e5252ba28f36a8f87b9acd6a726aa3ae5] Merge tag
> 'iommu-fixes-v4.7-rc5' of
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
> git bisect good aa7a6c8e5252ba28f36a8f87b9acd6a726aa3ae5
> # good: [dbdc3bb74faeec5fd92e28c15c945045d5aab426] Merge tag
> 'acpi-4.7-rc6' of
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
> git bisect good dbdc3bb74faeec5fd92e28c15c945045d5aab426
> # good: [467ce7693f5111c11daeb75e02eba2ab9ee6f334] Merge tag
> 'spi-fix-v4.7-rc5' of
> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
> git bisect good 467ce7693f5111c11daeb75e02eba2ab9ee6f334
> # bad: [88c087109b5fedaf9b61839d08543fdaf9d5ec39] Merge tag
> 'drm-intel-fixes-2016-06-30' of
> git://anongit.freedesktop.org/drm-intel into drm-fixes
> git bisect bad 88c087109b5fedaf9b61839d08543fdaf9d5ec39
> # bad: [cab103274352721b77fc5923a631fc63350bef8e] drm/i915: Fix
> missing unlock on error in i915_ppgtt_info()
> git bisect bad cab103274352721b77fc5923a631fc63350bef8e
> # good: [fa7c13e5b1e2076b0ec716ed584ab76f9e65b7a6] drm/i915/hsw: Avoid
> early timeout during LCPLL disable/restore
> git bisect good fa7c13e5b1e2076b0ec716ed584ab76f9e65b7a6
> # bad: [42482b4546336ecd93acdd95e435bafd7a4c581c] drm/i915: Add more
> Kabylake PCI IDs.
> git bisect bad 42482b4546336ecd93acdd95e435bafd7a4c581c
> pavel@amd:/data/l/linux$
>
> I reverted ba34a65324259082dc6d2924cb82d562db1c6a6b on top of
> 4.8-rc1+, and it started booting.
>
> Now the question is... what is going on there...?

Timing magic, as many people have pointed out, you've been depending
on the detection order being fixed, while in reality it has not
been fixed for a long long long time.

This seemingly unrelated commit apparently manages to change
some timing in some way that the detection order changes,
could be as simple as it yielding a core and the usb core
workqueue getting that core to do detection earlier then
before.

I used to work on anaconda, the Fedora / RH installer, as
well as mkinitrd and later dracut and drive-order has
basically never been stable once we no longer had hda /
hdb for ide disks. So you really just need to fix the way
you're booting your system rather then blaming the kernel.

Regards,

Hans

[toc] | [prev] | [next] | [standalone]

#1462861

From"Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Date2016-08-15 17:10 +0200
Message-ID<s6rGy-7aD-9@gated-at.bofh.it>
In reply to#1461701
On 2016-08-13 15:30, Pavel Machek wrote:
> Hi!
>
> It seems that in v4.8-rc0, /dev/sdX got reordered, and now USB devices
> are probed before SATA drivers. That is pretty anti-social. It
> broke my boot on my primary machine, and unfortunately due to BIOS
> problems (keyboard does not work when connected through a hub) it is
> less fun than it should be.
>
The simple solution (which I'm surprised nobody else has suggested yet) 
is to build everything but the driver for your root device as a module. 
This will prevent anything else from getting enumerated first, and works 
regardless of whether or not your using an initrd and independently of 
what root= format you use.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.kernel

csiph-web