Anze Zagar wrote:
> On Tue, 2009-09-08 at 23:27 +0200, Jan Kiszka wrote:
>>> The last line dumps the following output in the dmesg (see attached
>>> dump.txt for the entire dmesg dump):
>>> rt_e1000_new 0000:0d:00.0: irq 52 for MSI/MSI-X
>>> rt_e1000_new 0000:0d:00.0: irq 52 for MSI/MSI-X
>>> irq event 52: bogus return value 2fb07cb0
>>> Pid: 0, comm: swapper Not tainted 2.6.30-xenomai-2.4.9 #3
>>> Call Trace:
>>>  [<ffffffff8026c690>] ? __report_bad_irq+0x30/0x7d
>>>  [<ffffffff8026c743>] ? note_interrupt+0x66/0x153
>>>  [<ffffffff8026d398>] ? handle_edge_irq+0xe4/0x114
>>>  [<ffffffff8020e315>] ? handle_irq+0x81/0x8a
>>>  [<ffffffff8020da0c>] ? do_IRQ+0x5a/0xa3
>>>  [<ffffffff8020d9b2>] ? do_IRQ+0x0/0xa3
>>>  [<ffffffff802702f4>] ? __ipipe_sync_stage+0x166/0x16c
>>>  [<ffffffff802702fa>] ? __xirq_end+0x0/0x6b
>>>  [<ffffffff8021faef>] ? __ipipe_handle_irq+0x18a/0x275
>>>  [<ffffffff8020c493>] ? common_interrupt+0x13/0x2c
>>>  [<ffffffff802120c9>] ? default_idle+0x8f/0x105
>>>  [<ffffffff80505b22>] ? __atomic_notifier_call_chain+0x46/0x69
>>>  [<ffffffff8020aadb>] ? cpu_idle+0x59/0x8b
>>> handlers:
>>> [<ffffffffa0360f33>] (e1000_intr_msi_test+0x0/0x71 [rt_e1000_new])
>>> rt_e1000_new 0000:0d:00.0: irq 52 for MSI/MSI-X
>>> e1000: rteth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full
>>> Duplex, Flow Control: RX/TX
>>>
>> Hmm, the msi-test IRQ seems to trigger this mess. Could you try if
>> disabling CONFIG_PCI_MSI changes the picture.
> 
> Yes, by disabling CONFIG_PCI_MSI this error no longer occurs. Can I
> expect any performance degradation due to that?
> 

Nothing relevant. But you may run earlier into IRQ conflicts with Linux
devices.

> 
>> Mathias, did you successfully tested or even used your driver with MSI
>> interrupts?
>>
>>>
>>> Note also that in order to build the experimental e1000 driver on this
>>> 64-bit system, I needed to patch the code a little:
>>> --- drivers/experimental/e1000/e1000_main.c 2009-08-29
>>> 17:41:04.000000000 +0200
>>> +++ drivers/experimental/e1000/e1000_main.c~        2009-02-28
>>> 14:34:03.000000000 +0100
>>> @@ -305,3 +305,3 @@
>>>  static int  e1000_intr(rtdm_irq_t *irq_handle);
>>> -static irqreturn_t e1000_intr_msi(rtdm_irq_t *irq_handle);
>>> +static int e1000_intr_msi(rtdm_irq_t *irq_handle);
>>>  static bool e1000_clean_tx_irq(struct e1000_adapter *adapter,
>> This doesn't apply to git head. What version are you using, what
>> patches?
> 
> I used the 0.9.11 release and the git head from about 10 days ago. Now,
> with the latest head, this has already been fixed.

Something must have went wrong on your side as the repos didn't change
in this area (see logs).

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to