From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, andre@linuxdiskcert.org
Subject: Re: [BUG] 2.4.18.3, ide-patch, read_dev_sector hangs in read_cache_page
Date: Wed, 16 Jan 2002 09:50:11 +0000 [thread overview]
Message-ID: <5.1.0.14.2.20020116094806.04f00380@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20020116102738.A21977@alpha.logic.tuwien.ac.at>
In-Reply-To: <20020116094935.A20738@alpha.logic.tuwien.ac.at> <E16QU3F-0005g6-00@libra.cus.cam.ac.uk> <20020115160315.A2515@alpha.logic.tuwien.ac.at> <20020116094935.A20738@alpha.logic.tuwien.ac.at>
At 09:27 16/01/02, Norbert Preining wrote:
>On Mit, 16 Jan 2002, preining wrote:
> > I have tried to follow the trace of the kernel but it looks to me as
> > read_cache_page is never called or printk in it are not executed. I filled
>
>Stupid me, somehow KERN_DEBUG was not shown.
>
>I traced it down from
>read_cache_page -> lock_page -> __lock_page -> schedule
>
>There it hangs and I was not able with my stupid methods or printk-ing
>to find the place where it hangs in sched.c (Maybe because of recursive
>calls to sched by printk).
>
>One more thing: Taking off hdf from the ide controller and everything
>works.
>Another: same with 2.4.18-pre4
You mean 2.4.18-pre4 (without any patches) dies in the same way on hdf?
If so that is very interesting...
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2002-01-16 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 13:54 Anton Altaparmakov
2002-01-15 15:03 ` Norbert Preining
[not found] ` <20020116094935.A20738@alpha.logic.tuwien.ac.at>
2002-01-16 9:27 ` Norbert Preining
2002-01-16 9:50 ` Anton Altaparmakov [this message]
2002-01-16 11:27 ` Norbert Preining
-- strict thread matches above, loose matches on Subject: below --
2002-01-15 12:29 Norbert Preining
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=5.1.0.14.2.20020116094806.04f00380@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=andre@linuxdiskcert.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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
all inboxes | Powered by JetHome®