SOLVED: virtualbox 3.2.0 flooding my logs with systraces

Discussions related to using VirtualBox on Linux hosts.

SOLVED: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 2. Jun 2010, 10:08

I am getting a lot of these messages below after upgrading to virtualbox 3.2.0 (3.1.6 was ok)
gentoo 10 x64, all updates, kernel 2.6.33-vanilla and 2.6.34-gentoo

problem seems to happen when network operations involved (not all though) - noticed with:
- clicking links in internet explorer/firefox (in guest)
- connecting by rdp

but does not seem to happen when using ftp or wireshark(?)

host os and guests seem to run fine, so flooding seems to be the only symptom so far. very annoying though. there might be other one - guest having problems with shutting down completely.

i was googling for it, also in here and bug reports and found nothing so far.

what do you guys think? does anybody else have this? shall i open bug report for this - here or for gentoo devs?

Jun 2 08:51:56 gizmo kernel: ------------[ cut here ]------------
Jun 2 08:51:56 gizmo kernel: WARNING: at net/core/dev.c:1737 skb_gso_segment+0xf9/0x239()
Jun 2 08:51:56 gizmo kernel: Hardware name: OEM
Jun 2 08:51:56 gizmo kernel: asix: caps=(0x0, 0x0) len=11434 data_len=0 ip_summed=1
Jun 2 08:51:56 gizmo kernel: Modules linked in: vboxnetadp vboxnetflt vboxdrv f71882fg coretemp hwmon cryptd aes_x86_64 aes_generic 8021q ipt_LOG xt_state iptable_filter xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 iptable_mangle ipt_addrtype xt_dscp xt_string xt_owner xt_multiport xt_mark xt_iprange xt_hashlimit xt_conntrack xt_connmark xt_DSCP xt_NFQUEUE xt_MARK xt_CONNMARK nf_conntrack ip_tables x_tables dahdi_echocan_mg2 wctdm dahdi crc_ccitt ipv6 reiserfs arc4 sr_mod cdrom ath9k ath9k_common mac80211 ath9k_hw ath cfg80211 snd_hda_codec_intelhdmi rtc_cmos iTCO_wdt asix rtc_core i2c_i801 usbnet led_class r8169 snd_hda_codec_realtek i2c_core pcspkr iTCO_vendor_support rtc_lib sg pata_jmicron snd_hda_intel snd_hda_codec snd_hwdep fan processor snd_pcm snd_timer snd soundcore psmouse snd_page_alloc thermal button ehci_hcd uhci_hcd thermal_sys usbcore
Jun 2 08:51:56 gizmo kernel: Pid: 7020, comm: VBoxHeadless Tainted: G W 2.6.34-gentoo-01 #1
Jun 2 08:51:56 gizmo kernel: Call Trace:
Jun 2 08:51:56 gizmo kernel: <IRQ> [<ffffffff8121bd01>] ? skb_gso_segment+0xf9/0x239
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121bd01>] ? skb_gso_segment+0xf9/0x239
Jun 2 08:51:56 gizmo kernel: [<ffffffff8102bc08>] ? warn_slowpath_common+0x77/0xa3
Jun 2 08:51:56 gizmo kernel: [<ffffffff8102bc90>] ? warn_slowpath_fmt+0x51/0x59
Jun 2 08:51:56 gizmo kernel: [<ffffffffa02c478a>] ? ipt_do_table+0x59f/0x5da [ip_tables]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa01331d7>] ? usbnet_get_drvinfo+0x50/0x7f [usbnet]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0148688>] ? asix_get_drvinfo+0x3c/0x51 [asix]
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121bd01>] ? skb_gso_segment+0xf9/0x239
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121bffb>] ? dev_hard_start_xmit+0x1ba/0x301
Jun 2 08:51:56 gizmo kernel: [<ffffffff8122c64e>] ? sch_direct_xmit+0x5a/0x15b
Jun 2 08:51:56 gizmo kernel: [<ffffffff8124109d>] ? ip_finish_output+0x0/0x28b
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121c4fe>] ? dev_queue_xmit+0x2bb/0x417
Jun 2 08:51:56 gizmo kernel: [<ffffffff8123c671>] ? ip_rcv_finish+0x321/0x33b
Jun 2 08:51:56 gizmo kernel: [<ffffffff8123c8f2>] ? ip_rcv+0x267/0x2a3
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121b5cd>] ? process_backlog+0x73/0xa1
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121b751>] ? net_rx_action+0x69/0x11d
Jun 2 08:51:56 gizmo kernel: [<ffffffff810304f1>] ? __do_softirq+0x8b/0x106
Jun 2 08:51:56 gizmo kernel: [<ffffffff81002ccc>] ? call_softirq+0x1c/0x28
Jun 2 08:51:56 gizmo kernel: <EOI> [<ffffffff810046d5>] ? do_softirq+0x31/0x63
Jun 2 08:51:56 gizmo kernel: [<ffffffff8121bbd3>] ? netif_rx_ni+0x19/0x1d
Jun 2 08:51:56 gizmo kernel: [<ffffffffa056a02f>] ? vboxNetFltPortOsXmit+0x7a/0x97 [vboxnetflt]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa056a9e9>] ? vboxNetFltRelease+0x297/0x386 [vboxnetflt]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa040752e>] ? g_abExecMemory+0x375ce/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0413efe>] ? g_abExecMemory+0x43f9e/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03edc74>] ? g_abExecMemory+0x1dd14/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03d8ca1>] ? g_abExecMemory+0x8d41/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03d8ca1>] ? g_abExecMemory+0x8d41/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03c61c2>] ? RTSpinlockAcquireNoInts+0xd/0x12 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0412aad>] ? g_abExecMemory+0x42b4d/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0414c37>] ? g_abExecMemory+0x44cd7/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0412652>] ? g_abExecMemory+0x426f2/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa041576a>] ? g_abExecMemory+0x4580a/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0444478>] ? g_abExecMemory+0x74518/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0444f2f>] ? g_abExecMemory+0x74fcf/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0445f92>] ? g_abExecMemory+0x76032/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa044642b>] ? g_abExecMemory+0x764cb/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa04464cd>] ? g_abExecMemory+0x7656d/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03e952d>] ? g_abExecMemory+0x195cd/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03ea6e7>] ? g_abExecMemory+0x1a787/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03d8ca1>] ? g_abExecMemory+0x8d41/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03edc74>] ? g_abExecMemory+0x1dd14/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03eb930>] ? g_abExecMemory+0x1b9d0/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03ff089>] ? g_abExecMemory+0x2f129/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03fd210>] ? g_abExecMemory+0x2d2b0/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03dfa4d>] ? g_abExecMemory+0xfaed/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffff81034e56>] ? process_timeout+0x0/0x5
Jun 2 08:51:56 gizmo kernel: [<ffffffff8103dc76>] ? prepare_to_wait+0x19/0x73
Jun 2 08:51:56 gizmo kernel: [<ffffffff8103dac0>] ? autoremove_wake_function+0x0/0x2e
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03d6a8a>] ? g_abExecMemory+0x6b2a/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03e3470>] ? g_abExecMemory+0x13510/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03ddc1b>] ? g_abExecMemory+0xdcbb/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03d8c42>] ? g_abExecMemory+0x8ce2/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa0412217>] ? g_abExecMemory+0x422b7/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03e2d1e>] ? g_abExecMemory+0x12dbe/0x180000 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03bc441>] ? supdrvIOCtlFast+0x41/0x53 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffffa03bc220>] ? SUPR0Printf+0xdd/0x232 [vboxdrv]
Jun 2 08:51:56 gizmo kernel: [<ffffffff810995d2>] ? vfs_ioctl+0x21/0x92
Jun 2 08:51:56 gizmo kernel: [<ffffffff81099acd>] ? do_vfs_ioctl+0x414/0x44c
Jun 2 08:51:56 gizmo kernel: [<ffffffff8104b58a>] ? sys_futex+0x113/0x131
Jun 2 08:51:56 gizmo kernel: [<ffffffff81099b42>] ? sys_ioctl+0x3d/0x5c
Jun 2 08:51:56 gizmo kernel: [<ffffffff81001eab>] ? system_call_fastpath+0x16/0x1b
Jun 2 08:51:56 gizmo kernel: ---[ end trace 8f28366478322075 ]---
Last edited by bodo on 13. Aug 2010, 18:47, edited 1 time in total.
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby Nemykal » 2. Jun 2010, 15:44

Getting this exact issue. See: http://pastebin.com/j84ZkxSP

Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785835] ------------[ cut here ]------------
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785840] WARNING: at net/core/dev.c:1688 skb_gso_segment+0x1da/0x2b0()
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785842] Hardware name: System Product Name
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785844] : caps=(0x2000, 0x0) len=8800 data_len=0 ip_summed=1
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785845] Modules linked in: vboxnetadp vboxnetflt vboxdrv ppp_deflate bsd_comp pppoe pppox pppoatm ppp_generic slhc br2684 solos_pci
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785852] Pid: 25541, comm: VBoxHeadless Tainted: G W 2.6.33-zen2-remilia-zen #2
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785854] Call Trace:
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785855] <IRQ> [<ffffffff8103aa48>] warn_slowpath_common+0x78/0xb0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785861] [<ffffffff8103aadc>] warn_slowpath_fmt+0x3c/0x40
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785863] [<ffffffff815ad6da>] skb_gso_segment+0x1da/0x2b0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785866] [<ffffffff8167320a>] ? tcp_manip_pkt+0xca/0x100
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785869] [<ffffffff815ad956>] dev_hard_start_xmit+0x1a6/0x370
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785872] [<ffffffff815c281e>] sch_direct_xmit+0xde/0x190
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785875] [<ffffffff815ae057>] dev_queue_xmit+0x3e7/0x570
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785878] [<ffffffff8162f27f>] ip_finish_output+0x20f/0x300
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785880] [<ffffffff8162f3e2>] ip_output+0x72/0xb0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785883] [<ffffffff8162ade8>] ip_forward_finish+0x38/0x50
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785885] [<ffffffff8162b003>] ip_forward+0x203/0x3f0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785887] [<ffffffff81629435>] ip_rcv_finish+0x105/0x410
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785890] [<ffffffff815ac94a>] ? netif_receive_skb+0x30a/0x580
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785892] [<ffffffff81629961>] ip_rcv+0x221/0x2f0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785895] [<ffffffff815ac94a>] netif_receive_skb+0x30a/0x580
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785898] [<ffffffff815acc34>] process_backlog+0x74/0xc0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785900] [<ffffffff815ad3db>] net_rx_action+0xdb/0x190
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785904] [<ffffffffa0019e32>] ? ppp_output_wakeup+0x12/0x20 [ppp_generic]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785907] [<ffffffff81040a96>] __do_softirq+0xa6/0x130
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785910] [<ffffffff81003c4c>] call_softirq+0x1c/0x30
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785911] <EOI> [<ffffffff81005dcd>] ? do_softirq+0x4d/0x80
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785915] [<ffffffff815ad4b8>] netif_rx_ni+0x28/0x30
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785918] [<ffffffffa02163aa>] vboxNetFltPortOsXmit+0xaa/0xd0 [vboxnetflt]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785921] [<ffffffffa0216bae>] vboxNetFltPortXmit+0x5e/0x1d0 [vboxnetflt]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785924] [<ffffffff8103332d>] ? resched_best_idle+0x15d/0x170
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785932] [<ffffffffa00a34be>] g_abExecMemory+0x43f9e/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785934] [<ffffffff816f948e>] ? common_interrupt+0xe/0x13
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785943] [<ffffffffa0053380>] ? RTSpinlockReleaseNoInts+0x10/0x20 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785951] [<ffffffffa00a206d>] ? g_abExecMemory+0x42b4d/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785958] [<ffffffffa00a41f7>] g_abExecMemory+0x44cd7/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785966] [<ffffffffa0048bef>] ? SUPR0ObjAddRefEx+0x14f/0x220 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785973] [<ffffffffa00a1c12>] ? g_abExecMemory+0x426f2/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785980] [<ffffffffa00a4d2a>] g_abExecMemory+0x4580a/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785988] [<ffffffffa00d3a38>] g_abExecMemory+0x74518/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.785995] [<ffffffffa00d44ef>] g_abExecMemory+0x74fcf/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786002] [<ffffffffa00d5552>] g_abExecMemory+0x76032/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786010] [<ffffffffa00d59eb>] g_abExecMemory+0x764cb/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786017] [<ffffffffa00d5a8d>] g_abExecMemory+0x7656d/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786024] [<ffffffffa0078aed>] ? g_abExecMemory+0x195cd/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786032] [<ffffffffa0079ca7>] g_abExecMemory+0x1a787/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786039] [<ffffffffa008b591>] ? g_abExecMemory+0x2c071/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786046] [<ffffffffa007aef0>] ? g_abExecMemory+0x1b9d0/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786054] [<ffffffffa008cf43>] g_abExecMemory+0x2da23/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786061] [<ffffffffa0070ed4>] g_abExecMemory+0x119b4/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786068] [<ffffffffa006e48e>] g_abExecMemory+0xef6e/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786071] [<ffffffff810466a0>] ? process_timeout+0x0/0x10
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786074] [<ffffffff81056499>] ? up+0x29/0x50
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786083] [<ffffffffa0052b64>] ? RTSemFastMutexRelease+0x44/0x50 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786090] [<ffffffffa006616d>] ? g_abExecMemory+0x6c4d/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786098] [<ffffffffa006d1db>] ? g_abExecMemory+0xdcbb/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786105] [<ffffffffa0068202>] g_abExecMemory+0x8ce2/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786112] [<ffffffffa00a17d7>] g_abExecMemory+0x422b7/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786119] [<ffffffffa00722de>] g_abExecMemory+0x12dbe/0x180000 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786126] [<ffffffffa004792a>] supdrvIOCtlFast+0x6a/0x70 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786133] [<ffffffffa00472e7>] VBoxDrvLinuxIOCtl+0x47/0x1c0 [vboxdrv]
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786136] [<ffffffff810e9fa8>] vfs_ioctl+0x38/0xd0
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786138] [<ffffffff810ea150>] do_vfs_ioctl+0x80/0x560
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786141] [<ffffffff816f6a91>] ? schedule+0x321/0xa40
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786144] [<ffffffff810639c6>] ? sys_futex+0xc6/0x170
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786146] [<ffffffff810ea67a>] sys_ioctl+0x4a/0x80
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786149] [<ffffffff81002dab>] system_call_fastpath+0x16/0x1b
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.786150] ---[ end trace 919fb6de01d05188 ]---



# cat /var/log/messages | grep ffffffff | wc -l
19366248
:|
Nemykal
 
Posts: 3
Joined: 2. Jun 2010, 15:35
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows 7 x64

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 2. Jun 2010, 16:57

cool, so i am not alone at least ;-) what's your setup?
distro,x64/x86,vbox version,kernel version etc.

write a bit more also on when/under what circumstances are you observing the problem.

btw. i have opened a bug report for it, so far for gentoo only: http://bugs.gentoo.org/show_bug.cgi?id=322475
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 2. Jun 2010, 16:59

WARNING: at net/core/dev.c:1688 skb_gso_segment+0x1da


see you are running 2.6.33, right? :-)

under 2.6.34 it changes into this, as far as i see
WARNING: at net/core/dev.c:1737 skb_gso_segment+0xf9/0x239
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 2. Jun 2010, 23:43

silly me, I decided to have a look at the link you included finally:
http://pastebin.com/j84ZkxSP

for anybody else who has a problem with clicking on links:
#
Weird problem. Getting tons of these warnings in dmesg, yet nothing seems to actually be broken.
#
vbox 3.2.0 / amd64 / gentoo linux 2.6.33
#
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.691852] ------------[ cut here ]------------
#
Jun 2 23:20:46 remilia-neechan kernel: [ 7985.691857] WARNING: at net/core/dev.c:1688 skb_gso_segment+0x1da/0x2b0()
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby Nemykal » 3. Jun 2010, 02:43

Yeah sorry, I should've included more information in my actual post.
I have only tried this with 2.6.33. I do have the zen-kernel.org patchset. I can try other kernel versions if needed.

I'm also running gentoo amd64 - that seems to be the only common ground between us?
Host machine specs are two intel xeon e5520's, asus z8pe-d18 motherboard, the nics are a couple e1000e and a couple e1000 cards.
Nemykal
 
Posts: 3
Joined: 2. Jun 2010, 15:35
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows 7 x64

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby Nemykal » 3. Jun 2010, 02:48

Interestingly, I've only tried this with a win7 guest, and I get an issue when RDPing sometimes. Says the machine doesnt have enough virtual memory and RDP crashes. I'll edit this post and attach a screenshot the next time it happens. BTW the VM has 4gb of ram and the host has 24gb. According to tcpdump/bwm-ng/iptraf the machine is still running, i just can't rdp to it. Sometimes it fixes itself if i turn VRDP off and on again.
Nemykal
 
Posts: 3
Joined: 2. Jun 2010, 15:35
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows 7 x64

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby frank » 10. Jun 2010, 12:25

There is a fix available, see here.
frank
Oracle Corporation
 
Posts: 3362
Joined: 7. Jun 2007, 09:11
Location: Dresden, Germany
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 10. Jul 2010, 17:46

Hi Frank,

Thx for the patch, it resolved the issue with systraces but it seems it caused a new problem. Here is the story:
- installed 3.2.6, noticed systraces problem is gone. huzzzaaaah!
- shortly after noticed dramatic network performance drop - connecting to W2K8R2 guest via RDP is soooo slow, noticed access to shares on the guest is also veeeery sloooow
- guest is bridged to gigabit ethernet interface
- there are also other network cards in the host with different link speed than the one above (e.g. wifi54g or 100Mbit)
- seems that accessing the guest from other machine on gigabit network works fine - no slow downdowns (at first sight this might not be completely true)
- tried pushing the file from W2K8R2 guest to win7 client over wifi - should be around 2MB/sec, measured around 10KB/s
- reverted to build 3.2.4-r1 from gentoo portage - all back to normal, i.e network performance awesome again, but systraces are killing my logs
- applied your patch posted in bug 6872, reinserted new modules into kernel, restarted the W2K8R2 guest - same problem as in 3.2.6 again (wanted to verify if something else was breaking the performance - seems this patch is responsible)
- back to 3.1.8 for me again :-(

Can you help again? I know I am stretching it, so thanks for any future fixes to this.

Rgds,
B.
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 10. Jul 2010, 18:08

followup: looks awefully similar to this bug:

Routed networking to hostonly if extremely slow after upgrade to 3.2.6
http://www.virtualbox.org/ticket/7081
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby frank » 3. Aug 2010, 10:01

Please go to the ticket and try the provided patch.
frank
Oracle Corporation
 
Posts: 3362
Joined: 7. Jun 2007, 09:11
Location: Dresden, Germany
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows

Re: virtualbox 3.2.0 flooding my logs with systraces

Postby bodo » 13. Aug 2010, 18:47

works beautifully now, 3.2.8 has to be the best vbox build so far! thx very much!
bodo
 
Posts: 12
Joined: 4. Apr 2010, 19:43
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: SOLVED: virtualbox 3.2.0 flooding my logs with systraces

Postby frank » 16. Aug 2010, 21:59

Thanks for your feedback! Always nice to read if something was fixed. We usually get much more complaints if something was not fixed or if there is a regression ...
frank
Oracle Corporation
 
Posts: 3362
Joined: 7. Jun 2007, 09:11
Location: Dresden, Germany
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows


Return to VirtualBox on Linux Hosts

Who is online

Users browsing this forum: No registered users and 25 guests