On Sat, Oct 20, 2012 at 10:32:28PM +0200, Pavel Machek wrote:
On Sat 2012-10-20 17:41:49, Artem S. Tashkinov wrote:
quoted
On Oct 20, 2012, Borislav Petkov wrote:
quoted
Yeah, your kernel is tainted with a proprietary module (vbox*, etc). Can
you reproduce your corruptions (this is what it looks like) without that
module?
Yes, I can reproduce this panic with zero proprietary/non-free modules loaded.
The problem is the kernel doesn't even print a kernel panic - the
system just freezes completely - cursor in a text console stops
blinking.
bugtraq? :-).
If remote website can crash your Linux, that's quite significant news.
(Cc-ed netdev@ and security@ ... this may be important).
I don't think that's the problem - I rather suspect the fact that he's
using virtualbox which is causing random corruptions by writing to
arbitrary locations.
Artem,
please remove virtualbox completely from your system, rebuild the kernel
and make sure the virtualbox kernel modules don't get loaded - simply
delete them so that they are completely gone; *and* *then* retest again.
Thanks.
--
Regards/Gruss,
Boris.