From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: george@mvista.com (george anzinger)
Cc: pozsy@sch.bme.hu (Pozsar Balazs),
acahalan@cs.uml.edu (Albert D. Cahalan),
linux-kernel@vger.kernel.org (linux-kernel)
Subject: Re: very strange (semi-)lockups in 2.4.5
Date: Mon, 18 Jun 2001 17:18:59 -0400 (EDT) [thread overview]
Message-ID: <200106182118.f5ILIxa187286@saturn.cs.uml.edu> (raw)
In-Reply-To: <3B2E686E.C1BCAA69@mvista.com> from "george anzinger" at Jun 18, 2001 01:45:34 PM
george anzinger writes:
> Pozsar Balazs wrote:
>> The NMI card would be interesting, if anyone tells me how to make
>> one, and how to patch the kernel to show useable information i'm
>> looking forward to do it, and send reports.
>
> Given that your system still handles interrupts:
> a.) It would probably not trigger an NMI timer (the interrupts would
> keep resetting it)
Huh? No, this isn't the NMI timer. It's an NMI you generate
with a pushbutton on the back of your PC. My computer doesn't
have the APIC hardware needed for an NMI timer anyway.
For a PCI card, one must assert the SERR# signal. This is supposed
to be done for 1 clock cycle, on the proper clock edge. Going a bit
beyond 1 clock cycle ought to be OK, but my hand on a button is
likely to assert SERR# for millions of clock cycles. I've no idea
if my motherboard will handle that well.
> b.) Using KGDB will, most likely, be all you need anyway.
I'd rather just get an oops, but even still the board would
be good to have. KGDB can be triggered by an NMI, right?
Building an NMI board would be fun, overkill or not. :-)
> If you have a complete freeze, then the NMI is useful, but even
> here, it is best to let KGDB handle the NMI. Much easier to see
> what's what than looking thru an OOPS.
I don't have an APIC. I have a plain Pentium MMX. If I want
an NMI it's going to come from a pushbutton.
next prev parent reply other threads:[~2001-06-18 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 7:05 Pozsar Balazs
2001-06-18 17:10 ` Albert D. Cahalan
2001-06-18 19:20 ` Pozsar Balazs
2001-06-18 20:45 ` george anzinger
2001-06-18 21:18 ` Albert D. Cahalan [this message]
2001-06-19 0:38 ` george anzinger
2001-06-19 13:09 ` Pavel Machek
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=200106182118.f5ILIxa187286@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
/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®