From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Alexander Hoogerhuis <alexh@ihatent.com>,
philippe.gramoulle@mmania.com, linux-kernel@vger.kernel.org
Subject: Re: Hard freeze with 2.5.65-mm1
Date: Wed, 19 Mar 2003 17:03:19 -0800 [thread overview]
Message-ID: <20030320010319.GB1240@holomorphy.com> (raw)
In-Reply-To: <20030319121909.74f957af.akpm@digeo.com>
Alexander Hoogerhuis <alexh@ihatent.com> wrote:
>> I've had I/O stall a few times while watching movies, but only the
>> mplayer process hung, and I could break it off and restart and it
>> woudl fun again for a few minutes.
On Wed, Mar 19, 2003 at 12:19:09PM -0800, Andrew Morton wrote:
> This is a bug in the new nanosleep code. mplayer asks the kernel for a 50
> millisecond sleep and the kernel gives it a two month sleep instead.
> Please set INITIAL_JIFFIES to zero and retest.
> With what compiler are you building your kernels?
Just hit it with xmms:
$ less /proc/1284/wchan
sys_rt_sigsuspend
$ less /proc/1285/wchan
schedule_timeout
$ less /proc/1286/wchan
schedule_timeout
$ less /proc/16656/wchan
do_clock_nanosleep
$ less /proc/16657/wchan
do_clock_nanosleep
kill -STOP `pidof xmms` ; kill -CONT `pidof xmms` gets it unstuck so
it's not lethal, but still...
-- wli
next prev parent reply other threads:[~2003-03-20 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 9:49 Hard freeze with 2.5.65-mm1 Philippe Gramoullé
2003-03-19 10:19 ` Alexander Hoogerhuis
2003-03-19 12:28 ` Philippe Gramoullé
2003-03-19 17:24 ` Philippe Gramoullé
2003-03-19 18:15 ` Alexander Hoogerhuis
2003-03-19 20:19 ` Andrew Morton
2003-03-19 20:51 ` Alexander Hoogerhuis
2003-03-19 22:42 ` Philippe Gramoullé
2003-03-20 1:03 ` William Lee Irwin III [this message]
2003-03-20 3:15 ` Andrew Morton
2003-03-20 17:01 ` Philippe Gramoullé
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=20030320010319.GB1240@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.gramoulle@mmania.com \
/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