https://bugzilla.novell.com/show_bug.cgi?id=848599 https://bugzilla.novell.com/show_bug.cgi?id=848599#c15 --- Comment #15 from Borislav Petkov <bpetkov@suse.com> 2014-07-04 19:58:50 UTC ---
You see, the test from the virtual Linux was also correct.
You're missing the point - you can't know whether vmware is doing proper passthrough to the guest kernel for that device so that we can be absolutely sure the communication between device and kernel happens unhindered. Especially if it is proprietary crap. So, for the future I'd strongly advise you to leave out vmware from any testing when reporting kernel bugs - otherwise people won't look at them. Now, on to the issue at hand: if you can reproduce it with the upstream kernel, you're best helped with if you open a bug report at bugzilla.kernel.org, against the proper component, v4l2 or so... There you have the v4l people who should be able to help you. If/when you get a fix there, please let us know so that we can apply it on the oS kernel too. HTH and thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.