From: "Professor Moriarty" <bofh.h4x@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: irq event 5: bogus return value 19
Date: Sun, 30 Apr 2006 12:19:50 -0700 [thread overview]
Message-ID: <2a56523e0604301219s67244272n7e8ee7c634a1933c@mail.gmail.com> (raw)
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?
~ Vasily Ivanov
next reply other threads:[~2006-04-30 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 19:19 Professor Moriarty [this message]
2006-04-30 20:28 ` Jiri Slaby
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=2a56523e0604301219s67244272n7e8ee7c634a1933c@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®