From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.50 hang when copying files, handwritten trace included
Date: Mon, 02 Dec 2002 10:41:54 -0800 [thread overview]
Message-ID: <3DEBA972.DB6AF8F1@digeo.com> (raw)
In-Reply-To: <3DEB70FE.C422A3EB@aitel.hist.no>
Helge Hafting wrote:
>
> 2.5.50 hung when copying 800M.
> mke2fs on a 10G partition, then try to copy
> the entire /home there. Source and destionation
> was on the same disk. After a while, this happened:
>
> EIP: wake_up_forked_process+0xb8/0x18c
> EAX: 5a5a5a5a (suspicious)
>
> trace:
> do_fork
> kernel_thread
> pdflush
> kernel_thread_helper
> start_one_pdflush_thread
> pdflush
> __pdflush
> __pdflush
> background_writeout
> kernel_thread_helper
>
Yes please - if you could gather sufficient info to enable
us to determine what eax is pointing at in wake_up_forked_process(),
that would help. Presumably it's the new process, which is rather
bizarre.
Also, does disabling preemption make it stop?
Thanks.
next prev parent reply other threads:[~2002-12-02 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 14:41 Helge Hafting
2002-12-02 18:41 ` Andrew Morton [this message]
2002-12-03 17:22 Helge Hafting
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=3DEBA972.DB6AF8F1@digeo.com \
--to=akpm@digeo.com \
--cc=helgehaf@aitel.hist.no \
--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
Powered by JetHome