From: Andrew Morton <andrewm@uow.edu.au>
To: Jasper Spaans <jasper@spaans.ds9a.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11pre2-ac1 and previous problem
Date: Sun, 12 Nov 2000 12:32:55 +1100 [thread overview]
Message-ID: <3A0DF347.43807CB5@uow.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.30.0011101806140.29502-100000@tfuj.ahoj.pl> <3A0C91DC.97693969@uow.edu.au>, <3A0C91DC.97693969@uow.edu.au>; from andrewm@uow.edu.au on Sat, Nov 11, 2000 at 11:25:00AM +1100 <20001111162750.A1031@spaans.ds9a.nl>
Jasper Spaans wrote:
>
> On Sat, Nov 11, 2000 at 11:25:00AM +1100, Andrew Morton wrote:
>
> > > NMI Watchdog detected LOCKUP on CPU3, registers:
>
> > Oh no. Another one. Could you please try this attached
> > patch (against test11-pre2) and see if the diagnostics
> > come out?
>
> And yet another one... I applied your patch, and ran my oopses through
> ksymoops, results attached.
>
> Kernel: 2.4.0-test11-pre2 + reiserfs-3.6.18
> 2 * P-II 350, 256 MB RAM, no special hardware, AFAIK.
>
> Of course, more details are available.
That's a pretty wierd trace. You seem to have addresses related
to the `apm' kernel thread on mysqld's stack.
Are you saying that your machine is getting NMI lockups but
it is not usually able to print the register and stack
dumps? (ie: a printk deadlock)?
Do they go away if you disable APM?
-
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/
next prev parent reply other threads:[~2000-11-12 1:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 17:17 2.4.0-test11pre2-ac1 and previous problem Pawe³ Kot
2000-11-10 17:30 ` Rik van Riel
2000-11-10 17:36 ` Pawe³ Kot
2000-11-11 0:25 ` Andrew Morton
2000-11-11 15:27 ` Jasper Spaans
2000-11-12 1:32 ` Andrew Morton [this message]
2000-11-12 2:27 ` Keith Owens
2000-11-13 8:58 ` Jasper Spaans
2000-11-13 10:44 ` Keith Owens
2000-11-13 11:16 ` Andrew Morton
2000-11-13 12:11 ` Andrew Morton
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=3A0DF347.43807CB5@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=jasper@spaans.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.