On Tue, 2006-01-24 at 14:33 +0100, Michal Piotrowski wrote:
> Great thanks!
>
> Now 2.6.15-rt14 works fine (after disabling CONFIG_DEBUG_STACKOVERFLOW).
>
> I have noticed only one warning
> WARNING: softirq-tasklet/8 changed soft IRQ-flags.
> [<c0103b1b>] dump_stack+0x1b/0x1f (20)
> [<c0135218>] illegal_API_call+0x41/0x46 (20)
> [<c0135267>] local_irq_disable+0x1d/0x1f (8)
> [<f886dbd5>] skge_extirq+0x117/0x138 [skge] (32)
> [<c01202d5>] tasklet_action+0x8a/0xf1 (24)
> [<c01205c1>] ksoftirqd+0x10f/0x19e (32)
> [<c012d7ca>] kthread+0x7b/0xa9 (36)
> [<c01010c5>] kernel_thread_helper+0x5/0xb (1047875612)
> ---------------------------
> | preempt count: 00000000 ]
> | 0-level deep critical section nesting:
> ----------------------------------------
>
> ------------------------------
> | showing all locks held by: | (softirq-tasklet/8 [c18a97d0, 98]):
> ------------------------------
Yeah, I've seen this too. Since it's just a warning, it's been push to
the back of the TODO list.
>
> And problems while loading ipv6 module
> Running ntpdate to synchronize clockCould not allocate 4 bytes percpu data
> modprobe: FATAL: Error inserting ipv6
> (/lib/modules/2.6.15-rt14/kernel/net/ipv6/ipv6.ko): Cannot allocate
> memory
>
> Could not allocate 4 bytes percpu data
> modprobe: FATAL: Error inserting ipv6
> (/lib/modules/2.6.15-rt14/kernel/net/ipv6/ipv6.ko): Cannot allocate
> memory
Is this new with the -rt14? or has this happened before. If it has
happened before, then could you tell us when it started.
Thanks,
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
