mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Pawel Golaszewski <blues@gda.pl>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Dhaval Giani <dhaval.giani@gmail.com>
Subject: Re: PROBLEM: oops
Date: Wed, 26 Aug 2009 07:49:02 +0200	[thread overview]
Message-ID: <1251265742.7538.1192.camel@twins> (raw)
In-Reply-To: <alpine.LNX.2.00.0908252317080.17744@fgnss.gnfx.tqn.cy>

On Tue, 2009-08-25 at 23:23 +0200, Pawel Golaszewski wrote:
> On Tue, 25 Aug 2009, Peter Zijlstra wrote:
> > > > could you try to reproduce without that?
> > > > 
> > > > CONFIG_GROUP_SCHED=n
> > > I'll try. 
> 
> It seems that problem still exists - system has crashed too. From 
> netconsole:

> Any ideas?
> 
> Last kernel I was using is 2.6.27.13 - works fine. None between 13 and 31 
> tested...

# git log --format=oneline v2.6.27.13..v2.6.27.31 kernel/sched*
2b46f3769896dc04e1e49144d282e4655677105a wait: prevent exclusive waiter starvation

Nothing changed anywhere near the code that is falling apart..

Also:

[20621.263297] BUG: unable to handle kernel paging request at ffffffd8
[20621.263396] IP: [<c081cc50>] hrtick_start_fair+0x0/0x30


#ifndef CONFIG_FAIR_GROUP_SCHED

static inline struct cfs_rq *cfs_rq_of(struct sched_entity *se)
{
        struct task_struct *p = task_of(se);
        struct rq *rq = task_rq(p);

        return &rq->cfs;
}

#endif

SCHED_FEAT(HRTICK, 0)

static void hrtick_start_fair(struct rq *rq, struct task_struct *p)
{
        struct sched_entity *se = &p->se;
        struct cfs_rq *cfs_rq = cfs_rq_of(se);

        WARN_ON(task_rq(p) != rq);

        if (hrtick_enabled(rq) && cfs_rq->nr_running > 1) {

		/* won't get here since HRTICK is disabled by default */

        }
}

Suggests something went terribly wrong and corrupted a fundamental data
structure.

Maybe turning on each and every debug feature related to memory
debugging might help.

  reply	other threads:[~2009-08-26  5:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 13:55 Paweł Gołaszewski
2009-08-25 14:06 ` Peter Zijlstra
2009-08-25 14:11   ` Pawel Golaszewski
2009-08-25 14:15     ` Peter Zijlstra
2009-08-25 14:28       ` Pawel Golaszewski
2009-08-25 14:44         ` Peter Zijlstra
2009-08-25 15:03           ` Pawel Golaszewski
2009-08-25 15:07             ` Peter Zijlstra
2009-08-25 21:23               ` Pawel Golaszewski
2009-08-26  5:49                 ` Peter Zijlstra [this message]
2009-08-26  9:21                   ` Pawel Golaszewski
2009-08-27  7:58                     ` Paweł Gołaszewski
2009-08-27  9:10                       ` Peter Zijlstra
2009-08-27  9:24                         ` Pawel Golaszewski
2009-08-27  9:40                           ` Peter Zijlstra
2009-09-14 10:21                             ` Arkadiusz Miśkiewicz
2009-08-27 13:54                         ` Pawel Golaszewski
2009-08-28 10:50                           ` Paweł Gołaszewski
2009-08-28 21:46                         ` Pawel Golaszewski
2009-08-29 13:11                           ` Eric Paris

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=1251265742.7538.1192.camel@twins \
    --to=peterz@infradead.org \
    --cc=blues@gda.pl \
    --cc=dhaval.giani@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®