mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: rt-preempt and x86_64?
Date: Sun, 17 Jul 2005 21:04:40 +0100	[thread overview]
Message-ID: <200507172104.40073.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <42DA8779.3020005@stud.feec.vutbr.cz>

On Sunday 17 Jul 2005 17:29, Michal Schmidt wrote:
> Alistair John Strachan wrote:
> > Hi Ingo,
> >
> > (I searched the list for rt realtime x86_64 x86-64 before posting this,
> > so I hope it's not a duplicate).
> >
> > I've noticed -31 compiles without notable error or warning on x86-64, so
> > I thought maybe it was a valid time to file a bug report about it not
> > working.
> >
> > The machine currently runs 2.6.12 but when booting with PREEMPT_RT mode
> > on the same machine I get:
> >
> > init[1]: segfault at ffffffff8010e9c4 rip ffffffff8010e9c4 rsp
> > 00007fffffe28018
> > [...]
>
> Do you have latency tracing enabled in the kernel config? Try disabling
> it. It's a known problem that it doesn't work on x86_64.
>

Thanks Michal, this was the problem. Unless x86_64 is going to receive an 
implementation of LATENCY_TRACE soon, it might be an idea to only let this be 
selectable on x86.

(Unfortunately I couldn't use the resulting kernel anyway, as my lirc modules 
hang the system when modprobe'd; it's probably easy even for me to fix if I 
inspect Ingo's rt-preempt patch.)

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

      reply	other threads:[~2005-07-17 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 12:46 Alistair John Strachan
2005-07-17 16:29 ` Michal Schmidt
2005-07-17 20:04   ` Alistair John Strachan [this message]

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=200507172104.40073.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®