From: David Woodhouse <dwmw2@infradead.org>
To: "David Cooper" <david@forcedpotato.com>
Cc: "Ilguiz Latypov" <ilatypov@superbt.com>,
"Linux MTD" <linux-mtd@lists.infradead.org>
Subject: Re: X Windows Performance with DOC 2000
Date: Fri, 21 Jun 2002 08:04:12 +0100 [thread overview]
Message-ID: <16562.1024643052@redhat.com> (raw)
In-Reply-To: <AIEOIMKIOAAJKHJOGAEFMEFCCEAA.david@forcedpotato.com>
david@forcedpotato.com said:
> - Mount operation mount /dev/nftla2 /mnt/doc causes the shell to
> hang. - Viewing the process "mount" using top shows that it is running
> continuously and using 84% CPU time. - All attempts to kill the mount
> process are futile.
OK, here we can find some clues. _What_ is it doing? Use SysRq-P a few
times to see where it's looping, look it up in your kernel image. If you
compile with '-g' you can get gdb to tell you the precise line.
--
dwmw2
next prev parent reply other threads:[~2002-06-21 7:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 3:09 X Windows Performance with DOC 2000 David Cooper
2002-06-15 22:32 ` Charles Manning
2002-06-17 22:30 ` David Cooper
2002-06-17 22:32 ` Ilguiz Latypov
2002-06-18 0:22 ` David Cooper
2002-06-18 0:40 ` Brendan J Simon
2002-06-21 23:33 ` Christopher Fowler
2002-06-18 14:11 ` Ilguiz Latypov
2002-06-20 19:41 ` David Cooper
2002-06-20 21:59 ` David Woodhouse
2002-06-21 0:33 ` David Cooper
2002-06-21 0:39 ` David Woodhouse
2002-06-21 5:46 ` David Cooper
2002-06-21 7:04 ` David Woodhouse [this message]
2002-06-26 18:30 ` David Cooper
2002-06-26 21:28 ` David Woodhouse
2002-06-21 13:56 ` Ilguiz Latypov
2002-06-21 14:09 ` cfowler
2002-06-21 14:12 ` David Woodhouse
2002-06-21 14:28 ` cfowler
2002-06-22 0:01 ` Ilguiz Latypov
2002-06-22 0:15 ` Christopher Fowler
2002-06-22 1:14 ` David Cooper
2002-06-22 1:11 ` Gonzalo Servat
2002-06-22 9:18 ` David Woodhouse
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=16562.1024643052@redhat.com \
--to=dwmw2@infradead.org \
--cc=david@forcedpotato.com \
--cc=ilatypov@superbt.com \
--cc=linux-mtd@lists.infradead.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.