This bug was fixed in the package linux - 4.10.0-22.24
---
linux (4.10.0-22.24) zesty; urgency=low
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2 TCE route (LP: #1690155)
- powerpc/powernv: Fix TCE kill on NVLink2
* CVE-2017-0605
- tracing: Use
~ # uname -a
Linux (none) 4.10.0-22-generic #24~lp1677297+test.1-Ubuntu SMP Fri Jun 2
18:09:55 UTC 2017 aarch64 GNU/Linux
~ #
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages,
I built DI and booted the netboot image on an SDP. DI works as expected
with the patch.
┌─┤ [!!] Configure the network ├──┐
│ │
│ Your system has multiple network interfaces.
kleber-souza,
Oh wow I did not notice that it was still loading the GA kernel and
there is no netboot image for arm64 in daily. I will build a DI and test
it and report back here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi @manjo,
It seems that we don't have daily netboot install images for arm64.
Could you please try to create a DI with Zesty kernel 4.10.0-22.24 and
check whether the module is being loaded properly?
Thank you.
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status:
This bug was fixed in the package linux - 4.10.0-22.24
---
linux (4.10.0-22.24) zesty; urgency=low
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2 TCE route (LP: #1690155)
- powerpc/powernv: Fix TCE kill on NVLink2
* CVE-2017-0605
- tracing: Use
The fix was included on Zesty kernel 4.10.0-22.24, the netboot installer
is loading 4.10.0-19, which is probably the GA kernel. I'm trying to
find some sort of daily netboot build so it can be tested with the
latest kernel.
--
You received this bug notification because you are a member of Kernel
Downloaded the netboot installer from
http://ports.ubuntu.com/dists/zesty-proposed/main/installer-arm64/current/images/netboot/
But I dont see the qcom_emac driver
/lib/modules/4.10.0-19-generic/kernel/drivers/net/ethernet # ls
3com broadcom fealnx.ko natsemisfc
8390
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag
** Tags added: qdf2400
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677297
Title:
[Zesty] d-i: replace msm_emac with qcom_emac
Status in linux package in Ubuntu:
Incomplete
Status
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677297
Title:
[Zesty] d-i: replace msm_emac with qcom_emac
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: Timur Tabi (timur-tabi) => Manoj Iyer (manjo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677297
Title:
[Zesty] d-i: replace msm_emac
qcom_emac works fine with the generic phy driver, either the at803x
driver needs to be fixed or the underlying userspace utils like dhclient
needs to retry bringing up the link when it is reported as down. This
should not be a blocker for switching from msm_emac to qcom_emac for
d-i.
--
You
Timur found that the at803x module (needed for an erratum) is the reason
we are unable to get a dhcp lease on the emac interface. He is exploring
his options on fixing the issue, ie have a an option to pass in a phy
driver if the erratum is encountered. We found that on my SDP we did not
need the
on my qdf2400 server. Looks like dhclient is able to get a lease and
ifconfig displays the ip address.
ubuntu@ubuntu:~$ sudo dhclient -v eth0
[sudo] password for ubuntu:
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info,
Also we tried the workaround in comment #16 and blacklisting the
mlx5_core module during the install and eth0 was not available.
[ 16.198090] Atheros 8031 ethernet QCOM8070:00:04: attached PHY driver
[Atheros 8031 ethernet] (mii_bus:phy_addr=QCOM8070:00:04, irq=-2)
[ 16.198153] IPv6:
I did a D-I install on the qdf 2400 server with zesty + the patchset,
using the Mellanox adapter (Ethernet controller: Mellanox Technologies
MT27700 Family [ConnectX-4]). The qcom_emac driver is installed but the
port (eth0) does not get an IP address without running dhclient -v. An
IP address is
The qcom_emac driver in the installer is able to get a DHCP lease once I
blacklisted the mlx5_core module.
~ # lsmod
Module Size Used by
uas28672 0
usb_storage77824 1 uas
at803x 16384 1
devlink36864 0
ptp
Timur,
I strongly suspect that the NMI watchdog softlockups caused by mlx5_core
dma mapping is the root cause of why qcom_emac driver is unable to get a
dhcp address. I blacklisted the mlx5_core driver and the soft lockups
went away. Nate suggested that we might need some additional iommu
related
How about the ifconfig command to bring the interface up? This just
shows that the drivers have loaded.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677297
Title:
[Zesty] d-i:
~ # rmmod qcom_emac
~ # modprobe qcom_emac
~ # dmesg | tail -n 15
[ 211.382709] Atheros 8031 ethernet QCOM8070:00:04: attached PHY driver
[Atheros 8031 ethernet] (mii_bus:phy_addr=QCOM8070:00:04, irq=-2)
[ 211.382789] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4479.862691] Atheros
Can you try bringing up the interface manually, with ifconfig and a
static IP address? The driver that's already in 4.10 should work as-is.
I need to see the console output as the driver tries to bring the
interface up, and dhclient hides all that.
--
You received this bug notification because
I built a DI where the initrd has both the PHY and the qcom_emac driver.
The d-i installer now loads both at803x and qcom_emac, but dhclient
fails to get a DHCP address. So, I am not sure what is going on with
qcom_emac.. is there another module dependency I am missing ?
~ # lsmod
Module
24 matches
Mail list logo
