public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ALSA errors when renicing unrelated process
Date: Tue, 13 Jul 2004 21:08:42 -0400	[thread overview]
Message-ID: <1089767321.2729.4.camel@mindpipe> (raw)

I have found that I can reliably produce the following errors by
renicing the X server from -10 (the default on Debian) to 0 and back.  I
get the same error going from 0 to -10 as -10 back to 0, as if renicing
the process causes some kind of hiccup in the scheduler.  I do not seem
to get XRUNs when this happens.

Jul 13 21:02:13 mindpipe kernel:
Jul 13 21:02:13 mindpipe kernel: ALSA /usr/src/alsa-cvs-1.0.5/alsa-driver/alsa-kernel/core/pcm_lib.c:199: Unexpected hw_pointer value [1] (stream = 0, delta: -31, max jitter = 32): wrong interrupt acknowledge?
Jul 13 21:02:13 mindpipe kernel:  [dump_stack+23/32] dump_stack+0x17/0x20
Jul 13 21:02:13 mindpipe kernel:  [__crc_totalram_pages+46349/3558647] snd_pcm_period_elapsed+0x1a7/0x400 [snd_pcm]
Jul 13 21:02:13 mindpipe kernel:  [__crc_totalram_pages+115629/3558647] snd_emu10k1_interrupt+0x377/0x400 [snd_emu10k1]
Jul 13 21:02:13 mindpipe kernel:  [handle_IRQ_event+51/96] handle_IRQ_event+0x33/0x60
Jul 13 21:02:13 mindpipe kernel:  [do_IRQ+165/368] do_IRQ+0xa5/0x170
Jul 13 21:02:13 mindpipe kernel:  [common_interrupt+24/32] common_interrupt+0x18/0x20
Jul 13 21:02:13 mindpipe kernel:  [do_anonymous_page+124/384] do_anonymous_page+0x7c/0x180
Jul 13 21:02:13 mindpipe kernel:  [do_no_page+78/784] do_no_page+0x4e/0x310
Jul 13 21:02:13 mindpipe kernel:  [handle_mm_fault+193/368] handle_mm_fault+0xc1/0x170
Jul 13 21:02:13 mindpipe kernel:  [do_page_fault+805/1356] do_page_fault+0x325/0x54c
Jul 13 21:02:13 mindpipe kernel:  [error_code+45/64] error_code+0x2d/0x40
Jul 13 21:02:13 mindpipe kernel:
Jul 13 21:02:13 mindpipe kernel: ALSA /usr/src/alsa-cvs-1.0.5/alsa-driver/alsa-kernel/core/pcm_lib.c:199: Unexpected hw_pointer value [1] (stream = 0, delta: -31, max jitter = 32): wrong interrupt acknowledge?
Jul 13 21:02:13 mindpipe kernel:  [dump_stack+23/32] dump_stack+0x17/0x20
Jul 13 21:02:13 mindpipe kernel:  [__crc_totalram_pages+46349/3558647] snd_pcm_period_elapsed+0x1a7/0x400 [snd_pcm]
Jul 13 21:02:13 mindpipe kernel:  [__crc_totalram_pages+115629/3558647] snd_emu10k1_interrupt+0x377/0x400 [snd_emu10k1]
Jul 13 21:02:13 mindpipe kernel:  [handle_IRQ_event+51/96] handle_IRQ_event+0x33/0x60
Jul 13 21:02:13 mindpipe kernel:  [do_IRQ+165/368] do_IRQ+0xa5/0x170
Jul 13 21:02:13 mindpipe kernel:  [common_interrupt+24/32] common_interrupt+0x18/0x20
Jul 13 21:02:13 mindpipe kernel:  [do_anonymous_page+124/384] do_anonymous_page+0x7c/0x180
Jul 13 21:02:13 mindpipe kernel:  [do_no_page+78/784] do_no_page+0x4e/0x310
Jul 13 21:02:13 mindpipe kernel:  [handle_mm_fault+193/368] handle_mm_fault+0xc1/0x170
Jul 13 21:02:13 mindpipe kernel:  [do_page_fault+805/1356] do_page_fault+0x325/0x54c
Jul 13 21:02:13 mindpipe kernel:  [error_code+45/64] error_code+0x2d/0x40
Jul 13 21:02:13 mindpipe kernel:

Lee




                 reply	other threads:[~2004-07-14  1:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1089767321.2729.4.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --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