mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Markus Schoder <markus_schoder@yahoo.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Freeze on FPU exception with Athlon
Date: Sun, 19 Nov 2000 09:53:58 -0500	[thread overview]
Message-ID: <3A17E986.E4D5A06@didntduck.org> (raw)
In-Reply-To: <20001118190638.18296.qmail@web3407.mail.yahoo.com>

Markus Schoder wrote:
> 
> --- Linus Torvalds <torvalds@transmeta.com> schrieb: >
> 
> >
> > On Sat, 18 Nov 2000, adrian wrote:
> >
> > >
> > >
> > > On Sat, 18 Nov 2000, Linus Torvalds wrote:
> > >
> > > > There's almost certainly more than that. I'd
> > love to have a report on my
> > > > asm-only version, but even so I suspect it also
> > requires the 3dnow stuff,
> > >
> > > I tried all three versions, and no freezes.  I
> > forgot to mention the tests
> > > were run on a model 2 Athlon (original slot K7,
> > .18 micron).  The kernel
> > > is compiled with 3dnow support.
> >
> > Apparently it isn't the stepping, as we have Athlon
> > model 4's both showing
> > it and not showing it. The motherboard seems to be
> > the only real
> > difference here, which is why I like the irq13
> > explanation more and more.
> >
> > I've been wanting to get rid of irq13 anyway (some
> > boards wire up USB
> > and/or ACPI to irq13 and the fact that the FPU has
> > claimed it makes those
> > machines unhappy), so if the solution is to only
> > check for irq13 on old
> > i386 and i486sx machines and just leave it alone for
> > newer CPU's, I won't
> > complain.
> >
> > Markus, can you make the irq13 test the first thing
> > - don't worry about
> > 3dnow as that seems to not be a deciding factor..
> >
> >                       Linus
> >
> 
> Ok, that was it!  It's IRQ 13.  Guess I should have
> tried that first.  Now everything works perfectly.
> Thanks everybody.

What motherboard do you have?  I can't reproduce this on my FIC SD11.

-- 

						Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-19 15:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18 19:06 Markus Schoder
2000-11-19 14:53 ` Brian Gerst [this message]
2000-11-20  1:10 ` Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
2000-11-21  8:33 Aron Hsiao
2000-11-19 17:48 Markus Schoder
2000-11-18 18:22 Markus Schoder
2000-11-18 18:33 ` Udo A. Steinberg
2000-11-18 18:38 ` Linus Torvalds
2000-11-20  1:05 ` Horst von Brand
2000-11-18  1:40 Markus Schoder
2000-11-18  3:48 ` Linus Torvalds
2000-11-18  4:10 ` Linus Torvalds
2000-11-18  7:20   ` adrian
2000-11-18 14:53     ` Michael Meding
2000-11-18  7:48   ` Udo A. Steinberg
2000-11-18 17:17     ` Alan Cox
2000-11-18 18:03       ` Linus Torvalds
2000-11-18 18:27         ` Udo A. Steinberg
2000-11-18 18:34         ` adrian
2000-11-18 18:43           ` Linus Torvalds
2000-11-18 22:33           ` TimO
2000-11-18 14:15   ` Brian Gerst
2000-11-18 16:26     ` Linus Torvalds

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=3A17E986.E4D5A06@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus_schoder@yahoo.de \
    /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®