Jochen, On Wednesday 13 August 2008, Jochen Roderburg wrote: > Mostly "self-made" Linux with a Slackware core system (current version > 12.1). Stock Linux Kernels 2.6.25/2.6.26, self-compiled with gcc > 4.2.3/4.3.1 > > On the danger, that we follow a wrong track now: I can well imagine > that compiler errors could produce wrong code somewhere in the kernel > itself leading to such strange errors. I remember old days when Linux > kernels often could only be compiled successfully with specific > compiler versions. :-( > I have a number of kernels and compilers at hand for experiments in > such a direction, but I think I would need some time for that.
I trust both compilers (I use them myself). We still didn't test Linux 2.6.26 in detail. 2.6.25 works fine here (and I don't expect that 2.6.26 would not). > > Strange. I assume there is nothing in the VBox.log file? Is the > > connection to the outside broken after your started writing to > > the share? And does it remain broken or can you restore the > > connection by some activity? > > No, nothing in the log file. > Nothing broken with the net connection as such. After such write > errors all other net activities work normal. Hmm, so it seems like some network packets are dropped. > > Do you have VT-x / AMD-V enabled for your VM? Please check your > > VM session information window (if the mode cannot be used we silently > > fall back to the raw mode). > > Not enabled. CPU is Intel Core2 6600. You could try to enable it just to make sure. It shouldn't make any difference but who knows ... Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
