From: Tejun Heo <tj@kernel.org>
To: Michael Cree <mcree@orcon.net.nz>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
debian-alpha@lists.debian.org
Subject: Re: Generic kernel fails to boot on Alpha bisected to b38d08f3181c
Date: Thu, 13 Dec 2018 08:07:24 -0800 [thread overview]
Message-ID: <20181213160724.GU2509588@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <20181213082612.bi2dcd6uhzp3t6iq@tower>
Hello, Michael.
On Thu, Dec 13, 2018 at 09:26:12PM +1300, Michael Cree wrote:
> A kernel built for generic UP Alpha had been noted to fail to boot
> for quite some time (since the release of 3.18). The kernel either
> locks up before printing any messages to the console or just falls
> back into the SRM with a HALT instruction again before any messages
> are printed to the console. A work around is to either use a kernel
> built for generic SMP or to build a machine specific kernel as these
> boot correctly.
>
> Because there were other compile errors at the time it proved
> difficult to bisect, but we are continuing to get complaints about
> it as it renders the Debian Alpha installer somewhat useless, so I
> returned to trying to find the problem and managed to bisect it to:
>
> commit b38d08f3181c5025a7ce84646494cc4748492a3b
> Author: Tejun Heo <tj@kernel.org>
> Date: Tue Sep 2 14:46:02 2014 -0400
>
> percpu: restructure locking
>
> Any suggestions as to what might be the problem and a fix?
So, the only thing I can think of is that it's calling
spin_unlock_irq() while irq handling isn't set up yet. Can you please
try the followings?
1. Convert all spin_[un]lock_irq() to
spin_lock_irqsave/unlock_irqrestore().
2. If that still doesn't work, just convert all of them to
spin_lock/unlock(), which is obviously broken but still is useful
for debugging.
Thanks.
--
tejun
next prev parent reply other threads:[~2018-12-13 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 8:26 Michael Cree
2018-12-13 16:07 ` Tejun Heo [this message]
2018-12-14 4:47 ` Michael Cree
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=20181213160724.GU2509588@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
/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
all inboxes | Powered by JetHome®