All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Roman Pisl <rpisl@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Freeze on SMP x86-64
Date: Sat, 03 Oct 2009 18:01:58 +0200	[thread overview]
Message-ID: <4AC77576.9070700@domain.hid> (raw)
In-Reply-To: <4AC5FEAD.7000608@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]

Roman Pisl wrote:
> On 2.10.2009 14:39, Gilles Chanteperdrix wrote:
>> Roman Pisl wrote:
>>> Hello,
>>> I just tried x86-64 SMP Linux/Xenomai on my workstation (Intel Core2
>>> Quad) but it freezes immediately after latency test or clocktest is
>>> started. It freezes even during the boot, when Xenomai debbuging is
>>> enabled.
>>>
>>> The same kernel binary runs seamlessly in KVM on the same machine.
>>>
>>> When I completely disable ACPI, the kernel recognizes only one CPU and
>>> the latency test works.
>>>
>>> The same configuration but for 32bit x86 also runs without freeze.
>>>
>>> Do you have any ideas?
>>
>> Yes. As we repeated many times.
>> Tell us the versions of Xenomai and of the I-pipe patch you use.
>> Send us your .config
>> Manage to get the kernel console output (using a serial cable connected
>> to another PC, or the netconsole, some people even used to send us
>> photos about kernel crashes).
>>
> 
> I send dmesg output for both 32 and 64 bit. Unfortunately it just
> freezes with no kernel panic output. When Xenomai debugging is enabled,
> the kernel freezes after Xenomai is initialized (last message: Xenomai:
> starting RTDM services).

Does this patch make any difference?

Jan

------->

x86: Fix irq_move_cleanup virtualization

Call the right function and avoid a recursion when this interrupt
triggers.

Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
---

 arch/x86/kernel/ipipe.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/ipipe.c b/arch/x86/kernel/ipipe.c
index b8f9139..d4789c8 100644
--- a/arch/x86/kernel/ipipe.c
+++ b/arch/x86/kernel/ipipe.c
@@ -290,7 +290,7 @@ void __init __ipipe_enable_pipeline(void)
 
 	ipipe_virtualize_irq(ipipe_root_domain,
 			     ipipe_apic_vector_irq(IRQ_MOVE_CLEANUP_VECTOR),
-			     (ipipe_irq_handler_t)&irq_move_cleanup_interrupt,
+			     (ipipe_irq_handler_t)&smp_irq_move_cleanup_interrupt,
 			     NULL,
 			     &__ipipe_ack_apic,
 			     IPIPE_STDROOT_MASK);



--------------

PS:
...
> [    0.005664] Checking 'hlt' instruction... OK.
> [    0.020484] ACPI: Core revision 20090521
> [    0.259694] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> [    0.260001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC

This is an ipipe triggered oddity (if not bug), too. I'm seeing it over
kvm as well, and it goes away when disabling ipipe. Does it ring some
bell? Otherwise I will check this later.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  parent reply	other threads:[~2009-10-03 16:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 11:48 [Xenomai-help] Freeze on SMP x86-64 Roman Pisl
2009-10-02 12:39 ` Gilles Chanteperdrix
2009-10-02 13:22   ` Roman Pisl
2009-10-02 13:25     ` Gilles Chanteperdrix
2009-10-02 13:34     ` Philippe Gerum
2009-10-02 13:36       ` Philippe Gerum
2009-10-03 16:01     ` Jan Kiszka [this message]
     [not found]       ` <4AC9E655.5090006@domain.hid>
     [not found]         ` <4AC9ED6B.4050004@domain.hid>
     [not found]           ` <4AC9F4FA.5070409@domain.hid>
     [not found]             ` <4ACA013F.8040602@domain.hid>
2009-10-06 13:18               ` Roman Pisl
2009-10-06 13:56                 ` Jan Kiszka
2009-10-06 14:50                   ` Roman Pisl
2009-10-06 15:33                   ` Roman Pisl
2009-10-06 15:45                   ` Roman Pisl
2009-10-06 15:59                     ` Jan Kiszka
2009-10-02 12:45 ` Peter Soetens
2009-10-02 12:58   ` Roman Pisl
2009-10-02 13:40 ` Philippe Gerum
2009-10-02 14:14   ` Roman Pisl
2009-10-02 16:40     ` Gilles Chanteperdrix
2009-10-02 14:21 ` Jan Kiszka

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=4AC77576.9070700@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpisl@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.