Bug 143285 - [em] [regression] jumbo frames broken in 8.0
Summary: [em] [regression] jumbo frames broken in 8.0
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 8.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Eric Joyner
URL:
Keywords: IntelNetworking
Depends on:
Blocks:
 
Reported: 2010-01-27 10:30 UTC by Yuriy S.
Modified: 2017-12-18 20:53 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuriy S. 2010-01-27 10:30:01 UTC
8.0 side:
em1@pci0:4:0:1: class=0x020000 card=0x000015d9 chip=0x10968086 rev=0x01 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Intel PRO/1000 EB (Intel PRO/1000 EB)'
    class      = network
    subclass   = ethernet
    bar   [10] = type Memory, range 32, base rxc8220000, size 131072, enabled
    bar   [18] = type I/O Port, range 32, base rx2020, size 32, enabled
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x4(x4)

7.2 side:
em1@pci0:15:0:0:        class=0x020000 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82573L Intel PRO/1000 PL Network Adaptor'
    class      = network
    subclass   = ethernet
    bar   [10] = type Memory, range 32, base rxd0300000, size 131072, enabled
    bar   [18] = type I/O Port, range 32, base rx3000, size 32, enabled
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint

interconnected with copper cable directly
ifconfig em1 10.0.0.1/30 mtu 9000
when rxcsum and txcsum are not disabled, I can ping only other side
no data in tcpdump
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2010-01-27 10:41:51 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Andre Oppermann freebsd_committer 2010-08-23 15:37:11 UTC
Responsible Changed
From-To: freebsd-net->jfv

Over to maintainer.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2015-11-12 07:44:30 UTC
Reassign to erj@ for triage.  To submitter: is this issue still relevant?
Comment 4 Eric Joyner freebsd_committer 2017-12-18 20:53:20 UTC
FreeBSD 8 and its point releases have been EOL'd. If the submitter still needs jumbo frames, he/she should update to FreeBSD 10 or 11 and submit a new bug if it doesn't work.