From: Lee Revell <rlrevell@joe-job.com>
To: martin rumori <lists@rumori.de>
Cc: jackit-devel <jackit-devel@lists.sourceforge.net>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Jackit-devel] Re: little NPTL SCHED_FIFO test program
Date: Fri, 20 Aug 2004 05:42:59 -0400 [thread overview]
Message-ID: <1092994979.10063.80.camel@krustophenia.net> (raw)
In-Reply-To: <20040820092042.GA2496@amadora.tejo>
On Fri, 2004-08-20 at 05:20, martin rumori wrote:
> On Fri, Aug 20, 2004 at 03:38:44AM -0400, Lee Revell wrote:
> > > I have built a glibc with the patch you (Lee) sent to the bug-report.
> >
> > This fixes the problem, jackd now works correctly. I cannot take credit
> > for finding the problem though, Florian did most of the work in tracking
> > this down.
>
> same here, really great (debian unstable).
>
> wanted to try the volunteer preempt patch for the first time, (until
> now running 2.6.7-cko5 atm).
>
> tried to compile 2.6.8.1 with volunteer-preempt-P5 (latest), but
> wasn't able to boot into the new kernel. shows some lines of ACPI....
> directly after unpacking, then stops for about 1 second (without an
> error message, last line is something with a specific processor flag),
> then reboots. not long enough to see something meaningful...
>
I think you have an off-by-one error. The latest version is -P4.
Try the 'noacpi' boot option. Also, try disabling all power
management. I know this is not realistic for a laptop, it's just for
debugging purposes.
> ACPI is disabled in favor of APM, changed that, same behavior: there
> is some lines starting with ACPI on the screen, either way. applied
> latest acpi.sf.net patch, same thing. would like to keep APM since
> ACPI doesn't work that well with my machine. stock 2.6.8.1-acpi boots
> fine (with the usual acpi oddities, with or without acpi patch), apm
> with 2.6.8 not yet tried (don't expect problems).
>
> thinkpad t40p, PM-1600, 512 MB, latest bios/embeddecontroller.
>
> is there something like that known with volunteer-preempt? should i
> try an older version (== P4) first? are there some config options
> which are especially meaningful?
>
I am adding LKML and Ingo to the cc: list as he has requested any
reports of ACPI problems with the VP patches.
Lee
next parent reply other threads:[~2004-08-20 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040817121358.5adffd22@mango.fruits.de>
[not found] ` <200408172102.00964.pnambic@unu.nu>
[not found] ` <20040818004633.35eb6501@mango.fruits.de>
[not found] ` <200408180100.04955.pnambic@unu.nu>
[not found] ` <20040818023546.03e79fc4@mango.fruits.de>
[not found] ` <1092794828.813.49.camel@krustophenia.net>
[not found] ` <20040818050708.54a27a7e@mango.fruits.de>
[not found] ` <pan.2004.08.19.23.33.47.308243@gmx.de>
[not found] ` <1092987523.10063.62.camel@krustophenia.net>
[not found] ` <20040820092042.GA2496@amadora.tejo>
2004-08-20 9:42 ` Lee Revell [this message]
2004-08-20 17:53 ` problems with volunteer preempt patch WAS: little NPTL SCHED_FIFO test program martin rumori
2004-08-20 18:35 ` Ingo Molnar
2004-08-20 19:35 ` [Jackit-devel] " martin rumori
2004-08-21 0:29 ` martin rumori
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=1092994979.10063.80.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=jackit-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@rumori.de \
--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