> structures in an inconsistent state upon failure. Module unloading > simply shouldn't fail or cause kernel corruption, IMO. I assume ivtvfb > emitted "Framebuffer 0 is in use, cannot unload" in one of your logs. > > Regards, > Andy >
no, "rmmod ivtv" or "modprobe -r ivtv" didn't gave any error. Unloading ivtvfb was successful, because a second try gave "ERROR: Module ivtvfb does not exist in /proc/modules ". The kernel oops was not caused by unloading ivtvfb. The oops seems to happen, when the application trys to open the still existing /dev/fb0. The pvr350 uses this code http://ivtvdriver.org/viewcvs/ivtv/trunk/doc/conversion.txt?rev=3908&r1=3906&r2=3908 It founds the still persisting first /dev/fb number and this results in an oops when opening the device. > If this is the problem I'm thinking of, it's a long standing bug that was > reported once before, though not to this list. I'll admit that I'd forgotten > about it until it was mentioned here. > > It appeared to be linked to the kernel config. Using my normal config, > unloading the ivtvfb module would remove the entry from /proc/fb. With the > offending config, although the module would unload, the /proc/fb entry would > persist. At the time, I was able to reproduce this using another framebuffer > driver, which implied the bug was not in the ivtvfb code itself. > > In the event that an error occurs when trying to unregister the framebuffer, > the ivtvfb module should issue a warning, but behaviour beyond this point is > undefined. Given that you shouldn't be able to unload the module if the > framebuffer is in use, this situation should never arise. > > -- > Ian The problem seems to be that ivtvfb does not "know" that it is used by the console (have no other idea why the /proc/fb keeps existing), therefore giving no error when trying to unload it. I was using "fbcon=map:2" .This should disable the framebuffer console and prevent ivtvfb from being used for console. Obviously this doesn't work as expected. _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
