From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] S2API: problem unloading dvb_ttpci
Date: Sat, 13 Dec 2008 13:56:21 +0100 [thread overview]
Message-ID: <4943B0F5.2090306@cadsoft.de> (raw)
In-Reply-To: <4927F9D0.4050004@cadsoft.de>
On 22.11.2008 13:23, Klaus Schmidinger wrote:
> On 22.11.2008 13:07, Klaus Schmidinger wrote:
>> I'm making my first steps in using the S2API driver, and already
>> have a problem. When trying to do
>>
>> /sbin/rmmod dvb_ttpci
>>
>> I get the error
>>
>> ERROR: Removing 'dvb_ttpci': Device or resource busy
>>
>> 'lsmod' shows
>>
>> Module Size Used by
>> dvb_ttpci 348748 0
>>
>> So who is using dvb_ttpci?
>
> After rebooting and doing one more test, I got this when
> running /sbin/rmmod dvb_ttpci:
>
> Nov 22 13:21:35 vdr2 kernel: saa7146: unregister extension 'dvb'.
> Nov 22 13:21:35 vdr2 kernel: PANIC: double fault, gdt at c2015000 [255 bytes]
> Nov 22 13:21:35 vdr2 kernel: double fault, tss at c2017780
> Nov 22 13:21:35 vdr2 kernel: eip = f7881416, esp = bf88921e
> Nov 22 13:21:35 vdr2 kernel: eax = f7881408, ebx = f6df6cc8, ecx = f7401a7f, edx = f788144d
> Nov 22 13:21:35 vdr2 kernel: esi = f7881409, edi = f79231c1
>
> Looks like the S2API driver isn't in a state where it can actually be used, yet...
Just for the record: it turned out that there was a mixup between DVB driver
files from my SUSE 11.0 installation and the self-compiled driver source.
After making sure only the self-compiled driver files were loaded, I was
able to load/unload the S2API driver.
Sorry about the noise...
Klaus
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-12-13 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 12:07 [linux-dvb] S2API: problem unloading dvb_ttpci Klaus Schmidinger
2008-11-22 12:23 ` Klaus Schmidinger
2008-12-13 12:56 ` Klaus Schmidinger [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=4943B0F5.2090306@cadsoft.de \
--to=klaus.schmidinger@cadsoft.de \
--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 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.