Daniele Nicolodi wrote: > On 01/06/10 16:50, Jan Kiszka wrote: >> Daniele Nicolodi wrote: >>> On 01/06/10 13:23, Jan Kiszka wrote: >>>> Daniele Nicolodi wrote: >>>>> Hello. >>>>> >>>>> In the process of upgrading my data acquisition system from Xenomai >>>>> 2.5.0 to Xenomai 2.5.2, I also upgraded the kernel from the 2.6.30 >>>>> release to 2.6.32.14. >>>> Latest Xenomai is 2.5.3, latest 2.6.32 patch is >>>> adeos-ipipe-2.6.32.13-x86-2.6-04.patch [1]. Make sure you have both. >>> This adeos patch does not apply cleanly to 2.6.32.14 kernel sources. >>> Looks like a hunk in include/linux/modules.h has been applied upstream. >>> However this was easy to merge. >>> >>> Using the latest xenomai and adeos patch however results again in a >>> kernel that does not boot on my hardware. This problem is present since >>> the first time I have been trying to use xenomai on this box, as I wrote >>> in an email to the list on the 17th February early this year, it is thus >>> not a recent regression. >>> >>> Further suggestions? >> Please send an updated .config file. > > It is attached.
OK, will try to build a test kernel from it later. Does you system boot up as soon as you disable CONFIG_IPIPE (and Xenomai, of course)? CONFIG_IPIPE_DEBUG* has no influence either? > >> Note that the configs you sent in Feb. were broken /wrt power management >> setting (there should have been big fat warnings signs visible in the >> Xenomai sub-menu). I don't think this should cause the lock-ups, but you >> won't like the latency results (+ timing can be corrupted for the whole >> system). > > I did notice that, and I corrected it. This new configuration I'm using > should be a valid one. > > Thanks for your help, > Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux _______________________________________________ Xenomai-help mailing list Xenomai-help@gna.org https://mail.gna.org/listinfo/xenomai-help
