From: William Lee Irwin III <wli@holomorphy.com>
To: Pedro Larroy <piotr@member.fsf.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] D-states in test8
Date: Sun, 19 Oct 2003 16:02:40 -0700 [thread overview]
Message-ID: <20031019230240.GE1215@holomorphy.com> (raw)
In-Reply-To: <20031019222604.GA1140@81.38.200.176>
On Mon, Oct 20, 2003 at 12:26:04AM +0200, Pedro Larroy wrote:
> xmms D C010E5A9 0 5975 1595 1597 (NOTLB)
> d8327ed0 00000082 cbf02560 c010e5a9 00000002 c7ea6000 c7ea6004 df8f9a2c
> df8e5869 0000433f 1f9dff47 00001244 d2d306a0 c16f7318 d2d306a0 00000246
> c16f7320 c0107f6f 00000001 d2d306a0 c011a4e5 cdfade2c c16f7320 4095b000
> Call Trace:
> [do_gettimeofday+25/134] do_gettimeofday+0x19/0x86
> [__crc___ndelay+126735/403990] snd_pcm_trigger_tstamp+0x61/0x7e [snd_pcm]
> [__down+113/188] __down+0x71/0xbc
> [default_wake_function+0/46] default_wake_function+0x0/0x2e
> [unmap_page_range+67/105] unmap_page_range+0x43/0x69
> [__down_failed+8/12] __down_failed+0x8/0xc
> [__crc___ndelay+143015/403990] .text.lock.pcm_native+0xb9/0xc8 [snd_pcm]
> [__fput+221/239] __fput+0xdd/0xef
> [unmap_vma+115/125] unmap_vma+0x73/0x7d
> [unmap_vma_list+28/40] unmap_vma_list+0x1c/0x28
> [do_munmap+301/367] do_munmap+0x12d/0x16f
> [sys_munmap+68/100] sys_munmap+0x44/0x64
> [syscall_call+7/11] syscall_call+0x7/0xb
Here we have .text.lock.pcm_native ...
On Mon, Oct 20, 2003 at 12:26:04AM +0200, Pedro Larroy wrote:
> mplayer D 00000306 0 6016 1 6018 6028 1574 (NOTLB)
> cdfade18 00200082 c7f84a18 00000306 c03564f4 c1254c70 00000000 c7f8498c
> de7e4cc0 0001033e e7a80ee1 00001245 d5bb46a0 c16f7318 d5bb46a0 00200246
> c16f7320 c0107f6f 00000001 d5bb46a0 c011a4e5 c16f7320 d8327ee4 c7f84a18
> Call Trace:
> [__down+113/188] __down+0x71/0xbc
> [default_wake_function+0/46] default_wake_function+0x0/0x2e
> [__down_failed+8/12] __down_failed+0x8/0xc
> [__crc_fs_overflowgid+311048/1150401] .text.lock.pcm_oss+0x2d/0xa1 [snd_pcm_oss]
> [do_lookup+48/161] do_lookup+0x30/0xa1
> [link_path_walk+1391/2011] link_path_walk+0x56f/0x7db
> [default_wake_function+0/46] default_wake_function+0x0/0x2e
> [vfs_follow_link+51/344] vfs_follow_link+0x33/0x158
> [soundcore_open+195/394] soundcore_open+0xc3/0x18a
> [soundcore_open+0/394] soundcore_open+0x0/0x18a
> [chrdev_open+168/321] chrdev_open+0xa8/0x141
> [devfs_open+165/189] devfs_open+0xa5/0xbd
> [dentry_open+271/403] dentry_open+0x10f/0x193
> [filp_open+98/100] filp_open+0x62/0x64
> [sys_open+91/139] sys_open+0x5b/0x8b
> [syscall_call+7/11] syscall_call+0x7/0xb
and .text.lock.pcm.oss ... you seem to have the same problem as Diego.
-- wli
next prev parent reply other threads:[~2003-10-19 23:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 20:56 Pedro Larroy
2003-10-19 21:03 ` William Lee Irwin III
2003-10-19 22:26 ` Pedro Larroy
2003-10-19 23:02 ` William Lee Irwin III [this message]
2003-10-19 23:01 ` Andrew Morton
2003-10-20 1:29 ` Pedro Larroy
2003-10-20 1:36 ` Andrew Morton
2003-10-20 2:24 ` Pedro Larroy
2003-10-20 3:33 ` William Lee Irwin III
2003-10-20 12:53 ` Diego Calleja García
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=20031019230240.GE1215@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@member.fsf.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
Powered by JetHome