lkml.org 
[lkml]   [2005]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    Subjectrealtime-preempt-2.6.12-final-V0.7.51-01 compile error and more problems
    Compilation stops at this point:

    make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
    CHK include/linux/compile.h
    CHK usr/initramfs_list
    CC net/ipv4/netfilter/ip_conntrack_proto_tcp.o
    net/ipv4/netfilter/ip_conntrack_proto_tcp.c: In function
    `tcp_print_conntrack':
    net/ipv4/netfilter/ip_conntrack_proto_tcp.c:333: error: `tcp_lock'
    undeclared (first use in this function)
    net/ipv4/netfilter/ip_conntrack_proto_tcp.c:333: error: (Each undeclared
    identifier is reported only once
    net/ipv4/netfilter/ip_conntrack_proto_tcp.c:333: error: for each
    function it appears in.)
    net/ipv4/netfilter/ip_conntrack_proto_tcp.c:333: warning: type defaults
    to `int' in declaration of `type name'
    etc. etc..

    Most likely it depends on the redefinition of DECLARE_RWLOCK in lockhelp.h


    More problems....

    Patch 7.50-48 has been the first rt kernel that compiled and booted
    cleanly on my system.

    I'm testing the rt kernels because I want to use jack as my system sound
    mixer/router
    and to record lp's with my ice1712-based sound card. I have no rt
    requrements, of course,
    but I want to get rid of xruns. Kernel 2.6.12 vanilla is quite good
    already (a big improvement
    over previous kernels) but still ...

    Patch 7.50-48 been running for two days now and seems pretty stable but:

    1) My logs are filled with Apic errors all like this

    Jul 5 04:30:01 linux kernel: APIC error on CPU0: 02(02)

    every 2 seconds, or minute, at random. I've never seen these messages
    before with vanilla kernels,
    so it's a bit weird.

    2) Whenever I play an mp3 or watch a movie (through jack) I get
    thousands of times these errors in the logs

    Jul 5 20:45:56 linux kernel: `IRQ 8'[828] is being piggy.
    need_resched=0, cpu=0
    Jul 5 20:45:56 linux kernel: Read missed before next interrupt
    Jul 5 20:45:56 linux kernel: wow! That was a 12 millisec bump
    Jul 5 20:45:56 linux kernel: bug in rtc_read(): called in state S_IDLE!
    Jul 5 20:45:56 linux kernel: `IRQ 8'[828] is being piggy.
    need_resched=0, cpu=0
    Jul 5 20:45:56 linux kernel: Read missed before next interrupt
    Jul 5 20:45:56 linux kernel: wow! That was a 3 millisec bump
    Jul 5 20:45:56 linux kernel: bug in rtc_read(): called in state S_IDLE!

    This is a known issue, RTC interrupts are missed. I have noticed it
    many times when ntp is
    running. It stops working after a few minutes of playing when the the
    error exceeds 500 PPM.
    But I thought that ntp compared external reference clocks to the system
    timer, so the system
    was missing int 0, not int 8. My mobo has a crappy timer anyway. I had
    to reduce the tick to 9934
    in order to allow ntp to run.

    3) I had to disable polling of the cpu temperature by kacpid because
    whenever it did the sound
    stopped for 1-3 seconds. The polling took longer and longer after a few
    hours of uptime.
    The nice thing is, it caused no xruns. Kernel 2.6.12 vanilla has the
    same problem, though.

    4) Xruns occur every 10-60 minutes even when the system is practically
    idle (no playback
    or recording). When copying large files (between sata disks on two
    sil3112 controllers)
    xruns frequency is much higher. When sound is used xruns occur every 2
    or 20 minutes.


    This is a nForce2-mobo (Abit NF7-S V 2.0), Athlon 2800, 1 GB Ram,
    Terratec DMX6Fire,
    nVidia 4200 video card, 2 sil3112 sata controllers with 3 disks,etc.
    SuSE 9.1 with KDE 3.4 and
    uptodate jack, xmms, mplayer, sound libraries and recording apps.

    If more details are needed or I can perform some tests, feel free to ask.

    Cheers,

    Carlo Scarfoglio



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

    \
     
     \ /
      Last update: 2005-07-06 01:31    [W:0.049 / U:90.572 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site