From: Gergely Nagy <algernon@debian.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17rc2aa1
Date: Fri, 21 Dec 2001 20:34:42 +0100 [thread overview]
Message-ID: <83wuzgbc4t.wl@iluvatar.ath.cx> (raw)
In-Reply-To: <20011221025857.M1477@athlon.random>
In-Reply-To: <20011219161610.I1395@athlon.random> <83k7vjdk8j.wl@iluvatar.ath.cx> <20011219215208.U1395@athlon.random> <20011220181712.GA2494@iluvatar>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
> Not sure what's going on with the i_sem, are you playing with the loopfile
> somehow during the sync?
No. It's sitting in /var/cache/ext3test, and nothing else touches it.
> Can you also try to find more info about c01efe72
> <stext_lock+ee2/273a> with an objdump -j .text.lock? (should be the
> slow path of down() corresponding to the i_sem down in lo_send)
I guess I'm a bit uneducated, but objdump -j .text.lock vmlinux
doesn't work here, I'm obviously doing something wrong.
> are you sure it's really related to the loop device? (and not a
> ""genuine"" IDE lockup or something like that)
Yes, I'm sure. Without using the loop device, the system works fine,
as far as I can tell, and even with the loop device, 2.4.14 is OK.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2001-12-21 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011221025857.M1477@athlon.random>
2001-12-19 15:16 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-19 20:32 ` 2.4.17rc2aa1 Gergely Nagy
2001-12-19 20:52 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-20 18:17 ` 2.4.17rc2aa1 Gergely Nagy
2001-12-21 19:34 ` Gergely Nagy [this message]
2001-12-20 18:22 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-20 18:27 ` 2.4.17rc2aa1 Linus Torvalds
2001-12-20 18:32 ` 2.4.17rc2aa1 Andrea Arcangeli
2001-12-20 18:35 ` 2.4.17rc2aa1 Linus Torvalds
2001-12-20 19:28 ` 2.4.17rc2aa1 Christoph Hellwig
2001-12-25 20:22 ` 2.4.17rc2aa1 - blocking(?) in /proc Adam Schrotenboer
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=83wuzgbc4t.wl@iluvatar.ath.cx \
--to=algernon@debian.org \
--cc=andrea@suse.de \
--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