From: george anzinger <george@mvista.com>
To: Pozsar Balazs <pozsy@sch.bme.hu>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: very strange (semi-)lockups in 2.4.5
Date: Mon, 18 Jun 2001 13:45:34 -0700 [thread overview]
Message-ID: <3B2E686E.C1BCAA69@mvista.com> (raw)
In-Reply-To: <Pine.GSO.4.30.0106182118260.20838-100000@balu>
Pozsar Balazs wrote:
>
> First I thought this was an X-issue, but now I'm 100% sure that it isn't,
> as I met the desscribed hangup while working on the console too.
>
> 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)
b.) Using KGDB will, most likely, be all you need anyway.
KGDB (find it a sourceforge) requires a second computer which is hooked
to the "subject" over a rs232 serial line. The "host" computer needs to
have the vmlinux file as well as the sources for the kernel. Once the
"subject" becomes ill, a control-C (from the "host") on the serial line
will interrupt it and start a dialog with gdb running on the "host"
computer. If you have the second computer, this is the easiest way to
get to where you need to be.
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.
George
> regards
> Balazs Pozsar.
>
> On Mon, 18 Jun 2001, Albert D. Cahalan wrote:
>
> > Pozsar Balazs writes:
> >
> > > I'm having ~2 lockups a day. The following happens:
> > > If I was under X, i only can use the magic-key, but no other keyboard (eg
> > > numlock) or mouse response, the screen freezes, processes stop.
> > > If i was using textmode:
> > > numlock still works
> > > cursor blinks
> > > processess stop (eg, gpm doesn't work, outputs freeze)
> > > i can still switch vt's.
> > > BUT, i can only type into a few vt's, last time into 3,5,6,7,8, but not
> > > into 1,2 or 4!
> > >
> > > I cannot give you any traces, as i dont have any.
> > >
> > > Also note that magic-key works, and it says that it umounts filesystems if
> > > i press magic-u, but next time at mount i see that reiserfs is replaying
> > > transactions.
> > >
> > >
> > > Any ideas?
> > >
> > > The machine is a P3-750, 512M ram, abit vp6 mb. No overclocking, and it
> > > passes memtest86.
> >
> > I think I'm getting the same thing, but I don't have the magic-key
> > compiled in. I'm going to hook up a VT510 to the serial port, in case
> > this is just XFree86 crashing. For anyone collecting statistics:
> >
> > kernels 2.4.4-pre6 (?) and now 2.4.6-pre3
> > plain Pentium MMX @ 200 MHz
> > Intel motherboard -- see below
> > stable since 1996, on a UPS, dust-free, and the fan works
> > one lockup per day with desktop usage
> >
> > In case the serial console doesn't work, could someone post plans
> > for a safe NMI board? (both ISA and PCI) The best I found:
> > http://www.sandelman.ottawa.on.ca/linux-ipsec/html/2000/02/msg00425.html
> > http://www.sandelman.ottawa.on.ca/linux-ipsec/html/2000/02/msg00391.html
> > (for PCI you're supposed to assert SERR# on the clock -- how?)
> >
> > 00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
> > 00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01)
> > 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
> > 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
> > 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01)
> > 00:11.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 [Tulip] (rev 23)
> > 00:13.0 Ethernet controller: Lite-On Communications Inc LNE100TX Fast Ethernet Adapter (rev 25)
> > 00:14.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c)
> >
>
> --
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-06-18 20:46 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 [this message]
2001-06-18 21:18 ` Albert D. Cahalan
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=3B2E686E.C1BCAA69@mvista.com \
--to=george@mvista.com \
--cc=acahalan@cs.uml.edu \
--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®