From: "Van Maren, Kevin" <kevin.vanmaren@unisys.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Panic in linuxrc (2.4.7)
Date: Wed, 01 Aug 2001 23:27:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005987@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005983@msgid-missing>
> I've just got my first (secondhand) IA64 box, and I'm trying
> to get 2.4.7
> running so port some other kernel code (loadable security
> modules) to the
> IA64.
>
> Taking a vanilla 2.4.7, applying the 0726 patch (#2) and the suggested
> compiler fix as I'm using stock RedHat 7.1, I get...
> Freeing initrd memory: 736kB freed
> VFS: Mounted root (ext2 filesystem).
> linuxrc[8]: IA-64 Illegal operation fault 0
> Running this through ksymoops gave
>
> Warning (Oops_read): Code line not seen, dumping what data is
> available
>
> >>IP; e000000004721ee0 <long_do_clear+70/110> <==> >>b0; e00000000440ef90 <do_linuxrc+d0/100>
> >>b6; e000000004482060 <generic_file_mmap+0/1a0>
> >>b7; e00000000440f810 <ia64_switch_to+b0/120>
> Trace; e0000000044140b0 <show_stack+50/c0>
> Any clues ?
I sent an email about this on 7/28, but didn't get a reply (but you sent
more info than I did):
I tried upgrading to 2.4.7+IA64-010726, but when I did that, "init" dies:
init[1]: IA-64 Illegal operation fault 0
[...]
Kernel panic: Attempted to kill init!
The 2.4.5 kernel boots with the 6/26 patches, but I'd like to run a newer
kernel too :-)
Kevin
next prev parent reply other threads:[~2001-08-01 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 23:05 [Linux-ia64] Panic in linuxrc (2.4.7) richard offer
2001-08-01 23:15 ` David Mosberger
2001-08-01 23:16 ` Broadfoot, Ken P
2001-08-01 23:22 ` richard offer
2001-08-01 23:27 ` Van Maren, Kevin [this message]
2001-08-02 1:13 ` David Mosberger
2001-08-02 7:12 ` Van Maren, Kevin
2001-08-02 19:58 ` richard offer
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=marc-linux-ia64-105590693005987@msgid-missing \
--to=kevin.vanmaren@unisys.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.