On Tue, 2006-02-21 at 19:53 +0100, Michal Piotrowski wrote:
> On 21/02/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> [snip]
> > Here is config http://www.stardust.webpages.pl/files/rt/2.6.15-rt17/rt-config
> > Here is dmesg http://www.stardust.webpages.pl/files/rt/2.6.15-rt17/rt-dmesg
> 
> Here is updated config
> http://www.stardust.webpages.pl/files/rt/2.6.15-rt17/rt-config2
> Here is updated dmesg
> http://www.stardust.webpages.pl/files/rt/2.6.15-rt17/rt-dmesg2
> 
> BTW. thanks for fixing CONFIG_DEBUG_HIGHMEM=y

The stack maximum messages are harmless. They just report a new
watermark high quite verbose. You can turn them off by disabling
DEBUG_STACKOVERFLOW.

skge eth0: Link is up at 100 Mbps, full duplex, flow control tx and rx
WARNING: softirq-tasklet/8 changed soft IRQ-flags.
 [<c0103b33>] dump_stack+0x1b/0x1f (20)
 [<c0134035>] illegal_API_call+0x41/0x46 (20)
 [<c0134084>] local_irq_disable+0x1d/0x1f (8)
 [<f8839bf3>] skge_extirq+0x117/0x138 [skge] (32)
 [<c0120a73>] __tasklet_action+0xb8/0xfd (28)
 [<c0120afc>] tasklet_action+0x44/0x4e (28)
 [<c0120ce8>] ksoftirqd+0x10f/0x19e (32)
 [<c012dfa6>] kthread+0x7b/0xa9 (36)
 [<c01010dd>] kernel_thread_helper+0x5/0xb (1037991964)

This one is interesting. It brought my attention to that piece of code
which is a long standing problem on one of my boxen anyway. Patch
attached.

	tglx