From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Rival <frival@zk3.dec.com>
Subject: Re: 2.4.17-rc1 does not boot my Alphas
Date: Mon, 17 Dec 2001 15:52:03 -0700 [thread overview]
Message-ID: <20011217155203.B14805@mail.harddata.com> (raw)
In-Reply-To: <20011216160404.A2945@mail.harddata.com> <3C1D4871.82053E7A@zk3.dec.com> <20011216225013.A4984@mail.harddata.com>
In-Reply-To: <20011216225013.A4984@mail.harddata.com>; from michal@harddata.com on Sun, Dec 16, 2001 at 10:50:13PM -0700
On Sun, Dec 16, 2001 at 10:50:13PM -0700, Michal Jaegermann wrote:
>
> Tommorow I will try to graft 'arch/alpha' from 2.4.13-ac8 to 2.4.17rc1
> just to see what will happen.
Not much is left from these changes if one wants to stay within
"reasonable and compilable". :-) Anyway, even after this compiles my
Nautilus boxes still do not boot nor show any inclinations to inform why
they are unhappy.
At the very bottom of arch/alpha/kernel/setup.c one can find the
following:
static int alpha_panic_event(struct notifier_block *this,
unsigned long event,
void *ptr)
{
#if 1
/* FIXME FIXME FIXME */
/* If we are using SRM and serial console, just hard halt here. */
if (alpha_using_srm && srmcons_output)
__halt();
#endif
return NOTIFY_DONE;
}
After I changed "#if 1" to "#if 0" results were that most of the time,
although not always, after aboot loader messages I was sooner or later
quietly back at SRM prompt and yes - "srmcons" was given in boot flags.
On some occasions an attempt to boot would simply lock up. To be sure
this was happening both with CONFIG_ALPHA_LEGACY_START_ADDRESS set
and not set.
Anybody with some ideas where I should really look?
Michal
next prev parent reply other threads:[~2001-12-17 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 23:04 2.4.17-rc1 does not boot my Alphas Michal Jaegermann
2001-12-17 1:20 ` Peter Rival
2001-12-17 5:48 ` Jurriaan on Alpha
2001-12-17 5:50 ` Michal Jaegermann
2001-12-17 22:52 ` Michal Jaegermann [this message]
2001-12-18 15:35 ` Alan Cox
2001-12-20 6:30 ` Michal Jaegermann
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=20011217155203.B14805@mail.harddata.com \
--to=michal@harddata.com \
--cc=frival@zk3.dec.com \
--cc=linux-kernel@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