On Sun, Oct 28, 2001 at 02:03:05PM +0000, Philip Blundell wrote: > Was there any particular set of changes you were worried about?
I don't know which of the changes make the difference, but regular RMK kernels have never worked for me, I get kernel oopses left, right and center for everyday commands such as "ls". See below for an oops of 2.4.9-ac9-rmk2 (not the freshest, I know...) Sometime after starting up pppd, I even get an endless loop of "kernel BUG at sched.c:543!" errors. Does the Netwinder tree by chance contain changes to the alignment trap handler, or similar? Of course it could also be a problem with my compiler (2.95.3). But I doubt that, I've successfully used it for cross-compiling Debian packages. Cheers, Richard -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/�| http://atterer.net | Universit�t M�nchen, Germany | 0x888354F7 � �` � ksymoops 2.4.3 on armv3l 2.4.3. Options used -V (default) -k oops-ksyms (specified) -l oops-modules (specified) -o /lib/modules/2.4.9-ac9-rmk2 (specified) -m /boot/System.map-2.4.9-ac9-rmk2 (specified) No modules in ksyms, skipping objects Warning (read_lsmod): no symbols in lsmod, is oops-modules a valid lsmod file? Warning (compare_maps): ksyms_base symbol fp_printk not found in System.map. Ignoring ksyms_base entry Warning (compare_maps): ksyms_base symbol fp_send_sig not found in System.map. Ignoring ksyms_base entry Warning (compare_maps): ksyms_base symbol kern_fp_enter not found in System.map. Ignoring ksyms_base entry [...] Unable to handle kernel paging request at virtual address 8000004c *pgd = 00000000, *pmd = 00000000 Internal error: Oops: 0 CPU: 0 pc : [<c001f994>] lr : [<c00230d0>] sp : c0565f20 ip : 00000010 fp : bffffbfc r10: 4017f134 r9 : 00000001 r8 : 001e8481 Warning (Oops_set_i370_regs): garbage 'r9 : 00000001 r8 : 001e8481' at end of i370 register line ignored r7 : e1073093 r6 : 00000000 r5 : 80000010 r4 : c0564000 r3 : 01000000 r2 : c0564232 r1 : 00000010 r0 : c0115c50 Flags: nZcv IRQs off FIQs on Mode SVC_32 Segment user Control: EE133F10 Table: EB002A0C DAC: EA00000C Process ls (pid: 16, stackpage=c0565000) c0565f00: c00230d0 c001f994 40000093 ffffffff c0565f20: e1073093 c03ba1a0 c0564000 00000000 c0036a74 c05605b8 c0036a74 c000eba0 c0565f40: c0564000 ffffffff 4016e094 00000000 00000000 c03ba1a0 c0021b14 c03ba1bc c0565f60: c0564000 c0565fb8 c03ba1a0 c0565fb8 4016e094 c0021c90 4006ea24 00000000 c0565f80: e59fa0a4 4016e094 c0565fb8 c0116d28 00000007 00000001 4017f134 c0022840 c0565fa0: e59fa0a4 e1073093 c0565ff4 00000000 0000017f c00230d0 4015e198 00000000 c0565fc0: 4016a15c 00000001 00000000 bffffbd0 00000000 4015e198 001e8481 00000001 c0565fe0: 4017f134 bffffbfc bffffc00 bffffbd0 4016dffc 4016e3fc 80000010 ffffffff Backtrace: invalid frame pointer 0xbffffbfc Code: e3822002 e1a0100c (e595603c) eb001be2 e1a00005 >>PC; c001f994 <baddataabort+34/a0> <===== >>r10; 4017f134 Before first symbol Code; c001f98c <baddataabort+2c/a0> 00000000 <_PC>: Code; c001f98c <baddataabort+2c/a0> 0: e3822002 orr r2, r2, #2 ; 0x2 Code; c001f990 <baddataabort+30/a0> 4: e1a0100c mov r1, ip Code; c001f994 <baddataabort+34/a0> <===== 8: e595603c ldr r6, [r5, #60] <===== Code; c001f998 <baddataabort+38/a0> c: eb001be2 bl 6f9c <_PC+0x6f9c> c0026928 <printk+0/174> Code; c001f99c <baddataabort+3c/a0> 10: e1a00005 mov r0, r5 8 warnings issued. Results may not be reliable.
