Le mercredi 04 janvier 2006 à 18:19 +0100, Gilles Chanteperdrix a
écrit :
> Stelian Pop wrote:
> > Before hanging, sometimes it just prints:
> >Unable to handle kernel NULL pointer dereference at virtual address
> 004d
> >
> > Sometimes the oops is more complete (note that sometimes i
Stelian Pop wrote:
> Before hanging, sometimes it just prints:
> Unable to handle kernel NULL pointer dereference at virtual address
> 004d
>
> Sometimes the oops is more complete (note that sometimes it also hangs in
> the middle of
> the printout):
> Unable to handle kern
Le mercredi 04 janvier 2006 à 17:49 +0100, Jan Kiszka a écrit :
> Stelian Pop wrote:
> > Hi,
> >
> 88> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> > klatency module and I encounter some problems.
> >
> > This is on my in-progress ARM Xenomai port. User space latency an
Stelian Pop wrote:
> Hi,
>
> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> klatency module and I encounter some problems.
>
> This is on my in-progress ARM Xenomai port. User space latency and old
> klatency work great (my board has some hardware latency problems though
Hi,
I'm trying to use the xeno_timerbench as a replacement to the old 2.0
klatency module and I encounter some problems.
This is on my in-progress ARM Xenomai port. User space latency and old
klatency work great (my board has some hardware latency problems though
- latencies can be as high as 500
Le mercredi 04 janvier 2006 à 18:19 +0100, Gilles Chanteperdrix a
écrit :
> Stelian Pop wrote:
> > Before hanging, sometimes it just prints:
> >Unable to handle kernel NULL pointer dereference at virtual address
> 004d
> >
> > Sometimes the oops is more complete (note that sometimes i
Stelian Pop wrote:
> Before hanging, sometimes it just prints:
> Unable to handle kernel NULL pointer dereference at virtual address
> 004d
>
> Sometimes the oops is more complete (note that sometimes it also hangs in
> the middle of
> the printout):
> Unable to handle kern
Le mercredi 04 janvier 2006 à 17:49 +0100, Jan Kiszka a écrit :
> Stelian Pop wrote:
> > Hi,
> >
> 88> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> > klatency module and I encounter some problems.
> >
> > This is on my in-progress ARM Xenomai port. User space latency an
Stelian Pop wrote:
> Hi,
>
> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> klatency module and I encounter some problems.
>
> This is on my in-progress ARM Xenomai port. User space latency and old
> klatency work great (my board has some hardware latency problems though
Hi,
I'm trying to use the xeno_timerbench as a replacement to the old 2.0
klatency module and I encounter some problems.
This is on my in-progress ARM Xenomai port. User space latency and old
klatency work great (my board has some hardware latency problems though
- latencies can be as high as 500
10 matches
Mail list logo
