Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Craig D. Lansing" <lansing@beldar.com>
To: <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Kernel ?
Date: Sun, 30 Dec 2001 09:25:54 -0500	[thread overview]
Message-ID: <001c01c1913d$ee1b8ca0$0101a8c0@pogo> (raw)

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

In an attempt to solve my J2240 STI and Eth0/1 problems I am trying to upgrade the kernel from the 2.4.9-32 on the 0.9.3 ISO to something more recent.  Specifically, I've tried 32-2.4.16-pa24 and pa29.  I ftp'd the tar files from the 32-bit directory, untarred / unzipped the contents, copied them into /boot, changed the link for vmlinux, and modified /etc/palo.conf.  However, in both cases when I boot, everything initially looks like it will boot OK, but I eventually get a stack pointer error, a long hex dump, and finally "Kernel Fault: Code=15 regs=102af4c0 (Addr=00368004)" ....  This all appears on the STI head, even though I changed console to ttyS0, and scrolls by too fast to get much meaningful info prior to the hex dump.  

Do I have to upgrade from source (which I'll try next) or am I doing something wrong or both?



[-- Attachment #2: Type: text/html, Size: 1297 bytes --]

                 reply	other threads:[~2001-12-30 14:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='001c01c1913d$ee1b8ca0$0101a8c0@pogo' \
    --to=lansing@beldar.com \
    --cc=parisc-linux@lists.parisc-linux.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