All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Professor Moriarty <bofh.h4x@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: irq event 5: bogus return value 19
Date: Sun, 30 Apr 2006 22:27:39 +0159	[thread overview]
Message-ID: <44551DD2.3080708@gmail.com> (raw)
In-Reply-To: <2a56523e0604301219s67244272n7e8ee7c634a1933c@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Professor Moriarty napsal(a):
> On debugging a soundcard driver (the Riptide driver from linuxant,
> ported by me to 2.6), I seem to have 2 weird bugs that are giving me a
> headache:
> Both occur when I try to actually play a file
> The first: ppos != &file->f_pos
> If I comment that check out, I get a kernelpanic. If I comment out the
> schedule_work() to run the bottom half of the IRQ handler, I get the
> message:
> irq event 5: bogus return value 19
> Followed by:
> kernel: Disabling IRQ #5
> At this point, the first 4K of raw PCM plays, and then /dev/dsp
> blocks, while the speakers repeat the 4K of data repeatedly until I
> ctrl+C mplayer. Trying to cat data to /dev/dsp plays first 4K, then
> cat says /dev/dsp is out of space.
> 
> Any ideas?
Give us (at least parts of) the code and then we can tell you, now it may be
like a shot in the dark.

regards,
- --
Jiri Slaby         www.fi.muni.cz/~xslaby
\_.-^-._   jirislaby@gmail.com   _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFEVR3SMsxVwznUen4RAgDzAJ9pSjjRRzeiD5PYgF1eon1Q6dYmEwCeOVRN
pmURuwCGXGVXwUN2Qbafvn0=
=5Tj8
-----END PGP SIGNATURE-----

      reply	other threads:[~2006-04-30 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30 19:19 irq event 5: bogus return value 19 Professor Moriarty
2006-04-30 20:28 ` Jiri Slaby [this message]

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=44551DD2.3080708@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=bofh.h4x@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.