Jan Kiszka wrote: > Philippe Gerum wrote: >> [EMAIL PROTECTED] wrote: >>>>> Found it. Could you give this patch a try and report the result? >>>>> >>>>> http://permalink.gmane.org/gmane.linux.kernel/682362 >>> Applied and tested, no luck... >>> >>> I-pipe: Detected illicit call from domain 'RTAI' >>> into a service reserved for domain 'Linux' and below. >>> Pid: 0, comm: swapper Not tainted 2.6.26.2-FuCS #1 >>> [<c0156866>] ipipe_check_context+0xd6/0xf0 >>> e1000: rteth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex >>> [<c03e206e>] _spin_lock_irqsave+0x1e/0x80 >>> [<c024a7a6>] pci_bus_read_config_word+0x36/0x80 >>> [<c0254156>] __msi_set_enable+0x46/0x80 >>> [<c01176f3>] ? mcount+0x1f/0x23 >>> [<c0254498>] msi_set_mask_bits+0xd8/0xe0 >>> [<c01176f3>] ? mcount+0x1f/0x23 >>> [<c0254737>] unmask_msi_irq+0x17/0x30 >>> [<c01542da>] default_enable+0x1a/0x30 >>> [<f892f1ee>] rt_enable_irq+0xe/0x10 [rtai_hal] >>> [<f8dabd99>] ? xnintr_irq_handler+0x149/0x1f0 [rtai_rtdm] >>> [<f893164b>] rtai_hirq_dispatcher+0xfb/0x430 [rtai_hal] >>> [<c01021c5>] default_idle+0x45/0x60 >>> [<c0102180>] default_idle+0x0/0x60 >>> [<c0103cc7>] common_interrupt+0x2f/0x54 >>> [<c0102180>] default_idle+0x0/0x60 >>> [<c01500d8>] cgroup_file_write+0x118/0x140 >>> [<c01021c5>] default_idle+0x45/0x60 >>> [<c0101b76>] cpu_idle+0x86/0x140 >>> [<c03dd7fd>] start_secondary+0x16d/0x210 >>> [<c03d3a88>] initialize_secondary+0x8/0x20 >>> ======================= >>> I-pipe tracer log (100 points): >>> | +*func 0 ipipe_trace_panic_freeze+0x9 >> >> I see no option aside of ironing the inner code that reads/writes the PCI >> config, so here is an ugly yet possible solution for x86, that might work >> (totally untested): > > Very ugly. There is potentially some heavy code under this lock.
No, actually, the worst-case code you could have is as usual x86-based, i.e. BIOS calls for raw pci_read/writes. Since we cannot cache PCI config values, there is no escape. > Wouldn't it be better to switch to soft-disabling directly, also given > that not all devices will support that method anyway? > Then you would have to teach all your clients on top of the I-pipe about this. Basically, the pipeline does not care that much here because soft disabling is already in place: this is a client issue. > Jan > -- Philippe. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
