DomU causes 'Frag is bigger than frame'

[Stefan]

Woke up to notice one of the domU's on a dom0 with Xen version 4.2.1 down.

The domU was still running, but its virtual network device was disabled. No log messages on the domU, but the dom0 logged

Apr 21 03:05:11 dom0 kernel: [312516.199286] vif vif-9-0: vif9.0: Frag is bigger than frame.
Apr 21 03:05:11 dom0 kernel: [312516.199295] vif vif-9-0: vif9.0: fatal error; disabling device
Apr 21 03:05:11 dom0 kernel: [312516.199377] xenbr0: port 5(vif9.0) entering forwarding state

This was the time when the domU network went down.
A similar (very recent) bug report is filed on debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701744 . This same issue may be affecting Ubuntu here.

Dom0

# uname -a
Linux dom0 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -rd
Description: Ubuntu 12.04.2 LTS
Release: 12.04

Dom U

# uname -a
Linux domu 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -rd
Description: Ubuntu 12.04.2 LTS
Release: 12.04
---
AcpiTables:

AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Apr 18 12:28 seq
 crw-rw---T 1 root audio 116, 33 Apr 18 12:28 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=fcf19b1a-54be-4ad2-894c-e3aa0957f0aa
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MarkForUpload: True
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: root=UUID=e309a8d9-f97d-4848-8f77-45c11c0c60fb ro console=hvc0 quiet splash $vt_handoff
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-40-generic N/A
 linux-backports-modules-3.2.0-40-generic N/A
 linux-firmware 1.79.1
RfKill: Error: [Errno 2] No such file or directory
Tags: precise
Uname: Linux 3.2.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1171135

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Stefan (sewi)]

apport information

[Mark Dokter (dokter)]

I observed this behaviour on a xen host running precise 12.04.2.
Happened two times up to now with the ubuntu kernel 3.2.0-39-generic and xen 4.1.2.
The machine was hosting a Ubuntu Linux 12.04.2 HVM and a Windows XP HVM.
There was nothing suspicious in the log of the (Linux) guest.

Attached is the relevant part from the dom0 kernel log.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc8-raring/

[Stefan (sewi)]

Test the unstable kernel on what, the dom0, or the domU?

Note this is a production system! I really don't want to upgrade kernels (from LTS to unstable) just to find out not having it boot anymore, so that I can add the tag 'kernel-unable-to-test-upstream'. I will therefore add the tag as you suggested in the template reply, because I'm unable to test it on my production system (without loss of service to clients). If someone else is able to (Mark?), be my guest.

[Stefan (sewi)]

http://osdir.com/ml/general/2013-04/msg49699.html may be relevant.

[Mark Dokter (dokter)]

Same situation here. I can't test any kernels because this is a production system. Even if I had the resources to set up a test system, it would be hard to check if an unstable kernel fixes the problem because I don't know how to trigger the error.