All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Jack Miller <jack.miller@pioneer-pdt.com>
Cc: Linux-Mips <linux-mips@linux-mips.org>
Subject: Re: kernel BUG at sched.c:784!
Date: Fri, 18 Jul 2003 13:08:59 -0400	[thread overview]
Message-ID: <3F1829AB.9090303@realitydiluted.com> (raw)
In-Reply-To: <JCELLCFDJLFKPOBFKGFNGEKJCFAA.jack.miller@pioneer-pdt.com>

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 ?
>
Are you using their reference platform 93725 or 93730 or what?

> Linux version 2.4.17 (jack@saturn) (gcc version 3.2.2 20030322 (Pioneer
 >
Before I left Broadcom, I had that kernel at 2.4.18 I believe and the
703x drivers were working fine. Is there some reason you are not using
the Broadcom kernel? I did notice one of the lines had the smartcard
interrupt firing. Those drivers were not exactly supported well. Can
you provide more information on the hardware platform and version of
the drivers? Thanks.

-Steve, ex. Broadcom settop kernel developer

  reply	other threads:[~2003-07-18 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 16:57 kernel BUG at sched.c:784! Jack Miller
2003-07-18 17:08 ` Steven J. Hill [this message]
2003-07-18 17:22 ` Jun Sun
2003-07-18 17:26   ` Jack Miller
2003-07-18 17:44     ` Jun Sun
2003-07-18 17:48       ` Jack Miller
2003-07-18 18:29         ` Jun Sun
2003-07-18 18:48           ` Jack Miller
2003-07-18 22:51           ` Jack Miller
2003-07-18 22:59             ` Jun Sun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F1829AB.9090303@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=jack.miller@pioneer-pdt.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.