From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266397AbUGJU2a (ORCPT ); Sat, 10 Jul 2004 16:28:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266409AbUGJU2a (ORCPT ); Sat, 10 Jul 2004 16:28:30 -0400 Received: from fw.osdl.org ([65.172.181.6]:28616 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S266397AbUGJU22 convert rfc822-to-8bit (ORCPT ); Sat, 10 Jul 2004 16:28:28 -0400 Date: Sat, 10 Jul 2004 13:27:11 -0700 From: Andrew Morton To: Marcin =?ISO-8859-1?B?R2lidV9fYQ==?= Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.7-mm7 Message-Id: <20040710132711.52ee2343.akpm@osdl.org> In-Reply-To: <200407102204.35889.mg@iceni.pl> References: <20040708235025.5f8436b7.akpm@osdl.org> <200407102204.35889.mg@iceni.pl> X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Marcin Gibu__a wrote: > > On Friday 09 July 2004 08:50, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-m > >m7/ > > Hi, > I've encountered a process locked up in D state while using this kernel. The > process is mpg123 playing mp3 from ntfs partition. I'm using cfq elevator. > > Alt-SysRq-T reveals that: > > mpg123 D 00000D33 0 18012 18592 (NOTLB) > d8c11e28 00200086 37c2b380 00000d33 00000000 37c2b380 00000d33 c8761190 > c8761338 c1253760 c14011e8 00000275 d8c11e30 c02e9c27 00000275 c0127522 > c1253760 00000000 00000001 c8761190 c01272e1 d8c11e6c d8c11e6c c153d480 > Call Trace: > [] io_schedule+0xe/0x16 > [] __lock_page+0xa7/0xba > [] page_wake_function+0x0/0x36 > [] page_wake_function+0x0/0x36 > [] do_generic_mapping_read+0x15d/0x2f4 > [] __generic_file_aio_read+0x198/0x1b6 > [] file_read_actor+0x0/0xbd > [] generic_file_read+0x68/0x7c > [] snd_pcm_oss_write1+0x131/0x165 > [] vfs_read+0x9d/0xc9 > [] sys_read+0x2c/0x42 > [] sysenter_past_esp+0x52/0x71 Is it repeatable at all? If so, does using a different I/O scheduler fix it up?