All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saku Ytti <saku+xen-devel@ytti.fi>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU network data payload corruption
Date: Thu, 9 Feb 2006 19:07:55 +0200	[thread overview]
Message-ID: <20060209170755.GC26540@ytti.fi> (raw)
In-Reply-To: <e9d548a55d8a96dc9279e48037e868a9@cl.cam.ac.uk>

On (2006-02-09 17:03 +0000), Keir Fraser wrote:

Hello Keir,
 
> How much RAM does your system have? Are you running 32-bit, PAE, or 
> 64-bit? What does the Ethernet driver print out during boot (may tell 
> us what sub-version forcedeth you have)?

4GB, dual core AMD athalon, 64b (no 32b emulation support compiled in
in domU or dom0). No SMP support compiled in in domU or dom0.

forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.49.
eth0: forcedeth.c: subsystem: 01043:8141 bound to 0000:00:0a.0

0000:00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
        Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard IRQ 16
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16
        Memory at d5400000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at b000 [size=8]anagement version 2 Bridge (rev a3)
        Capabilities: [44] Power Management version 2 Bridge (rev a3)

Last entry in forcedeth.c changelog
 *      0.49: 10 Dec 2005: Fix tso for large buffers.

I'll try to see if I have extra PCI NIC's at home to see if it's NIC
specific issue. If not need to loan one from work tomorrow.

Thanks for quick reply,

-- 
  ++ytti

  reply	other threads:[~2006-02-09 17:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 16:34 domU network data payload corruption Saku Ytti
2006-02-09 17:01 ` Saku Ytti
2006-02-09 17:03 ` Keir Fraser
2006-02-09 17:07   ` Saku Ytti [this message]
2006-02-09 17:26     ` Keir Fraser
2006-02-09 17:23       ` Saku Ytti
2006-02-09 17:59       ` Saku Ytti
2006-02-09 18:17         ` Keir Fraser
2006-02-09 17:13   ` Keir Fraser
2006-02-09 17:09     ` Saku Ytti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060209170755.GC26540@ytti.fi \
    --to=saku+xen-devel@ytti.fi \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.