Re: 2.6.14-rc4-rt1

[Mark Knecht]

On 10/11/05, Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
> On Tue, 2005-10-11 at 14:13 -0700, Mark Knecht wrote:
> > The machine had been essentially 'User space idle' for the previous
> > two hours. The screen saver had kicked in. Audio was running and the
> > machine was busy. I woke it up, gave xscreensaver my password, read
> > email, sent the previous mail, then picked up the telephone to make a
> > call. Not 2 seconds later the xruns occurred!
>
> So what does /proc/latency_trace report?
>
> Lee

Well, unfortunately it doesn't appear to report anythign helpful. The
maximum latency report did not change when the xrun occurred. This was
the last one reported and it happened long before the xrun:

(          ardour-8101 |#0): new 22 us maximum-latency critical section.
 => started at timestamp 1104476939: <do_IRQ+0x29/0x50>
 =>   ended at timestamp 1104476962: <do_IRQ+0x39/0x50>

Call Trace: <IRQ> <ffffffff8014c42c>{check_critical_timing+492}
       <ffffffff8014c64b>{sub_preempt_count_ti+75} <ffffffff80110159>{do_IRQ+57}
       <ffffffff8010e16c>{ret_from_intr+0}  <EOI>
<ffffffff8014c64b>{sub_preempt_count_ti+75}
       <ffffffff80249a37>{clear_page+7} <ffffffff8015b75a>{buffered_rmqueue+634}
       <ffffffff8015b963>{__alloc_pages+243} <ffffffff80167018>{do_no_page+264}
       <ffffffff801674ee>{__handle_mm_fault+414}
<ffffffff8014c64b>{sub_preempt_count_ti+75}
       <ffffffff80167c1b>{get_user_pages+971}
<ffffffff80167e00>{make_pages_present+176}
       <ffffffff8016aa0c>{do_mmap_pgoff+1756} <ffffffff801139d6>{sys_mmap+150}
       <ffffffff8010dbc6>{system_call+126}
 =>   dump-end timestamp 1104477102

mark@lightning ~ $

What next? IRQ-off possibly? I think it may be broken for AMD64 right now.

- 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/