From: Antti Palosaari <crope@iki.fi>
To: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Cc: mchehab@redhat.com, linux-media@vger.kernel.org
Subject: Re: unload/unplugging (Re: success! (Re: media_build and Terratec Cinergy T Black.))
Date: Sat, 07 Jul 2012 12:42:49 +0300 [thread overview]
Message-ID: <4FF80499.4010808@iki.fi> (raw)
In-Reply-To: <1341627993.41434.YahooMailClassic@web29403.mail.ird.yahoo.com>
Hello Hin-Tak
On 07/07/2012 05:26 AM, Hin-Tak Leung wrote:
> BTW, I tried just pulling the USB stick out while mplayer is running. Strangely enough mplayer did not notice it gone and kept going for some 5 to 10 seconds. Probably buffering?
yes
> The only sign about it is two lines in dmesg (other than the usual usb messages about device being unplug).
>
> [227690.953311] rtl2832: i2c rd failed=-19 reg=01 len=1
> [227710.818089] usb 1-2: dvb_usbv2: streaming_ctrl() failed=-19
Jul 7 12:40:42 localhost kernel: [ 906.030829] usb 2-2: USB
disconnect, device number 4
Jul 7 12:40:42 localhost kernel: [ 906.035518] rtl2832: i2c rd
failed=-19 reg=01 len=1
Next application kills (I think so) and closes file nodes => device is
unloaded:
Jul 7 12:40:49 localhost kernel: [ 912.751437] usb 2-2: dvb_usbv2:
streaming_ctrl() failed=-19
Jul 7 12:40:49 localhost kernel: [ 912.751981] usb 2-2: dvb_usbv2:
'Terratec Cinergy T Stick Black' successfully deinitialized and disconnected
> I also have quite a few :
>
> [224773.229293] DVB: adapter 0 frontend 0 frequency 2 out of range (174000000..862000000)
>
> This seems to come from running w_scan.
yes, those warnings are coming when application request illegal
frequency. Setting frequency as a 2 Hz is something totally wrong, wild
guess, it is some other value set accidentally as frequency.
> The kernel seems happy while having the device physically pulled out. But the kernel module does not like to be unloaded (modprobe -r) while mplayer is running, so we need to fix that.
Yep, seems to refuse unload. I suspect it is refused since there is
ongoing USB transmission as it streams video. But should we allow that?
And is removing open device nodes OK as applications holds those?
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-07-07 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 10:54 media_build and Terratec Cinergy T Black Hin-Tak Leung
2012-07-06 11:01 ` Hin-Tak Leung
2012-07-06 11:38 ` Antti Palosaari
2012-07-06 21:06 ` Hin-Tak Leung
2012-07-07 0:42 ` bugs in dvbscan/scan, dvb-apps(Re: media_build and Terratec Cinergy T Black.) Hin-Tak Leung
2012-07-07 2:11 ` success! (Re: " Hin-Tak Leung
2012-07-07 2:26 ` unload/unplugging (Re: success! (Re: media_build and Terratec Cinergy T Black.)) Hin-Tak Leung
2012-07-07 9:42 ` Antti Palosaari [this message]
2012-07-07 10:10 ` Hin-Tak Leung
2012-07-07 10:26 ` Antti Palosaari
2012-07-07 10:47 ` Hin-Tak Leung
2012-07-07 10:03 ` success! (Re: media_build and Terratec Cinergy T Black.) Antti Palosaari
2012-07-07 10:37 ` channel scanning (Re: success! (Re: media_build and Terratec Cinergy T Black.)) Hin-Tak Leung
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=4FF80499.4010808@iki.fi \
--to=crope@iki.fi \
--cc=hintak_leung@yahoo.co.uk \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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;
as well as URLs for NNTP newsgroup(s).