On 3/6/2007, "Guennadi Liakhovetski" <[EMAIL PROTECTED]> wrote:
>On Tue, 6 Mar 2007, Guennadi Liakhovetski wrote:
>
>> Ok, just tried 20-rt8. Of 3 problems described earlier the first two:
>> non-working syslog(2) and irdadump showing packets only in one direction
>> are now gone. Whereas the thi
(I think, we can remove Thomas and linux-rt-users from CC: now that it's
clearly not a -rt bug, unless they express their interest in this
thread:-))
On Tue, 6 Mar 2007, Samuel Ortiz wrote:
On 3/6/2007, "Guennadi Liakhovetski" <[EMAIL PROTECTED]> wrote:
On Tue, 6 Mar 2007, Guennadi Liakhove
On Tue, 6 Mar 2007, Guennadi Liakhovetski wrote:
Ok, just tried 20-rt8. Of 3 problems described earlier the first two:
non-working syslog(2) and irdadump showing packets only in one direction
are now gone. Whereas the third one:
[...]
is still there.
Ok, I also managed to reproduce this wi
Ok, just tried 20-rt8. Of 3 problems described earlier the first two:
non-working syslog(2) and irdadump showing packets only in one direction
are now gone. Whereas the third one:
On Fri, 2 Mar 2007, Guennadi Liakhovetski wrote:
>> 2. sometimes, especially after a connection break down, the con
Added Thomas to CC: as it is a PXA270 CPU and it looks like the kernel has
some other peculiarities that the no-rt one doesn't have. In principle,
the kernel runs fine, many various hardware drivers, realtime threads.
But, I just noticed, klogd doesn't get woken up from printk(). I.e.,
syslog(2
Hi
Ok, the kernel is a bit old, but maybe someone has an idea... Running ppp
over irnet, one side with the above kernel, another is a verified
reference system. The following strange fenomena are observed:
1. irdadump on the 2.6.18-rt6 side shows only incoming packets
2. sometimes, especially
