Mike, As a developer myself, I can fully understand the importance of this discovery!! I have no doubt that the stack trace differences you're observing are due to offset shifts from the added debug instructions (they have to be stored somewhere, after all). This is encouraging news!! Thanks for not giving up! As always: let me know if there's any way I can help the process! Cheers!
On Sun, 2019-10-13 at 18:15 -0500, Mike Isely wrote: > Diego: > I was *finally* able to reproduce the precise kernel oops you got. I had to > load the exact same > Ubuntu kernel you are using and the test had to run specifically against an > HVR-1950. The older > (simpler) device I had been trying won't fail. But with that said, I got > your exact call trace. > Now that I see the signature, I immediately tested again using a 5.2.13 > kernel.org vanilla kernel > that is larded full of printk() statements in the driver, again on an > HVR-1950. And it blew > chunks again. The signature wasn't precisely the same (stack trace is > slightly different) but > it's close enough that I believe it's the same root cause. > Now the real digging starts. > Note: This is ignoring the sysfs tear-down collision I had mentioned earlier > (which, interestingly > didn't happen this time, probably because this oops stopped the tear-down > before it got that > far). This is also with the external userspace I2C access disabled so I can > keep that source of > log noise out of the way, for now. So there's really 3 issues here. Trying > to focus on the one > that is burning you specifically. > If it turns out that what I'm seeing in the 5.2.13 kernel is actually > different, well then that > just means there are 4 problems :-( But right now I'm betting it's the same > so that's the avenue > I'm going to chase. If I run aground, then I'm going to backtrack to that > specific Ubuntu kernel > and rebuild it with all my debug code added and other config tweaks to help > with chasing the > problem. > -Mike -- Diego Rivera
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
