[palinux-palo] bug#92: Won't boot after editing entries

X-PA-RISC Linux-PR-Message: report 92
X-PA-RISC Linux-PR-Package: palo
X-Loop: daniel_frazier@hp.com
Received: via spool by bugs@bugs.parisc-linux.org id=B.9852376629192
          (code B ref -1); Thu, 22 Mar 2001 05:18:02 GMT
Date: Thu, 22 Mar 2001 05:07:39 +0000
From: Matthew Wilcox <matthew@wil.cx>
To: submit@bugs.parisc-linux.org
Message-ID: <20010322050739.O5491@parcelfarce.linux.theplanet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: <willy@www.linux.org.uk>

Package: palo
Version: Unsure

After interacting with IPL and editing the load options, I frequently
get a hang as demonstrated by the following boot log:

Main Menu: Enter command > bo lan
Interact with IPL (Y, N, Q)?> y
INI C740: initialize other path

Booting...
Network Station Address 001083-357d75

System IP Address 15.1.51.80
Server IP Address 15.1.50.190

Boot IO Dependent Code (IODC) revision 2
INI C780: load IPL other path
INI C30C: monarch slave check
INI CC41: CPU1 memory rendezvous
INI CC43: CPU3 memory rendezvous
INI CC42: CPU2 memory rendezvous
INI 10CA: CPU0 initialize system bus arbitration


HARD Booted.
INI C7FF: launch IPL other
palo ipl willy@chrysl Sat Feb 17 02:25:19 MST 2001
0/vmlinux 2564549 bytes @ 0x6800
0/palo-cmdline '0/vmlinux HOME=/ TERM=linux root=/dev/sda1 console=ttyS0 init=/bin/sh'
Current command line:
0/vmlinux HOME=/ TERM=linux root=/dev/sda1 console=ttyS0 init=/bin/sh
 0: 0/vmlinux
 1: HOME=/
 2: TERM=linux
 3: root=/dev/sda1
 4: console=ttyS0
 5: init=/bin/sh

Edit which field?
(or 'b' to boot with this command line)? 3
root=/dev/nfs nfsroot=15.1.50.190
Current command line:
0/vmlinux HOME=/ TERM=linux root=/dev/nfs nfsroot=15.1.50.190 console=ttyS0 init=/bin/sh
 0: 0/vmlinux
 1: HOME=/
 2: TERM=linux
 3: root=/dev/nfs
 4: nfsroot=15.1.50.190
 5: console=ttyS0
 6: init=/bin/sh

Edit which field?
(or 'b' to boot with this command line)? b
Kernel: partition 0 file /vmlinux

(hangs for long time, then):

ERROR: Read from boot device failed (status = -3).
byteio_read: seekread() returned -1 expected 2048
ERROR: Read from boot device failed (status = -3).
byteio_read: seekread() returned -1 expected 2048
ERROR: Read from boot device failed (status = -3).
byteio_read: seekread() returned -1 expected 2048
Couldn't grok your kernel executable format
failed to load kernel                                                           

This palo may be somewhat out of date.  To help, we have:

willy@chrysl:~/parisc/palo$ cvs -n up
C Makefile
U ipl/Makefile
U ipl/crt0.S
U ipl/ipl.c
U ipl/pdc_misc.c
$ cat ipl/CVS/Entries 
/Makefile/1.14/Mon Feb 12 22:16:03 2001//
/ipl.c/1.13/Mon Feb 12 22:16:03 2001//
/pdc_misc.c/1.6/Tue Sep  5 16:04:15 2000//
/crt0.S/1.11/Sat Feb 17 09:22:24 2001//

i hope this helps you tell whether this bug has been fixed already.

-- 
Revolutions do not require corporate support.