Bug 4962
| Summary: | b2c2-flexcop stops outputting data | ||
|---|---|---|---|
| Product: | v4l-dvb | Reporter: | Ruslan (br) |
| Component: | v4l-other | Assignee: | Mauro Carvalho Chehab (mchehab) |
| Status: | REJECTED INSUFFICIENT_DATA | ||
| Severity: | normal | CC: | akpm, alexn, bunk, protasnb |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.13-rc3 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
|
Description
Ruslan
2005-07-29 01:35:46 UTC
A bunch of patches went into the flexcop driver between 2.6.13-rc2 and 2.6.13-rc3. Are you able to test 2.6.13-rc2? Thanks. ok, i will test 2.6.13-rc2. 2.6.11 kernel (standart in FedoraCore4) skystar2.ko cause system freeze if i try to rmmod -f From the helptext of rmmod:
-f (or --force) forces a module unload, and may crash your
machine. This requires the Forced Module Removal option
when the kernel was compiled.
Why are you still using it? Doesn't it get removed without it? Something may
hold reference counts to it and removing it with force then is bad.
so how then i can reload modules if skystar2 freeze? rmmod modprobe -r resulted "resource temproray unavable" The real problem is that the driver freezes in the first place. When that happens the next time please press alt+sysrq+t 3-4 times, run dmesg -s 10000, include that output in a report where you describe your problems and send it to: DVB SUBSYSTEM AND DRIVERS P: LinuxTV.org Project M: linux-dvb-maintainer@linuxtv.org L: linux-dvb@linuxtv.org (subscription required) W: http://linuxtv.org/developer/dvb.xml S: Supported bugme-daemon@kernel-bugs.osdl.org wrote: > > The real problem is that the driver freezes in the first place. When that > happens the next time please press alt+sysrq+t 3-4 times, run dmesg -s 10000, > include that output in a report where you describe your problems and send it to: Make that `dmesg -s 1000000'. The initial bug report mixes two things: - "usually (1 or 2 time in day) freeze": I guess this is a well known bug where the hardware stops to generate interrupts for some unknown reason (we believe it is a hardware issue but people claim that it never happens with the Windows driver). The flexcop-pci driver recently added a workaround which resets the PID filter block in the demux everytime we tune to a different transport stream, which helped a lot. Apparently this won't help if you never tune (which is likely when using dvb_net). As a workaround one could add a watchdog and reset the pid filter block when the card stops generating irqs for a while. Please send patches. - one needs to stop the dvb_net interface with ifconfig and release the interface with the dvbnet utility before the driver can be unloaded; forcing an unload naturally leads to Oopses. I believe the module refcount handling is correct, if someone manages to get an Oops please post it I tried to put a more sensible title on this bug, but failed ... could someone who understands what's going on here update the summary field please? Would be nice to have something other than "?" in akpm's tracking list ... summary should be changed from "b2c2-flexcop module freezes" to "b2c2-flexcop stops outputting data" severity should be changed to "normal" as this bug is uncritical, just annoying however, bugzilla prevents me from doing so myself, only the owner or submitter are allowed change these fields :-( This mistake also is present at version 2.6.20.3. Ruslan, Evgeniy and others who had this problem - has it been resolved for you in recent kernels, 2.6.23+ as of now? Thanks. |