xgene-enet: doesn't work at 100Mbit

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

apport-collect 1433290

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.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 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/v4.0-rc4-vivid/

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

I have been going around and around trying to get Ubuntu on Mustang to connect to the network, and have been unable to do so.

I have configured the system to use DHCP, but it doesn’t get an IP address assigned.
I have configured the system with a static IP (the same one that I used to boot up OpenEmbedded, and to do the download and install of Ubuntu), but it is unable to see any other systems on the same subnet.
I have configured the system with a peer-to-peer connection with a desktop system, assigning IP addresses 192.168.1.101 to the desktop, and 192.168.1.102 to the Mustang board, but the two systems are unable to see each other. I have verified that another computer connected to the desktop with the same cable was able to ping the desktop, and that the desktop could ping the other computer.

I have also been corresponding with someone at Linaro Support, sending him log files, and he made this comment:
• The kernel is definitively seeing network traffic on the card (otherwise libpcap wouldnt be able to feed the data to tcpdump) so I dont think it is a problem with the drivers or hardware. It might be a configuration option that I am not aware of.

Does anyone have any clue why this system won’t connect to the network, or even acknowledge that there is a viable connection?

By moving the Mustang box into a lab that had a gigibit connection, it immediately connected with the network. It's surprising that the network worked just fine on a 100Kb connection when running tftpboot and when installing Ubuntu, but not when running Ubuntu. This looks like a limitation in the Ubuntu 14.04 driver for aarch64, not with the Mustang box itself. It's just too bad that this limitation isn't documented anywhere, other than this bug report.

Fix posted and applied on the net tree. Can you please try the patch ?
http://www.spinics.net/lists/netdev/msg351594.html

On Sun, Nov 8, 2015 at 7:57 PM, Iyappan Subramanian
<email address hidden> wrote:
> Fix posted and applied on the net tree. Can you please try the patch ?
> http://www.spinics.net/lists/netdev/msg351594.html

I backported this to wily's 4.2 kernel, and verified that it does
resolve the issue.

  -dann

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-wily' to 'verification-done-wily'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug was fixed in the package linux - 4.2.0-21.25

---------------
linux (4.2.0-21.25) wily; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1522108

  [ Upstream Kernel Changes ]

  * staging/dgnc: fix info leak in ioctl
    - LP: #1509565
    - CVE-2015-7885
  * [media] media/vivid-osd: fix info leak in ioctl
    - LP: #1509564
    - CVE-2015-7884
  * KEYS: Fix race between key destruction and finding a keyring by name
    - LP: #1508856
    - CVE-2015-7872
  * KEYS: Fix crash when attempt to garbage collect an uninstantiated
    keyring
    - LP: #1508856
    - CVE-2015-7872
  * KEYS: Don't permit request_key() to construct a new keyring
    - LP: #1508856
    - CVE-2015-7872
  * isdn_ppp: Add checks for allocation failure in isdn_ppp_open()
    - LP: #1508329
    - CVE-2015-7799
  * ppp, slip: Validate VJ compression slot parameters completely
    - LP: #1508329
    - CVE-2015-7799

linux (4.2.0-20.24) wily; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #1521753

  [ Andy Whitcroft ]

  * [Tests] gcc-multilib does not exist on ppc64el
    - LP: #1515541

  [ Joseph Salisbury ]

  * SAUCE: scsi_sysfs: protect against double execution of
    __scsi_remove_device()
    - LP: #1509029

  [ Manoj Kumar ]

  * SAUCE: (noup) cxlflash: Fix to escalate LINK_RESET also on port 1
    - LP: #1513583

  [ Matthew R. Ochs ]

  * SAUCE: (noup) cxlflash: Fix to avoid virtual LUN failover failure
    - LP: #1513583

  [ Oren Givon ]

  * SAUCE: (noup) iwlwifi: Add new PCI IDs for the 8260 series
    - LP: #1517375

  [ Seth Forshee ]

  * [Config] CONFIG_DRM_AMDGPU_CIK=n
    - LP: #1510405

  [ Upstream Kernel Changes ]

  * net/mlx5e: Disable VLAN filter in promiscuous mode
    - LP: #1514861
  * drivers: net: xgene: fix RGMII 10/100Mb mode
    - LP: #1433290
  * HID: rmi: Disable scanning if the device is not a wake source
    - LP: #1515503
  * HID: rmi: Set F01 interrupt enable register when not set
    - LP: #1515503
  * net/mlx5e: Ethtool link speed setting fixes
    - LP: #1517919
  * scsi_scan: don't dump trace when scsi_prep_async_scan() is called twice
    - LP: #1517942
  * x86/ioapic: Disable interrupts when re-routing legacy IRQs
    - LP: #1508593
  * xhci: Workaround to get Intel xHCI reset working more reliably
  * megaraid_sas: Do not use PAGE_SIZE for max_sectors
    - LP: #1475166
  * net: usb: cdc_ether: add Dell DW5580 as a mobile broadband adapter
    - LP: #1513847
  * KVM: svm: unconditionally intercept #DB
    - LP: #1520184
    - CVE-2015-8104

 -- Luis Henriques <email address hidden> Wed, 02 Dec 2015 17:30:58 +0000

This bug was nominated against a series that is no longer supported, ie vivid. The bug task representing the vivid nomination is being closed as Won't Fix.

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