All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Mayer <h.mayer@domain.hid>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Scheduling while atomic
Date: Wed, 18 Jan 2006 23:13:36 +0100	[thread overview]
Message-ID: <43CEBD90.7080603@domain.hid> (raw)
In-Reply-To: <fd6a47a90601181334y14b06d6an@domain.hid>

Jeroen Van den Keybus wrote:
> - Could you replace MAXLONG on line 119 with TM_INFINITE and rerun the 
> sem test (to avoid printf'ing) You can terminate with Ctrl+C.
> - Could you try to run with tmax somewhat lower (to increase the load): 
> e.g. ./sem 5.0e6 or so. Be careful not to starve Linux. I think 1.0e5 
> will be too low.
>  
> Crashes with me happen within the first 10 secs with 1.0e7

On Xeno2.0, kernel 2.6.13.4:

# ./sem 1.0e5
Running for 2.15 seconds.
L119: Operation not permitted.

Kernel.log:
Unable to handle kernel NULL pointer dereference at virtual address 00000114
[freeze]

# ./sem 1.0e4
Running for 2.15 seconds.

Kernel.log:
(sorry no serial console available yet)
...default_idle
...ipipe_supend_domain
...default_idle
...cpu_idle
...start_kernel
...unknown_bootoption
Kernel panic

# ./mutex 1.0e5
ALERT: No lock! (lockcnt=0) Offending task: task0
ALERT: No lock! (lockcnt=0) Offending task: task0
ALERT: No lock! (lockcnt=0) Offending task: task0
[...]
[freeze]

kernel.log:
[off-screen]
...panic
...do_exit
...printk
...die
...__ipipe_sync_stage
...do_page_fault
...__do_softirw
...irq_exit
...do_IRQ
...restore_raw
...__ipipe_handle_exception
...error_code
...__ipipe_sync_stage
...default_idle
...ipipe_supend_domain
...default_idle
...cpu_idle
...start_kernel
...unknown_bootoption
Kernel panic

Best regards,
Hannes.


  parent reply	other threads:[~2006-01-18 22:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 20:04 [Xenomai-core] Scheduling while atomic Jeroen Van den Keybus
2006-01-18 20:20 ` Hannes Mayer
2006-01-18 21:12   ` Jan Kiszka
2006-01-18 21:26     ` Hannes Mayer
     [not found]       ` <fd6a47a90601181334y14b06d6an@domain.hid>
2006-01-18 22:13         ` Hannes Mayer [this message]
2006-01-18 22:26           ` Jeroen Van den Keybus
2006-01-18 22:17         ` Jeroen Van den Keybus
  -- strict thread matches above, loose matches on Subject: below --
2006-01-17 23:59 Jeroen Van den Keybus
2006-01-18  9:18 ` Gilles Chanteperdrix
2006-01-18 20:06 ` Jan Kiszka
2006-01-18 20:14   ` Jan Kiszka
2006-01-18 20:25     ` Jan Kiszka
2006-01-29 23:28     ` Philippe Gerum
2006-01-18 20:21   ` Gilles Chanteperdrix
2006-01-18 20:26   ` Gilles Chanteperdrix
2006-01-18 20:30     ` Jan Kiszka
2006-01-18 20:46       ` Jan Kiszka
     [not found]       ` <fd6a47a90601181236u5a482ba5q@domain.hid>
     [not found]         ` <43CEA7AC.9080300@domain.hid>
     [not found]           ` <fd6a47a90601181254s11edbb28l@domain.hid>
     [not found]             ` <43CEADBE.4040802@domain.hid>
2006-01-18 21:11               ` Jeroen Van den Keybus
2006-01-18 21:16                 ` Jan Kiszka
2006-01-18 21:39                   ` Jeroen Van den Keybus
2006-01-18 23:49                     ` Jeroen Van den Keybus
2006-01-18 23:51                       ` Jeroen Van den Keybus
2006-01-19 10:10                         ` Jeroen Van den Keybus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43CEBD90.7080603@domain.hid \
    --to=h.mayer@domain.hid \
    --cc=jeroen.vandenkeybus@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.