mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael J. Cohen" <mjc@unre.st>
To: Ingo Molnar <mingo@elte.hu>
Cc: sboyce@blueyonder.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.7
Date: Thu, 04 Nov 2004 13:31:57 -0500	[thread overview]
Message-ID: <1099593117.7982.14.camel@optie.uni.325i.org> (raw)
In-Reply-To: <20041104142317.GA19476@elte.hu>

On Thu, 2004-11-04 at 15:23 +0100, Ingo Molnar wrote:
> * Michael J. Cohen <mjc@unre.st> wrote:
> 
> > config attached, and I'll try booting with nmi_watchdog=1 next time it
> > locks.
> 
> i'd also suggest to turn CONFIG_RWSEM_DEADLOCK_DETECT on.
> 
> 	Ingo
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

threw in your tcp_window oneliner mentioned in another thread and that
seemed to curb the lockups I was getting.  xmms+jackd in realtime mode
is getting some xruns during any kind of IDE activity. network isn't
quite as fussy.

http://325i.org/kernel/2.6.10-rc1-mm2-RT-V0.7.8
+tcp_window-jackd-diskio.dmesg is the dmesg to go with the following
jackd log.  during the entire test I used xmms-jack with an mp3 read
from an nfs source.

optie ~ # jackd -R -d alsa -P -HMm -z s -o 6   
jackd 0.99.0
Copyright 2001-2003 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

loading driver ..
creating alsa driver ... hw:0|-|1024|2|48000|0|6|hwmon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Noise-shaped dithering at 16 bits
**** alsa_pcm: xrun of at least 55.205 msecs
**** alsa_pcm: xrun of at least 7.287 msecs
**** alsa_pcm: xrun of at least 101.226 msecs
**** alsa_pcm: xrun of at least 21.544 msecs
**** alsa_pcm: xrun of at least 78.721 msecs
**** alsa_pcm: xrun of at least 278.089 msecs

to produce the disk load I ran 'emerge metadata'.

upon running bonnie++, I got:

**** alsa_pcm: xrun of at least 808.719 msecs
**** alsa_pcm: xrun of at least 702.963 msecs
**** alsa_pcm: xrun of at least 78.230 msecs
**** alsa_pcm: xrun of at least 78.351 msecs
**** alsa_pcm: xrun of at least 78.390 msecs
**** alsa_pcm: xrun of at least 77.898 msecs
**** alsa_pcm: xrun of at least 78.354 msecs
**** alsa_pcm: xrun of at least 78.394 msecs
**** alsa_pcm: xrun of at least 77.835 msecs
**** alsa_pcm: xrun of at least 19.489 msecs
**** alsa_pcm: xrun of at least 85.666 msecs
**** alsa_pcm: xrun of at least 14.937 msecs
**** alsa_pcm: xrun of at least 16.331 msecs
**** alsa_pcm: xrun of at least 2.079 msecs

bonnie++ measurements are at
http://325i.org/kernel/2.6.10-rc1-mm2-RT-V0.7.8
+tcp_window-jackd-diskio.bonnie++

finally I downloaded a 700MB avi to /dev/null from the box beside it:
100%[====================================>] 734,797,824   11.08M/s   ETA
00:00

0 xruns

then to /root:

100%[====================================>] 734,797,824   11.07M/s
ETA 00:00

0 xruns during download but 2 xruns while rm'ing the file:

**** alsa_pcm: xrun of at least 41.071 msecs
**** alsa_pcm: xrun of at least 66.074 msecs


I could only find tcp related info in dmesg. strange.

HTH,

Michael Cohen



  reply	other threads:[~2004-11-04 18:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 17:08 Sid Boyce
2004-11-03 18:51 ` K.R. Foley
2004-11-04  0:00   ` Sid Boyce
2004-11-04  1:40     ` K.R. Foley
2004-11-04  9:59       ` Michael J. Cohen
2004-11-04 10:06       ` Ingo Molnar
2004-11-04 10:23         ` Michael J. Cohen
2004-11-04 11:17           ` Ingo Molnar
2004-11-04 11:17           ` Michael J. Cohen
2004-11-04 11:45             ` Ingo Molnar
2004-11-04 12:59               ` Michael J. Cohen
2004-11-04 13:34                 ` Michael J. Cohen
2004-11-04 14:05                   ` Ingo Molnar
2004-11-04 14:13                     ` Michael J. Cohen
2004-11-04 14:23                       ` Ingo Molnar
2004-11-04 18:31                         ` Michael J. Cohen [this message]
2004-11-04 19:38                           ` Ingo Molnar
2004-11-05 12:16                             ` Sid Boyce
2004-11-05 19:53                             ` Michael J. Cohen
2004-11-06  7:36                               ` Ingo Molnar
2004-11-04 12:53         ` Sid Boyce
2004-11-03 20:40 [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1 Mark_H_Johnson
2004-11-04  0:17 ` [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.7 Rui Nuno Capela

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=1099593117.7982.14.camel@optie.uni.325i.org \
    --to=mjc@unre.st \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sboyce@blueyonder.co.uk \
    /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®