On Wed, Nov 04, 2009 at 11:16:21PM +0100, Philippe Gerum wrote:
Core 0 waits for core 1 to acknowledge the critical IPI, but that
lazybones prefers to sleep. Likely because it did not receive the IPI in
question, actually (it should raise a bit in __ipipe_cpu_sync_map, see
On Fri, 2009-11-06 at 09:10 +0100, Richard Cochran wrote:
On Wed, Nov 04, 2009 at 11:16:21PM +0100, Philippe Gerum wrote:
Core 0 waits for core 1 to acknowledge the critical IPI, but that
lazybones prefers to sleep. Likely because it did not receive the IPI in
question, actually (it should
On Fri, Nov 06, 2009 at 09:26:58AM +0100, Philippe Gerum wrote:
Ouch. I just can't believe this went unnoticed for that long... Well, no
wonder why then, the critical IPI never gets registered, so never
detected by the pipeline core in __ipipe_grab_irq. Thanks for the heads
up.
This may
On Fri, 2009-11-06 at 10:20 +0100, Richard Cochran wrote:
On Fri, Nov 06, 2009 at 09:26:58AM +0100, Philippe Gerum wrote:
Ouch. I just can't believe this went unnoticed for that long... Well, no
wonder why then, the critical IPI never gets registered, so never
detected by the pipeline core
On Wed, 2009-11-04 at 06:56 +0100, Richard Cochran wrote:
On Tue, Nov 03, 2009 at 03:44:24PM +0100, Philippe Gerum wrote:
On Tue, 2009-11-03 at 14:34 +0100, Richard Cochran wrote:
If I enable ipipe only, I can still boot SMP. If Xenomai is enabled,
then the machine freezes as soon as
On Wed, Nov 04, 2009 at 10:54:24AM +0100, Philippe Gerum wrote:
The issue is more likely in the interrupt pipeline. When Xenomai is
compiled as modules, does the system lock up when loading the nucleus,
Yes.
I looked at this problem using my shiny new BDI3000.
mpcl8572select 0
Target
On Wed, 2009-11-04 at 12:15 +0100, Richard Cochran wrote:
On Wed, Nov 04, 2009 at 10:54:24AM +0100, Philippe Gerum wrote:
The issue is more likely in the interrupt pipeline. When Xenomai is
compiled as modules, does the system lock up when loading the nucleus,
Yes.
I looked at this
On Wed, Nov 04, 2009 at 12:26:45PM +0100, Philippe Gerum wrote:
Ok, this is a porting issue. The critical IPI (IPIPE_CRITICAL_IPI) does
not seem to be properly handled on this platform.
I'll try and pull this apart some more...
I was able to get SMP to boot, by accident.
Using the
On Wed, Nov 04, 2009 at 03:08:32PM +0100, Richard Cochran wrote:
On Wed, Nov 04, 2009 at 12:26:45PM +0100, Philippe Gerum wrote:
Ok, this is a porting issue. The critical IPI (IPIPE_CRITICAL_IPI) does
not seem to be properly handled on this platform.
Okay, after playing with the BDI3000
On Wed, 2009-11-04 at 19:19 +0100, Richard Cochran wrote:
On Wed, Nov 04, 2009 at 03:08:32PM +0100, Richard Cochran wrote:
On Wed, Nov 04, 2009 at 12:26:45PM +0100, Philippe Gerum wrote:
Ok, this is a porting issue. The critical IPI (IPIPE_CRITICAL_IPI) does
not seem to be properly
I have compiled and run ipipe-2.6.30.3-powerpc-2.7-02 and Xenomai
v2.4.9.1 (well, actually c4c3c82791951df998ac4dc463f79a76884577b6), on
two similar Freescale boards, the MPC8572DS and the P2020DS. Both are
dual core, and both run fine using vanilla Linux 2.6.30 with SMP.
If I enable ipipe only,
On Tue, 2009-11-03 at 14:34 +0100, Richard Cochran wrote:
I have compiled and run ipipe-2.6.30.3-powerpc-2.7-02 and Xenomai
v2.4.9.1 (well, actually c4c3c82791951df998ac4dc463f79a76884577b6), on
two similar Freescale boards, the MPC8572DS and the P2020DS. Both are
dual core, and both run fine
On Tue, Nov 03, 2009 at 03:44:24PM +0100, Philippe Gerum wrote:
On Tue, 2009-11-03 at 14:34 +0100, Richard Cochran wrote:
If I enable ipipe only, I can still boot SMP. If Xenomai is enabled,
then the machine freezes as soon as Xenomai is started. (As a module,
Xenomai locks the machine when
13 matches
Mail list logo
