2.4.21-paX on an rp2430

pa,

Downloaded vmlinux-64-2.4.21-pa2 from cvs.parisc-linux.org

palo --commandline='0/vmlinux64 console=/dev/ttyS0 root=/dev/sda2' \
     -k ./vmlinux-64-2.4.21-pa2 \
     -s ./lifimage64

Then proceeded to netboot this kernel from a new rp2430, and I didn't get very far :(

Has anyone tried testing the prebuilt kernels on newer machines?

I also tried a newer vmlinux-2.4.20-pa10-UP and the kernel oopses :(

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

Booting...
Network Station Address 00306e-48a712
System IP Address 192.168.1.200
Server IP Address 192.168.1.222

Boot IO Dependent Code (IODC) revision 2

HARD Booted.
palo ipl 1.2 root@b2000 Tue Jan 14 13:13:07 MST 2003

Boot image contains:

    0/vmlinux64 5196863 bytes @ 0x8800

Current command line:
0/vmlinux64 console=/dev/ttyS0 root=/dev/sda2
0: 0/vmlinux64
1: console=/dev/ttyS0
2: root=/dev/sda2

Edit which field?
(or 'b' to boot with this command line)? b

Command line for kernel: 'console=/dev/ttyS0 root=/dev/sda2 palo_kernel=0/vmlinux64' Selected kernel: /vmlinux64 from partition 0
ELF64 executable
Entry 00100000 first 00100000 n 4
Segment 0 load 00100000 size 2789296 mediaptr 0x1000
Segment 1 load 003aa000 size 1012928 mediaptr 0x2aa000
Segment 2 load 004a4000 size 319568 mediaptr 0x3a2000
Segment 3 load 004f4000 size 49152 mediaptr 0x3f1000
Branching to kernel entry point 0x00100000. If this is the last message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************

LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
       ON       FLASH         OFF       ON         ON

LED State: There was a system interruption that did not take the system down. Check Chassis and Console Logs for error messages.

processor                 system initialization      1C00
processor                 system initialization      1C00

Le lundi, 14 jul 2003, =E0 20:23 Europe/Paris, Carlos O'Donell a =E9crit = :

these two messages show that the kernel went up to calling INIT (the second "system initialization" is sent just before INIT is called).

You can check the real logs by issuing the CL command in your GSP. You'll find there the console log, without the VFP messages.

HTH,

Thibaut VARENE
The PA/Linux ESIEE Team
http://pateam.esiee.fr/=

What does this mean from the viewpoint of the boot process? Did the kernel actually boot or just got stuck here?

c.

sorry - I still build my own to test my own changes.

i've uploaded a *PRE-RELEASE* 2.4.21-pa5.tgz to:

	ftp://ftp.parisc-linux.org/kernels/a500/2.4.21-pa5.tgz

This boots and runs on my a500-65 and recent rp2430s.

FYI, I used lifimage-2.4.20-pa35-20030513 which I think came from the ESIEE web site. Should be available from ftp.p-l.o as well.

grant

BTW, I'm trying to fix "sendfile". I missing some peice to make the 32-bit syscall wrapper to work right.

It works fine to 32-bit kernel
grundler <504>./sftest foo
sendfile returned ret = 7013 off = 7013 errno = 0
grundler <505>ls -l foo
-rw-r--r-- 1 grundler grundler 7013 Jul 14 14:03 foo
grundler <506>uname -a
Linux debian 2.4.21-pa2 #46 Sat Jul 5 23:28:38 PDT 2003 parisc GNU/Linux

But not for 64-bit kernel:

grundler@gsyprf11:~$ ./sftest x
sendfile returned ret = 7013 off = 0 errno = 0
grundler@gsyprf11:~$ ls -l x
-rw-r--r--    1 grundler users        7013 Jul 14 14:05 x

and thanks to tausq for whipping up the simple test case. "distcc" won't work on my a500 "mini cluster" until this is fixed. :^)

grant