Giuseppe Sacco wrote: > Hi all, > compiled the latest kernel 2.6.22.4 using the .config from Debian > linux-image-2.6.22-1-r5k_ip32 and activating CONFIG_NFSD_V4 and a few > network device drivers. > The command I used was: > > $ fakeroot make-kpkg --revision 2:2.6.22 \ > --append-to-version -1gs-r5k-ip32 --arch-in-name buildpackage > > When I boot an O2 r5k with this kernel, I get this error message: > --------------------------------------------------------------------------- > Loading 64-bit executable
Have you tried the ELF32 variant (vmlinux.32)? > Loading program segment 1 at 0x80005000, offset=0x0 4000, size = 0x0 4f8086 > 5dc000 (cache: 95.0%)Zeroing memory ar 0x82f611, size 0 0x0 > Starting ELF64 kernel > > Exception: <vector=Normal> > Status register: 0x34010082<CU1,CU0,FR,DE,IPL=8,KX,MODE=KERNEL> > Cause register: 0x8014<CE=0,IP8,EXC=WADE> > Exception PC: 0x802204fc, Exception RA: 0x804da7ac > Write address error exception, bad address: 0xfffff000 > Saved user regs in hex (&gpda 0x81060e08, &_regs 0x81061008): > arg: 81070000 0 804ff518 1 > tmp: 81070000 1000 80516868 fff8054b ffffffff 81412ef4 a13fb0d0 8 > sve: 81070000 4083ae51 0 4608a976 0 0 0 80ee80d5 > t8 81070000 t9 0 at 0 v0 0 v1 0 k1 fffff000 > gp 81070000 fp 0 sp 0 ra 0 > > PANIC: Unexpected exception > > [Press reset or ENTER to restart.] > --------------------------------------------------------------------------- > > If I understand correctly the problem happened at address 0x802204fc, so > I checked the system.map file and found > ffffffff802204c4 T __bzero > ffffffff80220524 t memset_partial > > If I understand correctly, the kernel was executing the __bzero function > and tried accessing the invalid address 0xfffff000. It could be any of: - broken RAM - Arcboot messing up the kernel load, so __bzero runs invalid code - __bzero gets called with wrong parameters Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
