From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 18 Jul 2003 18:23:02 +0100 (BST) Received: from gateway-1237.mvista.com ([IPv6:::ffff:12.44.186.158]:14844 "EHLO orion.mvista.com") by linux-mips.org with ESMTP id ; Fri, 18 Jul 2003 18:22:59 +0100 Received: (from jsun@localhost) by orion.mvista.com (8.11.6/8.11.6) id h6IHMu332075; Fri, 18 Jul 2003 10:22:56 -0700 Date: Fri, 18 Jul 2003 10:22:56 -0700 From: Jun Sun To: Jack Miller Cc: Linux-Mips , jsun@mvista.com Subject: Re: kernel BUG at sched.c:784! Message-ID: <20030718102256.D31523@mvista.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jack.miller@pioneer-pdt.com on Fri, Jul 18, 2003 at 09:57:01AM -0700 Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 2821 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: jsun@mvista.com Precedence: bulk X-list: linux-mips Your kernel looks old, and probably don't have the CPU bug workaround code at the beginning of vec3 exception handler. NESTED(except_vec3_generic, 0, sp) #if R5432_CP0_INTERRUPT_WAR mfc0 k0, CP0_INDEX #endif Try this. Jun On Fri, Jul 18, 2003 at 09:57:01AM -0700, Jack Miller wrote: > We are developing a system based around a NEC VR5432 CPU and Broadcom > BCM703X System Controller. When the system is running with the intended > application and drivers we intermittently experience a kernel OOPS in the > scheduler. Would someone please provide some insight to the following OOPS > ? It appears (with my limited understanding of the scheduler) that the > scheduler is trying to schedule the 'idle' task. What condition prevails to > cause this to happen ? > > Using a J-TAG Debugger, I "walked" the task list (in both directions) and > everthing appears to be in order. > > Thanks in advance for your help. > > Regards, > Jack > > > Linux version 2.4.17 (jack@saturn) (gcc version 3.2.2 20030322 (Pioneer > Voyager)) #1 Fri May 30 14:55:32 PDT 2003 > ksymoops 2.4.6 on mips 2.4.17. Options used > -v vmlinux (specified) > -k /proc/ksyms (default) > -l /proc/modules (default) > -o /lib/modules/2.4.17/ (default) > -m System.map (specified) > -T 32 > > root@stb2073:~# kernel BUG at sched.c:784! > Unable to handle kernel paging request at virtual address 00000000, epc == > 8001524c, ra == 8001524c > $0 : 00000000 b001f800 0000001b 00000000 ffffff9d 80008000 0000001f 828f4a20 > $8 : 00000001 ffffd890 00001890 801cb119 00000000 00000000 fffffff9 ffffffff > $16: 00000000 00000000 809ae000 828f4a20 80008000 00000000 80008000 1001ccf8 > $24: 0000000a 00000002 809ae000 809afe90 809afe90 8001524c > epc : 8001524c Tainted: P > Using defaults from ksymoops -t elf32-tradbigmips -a mips:3000 > Status: b001f803 > Cause : 8000c40c > Process pvrd (pid: 331, stackpage=809ae000) > Stack: 8016eda8 8016edc0 00000310 fffffc18 00138f80 00000002 809afed8 > 00000070 > 00000000 1001cd00 1001ccfc 809afec8 80014e74 80014e6c 00000400 > 00000200 > c008422b 80bd4160 00000000 00000000 00138f80 809ae000 80014dd4 > 2aac2000 > 00000000 809aff18 00001807 7edffa50 8002242c 00000070 00000000 > 8016c290 > 00000000 00000000 00000000 00989680 7edffa40 00000000 8000f7c4 > 8000f7c4 > 00000000 ... > Call Trace: [<8016eda8>] [<8016edc0>] [<80014e74>] [<80014e6c>] [] > [<80014dd4>] > [<8002242c>] [<8016c290>] [<8000f7c4>] [<8000f7c4>] > Code: 24a5edc0 0c0062f7 24060310 <08005485> ae200000 40016000 00000000 > 3421001f 3821001e > > > >>RA; 8001524c > >>$1; b001f800 <_end+2fe2aea0/3fe2a6a0> > >>$5; 80008000 > >>$7; 828f4a20 <_end+27000c0/3fe2a6a0> > >>$11; 801cb119 > >>$18; 809ae000 <_end+7b96a0/3fe2a6a0> > >>$19; 828f4a20 <_end+27000c0/3fe2a6a0> > >>$20; 80008000 > >>$22; 80008000 > >>$23; 1001ccf8 <_binary_ramdisk_gz_size+1001a6da/7fffe9e2> > >>$28; 809ae000 <_end+7b96a0/3fe2a6a0> > >>$29; 809afe90 <_end+7bb530/3fe2a6a0> > >>$30; 809afe90 <_end+7bb530/3fe2a6a0> > >>$31; 8001524c > > >>PC; 8001524c <===== > > Trace; 8016eda8 > Trace; 8016edc0 > Trace; 80014e74 > Trace; 80014e6c > Trace; c008422b <[bcm7030]scard_interrupt+f/340> > Trace; 80014dd4 > Trace; 8002242c > Trace; 8016c290 > Trace; 8000f7c4 > Trace; 8000f7c4 > > Code; 80015240 > 00000000 <_PC>: > Code; 80015240 > 0: 24a5edc0 addiu a1,a1,-4672 > Code; 80015244 > 4: 0c0062f7 jal 18bdc <_PC+0x18bdc> 8002de1c > > Code; 80015248 > 8: 24060310 li a2,784 > Code; 8001524c <===== > c: 08005485 j 15214 <_PC+0x15214> 8002a454 <__vma_link+9c/e0> > <===== > Code; 80015250 > 10: ae200000 sw zero,0(s1) > Code; 80015254 > 14: 40016000 mfc0 at,$12 > Code; 80015258 > 18: 00000000 nop > Code; 8001525c > 1c: 3421001f ori at,at,0x1f > Code; 80015260 > 20: 3821001e xori at,at,0x1e > > > Jack Miller > Pioneer Digital Technologies, Inc. > 6170 Cornerstone Court East > Suite 330 > San Diego, CA 92121-3767 > vox: (858)824-0790 x356 > fax: (858)824-0796 > >