From: Mateusz.Blaszczyk@nask.pl
To: Ingo Molnar <mingo@elte.hu>
Cc: rml@tech9.net, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch, 2.6.9-rc4-mm1] fix oops in sched_setscheduler
Date: Fri, 15 Oct 2004 12:52:29 +0200 (CEST) [thread overview]
Message-ID: <Pine.GSO.4.58.0410151251150.5009@boromir> (raw)
In-Reply-To: <20041015090336.GA14362@elte.hu>
On Fri, 15 Oct 2004, Ingo Molnar wrote:
>
> * Mateusz.Blaszczyk@nask.pl <Mateusz.Blaszczyk@nask.pl> wrote:
>
> > Running cdrecord caused oops in sched_setscheduler syscall (i think)
> > so i tested with my little setp.c program that follows. It seems that
> > it always oops - no matter what policy I request. It runs ok on
> > 2.6.9-rc2-mm1, same config. Rc3 not tested. I run setp. 3 times. The
> > first I decoded using ksymoops. My .config follows at the end.
>
> the crash happens if 1) someone doesnt have profiling enabled 2) uses an
> UP kernel and 3) does setscheduler. The patch below fixes 3 problems:
> finishes and fixes the consolidation and fixes the profile=schedule
> feature. Against 2.6.9-rc4-mm1. Tested.
tested, works.
-mat
--
Pozdrowienia,Regards,Cheers,Grüße,A plus!,
next prev parent reply other threads:[~2004-10-15 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 7:13 Oops sched_setscheduler in 2.6.9-rc4-mm1 Mateusz.Blaszczyk
2004-10-15 9:03 ` [patch, 2.6.9-rc4-mm1] fix oops in sched_setscheduler Ingo Molnar
2004-10-15 9:07 ` Andrew Morton
2004-10-15 9:20 ` [patch, 2.6.9-rc4-mm1, 2.6.9-rc4] fix the prof=schedule feature Ingo Molnar
2004-10-15 10:52 ` Mateusz.Blaszczyk [this message]
2004-10-15 10:56 ` [patch, 2.6.9-rc4-mm1] fix oops in sched_setscheduler William Lee Irwin III
2004-10-15 11:49 ` Ingo Molnar
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=Pine.GSO.4.58.0410151251150.5009@boromir \
--to=mateusz.blaszczyk@nask.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.com \
/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®