decoded problem in 2.4.22-pre10
Quoted 5 lines · Stephan von Krawczynski
Quoted 2 lines · On Tue, 5 Aug 2003 10:00:40 +0200 Stephan von Krawczynski <[email protected]>…
Hello all,
Quoted 8 lines
Quoted 4 lines
the testbox crashed again this night, unfortunately I made a mistake yesterday and started vmware once. Although only the usual modules were loaded at crash time and not the application, the kernel was tainted of course. Nevertheless I present the data:
I re-checked the setup with vmware and found out I can shoot it down in no time. So you probably should just forget about this bug report, because loading vmware modules does obviously do harm.
Any details? Were there some warning while vmmon was built?
Petr
Quoted 11 lines · On Tue, 5 Aug 2003 14:02:38 +0200 "Petr Vandrovec" <[email protected]> wrote:
Quoted 10 lines · Stephan von Krawczynski
Quoted 6 lines · On Tue, 5 Aug 2003 10:00:40 +0200 Stephan von Krawczynski <[email protected]>…
Hello all,
the testbox crashed again this night, unfortunately I made a mistake yesterday and started vmware once. Although only the usual modules were loaded at crash time and not the application, the kernel was tainted of course. Nevertheless I present the data:
Quoted 6 lines
Quoted 3 lines
I re-checked the setup with vmware and found out I can shoot it down in no time. So you probably should just forget about this bug report, because loading vmware modules does obviously do harm.
Any details? Were there some warning while vmmon was built?
Petr
Hello Petr,
at this time I can't provide you with details or exact reporting as the box has to be used for finding the 2.4.22-pre stability problem I see. And since the crashes take quite some time to occur I cannot reboot and check out what's the deal with the vmware modules.
And frankly: I find the application quite ok but tainting the kernel with the closed source modules is really something to think about, especially since there should be easy ways to avoid that completely.
Btw I already stopped using nvidia equipment completely due to not being able to produce valuable debugging output while running an nvidia-tainted kernels.
I might come back to your request for details when 2.4.22 got stable.
Regards,
Stephan