From: Keith Owens <kaos@ocs.com.au>
To: Gerard Beekmans <gerard@linuxfromscratch.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0-test11/12 freezes when copying large amounts of data to loop file system
Date: Sat, 16 Dec 2000 17:16:59 +1100 [thread overview]
Message-ID: <12757.976947419@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 14 Dec 2000 14:55:59 CDT." <00121414555900.00305@gwaihir>
On Thu, 14 Dec 2000 14:55:59 -0500,
Gerard Beekmans <gerard@linuxfromscratch.org> wrote:
>Every time I try to copy a specific directory to a mounted loop file system,
>Linux freezes up on me. I've tried this several times and it freezes up at
>the same place every time. When I copy that same directory to a regular file
>system everything is ok.
Gerard, reporting "kernel freezes" without any diagnostics is not very
useful. If you apply the kdb patch[*] you will get some diagnostics.
Apply the patch and configure. Under Kernel debugging, select kdb and
no frame pointers. If your box is UP, under Processor type select APIC
and IO-APIC support on uniprocessors, then NMI watchdog active for
uniprocessors. SMP boxes automatically get NMI watchdog. Recompile,
install, reboot.
When it freezes, after 5 seconds the NMI watchdog will trip and drop
you into kdb. Issue a 'bt' command to see where it is hanging, send
this trace to the list. A serial console run to a second machine makes
it a lot easier to capture the trace, otherwise you have to write it
down by hand.
[*] http://oss.sgi.com/projects/kdb/download/ix86/, pick the relevant
patch for your kernel. You also need a recent modutils from
ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/modutils/v2.3
-
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/
prev parent reply other threads:[~2000-12-16 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 19:55 Linux 2.4.0-test11/12 freezes when copying large amounts of data to loop file system Gerard Beekmans
2000-12-16 6:16 ` Keith Owens [this message]
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=12757.976947419@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=gerard@linuxfromscratch.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox