Re: 2.6.14-rc3-rt2

From: Mark Knecht
Date: Tue Oct 04 2005 - 13:11:55 EST


On 10/4/05, Mark Knecht <markknecht@xxxxxxxxx> wrote:
> On 10/4/05, Ingo Molnar <mingo@xxxxxxx> wrote:
<SNIP>
> >
> > ugh. uploaded -rt6.
> >
> > Ingo
>
> Hi Ingo,
> OK, I'm up and running 2.6.14-rc3-rt7. I see no run-time problems yet...
<SNIP>

I have now had one burst of xruns. As best I can tell I was
downloading some video files for mplayer to look at, or possibly
running one of them. I see this in qjackctl:

configuring for 44100Hz, period = 128 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
09:59:12.079 Server configuration saved to "/home/mark/.jackdrc".
09:59:12.079 Statistics reset.
09:59:12.224 Client activated.
09:59:12.226 Audio connection change.
09:59:12.242 Audio connection graph change.
09:59:17.819 Audio connection graph change.
09:59:17.927 Audio connection change.
09:59:19.985 Audio connection graph change.
10:09:22.377 XRUN callback (1).
**** alsa_pcm: xrun of at least 0.336 msecs
10:09:28.450 XRUN callback (2).
**** alsa_pcm: xrun of at least 0.306 msecs
10:11:33.241 XRUN callback (3).
**** alsa_pcm: xrun of at least 4.058 msecs
subgraph starting at qjackctl-8560 timed out (subgraph_wait_fd=17,
status = 0, state = Finished)
10:12:02.490 XRUN callback (4).
**** alsa_pcm: xrun of at least 3.135 msecs
subgraph starting at qjackctl-8560 timed out (subgraph_wait_fd=17,
status = 0, state = Finished)
10:16:22.910 XRUN callback (5).
**** alsa_pcm: xrun of at least 1.848 msecs

There have been no more xruns since that burst about an hour ago.

Looking in the logs there is a suspicious 1394 access problem:

Oct 4 10:00:40 lightning ieee1394.agent[8630]: ... no drivers for
IEEE1394 product 0x/0x/0x
Oct 4 10:04:32 lightning kjournald starting. Commit interval 5 seconds
Oct 4 10:04:32 lightning EXT3 FS on sdc2, internal journal
Oct 4 10:04:32 lightning EXT3-fs: mounted filesystem with ordered data mode.
Oct 4 10:09:05 lightning attempt to access beyond end of device
Oct 4 10:09:05 lightning sdb1: rw=0, want=5621502224, limit=117210177
Oct 4 10:09:05 lightning attempt to access beyond end of device
Oct 4 10:09:05 lightning sdb1: rw=0, want=8263631504, limit=117210177
Oct 4 10:09:05 lightning attempt to access beyond end of device
Oct 4 10:09:05 lightning sdb1: rw=0, want=27135269176, limit=117210177
Oct 4 10:09:05 lightning attempt to access beyond end of device
Oct 4 10:09:05 lightning sdb1: rw=0, want=25260813976, limit=117210177
Oct 4 10:09:05 lightning attempt to access beyond end of device
Oct 4 10:09:05 lightning sdb1: rw=0, want=5621502224, limit=117210177
Oct 4 10:10:02 lightning cron[8737]: (root) CMD (test -x
/usr/sbin/run-crons && /usr/sbin/run-crons )
Oct 4 10:20:01 lightning cron[8762]: (root) CMD (test -x
/usr/sbin/run-crons && /usr/sbin/run-crons )
Oct 4 10:30:01 lightning cron[8800]: (root) CMD (test -x
/usr/sbin/run-crons && /usr/sbin/run-crons )
Oct 4 10:40:01 lightning cron[8847]: (root) CMD (test -x
/usr/sbin/run-crons && /usr/sbin/run-crons )


/dev/sdb1 in this case holds a 50GB ogg-based music library. It's been
streaming since I brought the kernel up.

1394 problems????

Thanks,
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/