From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] CX88 IRQ Loop
Date: Mon, 22 Sep 2008 23:38:31 +0100 [thread overview]
Message-ID: <4FE87384AC%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAACQaAAE2cqNLuI5vSe3nryTCgAAAEAAAAEH2unQOalpGjvGmwr9GMIQBAAAAAA==@stahurabrenner.com>
I demand that Timothy E. Krantz may or may not have written...
> I am getting the following problems as reported in dmesg.
> Any help would be appreciated.
> Linux video capture interface: v2.00
> cx2388x alsa driver version 0.0.6 loaded
> ACPI: PCI Interrupt 0000:00:09.1[A] -> GSI 17 (level, low) -> IRQ 20
> cx88[0]: subsystem: 11bd:0051, board: Pinnacle PCTV HD 800i
[snip]
> xc5000: firmware upload
[snip]
> NVRM: loading NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008
[snip]
> ndiswrapper version 1.51 loaded (smp=yes, preempt=no)
> usb 1-5: reset high speed USB device using ehci_hcd and address 2
> ndiswrapper: driver netmw245 (Marvell,11/27/2006,1.0.4.9) loaded
[snip]
> cx88[0]/2-mpeg: general errors: 0x00140000
> cx88[0]/2-mpeg: clearing mask
> cx88[0]/0: irq loop -- clearing mask
[snip]
> cx88[0]: irq mpeg [0xa0000] par_err* pci_abort*
> cx88[0]/2-mpeg: general errors: 0x000a0000
> irq 20: nobody cared (try booting with the "irqpoll" option)
> Pid: 0, comm: swapper Tainted: P 2.6.24.4-64.fc8 #1
> [<c04612be>] __report_bad_irq+0x36/0x75
> [<f15a3a16>] nv_kern_isr+0xa5/0xb2 [nvidia]
Oh dear. I do believe that that's within nVidia's proprietary driver.
And you're using ndiswrapper, and it's loaded a driver module. That's another
source of kernel taint. This raises the possibility of some interaction
between the two, which basically You Don't Want To See. Ever.
Which isn't good because one or other, or some interaction between them, is a
possible source of the problem. So you need to be able to produce this
without one or both taint sources: without one, it's likely caused by the
other piece of taintware; without both, you know that the problem isn't
caused by taintware (it's either a cx88 driver bug or a hardware fault). If,
however, it only ever happens with both lots of taint applied, you have a
problem somewhere between nVidia and either ndiswrapper or netwm245 – good
luck ;-)
(Taint removal: prevent the taintware from being loaded, then reboot.)
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + At least 4000 million too many people. POPULATION LEVEL IS UNSUSTAINABLE.
Hire the morally handicapped.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-22 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 13:27 [linux-dvb] CX88 IRQ Loop Timothy E. Krantz
2008-09-22 22:38 ` Darren Salt [this message]
2008-09-23 12:42 ` Timothy E. Krantz
2008-09-23 14:55 ` [linux-dvb] Start making stv0903, stv0900, stv6110 support Igor M. Liplianin
2008-09-23 15:16 ` Manu Abraham
2008-09-23 15:48 ` Igor M. Liplianin
2008-09-23 15:59 ` Manu Abraham
2008-09-23 16:15 ` Igor M. Liplianin
2008-09-23 17:10 ` Darren Salt
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=4FE87384AC%linux@youmustbejoking.demon.co.uk \
--to=linux@youmustbejoking.demon.co.uk \
--cc=linux-dvb@linuxtv.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