Comment 7 for bug 1195474

Not to my knowledge. Also depends on the exact issue. Reading through the report there might be two separate issues.
1. Packet loss when this message appears. This is the the expected behaviour when trying to transmit
    a packet that would require more than 16+1 slots or 64kB.
    Compared to the Amazon kernel mentioned all kernels later than 3.7 have the following change:
    * xen/netfront: handle compound page fragments on transmit
   If there is something wrong with that, I have not yet seen a patch for it. There might be a related bug
   (bug #1275879) but hitting that would cause a BUG stacktrace in the guest.

2. That invalid socket state mentioned in comment #3. I wonder whether that could hint the netback driver
    running on the host side has closed the connection. There could be some messages to help in the host's
    dmesg but we cannot get to those (only Amazon can). If that is the case we should ensure those two
    patches are included in the kernel running in dom0 on the host:
      * xen-netback: don't disconnect frontend when seeing oversize packet
      * xen-netback: coalesce slots in TX path and fix regressions