Kernel and palo source broken

Hi,
I just cvs updated palo and kernel source, and grabbed a new
cross compiler build from Matt.

palo update results in by A180 boot stopping after:

Entry 00100000 first 00100000 n 3
Segment 0 load 00100000 size 1512788 mediaptr 0x1000 Segment 1 load 00272000 size 115348 mediaptr 0x173000 Segment 2 load 00290000 size 122880 mediaptr 0x190000 branching to kernel entry point 0x00100000 Set default PSW W bit to 0

Kernel wouldn't build - mostly arch/parisc/kernel/signal.c problems, needs to include linux/version.h, PF_PTRACED undefined...

I did cvs update -D '24 hours ago' on various things and my A180 boots again, but my 715/75 doesn't. It thinks it has three disks rather than two plus a tape, disk probing then fails, and finally it thinks it is sending BOOTP requests but nothing is seen on the network.

Boy, am I glad Friday lunchtime is pub time!

Richard

i just added sc_sar to the struct sigcontext. i'm sure dhd has the right fix and will commit it once he gets in... rebuilding now. Hmm. Wonder why that version number test doesn't work... oh well, changing it to #if 1 gets it compiled for me.

Ah yes, the quality of Friday afternoon code is definitely higher than the rest of the week :-)

Revolutions do not require corporate support.

Needs #include <linux/version.h>. I think I still had PF_PTRACED undefined after that.

Richard

Hi, i just though all should know that mke2fs works, but badblocks doesn't. badblocks was run from the PA/Linux Development CD 0.1
i ran 'mke2fs -c -v /dev/sda3'
and got:

mke2fs 1.19-WIP, 7-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev.Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
118528 inodes, 237030 blocks
11851 blocks (0.00%) reserved for the super user
First data block=0
8 block groups
32768 blocks per group, 32768 fragments per group
14816 inodes per group
Superblock backups stored on blocks:

        32768, 98304, 163840, 376

Running command: badblocks -b 4096 -s /dev/sda3 237030 do_page_fault() pid=21 command='badblocks'

PSW : 0004fe0b GR 1 : 00063580 GR 2 : 00000000 GR 3 : 00000000 GR 4 : 00000000 GR 5 : 00000000 GR 6 : 00000000 GR 7 : 00000000 GR 8 : 200200c8 GR 9 : 00000000 GR10 : 00000000 GR11 : 00000000 GR12 : 00000000 GR13 : 00000400 GR14 : 00000000 GR15 : 00001770 GR16 : 00000000 GR17 : 00000010 GR18 : 00061580 GR19 : 00000024 GR20 : 0006 GR21 : 81010100 GR22 : 62626262 GR23 : 00000000 GR24 : 00000000 GR25 : 200200c8 GR26 : 00000000 GR27 : 00061580 GR28 : 00000000 GR29 : ffffffff GR30 : 20020200 GR31 : 00011b73 SR0 : 00002005 SR1 : 00002005 SR2 : 00000000 SR3 : 00002005 SR4 : 00002005 SR5 : 00002005 SR6 : 00002005 SR7 : 00002005

IASQ : 00002005 00002005 IAOQ : 00005827 0000582b
IIR : 0ce01013 ISR : 00002005 IOR : 00000000

sending SIGSEGV
Segmentation fault
Writing inode tables: done
Writing superblocks and filesystem accounting information: done

L8R, Cloud.

Claudiu Carter writes...

[snip]

[snip]

I just rebuilt e2fsprogs(available on the ftp site) and tried the above. It still does the same thing.

If I run badblocks with out the "-b blocksize" flag it works fine.

Hopefully someone knows what this means :)

Matt Taggart
[email protected]