Re: [BUG] Linux-2.6.17-rt3 on arm ixdp465

[Milan Svoboda <msvoboda@ra.rockwell.com>]

> # 
> # Tulip family network device support 
> # 
> # CONFIG_NET_TULIP is not set 
> # CONFIG_HP100 is not set 
> CONFIG_NET_PCI=y 
> # CONFIG_PCNET32 is not set 
> # CONFIG_AMD8111_ETH is not set 
> # CONFIG_ADAPTEC_STARFIRE is not set 
> # CONFIG_B44 is not set 
> # CONFIG_FORCEDETH is not set 
> # CONFIG_DGRS is not set 
> CONFIG_EEPRO100=y 
> # CONFIG_E100 is not set 
> # CONFIG_FEALNX is not set 

I use "old" eepro100 network device driver...

Thank you for your answer, I look at it too...

Milan






Esben Nielsen <nielsen.esben@googlemail.com>
06/28/2006 07:02 PM

 
        To:     Milan Svoboda <msvoboda@ra.rockwell.com>
        cc:     linux-kernel@vger.kernel.org
        Subject:        Re: [BUG] Linux-2.6.17-rt3 on arm ixdp465


On Wed, 28 Jun 2006, Milan Svoboda wrote:

> Hello,
>
> I tried this kernel on arm ixdp465, it works well, but I got many
> of these messages:
>
> BUG: scheduling with irqs disabled: IRQ 25/0x00000000/683
> caller is rt_lock_slowlock+0xd8/0x1c8
> BUG: scheduling with irqs disabled: IRQ 25/0x00000000/683
> caller is rt_lock_slowlock+0xd8/0x1c8
> BUG: scheduling with irqs disabled: IRQ 25/0x00000000/683
> caller is rt_lock_slowlock+0xd8/0x1c8
> BUG: scheduling with irqs disabled: IRQ 25/0x00000000/683
> caller is rt_lock_slowlock+0xd8/0x1c8
> BUG: scheduling with irqs disabled: IRQ 25/0x00000000/683
> caller is rt_lock_slowlock+0xd8/0x1c8
>
> # cat /proc/interrupts
>           CPU0
> 5:      29620   IXP4xx Timer Tick
> 15:        876   serial
> 25:       3813   eth0
> Err:          0
>

Looks like a bug in your ethernet driver, which is?
It could be that that driver is not SMP compliant and uses irq 
disable/enable
as locking method instead of a spinlock.

Esben

> PS: Please CC me, I'm not subscribed...
>
> Best Regards,
> Milan Svoboda
>
>
>



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