From: Andrew Morton <andrewm@uow.edu.au>
To: Pawe³ Kot <pkot@linuxnews.pl>
Cc: lkml <linux-kernel@vger.kernel.org>, smp-linux-kernel@vger.kernel.org
Subject: Re: [prepatch] removal of oops->printk deadlocks
Date: Wed, 15 Nov 2000 22:17:13 +1100 [thread overview]
Message-ID: <3A1270B9.1A38133@uow.edu.au> (raw)
In-Reply-To: <3A1115C5.4C04CD6A@uow.edu.au> <Pine.LNX.4.30.0011141659020.29502-600000@tfuj.ahoj.pl>
"Pawe³ Kot" wrote:
>
> Hi,
>
> The whole oops produced by the 2.4.0-test11pre4 with this patch is in the
> attachment. Other system info is tehere as well.
>
> Oops is produced when runnning big-tables test from mysql sql-bench.
> It's reproducable. The machine is running only mysqld.
Thank you. Quad 700 meg Xeons? Nice machine, that.
The NMI oops changes are working well. We can see three CPUs are
stuck in different places spinning on the same lock with interrupts
disabled, but unfortunately something went wrong with your `ksymoops'
run.
Could you please rerun ksymoops, and make sure that you use the
correct symbol file? Take the `System.map' from the directory
where you built the kernel and run
ksymoops -m System.map < log_file
-
-
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-15 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 10:36 [prepatch] removal of oops->printk deadlocks Andrew Morton
2000-11-14 16:07 ` Pawe³ Kot
2000-11-15 11:17 ` Andrew Morton [this message]
2000-11-15 11:26 ` Pawe³ Kot
2000-11-15 11:39 ` Andrew Morton
2000-11-15 10:19 ` Ingo Molnar
2000-11-15 11:07 ` Andrew Morton
2000-11-15 12:23 ` Ingo Molnar
2000-11-15 13:23 ` Andrew Morton
2000-11-15 14:35 ` Ingo Molnar
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=3A1270B9.1A38133@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pkot@linuxnews.pl \
--cc=smp-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.