[parisc-linux] installation problems on an A500

[parisc-linux] installation problems on an A500

[Matthias Klose]

Trying to install Debian on the machine:

- trying to boot from the network, I get:

Main Menu: Enter command or menu > bo pri
Interact with IPL (Y, N, or Cancel)?> y

Booting... 
Network Station Address 00306e-132574
System IP Address 192.168.42.183
Server IP Address 192.168.42.5

Boot IO Dependent Code (IODC) revision 2

IPL error: bad LIF magic.

************* SYSTEM ALERT **************
SYSTEM NAME: gsphppa
DATE: 01/07/2002 TIME: 02:24:50
ALERT LEVEL: 6 = Boot possible, pending failure - action required

REASON FOR ALERT
SOURCE: 8 = I/O 
SOURCE DETAIL: 6 = disk   SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
       FLASH    FLASH         ON        ON         ON
LED State: Boot Failed.  Running non-OS code.  Non-critical error detected.
Check Chassis and Console Logs for error messages.

0x00000060860010C0 00000000 00000000 - type  0 = Data Field Unused
0x58000860860010C0 00006600 07021832 - type 11 = Timestamp 01/07/2002 02:24:50
A: ack read of this entry - X: Disable all future alert messages

the changelog on the bootp/tftpboot server shows:

Jan  7 03:26:00 gate bootpd[25080]: recvd pkt from IP addr 0.0.0.0
Jan  7 03:26:00 gate bootpd[25080]: bootptab mtime: Mon Jan  7 03:25:27 2002
Jan  7 03:26:00 gate bootpd[25080]: reading new "/etc/bootptab"
Jan  7 03:26:00 gate bootpd[25080]: read 2 entries (2 hosts) from "/etc/bootptab"
Jan  7 03:26:00 gate bootpd[25080]: request from Ethernet address 00:30:6E:13:25:74
Jan  7 03:26:00 gate bootpd[25080]: found 192.168.42.183 (hppa)
Jan  7 03:26:00 gate bootpd[25080]: bootfile="/tftpboot/palinux"
Jan  7 03:26:00 gate bootpd[25080]: vendor magic field is 99.130.83.99
Jan  7 03:26:00 gate bootpd[25080]: sending reply (with RFC1048 options)
Jan  7 03:26:00 gate bootpd[25080]: setarp 192.168.42.183 - 00:30:6E:13:25:74
Jan  7 03:26:02 gate in.tftpd[28213]: connect from hppa.local
Jan  7 03:26:02 gate tftpd[28214]: tftpd: trying to get file: /tftpboot/palinux 

Tried this with the lifimage from woody/main (2001-12-19) and the
lifimage from parisc-linux.org (2001-12-26), checked md5sums after
downloading.

Yesterday, I borrowed an external CD-ROM and tried to boot from a
CD-ROM (burnt the ISO image). Now getting:

bo 0/0/2/0.3
Interact with IPL (Y, N, or Cancel)?> y

Booting... 
Failed to initialize.

ENTRY_INIT 
Status = -3

00000000 FFFFFFFD 00000000 00000000 00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
00000000 00000000 00000000 00000012 00000000 00000000 00000000 00000000 
00000000 454E4841 00000000 00000000 00000000 00000000 00000000 454E4841 
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
00000000 00000400 00000000 00000000 00000000 00000000 00000000 00000000 

Failed to initialize.


Any hints how to start/continue?

Thanks, Matthias

Re: [parisc-linux] installation problems on an A500

[Grant Grundler]

Matthias Klose wrote:
> Main Menu: Enter command or menu > bo pri
> Interact with IPL (Y, N, or Cancel)?> y
> 
> Booting... 
> Network Station Address 00306e-132574
> System IP Address 192.168.42.183
> Server IP Address 192.168.42.5

bootp is working.

> Boot IO Dependent Code (IODC) revision 2
> 
> IPL error: bad LIF magic.

The image bootp got was not a LIF image.

The easiest way to build a bootable LIF image is to
have both linux/ and palo/ source trees from parisc-linux CVS.
(or ftp site). Then "make palo" from linux source tree.
Resulting LIF image is in palo/lifimage.

I don't think we have any lifimages on the ftp site
with recent kernels.

grant

Re: [parisc-linux] installation problems on an A500

[Matthias Klose]

Grant Grundler writes:
> > Boot IO Dependent Code (IODC) revision 2
> > 
> > IPL error: bad LIF magic.
> 
> The image bootp got was not a LIF image.
> 
> The easiest way to build a bootable LIF image is to
> have both linux/ and palo/ source trees from parisc-linux CVS.
> (or ftp site). Then "make palo" from linux source tree.
> Resulting LIF image is in palo/lifimage.
> 
> I don't think we have any lifimages on the ftp site
> with recent kernels.

extracted from ftp://ftp.parisc-linux.org/cd-images/palinux-0.9.3.iso

and

http://http.us.debian.org/debian/dists/woody/main/disks-hppa/3.0.18-2001-12-21/

Re: [parisc-linux] vmlinux header for savecrash.

[Paul Bame]

palo removes the "3/vmlinux" parameter (and the initrd= one too) before
passing command line to the kernel which is consistent with x86 I think.
Would it be helpful to add a kernel parameter like "palo_kernel=3/vmlinux"
which you could then retrieve from /proc/cmdline?  I know it's a pain
to turn 3/vmlinux into /boot/vmlinux but 3/vmlinux is all palo knows.

	-P

Re: [parisc-linux] vmlinux header for savecrash.

[Grant Grundler]

Paul Bame wrote:
> 
> palo removes the "3/vmlinux" parameter (and the initrd= one too) before
> passing command line to the kernel which is consistent with x86 I think.
> Would it be helpful to add a kernel parameter like "palo_kernel=3/vmlinux"
> which you could then retrieve from /proc/cmdline?

Sort of. Actually, I was thinking the dump driver could use "palo_kernel"
global to save off the file name of the vmlinux which crashed.
setup_cmdline could parse/squirrel away the palo_kernel parameter.

> I know it's a pain
> to turn 3/vmlinux into /boot/vmlinux but 3/vmlinux is all palo knows.

Isn't /vmlinux a symlink to /boot/vmlinux?
ie the file palo loaded is whatever the symlink points to.

BTW, I explicitly specify /boot/vmlinux in my palo.conf files
and see 3/boot/vmlinux in my palo command line.

thanks,
grant

Re: [parisc-linux] vmlinux header for savecrash.

[Enrik Berkhan]

On Tue, Jan 22, 2002 at 12:59:03PM -0700, Paul Bame wrote:
> palo removes the "3/vmlinux" parameter (and the initrd= one too) before
> passing command line to the kernel which is consistent with x86 I think.
> Would it be helpful to add a kernel parameter like "palo_kernel=3/vmlinux"
> which you could then retrieve from /proc/cmdline?  I know it's a pain
> to turn 3/vmlinux into /boot/vmlinux but 3/vmlinux is all palo knows.

Hmm, so why don't let palo calculate a CRC32 or MD5 (if affordable)
over the image it is about to boot and pass this as parameter that will
be saved in the dump? This would be very independent of filesystem
changes in the time between boot and crash (e.g. installing a new kernel
moving everything around in /boot). This could also be done for an
initrd image if used. And it still works if you have more than one
kernel image with the same "version" lying around.

Enrik
-- 
Enrik Berkhan                                         plan b. GmbH
                                                      Rüppurrer Straße 4
+49-721-388582 (voice)                                76137 Karlsruhe
+49-721-388581 (fax)                                  Germany

Re: [parisc-linux] vmlinux header for savecrash.

[phi 4369]

> Hmm, so why don't let palo calculate a CRC32 or MD5 (if affordable)
> over the image it is about to boot and pass this as parameter that will
> be saved in the dump? This would be very independent of filesystem
> changes in the time between boot and crash (e.g. installing a new kernel
> moving everything around in /boot). This could also be done for an
> initrd image if used. And it still works if you have more than one
> kernel image with the same "version" lying around.
> 

Having the CRC at dump time doesn't add more than just the utsname (i.e the
uname -a if you wish) as the utsname does have the uniq signature of the os
version PLUS the build time. So it is not possible to have 2 kernel with the
exact same version AND the same build time if they are different, or not only
different but compiled at different time.

The problem afterward at next reboot (while the dump seat in the dump area,
often the swap area) and while sometime rebooting a recovery kernel, i.e not
the one that just dumped, is to run savescrah, and have savecrash placing the
core along with its accompagnying kernel (and the loaded module too, more on
that later).

Finding the kernel who crash assuming a signature, mean then a scan of all the
kernel we could find on the machime, with simple heuristic we could reduce
this to / and /boot, then compare the utsname (version build time) for each.
This is rather brute force and it will be our 1st implementation, until we can
find the boot kernel path probably given by palo as palo is the one that can
get interactivly any kernel path....

Ultimatly if we can't figure out what was the kernel who crashed, we can ask
interactivly :-(

Cheers,
Phi




--
mailto:Philippe_Benard@hp.com
WTEC HP-UX kernel debugging tools

Re: [parisc-linux] vmlinux header for savecrash.

[Andreas Deresch]

> > I know it's a pain
> > to turn 3/vmlinux into /boot/vmlinux but 3/vmlinux is all palo knows.
>
> Isn't /vmlinux a symlink to /boot/vmlinux?
> ie the file palo loaded is whatever the symlink points to.
Can you guarantee, that everybody will have this link?
(I for example don't right now - I always thought, this is just for
historical reasons)

> BTW, I explicitly specify /boot/vmlinux in my palo.conf files
> and see 3/boot/vmlinux in my palo command line.
Which means, /boot is not a separate partition as some people like to keep
it. So you can't count on that either.

ad

Re: [parisc-linux] vmlinux header for savecrash.

[Grant Grundler]

Andreas Deresch wrote:
> > Isn't /vmlinux a symlink to /boot/vmlinux?
> > ie the file palo loaded is whatever the symlink points to.
> Can you guarantee, that everybody will have this link?

Of course not. I'm refering to a default installation.
I delete that link and replace /etc/palo.conf with my own.
But I'm hardly a "regular" user.

> (I for example don't right now - I always thought, this is just for
> historical reasons)


> > BTW, I explicitly specify /boot/vmlinux in my palo.conf files
> > and see 3/boot/vmlinux in my palo command line.
> Which means, /boot is not a separate partition as some people like to keep
> it. So you can't count on that either.

Right. I like to have lots of room for kernels. :^)
And if one wanted to have / as an ext3, it would make
sense to have /boot as an ext2 for loading kernels and then
the / could be the rest of the disk (ignoring the 2GB
IODC limitation).

grant