#9294 closed defect (invalid)

Kernel oops on VBox VM startup leading to total networking fault (reproducible)

I'm running vanilla Linux kernel 3.0, i686.

On startup of a VM with a bridged networking I get a kernel oops and networking becomes unusable from this point.

The whole OS also becomes unusable and semi-dead at this point. I can close some applications, but I cannot even reboot normally.

ifconfig hangs on invocation (entering the Zombie state).

startup.png (42.6 KB ) - added by Artem S. Tashkinov 14 years ago.: A VBox window
ooops.txt (3.7 KB ) - added by Artem S. Tashkinov 14 years ago.: kernel oops message
VBox.log (36.5 KB ) - added by Artem S. Tashkinov 14 years ago.: VBox.log

Download all attachments as: .zip

Attachment:	startup.png added

A VBox window

Attachment:	ooops.txt added

kernel oops message

Attachment:	VBox.log added

VBox.log

This seems like a duplicate of bug 8712, but I was using GCC 4.2.4 for building the kernel and the VBox modules.

I'm now rebuilding everything using GCC 4.5.2, let's see if it helps.

With GCC 4.5.2 everything works just fine.

Resolution:	→ invalid
Status:	new → closed

Note: See TracTickets for help on using tickets.