Alpha arch development list
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: linux-alpha@vger.kernel.org
Subject: [BUG] 4.14 cannot find configured disks/partitions
Date: Wed, 29 Nov 2017 23:48:23 -0600	[thread overview]
Message-ID: <20171130054823.GA14814@gherkin.frus.com> (raw)

(Forgot to include "linux-alpha" in the original recipient list, so
the next few messages are an attempt to fix that.  Please copy
"debian-alpha" on any replies.)

Perhaps the subject isn't entirely accurate, but that's what seems to be
the case.  After loading the initial ramdisk, the boot process stalls
(loops indefinitely) with "mdadm" complaining about not being able to scan 
the disks defined in its configuration file, which is bone-stock.  What
makes this particularly infuriating is, I don't have anything configured
for "mdadm" to worry about, which is what's normally found, i.e.,
nothing of interest.

The 4.13 kernel loads and boots just fine with exactly the same
up-to-date (unstable/experimental) userspace libraries and utilities.

Bottom line: the 4.14 kernel doesn't seem to detect my SCSI disks for
some reason.  All the recent patches (end of October time frame) for PCI
on alpha (I *think* mostly having to do with addressing some weird kind
of libata conflict) didn't make any difference.

Any idea what's causing this?  Thanks...

--Bob

             reply	other threads:[~2017-11-30  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  5:48 Bob Tracy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-30  5:48 [BUG] 4.14 cannot find configured disks/partitions Bob Tracy
2017-11-30  5:49 Bob Tracy
2017-11-30  5:50 Bob Tracy
     [not found] <20171124051010.GA18422@gherkin.frus.com>
     [not found] ` <20171129054955.GA9467@gherkin.frus.com>
2017-12-01 21:16   ` Michael Cree
2017-12-02  0:22     ` Bob Tracy
2017-12-02  4:49       ` Bob Tracy

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=20171130054823.GA14814@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=linux-alpha@vger.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