All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Koehrer" <mathias_koehrer@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Xenomai and MSI enabled crashes kernel
Date: Thu, 26 Apr 2007 14:04:12 +0200 (CEST)	[thread overview]
Message-ID: <4850965.1177589052502.JavaMail.ngmail@domain.hid> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4339 bytes --]

Hi everybody,

I am using kernel 2.6.20.4 and Xenomai 2.3.1 on a SMP enabled dual core Pentium 4.
Everything works fine when I do not enable the CONFIG_PCI_MSI (Messages signaled interrupts) for
PCI Express.
As I am always short with interrupts I want to use MSI for the PCIe base
I/O devices like Ethernet.

When I run the same kernel without any Xenomai patch, it works really fine.
My onboard PCIe e1000 network adapter will be loaded fine and gets the (cool) interrupt number 219!
Perfect!

When I use the Adeos patch from Xenomai 2.3.1 on this kernel the modprobe of the e1000 driver
leads to a kernel crash.
At this stage no real time application is running.
Using a serial console, I was able to log the kernel dump.
Here it is:

BUG: unable to handle
 kernel NULL pointer dereference at virtual address 00000000
 printing eip:
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in: e1000
CPU:    0
EIP:    0060:[<00000000>]    Not tainted VLI
EFLAGS: 00010086   (2.6.20.4 #7)
EIP is at _stext+0x3feffc70/0x14
eax: c0112244   ebx: 00000006   ecx: c011434d   edx: c168c000
esi: 00000006   edi: 00000046   ebp: ffffffff   esp: c168de20
ds: 007b   es: 007b   ss: 0068
Process ifconfig (pid: 1231, ti=c168c000 task=c1692a90 task.ti=c168c000)
Stack: c03e5680 000000db 00000000 c03d9100 c010ef83 00006d80 00000001 00000060
       e099a210 00000286 ffffff24 df77b5c8 00000000 0000000f 00000001 c0103439
       df77b5c8 e099a0ff e09c0000 00000000 0000000f 00000001 80080740 dfd2007b
Call Trace:
 [<c010ef83>] __ipipe_handle_irq+0x1b9/0x20b
 [<e099a210>] e1000_set_multi+0x111/0x189 [e1000]
 [<c0103439>] common_interrupt+0x21/0x38
 [<e099a0ff>] e1000_set_multi+0x0/0x189 [e1000]
 [<e099a210>] e1000_set_multi+0x111/0x189 [e1000]
 [<c02dcf81>] __dev_mc_upload+0x1d/0x1e
 [<c02dd0a1>] dev_mc_upload+0x24/0x37
 [<c02db5ac>] dev_open+0x44/0x62
 [<c02da079>] dev_change_flags+0x47/0xe4
 [<c030d192>] devinet_ioctl+0x252/0x56f
 [<c02db18a>] dev_ifsioc+0x113/0x38d
 [<c02d15a4>] sock_ioctl+0x0/0x1ad
 [<c02d1732>] sock_ioctl+0x18e/0x1ad
 [<c02d15a4>] sock_ioctl+0x0/0x1ad
 [<c015e18f>] do_ioctl+0x1f/0x62
 [<c015e416>] vfs_ioctl+0x244/0x256
 [<c015e45b>] sys_ioctl+0x33/0x4c
 [<c01029f3>] sysenter_past_esp+0x6c/0x70
 =======================
Code:  Bad EIP value.
EIP: [<00000000>] _stext+0x3feffc70/0x14 SS:ESP 0068:c168de20
 <0>Kernel panic - not syncing: Fatal exception in interrupt
 BUG: at arch/i386/kernel/smp.c:565 smp_call_function()
 [<c010b903>] smp_call_function+0x66/0x10a
 [<c0118e12>] printk+0x62/0xd5
 [<c010b9c2>] smp_send_stop+0x1b/0x2b
 [<c01183ad>] panic+0x4d/0xe4
 [<c0103f71>] die+0x1f2/0x226
 [<c011167c>] do_page_fault+0x447/0x517
 [<c010f61d>] __ipipe_handle_exception+0xce/0x158
 [<c010bb1e>] smp_call_function_interrupt+0x31/0x4c
 [<c033336d>] error_code+0x81/0x90
 [<c011434d>] try_to_wake_up+0x33c/0x346
 [<c0112244>] __activate_task+0x1c/0x29
 [<c010ef83>] __ipipe_handle_irq+0x1b9/0x20b
 [<e099a210>] e1000_set_multi+0x111/0x189 [e1000]
 [<c0103439>] common_interrupt+0x21/0x38
 [<e099a0ff>] e1000_set_multi+0x0/0x189 [e1000]
 [<e099a210>] e1000_set_multi+0x111/0x189 [e1000]
 [<c02dcf81>] __dev_mc_upload+0x1d/0x1e
 [<c02dd0a1>] dev_mc_upload+0x24/0x37
 [<c02db5ac>] dev_open+0x44/0x62
 [<c02da079>] dev_change_flags+0x47/0xe4
 [<c030d192>] devinet_ioctl+0x252/0x56f
 [<c02db18a>] dev_ifsioc+0x113/0x38d
 [<c02d15a4>] sock_ioctl+0x0/0x1ad
 [<c02d1732>] sock_ioctl+0x18e/0x1ad
 [<c02d15a4>] sock_ioctl+0x0/0x1ad
 [<c015e18f>] do_ioctl+0x1f/0x62
 [<c015e416>] vfs_ioctl+0x244/0x256
 [<c015e45b>] sys_ioctl+0x33/0x4c
 [<c01029f3>] sysenter_past_esp+0x6c/0x70
 =======================

I have attached my kernel config to this mail.
Any idea on this? Is there anybody out there that has MSI running succesfully with the Xenomai adeos patch?

Thanks for any feedback on that issue!

Regards

Mathias


-- 
Mathias Koehrer
mathias_koehrer@domain.hid


50€ AMAZON-Einkaufsgutschein bei Bestellung von Arcor-DSL:
Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT JETZT bei Arcor: günstig
und schnell mit DSL - das All-Inclusive-Paket für clevere Doppel-Sparer,
nur  39,85 €  inkl. DSL- und ISDN-Grundgebühr!
http://www.arcor.de/rd/emf-dsl-2

[-- Attachment #2: config.gz --]
[-- Type: application/octetstream, Size: 8598 bytes --]

             reply	other threads:[~2007-04-26 12:04 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 12:04 M. Koehrer [this message]
2007-04-27 11:48 ` [Xenomai-help] Xenomai and MSI enabled crashes kernel Jan Kiszka
2007-04-27 13:14   ` Philippe Gerum
2007-04-27 13:22     ` Jan Kiszka
2007-04-27 13:31       ` M. Koehrer
2007-04-27 13:47         ` Jan Kiszka
2007-04-27 14:08           ` M. Koehrer
2007-04-27 14:19             ` Philippe Gerum
2007-04-27 14:28               ` M. Koehrer
2007-04-27 14:40                 ` Philippe Gerum
2007-04-27 14:56                 ` Philippe Gerum
2007-04-27 15:05                   ` Philippe Gerum
2007-04-27 15:10                     ` M. Koehrer
2007-04-27 15:36                       ` Philippe Gerum
2007-04-27 15:41                         ` M. Koehrer
2007-04-30  9:05                           ` Jan Kiszka
2007-04-30 10:11                             ` M. Koehrer
2007-04-30 11:27                               ` Jan Kiszka
2007-04-30 12:51                                 ` M. Koehrer
2007-04-30 15:10                                   ` Jan Kiszka
2007-04-27 20:39                       ` Philippe Gerum
2007-04-30 15:39                         ` Philippe Gerum
2007-05-02  7:05                           ` M. Koehrer
2007-05-02  8:39                             ` Jan Kiszka
2007-05-02  9:14                               ` M. Koehrer
2007-05-02  9:39                                 ` Jan Kiszka
2007-05-02 12:42                                 ` Philippe Gerum
2007-05-02 13:44                                   ` M. Koehrer
2007-05-02 13:49                                     ` Jan Kiszka
2007-04-27 14:31             ` Jan Kiszka
2007-04-27 14:52               ` M. Koehrer
2007-04-28 12:54 ` Bernhard Walle
  -- strict thread matches above, loose matches on Subject: below --
2007-05-02 12:57 M. Koehrer
2007-05-02 13:23 ` Jan Kiszka
2007-05-02 14:47 ` Philippe Gerum
2007-05-03  7:06   ` M. Koehrer
2007-05-03  8:29     ` Philippe Gerum
2007-05-04  7:45 M. Koehrer
2007-05-04  7:59 ` Jan Kiszka
2007-05-04  8:20   ` M. Koehrer
2007-05-04 12:20     ` Philippe Gerum
2007-05-04 12:46       ` M. Koehrer
2007-05-04 13:03         ` Philippe Gerum
2007-05-05 17:21       ` Philippe Gerum
2007-05-08 11:53         ` M. Koehrer
2007-05-08 12:28           ` Philippe Gerum
2007-05-08 12:38             ` M. Koehrer
2007-05-08 13:28               ` Philippe Gerum
2007-05-08 13:37               ` Philippe Gerum
2007-05-08 14:35                 ` M. Koehrer
2007-05-09  8:00                   ` Philippe Gerum
2007-05-07  7:11 M. Koehrer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4850965.1177589052502.JavaMail.ngmail@domain.hid \
    --to=mathias_koehrer@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.