From: Alexey Klimov <klimov.linux@gmail.com>
To: video4linux-list@redhat.com
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: [PATCH 0/1] radio-mr800: fix unplug
Date: Wed, 19 Nov 2008 03:35:55 +0300 [thread overview]
Message-ID: <1227054955.2389.32.camel@tux.localhost> (raw)
Hello, all
This patch fix such thing. When you listening the radio with you
user-space application(kradio/gnomeradio/mplayer/etc) and suddenly you
unplug the device from usb port and then close application or change
frequency of the radio - a lot of oopses appear in dmesg. I also had big
problems with stability of kernel(different memory leaks, lockings) in
~30% of cases when using mplayer trying to reproduce this bug.
This thing happens with dsbr100 radio and radio-mr800. I told about this
thing to Douglas Schilling Landgraf and then he suggested right decision
for dsbr100. He told me that he get ideas of preventing this bug from
Tobias radio-si470x driver. Hopefully this bug didn't show up in
radio-si470x. Well, i used Douglas suggestion and code of si470x and
made this patch.
Douglas said that he's going to create patch for dsbr100.
Patch places a lof of safety checks in functions, adds disconnect_lock
mutex and changes disconnect and release functions of module. May be
it's good to add it to 2.6.28 because it fixes an issue.
I tested this thing under 2.6.28-rc5.
--
Best regards, Klimov Alexey
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-11-19 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 0:35 Alexey Klimov [this message]
2008-11-20 3:31 ` [PATCH 0/1] radio-mr800: fix unplug Douglas Schilling Landgraf
2008-11-20 7:42 ` Alexey Klimov
2008-11-20 14:33 ` Douglas Schilling Landgraf
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=1227054955.2389.32.camel@tux.localhost \
--to=klimov.linux@gmail.com \
--cc=mchehab@redhat.com \
--cc=video4linux-list@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