Yes.
> If so, what if the bug had nothing whatsoever to do with VMWARE,
> but was in fact a legit kernel bug? Is there not a way to tell
> at all?
Occasionally. Sometimes you get a clean trace and its obvious what occurred
from that you can then efficiently find bugs.
And its about efficiency. It isnt an efficienct use of my time to chase bugs
involving vmware.
> If Oops reports are 100% useless with 3rd party modules loaded,
> then that kindof sucks because it is such a useful application,
> and the source for the modules is available (comes with it).
If the modules don't enable an application to do uncontrolled stuff then
its rarely a big deal. In fact drivers have arrived in the Linux kernel
via the "I got this from my vendor but it crashes when..." route.
> "Upgrade to 2.2.12, and apply patch xxx, and yyy (please
> tell me what they are) to stabilize 2.2.12 until 2.2.13 comes
> out, then get it. Also, upgrade VMWARE to the latest released
> version."
2.2.13pre15 - which is I hope what will be 2.2.13. We've fixed a lot of bugs
including some that could cause random crashes. As to the vmware - upgrade
that later - one variable not two...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/