On Sat, 2005-07-30 at 12:18 -0600, Zwane Mwaikambo wrote:
> On Sat, 30 Jul 2005, Lee Revell wrote:
>
> > So it looks like artsd wastes way more power DMAing a bunch of silent
> > pages to the sound card than HZ=1000.
> >
> > There's nothing the ALSA layer can
On Sat, 2005-07-30 at 12:18 -0600, Zwane Mwaikambo wrote:
> On Sat, 30 Jul 2005, Lee Revell wrote:
>
> > So it looks like artsd wastes way more power DMAing a bunch of silent
> > pages to the sound card than HZ=1000.
> >
> > There's nothing the ALSA layer can
On Sat, 2005-07-30 at 12:06 +0200, Marc Ballarin wrote:
> On Fri, 29 Jul 2005 19:15:42 -0400
> Lee Revell <[EMAIL PROTECTED]> wrote:
>
> >
> > What kind of results do you get with a more realistic setup, like
> > running KDE or Gnome OOTB?
> >
On Sat, 2005-07-30 at 12:18 -0600, Zwane Mwaikambo wrote:
On Sat, 30 Jul 2005, Lee Revell wrote:
So it looks like artsd wastes way more power DMAing a bunch of silent
pages to the sound card than HZ=1000.
There's nothing the ALSA layer can do about this, it's a KDE bug.
I think
On Sat, 2005-07-30 at 12:18 -0600, Zwane Mwaikambo wrote:
On Sat, 30 Jul 2005, Lee Revell wrote:
So it looks like artsd wastes way more power DMAing a bunch of silent
pages to the sound card than HZ=1000.
There's nothing the ALSA layer can do about this, it's a KDE bug.
I think
On Sat, 2005-07-30 at 21:51 +0200, Pavel Machek wrote:
I think this is a good argument for leaving HZ at 1000 until some of
these userspace bugs are fixed.
WTF? HZ=1000 eats energy like crazy. artsd eats energy like crazy. And
you advocate breaking kernel because artsd is broken?!
Maybe I
On Sat, 2005-07-30 at 21:51 +0200, Pavel Machek wrote:
I think this is a good argument for leaving HZ at 1000 until some of
these userspace bugs are fixed.
WTF? HZ=1000 eats energy like crazy. artsd eats energy like crazy. And
you advocate breaking kernel because artsd is broken?!
Also as
On Sat, 2005-07-30 at 19:48 -0400, Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing interrupt handler.
How do I get the output to stop after the first
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard
On Sat, 2005-07-30 at 22:52 +0200, Ingo Molnar wrote:
* Peter Zijlstra [EMAIL PROTECTED] wrote:
Hi Ingo,
-02 needs the attached patch to compile with my config.
thanks, i've released -03 with your fixes.
Does not compile with highmem enabled:
CC arch/i386/mm/highmem.o
On Sat, 2005-07-30 at 00:49 +0200, Marc Ballarin wrote:
> - no daemons running
What kind of results do you get with a more realistic setup, like
running KDE or Gnome OOTB?
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Fri, 2005-07-29 at 13:51 -0700, Chris Wright wrote:
> * Chris Wright ([EMAIL PROTECTED]) wrote:
> > Yes, this requires updated pam patch.
>
> Here's the updated pam patch. I left the lower end at 0 rather than 1,
> since it's no harm.
>
> +/* Hack to test new rlimit values */
Does this
On Fri, 2005-07-29 at 13:51 -0700, Chris Wright wrote:
* Chris Wright ([EMAIL PROTECTED]) wrote:
Yes, this requires updated pam patch.
Here's the updated pam patch. I left the lower end at 0 rather than 1,
since it's no harm.
+/* Hack to test new rlimit values */
Does this still
On Sat, 2005-07-30 at 00:49 +0200, Marc Ballarin wrote:
- no daemons running
What kind of results do you get with a more realistic setup, like
running KDE or Gnome OOTB?
Lee
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
On Sun, 2005-07-03 at 18:53 -0400, Lee Revell wrote:
> Looks like a bug in the voice allocator. This is my fault, that bug was
> thought to have been fixed. Forwarding to alsa-devel.
>
This bug was previously closed in the ALSA BTS. Please find it and
reopen if possible.
Lee
>
On Thu, 2005-07-28 at 10:25 -0700, Andrew Morton wrote:
> Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
> >
> > Linus, please do an update from:
> >
> >rsync://rsync.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git
> >
> > ...
> > 65 files changed, 5059 insertions(+), 1122 deletions(-)
>
>
On Thu, 2005-07-28 at 17:04 +0200, Thorsten Knabe wrote:
> I'm the maintainer of the OSS AD1816 sound driver. I'm aware of two
> problems of the ALSA AD1816 driver, that do not show up with the OSS
> driver:
> - According to my own experience and user reports audio is choppy with
> some VoIP
On Thu, 2005-07-28 at 17:04 +0200, Thorsten Knabe wrote:
I'm the maintainer of the OSS AD1816 sound driver. I'm aware of two
problems of the ALSA AD1816 driver, that do not show up with the OSS
driver:
- According to my own experience and user reports audio is choppy with
some VoIP
On Thu, 2005-07-28 at 10:25 -0700, Andrew Morton wrote:
Jaroslav Kysela [EMAIL PROTECTED] wrote:
Linus, please do an update from:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git
...
65 files changed, 5059 insertions(+), 1122 deletions(-)
The git-alsa.patch
On Sun, 2005-07-03 at 18:53 -0400, Lee Revell wrote:
Looks like a bug in the voice allocator. This is my fault, that bug was
thought to have been fixed. Forwarding to alsa-devel.
This bug was previously closed in the ALSA BTS. Please find it and
reopen if possible.
Lee
On Mon, 2005-07
On Thu, 2005-07-28 at 03:21 +0200, Thomas Zehetbauer wrote:
> On Wed, 2005-07-27 at 16:44 -0400, Lee Revell wrote:
> > On Wed, 2005-07-27 at 21:46 +0200, Thomas Zehetbauer wrote:
> > > I cannot get my SB Live! 5.1's SPDIF (digital) output to work with
> > > kernel >
On Thu, 2005-07-28 at 03:21 +0200, Thomas Zehetbauer wrote:
> On Wed, 2005-07-27 at 16:44 -0400, Lee Revell wrote:
> > On Wed, 2005-07-27 at 21:46 +0200, Thomas Zehetbauer wrote:
> > > I cannot get my SB Live! 5.1's SPDIF (digital) output to work with
> > > kernel >
On Wed, 2005-07-27 at 18:00 -0700, Daniel Walker wrote:
> Don't you break sched_find_first_bit() , seems it's dependent on a
> 140-bit bitmap .
And doesn't POSIX specify 100 RT priority levels?
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Wed, 2005-07-27 at 01:38 +0200, Zoran Dzelajlija wrote:
> The OSS maestro driver works better on my old Armada E500 laptop. I tried
> ALSA after switching to 2.6, but the computer hung with 2.6.8.1 or 2.6.10 if
> I touched the volume buttons.
Please test a newer ALSA version, like the one in
On Wed, 2005-07-27 at 21:46 +0200, Thomas Zehetbauer wrote:
> Hi!
>
> I cannot get my SB Live! 5.1's SPDIF (digital) output to work with
> kernel > 2.6.12. I have not changed my mixer configuration and it is
> still working when I boot 2.6.11.12 or earlier. I am using FC4 with
>
On Wed, 2005-07-27 at 00:40 +0100, Alan Cox wrote:
> > > sound/oss/skeleton.c
>
> Reference for writing drivers
But we're not taking new OSS drivers, right?
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
> > What about audio? If there is a sound server running then you're going
> > to have a constant stream of interrupts and DMA activity from the sound
> > card even if the machine is idle and there aren't any sounds playing.
>
> Doesn't
On Wed, 2005-07-27 at 02:13 -0600, Zwane Mwaikambo wrote:
What about audio? If there is a sound server running then you're going
to have a constant stream of interrupts and DMA activity from the sound
card even if the machine is idle and there aren't any sounds playing.
Doesn't artsd at
On Wed, 2005-07-27 at 00:40 +0100, Alan Cox wrote:
sound/oss/skeleton.c
Reference for writing drivers
But we're not taking new OSS drivers, right?
Lee
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Wed, 2005-07-27 at 21:46 +0200, Thomas Zehetbauer wrote:
Hi!
I cannot get my SB Live! 5.1's SPDIF (digital) output to work with
kernel 2.6.12. I have not changed my mixer configuration and it is
still working when I boot 2.6.11.12 or earlier. I am using FC4 with
alsa-lib-1.0.9rf-2.FC4
On Wed, 2005-07-27 at 01:38 +0200, Zoran Dzelajlija wrote:
The OSS maestro driver works better on my old Armada E500 laptop. I tried
ALSA after switching to 2.6, but the computer hung with 2.6.8.1 or 2.6.10 if
I touched the volume buttons.
Please test a newer ALSA version, like the one in
On Wed, 2005-07-27 at 18:00 -0700, Daniel Walker wrote:
Don't you break sched_find_first_bit() , seems it's dependent on a
140-bit bitmap .
And doesn't POSIX specify 100 RT priority levels?
Lee
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Thu, 2005-07-28 at 03:21 +0200, Thomas Zehetbauer wrote:
On Wed, 2005-07-27 at 16:44 -0400, Lee Revell wrote:
On Wed, 2005-07-27 at 21:46 +0200, Thomas Zehetbauer wrote:
I cannot get my SB Live! 5.1's SPDIF (digital) output to work with
kernel 2.6.12. I have not changed my mixer
On Thu, 2005-07-28 at 03:21 +0200, Thomas Zehetbauer wrote:
On Wed, 2005-07-27 at 16:44 -0400, Lee Revell wrote:
On Wed, 2005-07-27 at 21:46 +0200, Thomas Zehetbauer wrote:
I cannot get my SB Live! 5.1's SPDIF (digital) output to work with
kernel 2.6.12. I have not changed my mixer
On Tue, 2005-07-26 at 19:35 -0400, Stephen Clark wrote:
> Additional info I don't see any interrupts in /proc/interrupts for the
> Allegro which is on int 5.
> I just tried the same laptop with knoppix and a 2.4.27 kernel and sound
> works great and I do
> see interrupts for Allegro on int 5.
So
On Wed, 2005-07-27 at 06:53 +0300, Al Boldi wrote:
> Gettimeofday loops using gcc-3.2.2 on 2.4.31 and 2.6.12.
>
> Also, 2.4 is faster than 2.6!
All this proves is that gettimeofday() is faster on 2.4 than 2.6.
Hardly surprising.
Lee
-
To unsubscribe from this list: send the line "unsubscribe
On Tue, 2005-07-26 at 11:48 -0400, Jeff Garzik wrote:
> NAK for i810_audio: ALSA doesn't have all the PCI IDs (which must be
> verified -- you cannot just add the PCI IDs for some hardware)
Some of them might be in snd-hda-intel in addition to snd-intel8x0.
Lee
-
To unsubscribe from this
On Tue, 2005-07-26 at 11:57 -0400, Jeff Garzik wrote:
> Lee Revell wrote:
> > On Tue, 2005-07-26 at 17:08 +0200, Adrian Bunk wrote:
> >
> >>This patch schedules obsolete OSS drivers (with ALSA drivers that
> >>support the same hardware) for removal.
> &
On Tue, 2005-07-26 at 17:08 +0200, Adrian Bunk wrote:
> This patch schedules obsolete OSS drivers (with ALSA drivers that
> support the same hardware) for removal.
How many non-obsolete OSS drivers were there?
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Tue, 2005-07-26 at 14:06 +0200, Ingo Molnar wrote:
> i'd not put it into stable just yet - the fact that it has not been
> tested in 2.6.12 _at all_ up until very recently means there's little
> QA feedback. Yes, it's simple, but it also triggers something we never
> did before. 2.6.13 ought
On Tue, 2005-07-26 at 14:06 +0200, Ingo Molnar wrote:
i'd not put it into stable just yet - the fact that it has not been
tested in 2.6.12 _at all_ up until very recently means there's little
QA feedback. Yes, it's simple, but it also triggers something we never
did before. 2.6.13 ought to be
On Tue, 2005-07-26 at 17:08 +0200, Adrian Bunk wrote:
This patch schedules obsolete OSS drivers (with ALSA drivers that
support the same hardware) for removal.
How many non-obsolete OSS drivers were there?
Lee
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
On Tue, 2005-07-26 at 11:57 -0400, Jeff Garzik wrote:
Lee Revell wrote:
On Tue, 2005-07-26 at 17:08 +0200, Adrian Bunk wrote:
This patch schedules obsolete OSS drivers (with ALSA drivers that
support the same hardware) for removal.
How many non-obsolete OSS drivers were
On Tue, 2005-07-26 at 11:48 -0400, Jeff Garzik wrote:
NAK for i810_audio: ALSA doesn't have all the PCI IDs (which must be
verified -- you cannot just add the PCI IDs for some hardware)
Some of them might be in snd-hda-intel in addition to snd-intel8x0.
Lee
-
To unsubscribe from this list:
On Wed, 2005-07-27 at 06:53 +0300, Al Boldi wrote:
Gettimeofday loops using gcc-3.2.2 on 2.4.31 and 2.6.12.
Also, 2.4 is faster than 2.6!
All this proves is that gettimeofday() is faster on 2.4 than 2.6.
Hardly surprising.
Lee
-
To unsubscribe from this list: send the line unsubscribe
On Tue, 2005-07-26 at 19:35 -0400, Stephen Clark wrote:
Additional info I don't see any interrupts in /proc/interrupts for the
Allegro which is on int 5.
I just tried the same laptop with knoppix and a 2.4.27 kernel and sound
works great and I do
see interrupts for Allegro on int 5.
So the
On Mon, 2005-07-25 at 23:21 -0400, Mace Moneta wrote:
> The response seems meaningless; does this constitute a violation of
> GPL?
> If so what, if any, action needs to be taken?
It sounds like they think you are asking for their userspace source
code, or that support rep does not know the
On Tue, 2005-07-26 at 04:43 +0200, Benoit Dejean wrote:
> Hi,
> i'm using Debian SID kernel-image-2.6.11-powerpc [1] (which is not
> tainted). I've unfortunately started sysutils [2] memtest as user (no caps, no
> sticky bit).
>
> /usr/sbin/memtest all
> As expected, a few minutes later,
On Mon, 2005-07-25 at 20:20 -0400, Steven Rostedt wrote:
> And I
> would also assume that you prefer x *= 2 over x <<= 1 (also since the
> first person to show this example used x <<= 2. Right Lee? :-)
Let us never speak of that again. These aren't the droids you're
looking for.
Lee
-
To
On Mon, 2005-07-25 at 17:19 -0400, Brown, Len wrote:
> >>>Question one, are there other actions to consider?
> >>
> >>
> >> Yes.
> >> Speaking for ACPI C3 state, note that DMA also
> >> wakes up the CPU -- even if there was no device interrupt.
> >> (aka, "the trouble with USB")
> >
> >Trouble?
On Mon, 2005-07-25 at 16:28 -0400, Steven Rostedt wrote:
> Ingo,
>
> I've CC you just because you are the schedule maintainer. You already
> accepted this patch into your RT tree.
>
Please make sure to pick up this patch from Andreas Steinmetz too,
otherwise the rlimits are broken:
---
On Mon, 2005-07-25 at 15:23 -0400, [EMAIL PROTECTED] wrote:
> I am using Red Hat sources, which has function open_kcore() hardcoded to
> return -EPERM always.
>
> Changing this function to the way it is defined in the public sources (as
> shown below) did the trick.
All these Red Hat / RHEL
On Mon, 2005-07-25 at 12:16 -0700, Philippe Troin wrote:
> Lee Revell <[EMAIL PROTECTED]> writes:
>
> > On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
> > > Doesn't matter. The cycles saved for old compilers is not rational to
> > > have obfusc
On Mon, 2005-07-25 at 20:23 +0100, Paulo Marques wrote:
> Lee Revell wrote:
> > On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
> >
> >>Doesn't matter. The cycles saved for old compilers is not rational to
> >>have obfuscated code.
> >
> &g
On Mon, 2005-07-25 at 12:16 -0700, Philippe Troin wrote:
> Lee Revell <[EMAIL PROTECTED]> writes:
>
> > On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
> > > Doesn't matter. The cycles saved for old compilers is not rational to
> > > have obfusc
On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
> Doesn't matter. The cycles saved for old compilers is not rational to
> have obfuscated code.
Where do we draw the line with this? Is x *= 2 preferable to x <<= 2 as
well?
Lee
-
To unsubscribe from this list: send the line
On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
Doesn't matter. The cycles saved for old compilers is not rational to
have obfuscated code.
Where do we draw the line with this? Is x *= 2 preferable to x = 2 as
well?
Lee
-
To unsubscribe from this list: send the line unsubscribe
On Mon, 2005-07-25 at 12:16 -0700, Philippe Troin wrote:
Lee Revell [EMAIL PROTECTED] writes:
On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
Doesn't matter. The cycles saved for old compilers is not rational to
have obfuscated code.
Where do we draw the line
On Mon, 2005-07-25 at 20:23 +0100, Paulo Marques wrote:
Lee Revell wrote:
On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
Doesn't matter. The cycles saved for old compilers is not rational to
have obfuscated code.
Where do we draw the line with this? Is x *= 2 preferable
On Mon, 2005-07-25 at 12:16 -0700, Philippe Troin wrote:
Lee Revell [EMAIL PROTECTED] writes:
On Mon, 2005-07-25 at 13:55 -0400, Steven Rostedt wrote:
Doesn't matter. The cycles saved for old compilers is not rational to
have obfuscated code.
Where do we draw the line
On Mon, 2005-07-25 at 15:23 -0400, [EMAIL PROTECTED] wrote:
I am using Red Hat sources, which has function open_kcore() hardcoded to
return -EPERM always.
Changing this function to the way it is defined in the public sources (as
shown below) did the trick.
All these Red Hat / RHEL threads
On Mon, 2005-07-25 at 16:28 -0400, Steven Rostedt wrote:
Ingo,
I've CC you just because you are the schedule maintainer. You already
accepted this patch into your RT tree.
Please make sure to pick up this patch from Andreas Steinmetz too,
otherwise the rlimits are broken:
---
On Mon, 2005-07-25 at 17:19 -0400, Brown, Len wrote:
Question one, are there other actions to consider?
Yes.
Speaking for ACPI C3 state, note that DMA also
wakes up the CPU -- even if there was no device interrupt.
(aka, the trouble with USB)
Trouble? Why would USB do DMA unless
On Mon, 2005-07-25 at 20:20 -0400, Steven Rostedt wrote:
And I
would also assume that you prefer x *= 2 over x = 1 (also since the
first person to show this example used x = 2. Right Lee? :-)
Let us never speak of that again. These aren't the droids you're
looking for.
Lee
-
To unsubscribe
On Tue, 2005-07-26 at 04:43 +0200, Benoit Dejean wrote:
Hi,
i'm using Debian SID kernel-image-2.6.11-powerpc [1] (which is not
tainted). I've unfortunately started sysutils [2] memtest as user (no caps, no
sticky bit).
/usr/sbin/memtest all
As expected, a few minutes later, my
On Mon, 2005-07-25 at 23:21 -0400, Mace Moneta wrote:
The response seems meaningless; does this constitute a violation of
GPL?
If so what, if any, action needs to be taken?
It sounds like they think you are asking for their userspace source
code, or that support rep does not know the
On Sun, 2005-07-24 at 17:03 -0400, Florin Malita wrote:
> the x86 timer interrupt
> frequency has increased from 100Hz to 1KHz (it's about to be lowered
> to 250Hz)
This is by no means a done deal. So far no one has posted ANY evidence
that dropping HZ to 250 helps (except one result on a
On Sun, 2005-07-24 at 17:03 -0400, Florin Malita wrote:
the x86 timer interrupt
frequency has increased from 100Hz to 1KHz (it's about to be lowered
to 250Hz)
This is by no means a done deal. So far no one has posted ANY evidence
that dropping HZ to 250 helps (except one result on a
On Sat, 2005-07-23 at 13:42 +0200, Andreas Steinmetz wrote:
> RLIMIT_RTPRIO is supposed to grant non privileged users the right to use
> SCHED_FIFO/SCHED_RR scheduling policies with priorites bounded by the
> RLIMIT_RTPRIO value via sched_setscheduler(). This is usually used by
> audio users.
>
>
On Sat, 2005-07-23 at 19:05 +1000, Con Kolivas wrote:
> Indeed, and the purpose of the benchmark is to quantify something rather than
> leave it to subjective feeling. Fortunately if I was to quantify the current
> kernel's situation I would say everything is fine.
Agreed. Unfortunately
On Sat, 2005-07-23 at 19:05 +1000, Con Kolivas wrote:
Indeed, and the purpose of the benchmark is to quantify something rather than
leave it to subjective feeling. Fortunately if I was to quantify the current
kernel's situation I would say everything is fine.
Agreed. Unfortunately
On Fri, 2005-07-22 at 20:31 -0700, Linus Torvalds wrote:
>
> On Fri, 22 Jul 2005, Lee Revell wrote:
> >
> > Con's interactivity benchmark looks quite promising for finding
> > scheduler related interactivity regressions.
>
> I doubt that _any_ of the reg
On Fri, 2005-07-22 at 21:15 -0500, Alejandro Bonilla wrote:
> OK, I will, but I first of all need to learn how to tell if benchmarks
> are better or worse.
Con's interactivity benchmark looks quite promising for finding
scheduler related interactivity regressions. It certainly has confirmed
On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
> I will get flames for this, but my laptop boots faster and sometimes
> responds faster in 2.4.27 than in 2.6.12. Sorry, but this is the fact
> for me. IBM T42.
Sorry dude, but there's just no way that any automated process can catch
On Wed, 2005-07-20 at 13:41 -0400, Lee Revell wrote:
> On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
> > Hi,
> > I just released a new version of kernel-desktop. New features are:
>
> > - Realtime LSM module (Useful for jack audio server)
>
>
On Fri, 2005-07-22 at 15:25 +0200, Gábor Lénárt wrote:
> Anyway, want to have 'free memory' is a thing like having dozens of cars
> in your garage which don't want to be used ...
>
Really? I thought it was good to leave some memory free to speed up
application startup, so we don't have to evict
On Fri, 2005-07-22 at 15:18 +0200, Ralf Hildebrandt wrote:
> * Denis Vlasenko <[EMAIL PROTECTED]>:
>
> > Not happening here on 2.6.12:
>
> 2.6.12 didn't have kexec (unless it's a -mm kernel)
> So how could you boot using kexec then?
>
Is kexec supposed to be transparent to all the subsystems,
On Fri, 2005-07-22 at 15:18 +0200, Ralf Hildebrandt wrote:
* Denis Vlasenko [EMAIL PROTECTED]:
Not happening here on 2.6.12:
2.6.12 didn't have kexec (unless it's a -mm kernel)
So how could you boot using kexec then?
Is kexec supposed to be transparent to all the subsystems, or does
On Fri, 2005-07-22 at 15:25 +0200, Gábor Lénárt wrote:
Anyway, want to have 'free memory' is a thing like having dozens of cars
in your garage which don't want to be used ...
Really? I thought it was good to leave some memory free to speed up
application startup, so we don't have to evict a
On Wed, 2005-07-20 at 13:41 -0400, Lee Revell wrote:
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
Hi,
I just released a new version of kernel-desktop. New features are:
- Realtime LSM module (Useful for jack audio server)
2.6.12 supports RLIMIT_RTPRIO and RLIMIT_NICE so
On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
I will get flames for this, but my laptop boots faster and sometimes
responds faster in 2.4.27 than in 2.6.12. Sorry, but this is the fact
for me. IBM T42.
Sorry dude, but there's just no way that any automated process can catch
On Fri, 2005-07-22 at 21:15 -0500, Alejandro Bonilla wrote:
OK, I will, but I first of all need to learn how to tell if benchmarks
are better or worse.
Con's interactivity benchmark looks quite promising for finding
scheduler related interactivity regressions. It certainly has confirmed
what
On Fri, 2005-07-22 at 20:31 -0700, Linus Torvalds wrote:
On Fri, 22 Jul 2005, Lee Revell wrote:
Con's interactivity benchmark looks quite promising for finding
scheduler related interactivity regressions.
I doubt that _any_ of the regressions that are user-visible are
scheduler
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
> Hi,
"You are not allowed to post to this mailing list, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at
[EMAIL PROTECTED]"
Please don't
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
> Hi,
> I just released a new version of kernel-desktop. New features are:
> - Realtime LSM module (Useful for jack audio server)
2.6.12 supports RLIMIT_RTPRIO and RLIMIT_NICE so this is no longer
needed.
The distros need to get with
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
Hi,
I just released a new version of kernel-desktop. New features are:
- Realtime LSM module (Useful for jack audio server)
2.6.12 supports RLIMIT_RTPRIO and RLIMIT_NICE so this is no longer
needed.
The distros need to get with the
On Wed, 2005-07-20 at 17:29 +0200, Jean-Eric Cuendet wrote:
Hi,
You are not allowed to post to this mailing list, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at
[EMAIL PROTECTED]
Please don't cc:
On Wed, 2005-07-20 at 08:16 +1000, Con Kolivas wrote:
> As a data point I went back to a 2.6.10 kernel which predates some
> latency fixes that went into mainline.
>
I think most of the important ones had already gone in by then. It
would be more interesting to compare it with 2.6.8.
Lee
-
To
On Tue, 2005-07-19 at 22:15 +0200, Jan Engelhardt wrote:
> >AFAIK it's not possible to use SSE and MME in kernel mode, since these
> >registers aren't preserved (it would be expensive).
>
> Floating point is anyway a no-no in the kernel.
However, there are a few exceptions like mmx_memcpy.
Lee
On Tue, 2005-07-19 at 15:29 -0400, Greg KH wrote:
> Ugh, you have a bad device or power supply, or aren't giving it enough
> power to drive the thing. Nothing we can do in Linux for that, sorry.
> Buy a wall-powered usb hub, that usually helps.
>
I get the same messages on boot from a bus with
On Tue, 2005-07-19 at 15:29 -0400, Greg KH wrote:
Ugh, you have a bad device or power supply, or aren't giving it enough
power to drive the thing. Nothing we can do in Linux for that, sorry.
Buy a wall-powered usb hub, that usually helps.
I get the same messages on boot from a bus with no
On Tue, 2005-07-19 at 22:15 +0200, Jan Engelhardt wrote:
AFAIK it's not possible to use SSE and MME in kernel mode, since these
registers aren't preserved (it would be expensive).
Floating point is anyway a no-no in the kernel.
However, there are a few exceptions like mmx_memcpy.
Lee
-
To
On Wed, 2005-07-20 at 08:16 +1000, Con Kolivas wrote:
As a data point I went back to a 2.6.10 kernel which predates some
latency fixes that went into mainline.
I think most of the important ones had already gone in by then. It
would be more interesting to compare it with 2.6.8.
Lee
-
To
On Sat, 2005-07-16 at 21:04 -0700, randy_dunlap wrote:
> On Sat, 16 Jul 2005 23:11:26 -0400 Lee Revell wrote:
>
> > On Sun, 2005-07-17 at 04:38 +0200, Adrian Bunk wrote:
> > > SCSI_QLA2XXX is automatically enabled for (SCSI && PCI).
> >
> > This has bugge
On Sat, 2005-07-16 at 19:35 -0700, Nish Aravamudan wrote:
> As you've seen, I think it depends on the timesource: for the PIT, it
> would be arch/i386/kernel/timers/timer_pit.c::setup_pit_timer().
That one looks pretty straightforward.
arch/i386/kernel/timers/timer_tsc.c really looks like fun.
On Sun, 2005-07-17 at 04:38 +0200, Adrian Bunk wrote:
> SCSI_QLA2XXX is automatically enabled for (SCSI && PCI).
This has bugged me for a while. Why does this one SCSI driver default
to Y in the first place?
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Sun, 2005-07-17 at 04:13 +0200, Jesper Juhl wrote:
> Where do we actually program the tick rate we want?
>
In arch/i386/kernel/timers/timer_pit.c:
166 void setup_pit_timer(void)
167 {
168 unsigned long flags;
169
170 spin_lock_irqsave(_lock, flags);
501 - 600 of 1258 matches
Mail list logo
