On Fri, Jan 18, 2013 at 3:40 PM, Michael Haberler mai...@mah.priv.atwrote:
Am 18.01.2013 um 02:43 schrieb Yishin Li:
[ 360.305178] INFO: task rsyslogd:359 blocked for more than 120 seconds.
[ 360.312006] echo 0 /proc/sys/kernel/hung_task_timeout_secs
disables
It could be
further to the Xenomai Beaglebone kernel hang:
Gilles suggested to use the ipipe patch from xenomai master, and I gave that a
try; results so far look promising (xeno-regression-test still running). I have
no positive evidence this fixes the kernel hang though; I just havent seen one
yet.
to
On 20-1-2013 15:35, Michael Haberler wrote:
further to the Xenomai Beaglebone kernel hang:
Gilles suggested to use the ipipe patch from xenomai master, and I gave that
a try; results so far look promising (xeno-regression-test still running). I
have no positive evidence this fixes the
Am 20.01.2013 um 17:51 schrieb Bas Laarhoven:
On 20-1-2013 15:35, Michael Haberler wrote:
further to the Xenomai Beaglebone kernel hang:
..
Michael,
Regrettably, running your kernel Linux version 3.2.21-xenomai+ (mah@precise)
(gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1
Am 18.01.2013 um 02:43 schrieb Yishin Li:
I stand corrected
I now remember to have seen that on the console as I was about to shut
everything down and head out, but I didnt make the connection with a kernel hang
so yes, I have the issue too
[ 360.305178] INFO: task rsyslogd:359 blocked for
On Wed, Jan 16, 2013 at 9:15 AM, Michael Haberler mai...@mah.priv.atwrote:
I have done no further work on the Raspberry, I do not consider that
platform particularly useful to base work on.
Is there any point to looking at the Beagleboard any further?
Eric
Eric Keller wrote:
On Wed, Jan 16, 2013 at 9:15 AM, Michael Haberler mai...@mah.priv.atwrote:
I have done no further work on the Raspberry, I do not consider that
platform particularly useful to base work on.
Is there any point to looking at the Beagleboard any further?
The
On Fri, Jan 18, 2013 at 12:59 PM, Jon Elson el...@pico-systems.com wrote:
The BeagleBoard, specifically, is somewhat obsolete, but the BeagleBone
seems to
be the most well supported variant. It also has a LOT more GPIO brought
out.
To be precise, I have a BeagleboardXM, which seems to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/18/2013 1:20 PM, Eric Keller wrote:
On Fri, Jan 18, 2013 at 12:59 PM, Jon Elson
el...@pico-systems.com wrote:
The BeagleBoard, specifically, is somewhat obsolete, but the
BeagleBone seems to be the most well supported variant. It also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/18/2013 1:35 PM, Charles Steinkuehler wrote:
On 1/18/2013 1:20 PM, Eric Keller wrote:
On Fri, Jan 18, 2013 at 12:59 PM, Jon Elson
el...@pico-systems.com wrote:
The BeagleBoard, specifically, is somewhat obsolete, but the
BeagleBone
On 1/17/2013 2:59 AM, Bas Laarhoven wrote:
I think that running linuxcnc is mandatory for the lockup. After a dozen
runs, it looks like I can reproduce the lockup with 100% certainty
within one hour.
Using the JTAG interface to attach a debugger to the Bone, I've found
that once stalled the
On 17-1-2013 22:57, Kent A. Reed wrote:
On 1/17/2013 2:59 AM, Bas Laarhoven wrote:
I think that running linuxcnc is mandatory for the lockup. After a dozen
runs, it looks like I can reproduce the lockup with 100% certainty
within one hour.
Using the JTAG interface to attach a debugger to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/17/2013 6:02 PM, Bas Laarhoven wrote:
On 17-1-2013 22:57, Kent A. Reed wrote:
Finally, with respect to your next email message, how universal
is your statement that TI ...decided not to support the PRUSS
anymore. Does this refer to the TI
a short update:
linuxcnc development branches:
there are no more major breakage reports outstanding from several folks having
tried it, so the dust is settling.
There are a few things left to do in the code: since there are several RT
kernels supported in the configuration, that currently
On 1/16/2013 9:15 AM, Michael Haberler wrote:
a short update:
There's a lot of really good news here, folks. My thanks and a tip of
the hat to Michael, John, Charles, and everyone else who has
contributed. I doubt most of us can appreciate how much work has been
done to get us to this point.
On 16-1-2013 15:15, Michael Haberler wrote:
a short update:
linuxcnc development branches:
there are no more major breakage reports outstanding from several folks
having tried it, so the dust is settling.
There are a few things left to do in the code: since there are several RT
kernels
Hi folks,
On 01/16/2013 08:15 AM, Michael Haberler wrote:
x86 kernels:
from the 'it doesnt boot on my machine' perspective it seems we're
through the worst with this kernel:
http://static.mah.priv.at/public/xenomai-debs/linux-image-3.2.21-xenomai+_0.4_i386.deb
. However, John is working
17 matches
Mail list logo
