public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Age Kamfjord <lakmailing@globelan.net>
To: linux-kernel@vger.kernel.org
Cc: stian@nixia.no
Subject: Re: timer + fpu stuff locks my console race
Date: Fri, 11 Jun 2004 08:08:48 +0200	[thread overview]
Message-ID: <40C94C70.3090502@globelan.net> (raw)
In-Reply-To: <20040610210042.GL31653@mail.hex.no>

This bug seems VERY serious.... Every machine I've tested with so far 
has crashed totally; and it happens with every version of 2.4 and 
2.6-kernels. I've tested with a 2.2.19-kernel, and that didn't crash, so 
it seems to be a bug in 2.4 and later..... Somebody really should look 
at this......


Lars Age Kamfjord

  reply	other threads:[~2004-06-11  6:08 UTC|newest]

Thread overview: 26+ 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10 18:59 Lars Age Kamfjord
2004-06-10 19:21 ` Lars Age Kamfjord
2004-06-10 19:27 Bård Kalbakk
2004-06-11 12:10 stian
2004-06-11 12:20 Gard Spreemann
2004-06-12 12:26 stian
2004-06-12 13:14 stian
2004-06-12 13:28 stian
2004-06-12 13:45 ` Manuel Arostegui Ramirez
2004-06-12 13:50 ` Kalin KOZHUHAROV

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=40C94C70.3090502@globelan.net \
    --to=lakmailing@globelan.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stian@nixia.no \
    /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