From: Meelis Roos <mroos@linux.ee>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-alpha@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: alpha boot hang - 4.14-rc* regression
Date: Wed, 25 Oct 2017 15:21:21 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1710251511090.10071@math.ut.ee> (raw)
In-Reply-To: <20171025092159.GA14222@red-moon>
> > (Added linux-pci to CC)
> >
> > > > I run Gentoo Linux on my alphas, with latest git kernels for test.
> > > > 4.13.0 worked well on 3 alphas but 4.13.0-09217-g5969d1bb3082 hangs on
> > > > boot on all 3 of them. Tried bisecting on PC164, got into unrelated
> > > > stuff, so probably it does not trigger always. Retried bisecting on
> > > > DS10L. On the first try I got that the same keel where I first saw bad
> > > > was the culprit, another bisect led me to
> > > > 0e4c2eeb758a91e68b9eaf7a4bee9bd5ed97ff2b which looks more related.
> > > >
> > > > This is how the crash looks on console:
> > > >
> > > > * Starting udev ...
> > > > starting version 225
> > > > [ ok ]
> > > > * Generating a rule to create a /dev/root symlink ...
> > > > [ ok ]
> > > > * Populating /dev with existing devices through uevents ...
> > > > [ ok ]
> > > >
> > > > halted CPU 0
> > > >
> > > > halt code = 5
> > > > HALT instruction executed
> > > > PC = fffffc00009bf914
> > > > boot failure
> > > > >>>
> > > >
> > > > What else can I do to debug this?
> > >
> > > Booting with debug ignore_loglevel I get also this:
> > [...]
> > > So maybe it is related pcspkr loading, or the just loaded libata or
> > > floppy...
> >
> > removing libata modules and rebooting fixes it - so it seems to be
> > loading of libata.
>
> Can you please cherry-pick:
>
> commit b1f9e5e355e9 ("ide: fix IRQ assignment for PCI bus order probing")
>
> from mainline and let us know if that solves the issue ?
No, still breaks the same way (b1f9e5e355e9 patched on top of
0e4c2eeb758a).
4.14.0-rc5-00095-g1c9fec470b81 was also still broken the same way (tried
on Sunday).
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2017-10-25 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.21.1710251043170.7098@math.ut.ee>
[not found] ` <alpine.LRH.2.21.1710251109150.7098@math.ut.ee>
2017-10-25 8:43 ` alpha boot hang - 4.14-rc* regression Meelis Roos
2017-10-25 9:21 ` Lorenzo Pieralisi
2017-10-25 12:21 ` Meelis Roos [this message]
2017-10-25 13:37 ` Lorenzo Pieralisi
2017-10-25 14:49 ` Meelis Roos
2017-10-25 15:14 ` Lorenzo Pieralisi
2017-10-25 15:54 ` Meelis Roos
2017-10-25 18:01 ` Meelis Roos
2017-10-26 8:54 ` Lorenzo Pieralisi
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=alpine.LRH.2.21.1710251511090.10071@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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;
as well as URLs for NNTP newsgroup(s).