From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-mm@kvack.org
Subject: 35-mm1 triggers watchdog
Date: Tue, 17 Sep 2002 07:38:48 -0400 [thread overview]
Message-ID: <200209170738.48565.tomlins@cam.org> (raw)
In-Reply-To: <3D86E19B.6476A9EA@digeo.com>
Hi Andrew,
I have had 35-mm1 reboot twice via the software watchdog. What is the best
way to debug this. I do have a serial term and can rebuild patched with the
kernel debugger, just need some instructions on how to catch the stall and
what info to gather. Is there a good FAQ on kernel debugger?
Kernel is 35-mm1 UP no preempth, plus ide probe fixes & a corrected slab callback
patch.
TIA
Ed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-17 11:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 4:43 dbench on tmpfs OOM's William Lee Irwin III
2002-09-17 4:43 ` William Lee Irwin III
2002-09-17 4:58 ` Andrew Morton
2002-09-17 4:58 ` Andrew Morton
2002-09-17 5:01 ` Martin J. Bligh
2002-09-17 5:01 ` Martin J. Bligh
2002-09-17 5:14 ` Andrew Morton
2002-09-17 5:14 ` Andrew Morton
2002-09-17 5:18 ` Martin J. Bligh
2002-09-17 5:18 ` Martin J. Bligh
2002-09-17 5:15 ` William Lee Irwin III
2002-09-17 5:15 ` William Lee Irwin III
2002-09-17 5:31 ` Andrew Morton
2002-09-17 5:31 ` Andrew Morton
2002-09-17 6:43 ` Christoph Rohland
2002-09-17 6:43 ` Christoph Rohland
2002-09-17 7:01 ` Hugh Dickins
2002-09-17 7:01 ` Hugh Dickins
2002-09-17 7:27 ` William Lee Irwin III
2002-09-17 7:27 ` William Lee Irwin III
2002-09-17 8:02 ` Andrew Morton
2002-09-17 8:02 ` Andrew Morton
2002-09-17 11:38 ` Ed Tomlinson [this message]
2002-09-17 20:12 ` 35-mm1 triggers watchdog Andrew Morton
2002-09-17 7:57 ` dbench on tmpfs OOM's Christoph Rohland
2002-09-17 7:57 ` Christoph Rohland
2002-12-10 5:28 ` William Lee Irwin III
2002-12-10 5:28 ` William Lee Irwin III
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=200209170738.48565.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.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.