[pvrusb2] Looking for kernel oops evidence...
Mike Isely
isely at isely.net
Sat Sep 10 06:19:33 CDT 2005
On Sat, 10 Sep 2005, Mike Isely wrote:
> On Sat, 10 Sep 2005 xavier.gnata at free.fr wrote:
>
> >
> > Hi,
> >
> > It looks strange...
> > I have try to plug/unplug the card very quickly but I can't reprodude that :(
> > We may add a debug test just before this line to store important pointers values
> > into the logs when sp is NULL (ok that is trivial so not very helpful ;))
> > @+
> > Xavier
>
> I just spent most of last night chasing this. So far I've been unable to
> reproduce the problem.
>
> I in fact implemented something similar to what you described. I added a
> signature word to the structure which is being checked now in front of a
> number of functions. If the check fails, the code will print the file
> name and line number of the failure along with the contents of the buffer
> and then it should force an oops. I've been running mplayer against this
> version of the driver now for the past 6 hours and it's still working
> perfectly.
>
> BTW, while inspecting the code last night for this problem, I found a
> memory leak. I'll have a new snapshot with that fixed before the weekend
> is over (no time this morning but hopefully tonight). The leak happens
> when streaming is stopped - the control buffers are not being freed but
> their pointers are being tossed. This is obviously a bad problem.
>
> -Mike
Oh, and I am definitely seeing a problem where unplugging the cable while
mplayer is running will result in a kernel oops. But the symptoms and
conditions are different than this oops report I'm looking at so that at
least is a different problem. When the cable is yanked, I get the oops
right after saa7115.ko disconnects from the driver. I will also try to
chase that one down tonight.
--
| Mike Isely | PGP fingerprint
Spammers Die!! | | 03 54 43 4D 75 E5 CC 92
| isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8
| |
More information about the pvrusb2
mailing list