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

[Esben Nielsen <nielsen.esben@googlemail.com>]

On Thu, 29 Jun 2006, Milan Svoboda wrote:

>> #
>> # 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...
>

"old"?

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

eepro100 seems to be SMP safe, so it shouldn't be there.
Have anyone else used eepro100 with preempt-realtime?

Anyway: I miss stack trace from the bugs. I don't know what to swich on at 
arm to get it to work - I think I remember getting stack traces years ago 
when I succeed in getting Linux 2.4 to run on a custom SA1110 based board. 
Try to swich on various debug like
  CONFIG_DEBUG_INFO
  CONFIG_UNWIND_INFO
  CONFIG_BUGVERBOSE
  CONFIG_FRAME_POINTER

Esben

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