mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: stian@nixia.no
To: "Alexander Nyberg" <alexn@telia.com>
Cc: linux-kernel@vger.kernel.org, "Sergey Vlasov" <vsu@altlinux.ru>,
	"Rik van Riel" <riel@redhat.com>
Subject: Re: timer + fpu stuff locks up computer
Date: Sat, 12 Jun 2004 16:42:33 +0200 (CEST)	[thread overview]
Message-ID: <1734.83.109.11.80.1087051353.squirrel@nepa.nlc.no> (raw)
In-Reply-To: <1087050351.707.5.camel@boxen>

> Sorry for this extremely informative mail but, doesn't work.
>
> Looks like the problem is only being delayed:

Makes sense, since fwait is done in kernel-mode and it takes some time for
the exception to rise, since this is a slow instruction. So the problem
gets delayed. What do you think Sergey?

Does the other dirty nasty patch work for you?


Stian Skjelstad

  reply	other threads:[~2004-06-12 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-09 21:02 timer + fpu stuff locks my console race stian
2004-06-10 21:00 ` Matias Hermanrud Fjeld
2004-06-11  6:08   ` Lars Age Kamfjord
2004-06-12  2:53 ` Rik van Riel
2004-06-12  3:50   ` Rik van Riel
2004-06-12 13:44     ` Sergey Vlasov
2004-06-12 13:57       ` stian
2004-06-12 14:28         ` Sergey Vlasov
2004-06-12 14:25       ` timer + fpu stuff locks up computer Alexander Nyberg
2004-06-12 14:42         ` stian [this message]
2004-06-12 15:20           ` martin capitanio
2004-06-12 16:15             ` stian
2004-06-12 15:14         ` Sergey Vlasov
2004-06-12 18:45           ` Sergey Vlasov
2004-06-12 20:27             ` Alexander Nyberg
2004-06-12  4:35   ` timer + fpu stuff locks my console race Matt Mackall
     [not found] <26h3z-t3-15@gated-at.bofh.it>
     [not found] ` <26hGq-Zr-29@gated-at.bofh.it>
     [not found]   ` <26isF-1Im-11@gated-at.bofh.it>
     [not found]     ` <26lJU-4lC-23@gated-at.bofh.it>
2004-06-12 22:08       ` timer + fpu stuff locks up computer Andi Kleen
2004-06-13 13:06         ` Sergey Vlasov

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=1734.83.109.11.80.1087051353.squirrel@nepa.nlc.no \
    --to=stian@nixia.no \
    --cc=alexn@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=vsu@altlinux.ru \
    /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®