public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
	jamespharvey20@gmail.com, regressions@leemhuis.info
Cc: hdegoede@redhat.com, tj@kernel.org, linux-ide@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	oliver@neukum.org, 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 18:06:53 +0200	[thread overview]
Message-ID: <20160814160653.GA3802@amd> (raw)
In-Reply-To: <20160814101438.GA27772@amd>

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

  reply	other threads:[~2016-08-14 16:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160813190340.GA29989@amd>
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
     [not found]             ` <alpine.DEB.2.02.1608140322400.9045-UEhY+ZBZOcqqLGM74eQ/YA@public.gmane.org>
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
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 [this message]
2016-08-14 17:55       ` Pavel Machek
2016-08-14 18:22         ` Hans de Goede

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=20160814160653.GA3802@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-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=regressions@leemhuis.info \
    --cc=stern@rowland.harvard.edu \
    --cc=tj@kernel.org \
    /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