From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Ross Alexander <ross.alexander@uk.neceur.com>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org
Subject: Re: Kernel oops with 2.6.21 while using cdda2wav & cooked_ioctl (x64-64) [untainted]
Date: Mon, 30 Apr 2007 21:39:44 +0600 [thread overview]
Message-ID: <46360DC0.2010404@ums.usu.ru> (raw)
In-Reply-To: <4635F462.30202@uk.neceur.com>
Ross Alexander wrote:
[warning: all of the below is just generic bug triage, I have no idea what
is really wrong]
> Call Trace:
> run_timer_softirq+0x156/0x1ac
> __do_softirq+0x50/0xbb
> call_softirq+0x1c/02x8
> do_softieq+0x2f/x097
> irq_exit+0x3d/0x4f
> smp_apic_timer_interrupt+0x46/0x58
> default_idle+0x0/0x3d
> apic_timer_interrupt+0x66/0x70
> <EOI> default_idle+0x29/0x3d
> cpu_idle+0x8b/0xcc
> start_kernel+0x266/0x26f
> _sinittext+0x175/0x179
Thanks, but this has nothing specific to extracting CD audio, and is
unrelated to the panic message you originally sent. I.e.: we have two
reports from you, one tainted about CD grabbing, and one untainted about
some generic IRQ-related issue. Could you please try producing an untainted
oops with the word scsi in one of the lines?
Maybe you are just causing the drive to try hard reading data that don't
exist, and thus deliver the IRQ at unusual time? Is this reproducible on
non-SMP kernels?
--
Alexander E. Patrakov
next prev parent reply other threads:[~2007-04-30 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 8:02 Kernel oops with 2.6.21 while using cdda2wav & cooked_ioctl (x64-64) Ross Alexander
2007-04-28 3:46 ` Alexander E. Patrakov
2007-04-30 13:51 ` Kernel oops with 2.6.21 while using cdda2wav & cooked_ioctl (x64-64) [untainted] Ross Alexander
2007-04-30 15:39 ` Alexander E. Patrakov [this message]
2007-05-04 8:16 ` Ross Alexander
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=46360DC0.2010404@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.alexander@uk.neceur.com \
/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