From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Joseph Fannin <jhf@rivenstone.net>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6.7-mm7
Date: Wed, 14 Jul 2004 15:01:50 -0700 [thread overview]
Message-ID: <20040714220150.GM21856@smtp.west.cox.net> (raw)
In-Reply-To: <20040709141103.592c4655.akpm@osdl.org>
On Fri, Jul 09, 2004 at 02:11:03PM -0700, Andrew Morton wrote:
>
> jhf@rivenstone.net (Joseph Fannin) wrote:
> >
> > On Thu, Jul 08, 2004 at 11:50:25PM -0700, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm7/
> >
> > > +detect-too-early-schedule-attempts.patch
> > >
> > > Catch attempts to call the scheduler before it is ready to go.
> >
> > With this patch, my Powermac (ppc32) spews 711 (I think)
> > warning messages during bootup.
>
> hm, OK. It could be that the debug patch is a bit too aggressive, or that
> ppc got lucky and happens to always be in state TASK_RUNNING when these
> calls to schedule() occur.
>
> Maybe this task incorrectly has _TIF_NEED_RESCHED set?
>
> Anyway, ppc guys: please take a look at the results from
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm7/broken-out/detect-too-early-schedule-attempts.patch
> and check that the kernel really should be calling schedule() at this time
> and place, let us know?
Now that kallsyms data is OK, I took a quick look.. and all of this
comes from generic code, at least on the machine I tried. So if the
code shouldn't be calling schedule() then, it's a more generic problem..
... or I'm not following.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-07-14 22:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 6:50 2.6.7-mm7 Andrew Morton
2004-07-09 8:15 ` 2.6.7-mm7 Stefano Rivoir
2004-07-09 9:41 ` 2.6.7-mm7 Andrew Morton
2004-07-09 10:27 ` 2.6.7-mm7 Stefano Rivoir
2004-07-09 10:32 ` 2.6.7-mm7 Stefano Rivoir
2004-07-09 11:45 ` 2.6.7-mm7 Jesse Stockall
2004-07-09 18:54 ` 2.6.7-mm7 Andrew Morton
2004-07-09 19:52 ` 2.6.7-mm7 Jesse Stockall
2004-07-09 20:00 ` 2.6.7-mm7 Andrew Morton
2004-07-09 22:21 ` 2.6.7-mm7 Greg KH
2004-07-09 19:56 ` 2.6.7-mm7 Alan Stern
2004-07-09 10:32 ` 2.6.7-mm7 Jurgen Kramer
2004-07-09 10:39 ` 2.6.7-mm7 Andrew Morton
2004-07-09 11:16 ` 2.6.7-mm7 Jurgen Kramer
2004-07-09 14:40 ` 2.6.7-mm7 Felipe Alfaro Solana
2004-07-09 16:40 ` 2.6.7-mm7 Jurgen Kramer
2004-07-09 11:44 ` 2.6.7-mm7 Michael Geithe
2004-07-09 22:15 ` 2.6.7-mm7 Greg KH
2004-07-10 0:07 ` 2.6.7-mm7 Michael Geithe
2004-07-09 20:38 ` 2.6.7-mm7 Joseph Fannin
2004-07-09 21:11 ` 2.6.7-mm7 Andrew Morton
2004-07-14 22:01 ` Tom Rini [this message]
2004-07-17 16:17 ` 2.6.7-mm7 Paul Mackerras
2004-07-17 19:19 ` 2.6.7-mm7 Joseph Fannin
2004-07-09 21:04 ` 2.6.7-mm7 William Lee Irwin III
2004-07-09 22:11 ` 2.6.7-mm7 William Lee Irwin III
2004-07-09 22:14 ` 2.6.7-mm7 Andrew Morton
2004-07-09 22:24 ` 2.6.7-mm7 James Bottomley
2004-07-09 23:40 ` 2.6.7-mm7 Andrew Morton
2004-07-10 2:47 ` 2.6.7-mm7 James Bottomley
2004-07-10 4:34 ` 2.6.7-mm7 Joshua Kwan
2004-07-10 4:40 ` 2.6.7-mm7 Joshua Kwan
2004-07-10 18:29 ` 2.6.7-mm7 Diego Calleja García
2004-07-10 20:04 ` 2.6.7-mm7 Marcin Gibuła
2004-07-10 20:10 ` 2.6.7-mm7 Marcin Gibuła
2004-07-10 20:27 ` 2.6.7-mm7 Andrew Morton
2004-07-10 20:32 ` 2.6.7-mm7 Marcin Gibuła
2004-07-11 4:19 ` 2.6.7-mm7 Dax Kelson
2004-07-11 4:40 ` 2.6.7-mm7 Andrew Morton
2004-07-10 6:21 2.6.7-mm7 Zoltan Boszormenyi
[not found] <A6974D8E5F98D511BB910002A50A6647615FFB70@hdsmsx403.hd.intel.com>
2004-07-11 2:23 ` 2.6.7-mm7 Len Brown
2004-07-11 10:23 ` 2.6.7-mm7 Thomas Svedberg
2004-07-11 15:49 ` 2.6.7-mm7 Zoltan Boszormenyi
[not found] <A6974D8E5F98D511BB910002A50A6647615FFA5D@hdsmsx403.hd.intel.com>
2004-07-11 2:34 ` 2.6.7-mm7 Len Brown
2004-07-11 18:32 ` 2.6.7-mm7 Michael Geithe
[not found] <A6974D8E5F98D511BB910002A50A6647615FFA8A@hdsmsx403.hd.intel.com>
2004-07-11 2:36 ` 2.6.7-mm7 Len Brown
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=20040714220150.GM21856@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=jhf@rivenstone.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®