lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 26 Jun 2008 12:01:04 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: e1000-devel@...ts.sourceforge.net Cc: bugme-daemon@...zilla.kernel.org, netdev@...r.kernel.org, mjc@...echpulse.com Subject: Re: [Bugme-new] [Bug 10990] New: e1000/e1000e driver doesn't work with gigabit connection (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 26 Jun 2008 11:49:14 -0700 (PDT) bugme-daemon@...zilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=10990 > > Summary: e1000/e1000e driver doesn't work with gigabit connection > Product: Drivers > Version: 2.5 > KernelVersion: 2.6.25.6-55.fc9.i686 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Network > AssignedTo: jgarzik@...ox.com > ReportedBy: mjc@...echpulse.com > > > Linux lyra 2.6.25.6-55.fc9.i686 #1 SMP Tue Jun 10 16:27:49 EDT 2008 i686 i686 > i386 GNU/Linux > > I have a multiple HP DC7700s with integrated Intel ethernet adapters. They work > when the network cable is plugged into a 10/100 port on a switch. They do not > work when plugged into a 10/100/1000 port. I also have DC7700s with integrated > Broadcom chips (tg3 driver) and they work fine. > > >From dmesg: > e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0 > e1000e: Copyright (c) 1999-2007 Intel Corporation. > ... > eth0: (PCI Express:2.5GB/s:Width x1) 00:0f:fe:4a:68:37 > eth0: Intel(R) PRO/1000 Network Connection > eth0: MAC: 4, PHY: 6, PBA No: 1002ff-0ff > > When plugged into a 10/100/1000 porting, forcing: > ethtool -s eth0 autoneg off speed 1000 duplex full > > results in erratic (some pings work) or dead operation (no pings work). > > Using: > ethtool -s eth0 autoneg off speed 100 duplex full > > seems to work OK. > > Returning it to autoneg results in erratic/dead operation: > > [root@...a ~]# ethtool -s eth0 autoneg on > [root@...a ~]# ethtool eth0 > Settings for eth0: > Supported ports: [ TP ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Supports auto-negotiation: Yes > Advertised link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Advertised auto-negotiation: Yes > Speed: 1000Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 1 > Transceiver: internal > Auto-negotiation: on > Supports Wake-on: pumbag > Wake-on: g > Current message level: 0x00000001 (1) > Link detected: yes > [root@...a ~]# ping server2 > PING server2.domain.avtechpulse.com (192.168.0.3) 56(84) bytes of data. > 64 bytes from server2.domain.avtechpulse.com (192.168.0.3): icmp_seq=1 ttl=64 > time=0.079 ms > 64 bytes from server2.domain.avtechpulse.com (192.168.0.3): icmp_seq=2 ttl=64 > time=0.158 ms > 64 bytes from server2.domain.avtechpulse.com (192.168.0.3): icmp_seq=7 ttl=64 > time=0.161 ms > 64 bytes from server2.domain.avtechpulse.com (192.168.0.3): icmp_seq=11 ttl=64 > time=0.113 ms > 64 bytes from server2.domain.avtechpulse.com (192.168.0.3): icmp_seq=12 ttl=64 > time=0.131 ms > 64 bytes from server2.domain.avtechpulse.com (192.168.0.3): icmp_seq=17 ttl=64 > time=0.127 ms > ^C > --- server2.domain.avtechpulse.com ping statistics --- > 18 packets transmitted, 6 received, 66% packet loss, time 17553ms > rtt min/avg/max/mdev = 0.079/0.128/0.161/0.028 ms > [root@...a ~]# > > This was confirmed with multiple 10/100/1000 switches from different > manufacturers. > > > [root@...a ~]# more /etc/modprobe.conf > alias eth0 e1000e #same behaviour with "e1000" > alias scsi_hostadapter libata > alias scsi_hostadapter1 ata_piix > alias snd-card-0 snd-hda-intel > options snd-card-0 index=0 > options snd-hda-intel index=0 > > > Need any additional data? > > - Mike > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists