[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2019-02-14 Thread Andy Whitcroft
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic

-- 
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/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2019-02-14 Thread Brad Figg
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

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!


** Tags added: verification-needed-bionic

-- 
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/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-12-10 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.18.0-1006.6

---
linux-azure (4.18.0-1006.6) cosmic; urgency=medium

  * linux-azure: 4.18.0-1006.6 -proposed tracker (LP: #1805244)

  * Accelerated networking (SR-IOV VF) broken in 18.10 daily (LP: #1794477)
- [Packaging] Move pci-hyperv and autofs4 back to linux-modules

linux-azure (4.18.0-1005.5) cosmic; urgency=medium

  * linux-azure: 4.18.0-1005.5 -proposed tracker (LP: #1802752)

  * [Hyper-V] Fix IRQ spreading on NVMe devices with lower numbers of channels
(LP: #1802358)
- SAUCE: genirq/affinity: Spread IRQs to all available NUMA nodes
- SAUCE: irq/matrix: Split out the CPU selection code into a helper
- SAUCE: irq/matrix: Spread managed interrupts on allocation
- SAUCE: genirq/matrix: Improve target CPU selection for managed interrupts.

  [ Ubuntu: 4.18.0-12.13 ]

  * linux: 4.18.0-12.13 -proposed tracker (LP: #1802743)
  * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- s390/zcrypt: Add ZAPQ inline function.
- s390/zcrypt: Review inline assembler constraints.
- s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.
- s390/zcrypt: fix ap_instructions_available() returncodes
- KVM: s390: vsie: simulate VCPU SIE entry/exit
- KVM: s390: introduce and use KVM_REQ_VSIE_RESTART
- KVM: s390: refactor crypto initialization
- s390: vfio-ap: base implementation of VFIO AP device driver
- s390: vfio-ap: register matrix device with VFIO mdev framework
- s390: vfio-ap: sysfs interfaces to configure adapters
- s390: vfio-ap: sysfs interfaces to configure domains
- s390: vfio-ap: sysfs interfaces to configure control domains
- s390: vfio-ap: sysfs interface to view matrix mdev matrix
- KVM: s390: interface to clear CRYCB masks
- s390: vfio-ap: implement mediated device open callback
- s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl
- s390: vfio-ap: zeroize the AP queues
- s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl
- KVM: s390: Clear Crypto Control Block when using vSIE
- KVM: s390: vsie: Do the CRYCB validation first
- KVM: s390: vsie: Make use of CRYCB FORMAT2 clear
- KVM: s390: vsie: Allow CRYCB FORMAT-2
- KVM: s390: vsie: allow CRYCB FORMAT-1
- KVM: s390: vsie: allow CRYCB FORMAT-0
- KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1
- KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2
- KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2
- KVM: s390: device attrs to enable/disable AP interpretation
- KVM: s390: CPU model support for AP virtualization
- s390: doc: detailed specifications for AP virtualization
- KVM: s390: fix locking for crypto setting error path
- KVM: s390: Tracing APCB changes
- s390: vfio-ap: setup APCB mask using KVM dedicated function
- [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module.
  * Bypass of mount visibility through userns + mount propagation (LP: #1789161)
- mount: Retest MNT_LOCKED in do_umount
- mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
  *  CVE-2018-18955: nested user namespaces with more than five extents
incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955
- userns: also map extents in the reverse map to kernel IDs
  * kdump fail due to an IRQ storm (LP: #1797990)
- SAUCE: x86/PCI: Export find_cap() to be used in early PCI code
- SAUCE: x86/quirks: Add parameter to clear MSIs early on boot
- SAUCE: x86/quirks: Scan all busses for early PCI quirks
  * crash in ENA driver on removing an interface (LP: #1802341)
- SAUCE: net: ena: fix crash during ena_remove()
  * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
(LP: #1797367)
- s390/qeth: reduce hard-coded access to ccw channels
- s390/qeth: sanitize strings in debug messages
  * Add checksum offload and TSO support for HiNIC adapters (LP: #1800664)
- net-next/hinic: add checksum offload and TSO support
  * smartpqi updates for ubuntu 18.04.2 (LP: #1798208)
- scsi: smartpqi: improve handling for sync requests
- scsi: smartpqi: improve error checking for sync requests
- scsi: smartpqi: add inspur advantech ids
- scsi: smartpqi: fix critical ARM issue reading PQI index registers
- scsi: smartpqi: bump driver version to 1.1.4-130
  * [GLK/CLX] Enhanced IBRS (LP: #1786139)
- x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation
- x86/speculation: Support Enhanced IBRS on future CPUs
  * Enable keyboard wakeup for S2Idle laptops (LP: #1798552)
- Input: i8042 - enable keyboard wakeups by default when s2idle is used
  * Overlayfs in user namespace leaks directory content of inaccessible
directories (LP: #1793458) // CVE-2018-6559
- SAUCE: overlayfs: ensure mounter privileges when reading directories
  * Update ENA driver to version 2.0.1K (LP: #1798182)
- net: ena: remove 

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-12-06 Thread Marcelo Cerri
** Changed in: linux (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Invalid
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-12-05 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.18.0-1006.6

---
linux-azure (4.18.0-1006.6) cosmic; urgency=medium

  * linux-azure: 4.18.0-1006.6 -proposed tracker (LP: #1805244)

  * Accelerated networking (SR-IOV VF) broken in 18.10 daily (LP: #1794477)
- [Packaging] Move pci-hyperv and autofs4 back to linux-modules

linux-azure (4.18.0-1005.5) cosmic; urgency=medium

  * linux-azure: 4.18.0-1005.5 -proposed tracker (LP: #1802752)

  * [Hyper-V] Fix IRQ spreading on NVMe devices with lower numbers of channels
(LP: #1802358)
- SAUCE: genirq/affinity: Spread IRQs to all available NUMA nodes
- SAUCE: irq/matrix: Split out the CPU selection code into a helper
- SAUCE: irq/matrix: Spread managed interrupts on allocation
- SAUCE: genirq/matrix: Improve target CPU selection for managed interrupts.

  [ Ubuntu: 4.18.0-12.13 ]

  * linux: 4.18.0-12.13 -proposed tracker (LP: #1802743)
  * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
- s390/zcrypt: Add ZAPQ inline function.
- s390/zcrypt: Review inline assembler constraints.
- s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.
- s390/zcrypt: fix ap_instructions_available() returncodes
- KVM: s390: vsie: simulate VCPU SIE entry/exit
- KVM: s390: introduce and use KVM_REQ_VSIE_RESTART
- KVM: s390: refactor crypto initialization
- s390: vfio-ap: base implementation of VFIO AP device driver
- s390: vfio-ap: register matrix device with VFIO mdev framework
- s390: vfio-ap: sysfs interfaces to configure adapters
- s390: vfio-ap: sysfs interfaces to configure domains
- s390: vfio-ap: sysfs interfaces to configure control domains
- s390: vfio-ap: sysfs interface to view matrix mdev matrix
- KVM: s390: interface to clear CRYCB masks
- s390: vfio-ap: implement mediated device open callback
- s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl
- s390: vfio-ap: zeroize the AP queues
- s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl
- KVM: s390: Clear Crypto Control Block when using vSIE
- KVM: s390: vsie: Do the CRYCB validation first
- KVM: s390: vsie: Make use of CRYCB FORMAT2 clear
- KVM: s390: vsie: Allow CRYCB FORMAT-2
- KVM: s390: vsie: allow CRYCB FORMAT-1
- KVM: s390: vsie: allow CRYCB FORMAT-0
- KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1
- KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2
- KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2
- KVM: s390: device attrs to enable/disable AP interpretation
- KVM: s390: CPU model support for AP virtualization
- s390: doc: detailed specifications for AP virtualization
- KVM: s390: fix locking for crypto setting error path
- KVM: s390: Tracing APCB changes
- s390: vfio-ap: setup APCB mask using KVM dedicated function
- [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module.
  * Bypass of mount visibility through userns + mount propagation (LP: #1789161)
- mount: Retest MNT_LOCKED in do_umount
- mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts
  *  CVE-2018-18955: nested user namespaces with more than five extents
incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955
- userns: also map extents in the reverse map to kernel IDs
  * kdump fail due to an IRQ storm (LP: #1797990)
- SAUCE: x86/PCI: Export find_cap() to be used in early PCI code
- SAUCE: x86/quirks: Add parameter to clear MSIs early on boot
- SAUCE: x86/quirks: Scan all busses for early PCI quirks
  * crash in ENA driver on removing an interface (LP: #1802341)
- SAUCE: net: ena: fix crash during ena_remove()
  * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding
(LP: #1797367)
- s390/qeth: reduce hard-coded access to ccw channels
- s390/qeth: sanitize strings in debug messages
  * Add checksum offload and TSO support for HiNIC adapters (LP: #1800664)
- net-next/hinic: add checksum offload and TSO support
  * smartpqi updates for ubuntu 18.04.2 (LP: #1798208)
- scsi: smartpqi: improve handling for sync requests
- scsi: smartpqi: improve error checking for sync requests
- scsi: smartpqi: add inspur advantech ids
- scsi: smartpqi: fix critical ARM issue reading PQI index registers
- scsi: smartpqi: bump driver version to 1.1.4-130
  * [GLK/CLX] Enhanced IBRS (LP: #1786139)
- x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation
- x86/speculation: Support Enhanced IBRS on future CPUs
  * Enable keyboard wakeup for S2Idle laptops (LP: #1798552)
- Input: i8042 - enable keyboard wakeups by default when s2idle is used
  * Overlayfs in user namespace leaks directory content of inaccessible
directories (LP: #1793458) // CVE-2018-6559
- SAUCE: overlayfs: ensure mounter privileges when reading directories
  * Update ENA driver to version 2.0.1K (LP: #1798182)
- net: ena: remove 

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-12-04 Thread Chris Valean
This does look resolved on WS2016 and Azure.
However, SR-IOV is broken in another way now on WS2019.

Affected proposed kernels:
- cosmic proposed
- bionic proposed edge - 4.18 based.

Tested this with cosmic linux-azure 4.18.0.1006.7 from proposed, same vhd:
- SR-IOV with Mellanox CX3 works fine on WS2016, all testing has passed.
- SR-IOV with Mellanox CX3/CX4 is broken on WS2019.

These are the relevant log portions showing the issue when the kernel
attempts to load the driver:

dmesg:
[   21.059766] mlx4_core: Mellanox ConnectX core driver v4.0-0
[   21.059775] mlx4_core: Initializing 9488:00:02.0
[   21.191481] mlx4_core 9488:00:02.0: Detected virtual function - running in 
slave mode
[   21.191508] mlx4_core 9488:00:02.0: Sending reset
[   21.191602] mlx4_core 9488:00:02.0: Sending vhcr0
[   21.193338] mlx4_core 9488:00:02.0: HCA minimum page size:512
[   21.193804] mlx4_core 9488:00:02.0: Timestamping is not supported in slave 
mode
[   93.148028] mlx4_core 9488:00:02.0: communication channel command 0x5 
(op=0x31) timed out
[   93.148031] mlx4_core 9488:00:02.0: device is going to be reset
[   93.171917] mlx4_core 9488:00:02.0: VF is sending reset request to Firmware
[   93.172584] mlx4_core 9488:00:02.0: VF Reset succeed
[   93.172585] mlx4_core 9488:00:02.0: device was reset successfully
[   93.195311] mlx4_core 9488:00:02.0: NOP command failed to generate MSI-X 
interrupt IRQ 24)
[   93.195312] mlx4_core 9488:00:02.0: Trying again without MSI-X
[   93.196258] mlx4_core 9488:00:02.0: Failed to close slave function
[   93.196866] mlx4_core: probe of 9488:00:02.0 failed with error -5



syslog:

Dec  4 14:35:18 ubuntu kernel: [   21.059766] mlx4_core: Mellanox ConnectX core 
driver v4.0-0
Dec  4 14:35:18 ubuntu kernel: [   21.059775] mlx4_core: Initializing 
9488:00:02.0
Dec  4 14:35:18 ubuntu kernel: [   21.191481] mlx4_core 9488:00:02.0: Detected 
virtual function - running in slave mode
Dec  4 14:35:18 ubuntu kernel: [   21.191508] mlx4_core 9488:00:02.0: Sending 
reset
Dec  4 14:35:18 ubuntu kernel: [   21.191602] mlx4_core 9488:00:02.0: Sending 
vhcr0
Dec  4 14:35:18 ubuntu kernel: [   21.193338] mlx4_core 9488:00:02.0: HCA 
minimum page size:512
Dec  4 14:35:18 ubuntu kernel: [   21.193804] mlx4_core 9488:00:02.0: 
Timestamping is not supported in slave mode
Dec  4 14:35:18 ubuntu kernel: [   93.148028] mlx4_core 9488:00:02.0: 
communication channel command 0x5 (op=0x31) timed out
Dec  4 14:35:18 ubuntu kernel: [   93.148031] mlx4_core 9488:00:02.0: device is 
going to be reset
Dec  4 14:35:18 ubuntu kernel: [   93.171917] mlx4_core 9488:00:02.0: VF is 
sending reset request to Firmware
Dec  4 14:35:18 ubuntu kernel: [   93.172584] mlx4_core 9488:00:02.0: VF Reset 
succeed
Dec  4 14:35:18 ubuntu kernel: [   93.172585] mlx4_core 9488:00:02.0: device 
was reset successfully
Dec  4 14:35:18 ubuntu kernel: [   93.195311] mlx4_core 9488:00:02.0: NOP 
command failed to generate MSI-X interrupt IRQ 24)
Dec  4 14:35:18 ubuntu kernel: [   93.195312] mlx4_core 9488:00:02.0: Trying 
again without MSI-X
Dec  4 14:35:18 ubuntu kernel: [   93.196258] mlx4_core 9488:00:02.0: Failed to 
close slave function
Dec  4 14:35:18 ubuntu kernel: [   93.196866] mlx4_core: probe of 9488:00:02.0 
failed with error -5

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-26 Thread Marcelo Cerri
** No longer affects: linux (Ubuntu Cosmic)

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: linux-azure (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: New => Fix Committed

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-22 Thread Marcelo Cerri
There's a second issue that also affects cosmic/linux-azure:

In 4.18, the module pci-hyperv moved from "drivers/pci/host/pci-
hyperv.ko" to "./drivers/pci/controller/pci-hyperv.c". That caused the
module to be included to the linux-modules-extra instead of the linux-
modules package.

I'm preparing a fix for it and adding some additional checks to prevent
modules to move silently to the linux-modules-extra when its based
location has changed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-22 Thread Marcelo Cerri
** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Confirmed

** Changed in: linux-azure (Ubuntu)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-22 Thread Marcelo Cerri
Small correction:

4.18.0-1005 is already built on the CKT PPA:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+packages?field.name_filter=azure-
edge_filter=published_filter=bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-22 Thread Marcelo Cerri
4.15.0-1005 is already built on the CKT PPA:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+packages?field.name_filter=azure-
edge_filter=published_filter=bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-22 Thread David Coronel
Hi Marcelo,

Maybe I'm doing something wrong but I still don't see the Mellanox
devices with this 4.18.0-1005 kernel from the CKT PPA:

ubuntu@lp1794477:~$ sudo add-apt-repository ppa:canonical-kernel-team/ppa
ubuntu@lp1794477:~$ sudo apt install linux-azure-edge
ubuntu@lp1794477:~$ sudo update-grub
ubuntu@lp1794477:~$ sudo reboot

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1005-azure #5~18.04.1-Ubuntu SMP Thu Nov 22 00:01:08 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
ubuntu@lp1794477:~$ lspci | grep -i mell
ubuntu@lp1794477:~$ lsmod | grep -i mlx

ubuntu@lp1794477:~$ apt-cache policy linux-image-4.18.0-1005-azure
linux-image-4.18.0-1005-azure:
  Installed: 4.18.0-1005.5~18.04.1
  Candidate: 4.18.0-1005.5~18.04.1
  Version table:
 *** 4.18.0-1005.5~18.04.1 500
500 http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu 
bionic/main amd64 Packages
100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
** Changed in: linux-azure (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Importance: Critical => High

** Changed in: linux (Ubuntu Cosmic)
   Importance: Critical => High

** Changed in: linux-azure (Ubuntu)
   Importance: Critical => High

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Marcelo Cerri
We already have identified the problem with bionic/azure-edge
4.18.0-1004. There was an issue on this version packaging that caused
most of the modules to be included to the linux-modules-extra package
instead of the linux-modules package.

The azure kernels do not install the linux-modules-extra package by
default, and that's the reason the Mellanox driver wasn't found. As an
workaround for 4.18.0-1004 the extra package can be installed with the
command "apt-get install linux-modules-extra-azure-edge".

The version for the current cycle (4.18.0-1005) is already fixed and
should be built in our PPA soon. We will post an update when this
version is already available on the PPA.

The corresponding cosmic/azure was not affected.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
bionic-tree/4.18.0-1004 with all the packages:

$ sudo dpkg -i 
linux-modules-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
 linux-modules-extra-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb 
\
 
linux-image-unsigned-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb 
\
 linux-azure-headers-4.18.0-1004_4.18.0-1004.4~18.04.1LP1794477_all.deb \
 linux-headers-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
 linux-azure-edge-tools-4.18.0-1004_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
 linux-tools-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb \
 
linux-azure-edge-cloud-tools-4.18.0-1004_4.18.0-1004.4~18.04.1LP1794477_amd64.deb
 \
 linux-cloud-tools-4.18.0-1004-azure_4.18.0-1004.4~18.04.1LP1794477_amd64.deb 

$ dpkg -l | grep 4.18.0
ii  linux-azure-edge-cloud-tools-4.18.0-1004 4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-azure-edge-tools-4.18.0-1004   4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-azure-headers-4.18.0-1004  4.18.0-1004.4~18.04.1LP1794477 
 all
ii  linux-cloud-tools-4.18.0-1004-azure  4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-headers-4.18.0-1004-azure  4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-image-unsigned-4.18.0-1004-azure   4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-modules-4.18.0-1004-azure  4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-modules-extra-4.18.0-1004-azure4.18.0-1004.4~18.04.1LP1794477 
 amd64
ii  linux-tools-4.18.0-1004-azure4.18.0-1004.4~18.04.1LP1794477 
 amd64

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #4~18.04.1LP1794477 SMP Wed Nov 21 20:57:54 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.937218] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.971114]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[6.016903] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
I built one more 1004 kernel from the bionic tree, but this time
including all of the packages.  This kernel can also be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1794477/bionic-tree/4.18.0-1004

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
bionic-tree/4.18.0-1004:


ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #4~18.04.1 SMP Wed Nov 21 20:07:48 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.337786] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.374260]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[6.393764] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
I built the 4.18.0-1004 kernel, but this time using the bionic tree and 
azure-edge-next branch. 
 This kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1794477/bionic-tree/4.18.0-1004

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
4.18.0-1004:

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1004-azure #5~lp1794477 SMP Wed Nov 21 19:19:16 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[6.009608] mlx4_core: Mellanox ConnectX core driver v4.0-0
[6.045063]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[6.085565] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
I built the 4.18.0-1004 kernel, which can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1004

Can you give this one a test?


If this kernel does not exhibit the bug, I'll start using the bionic azure-edge 
tree.  These prior test kernels are with the azure cosmic tree, so the commit 
that causes this bug may not have been introduced there.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
4.18.0-1003:

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1003-azure #4~lp1794477 SMP Wed Nov 21 18:32:18 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701478] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.732267]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[5.773481] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
I built the 4.18.0-1003 kernel, which can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1003

Can you give this one a test?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
4.18.0-1002:

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1002-azure #3~lp1794477 SMP Wed Nov 21 16:41:12 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.723350] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.751281]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[5.806824] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
4.18.0-1001:

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.18.0-1001-azure #2~lp1794477 SMP Wed Nov 21 16:06:45 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.701988] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.730013]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[5.780748] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
To try and speed up the kernel build time, I already built 4.18.0-1002
as well.  There are now two 4.18 kernels available for testing:

4.18.0-1001: http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1001/
4.18.0-1002: http://kernel.ubuntu.com/~jsalisbury/lp1794477/4.18.0-1002/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread Joseph Salisbury
Thanks for testing, David.  That means this regression was introduced in
4.18 and narrows down the number of commits we need to bisect through.
Can you next test the first 4.18 based kernel in the azure tree:

http://kernel.ubuntu.com/~jsalisbury/lp1794477

Install the .debs in the same order as before.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-21 Thread David Coronel
I can see the Mellanox devices with that 4.17.0-1001-azure kernel.

I installed the new kernel:

sudo dpkg -i linux-
modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb linux-
image-unsigned-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb

Fixed the missing depencies with:

sudo apt --fix-broken install

Updated grub just in case:

sudo update-grub

I rebooted and I see the devices:

ubuntu@lp1794477:~$ uname -a
Linux lp1794477 4.17.0-1001-azure #2~lp1794477 SMP Tue Nov 20 22:40:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@lp1794477:~$ dmesg | grep -i mella
[5.534382] mlx4_core: Mellanox ConnectX core driver v4.0-0
[5.564313]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[5.588721] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

ubuntu@lp1794477:~$ lspci | grep -i mell
ae9f:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

ubuntu@lp1794477:~$ lsmod | grep -i mlx
mlx4_en   114688  0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
For this particular bug, the tools packages are probably not needed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
You at least need to install the linux-modules, linux-modules-extra and
linux-image-unsigned .deb packages in that order.  You should be able to
do that with 'sudo dpkg -i package_name.deb'

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread David Coronel
These are the packages I see installed out of the box in the instance:

ubuntu@lp1794477:~/41701001$ dpkg -l | grep 4.15.0-1030.31 | sort

ii  linux-azure-cloud-tools-4.15.0-1030 4.15.0-1030.31  
amd64Linux kernel version specific cloud tools for version 
4.15.0-1030
ii  linux-azure-headers-4.15.0-1030 4.15.0-1030.31  
all  Header files related to Linux kernel version 4.15.0
ii  linux-azure-tools-4.15.0-1030   4.15.0-1030.31  
amd64Linux kernel version specific tools for version 4.15.0-1030
ii  linux-cloud-tools-4.15.0-1030-azure 4.15.0-1030.31  
amd64Linux kernel version specific cloud tools for version 
4.15.0-1030
ii  linux-headers-4.15.0-1030-azure 4.15.0-1030.31  
amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii  linux-image-4.15.0-1030-azure   4.15.0-1030.31  
amd64Signed kernel image azure
ii  linux-modules-4.15.0-1030-azure 4.15.0-1030.31  
amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-tools-4.15.0-1030-azure   4.15.0-1030.31  
amd64Linux kernel version specific tools for version 4.15.0-1030

And these are the files I downloaded from your link:

ubuntu@lp1794477:~/41701001$ ls -1 | sort

linux-azure-cloud-tools-4.17.0-1001_4.17.0-1001.2~lp1794477_amd64.deb
linux-azure-tools-4.17.0-1001_4.17.0-1001.2~lp1794477_amd64.deb
linux-cloud-tools-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb
linux-headers-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb
linux-image-unsigned-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb
linux-modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb
linux-modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb
linux-tools-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread David Coronel
Hi Joseph,

Is there a special way I should install these? I tried:

sudo dpkg -i *

But I get:

Selecting previously unselected package linux-azure-cloud-tools-4.17.0-1001.
(Reading database ... 56547 files and directories currently installed.)
Preparing to unpack 
linux-azure-cloud-tools-4.17.0-1001_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-azure-cloud-tools-4.17.0-1001 (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-azure-tools-4.17.0-1001.
Preparing to unpack 
linux-azure-tools-4.17.0-1001_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-azure-tools-4.17.0-1001 (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-cloud-tools-4.17.0-1001-azure.
Preparing to unpack 
linux-cloud-tools-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-cloud-tools-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-headers-4.17.0-1001-azure.
Preparing to unpack 
linux-headers-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-headers-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-image-unsigned-4.17.0-1001-azure.
Preparing to unpack 
linux-image-unsigned-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-image-unsigned-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-modules-4.17.0-1001-azure.
Preparing to unpack 
linux-modules-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-modules-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-modules-extra-4.17.0-1001-azure.
Preparing to unpack 
linux-modules-extra-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-modules-extra-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
Selecting previously unselected package linux-tools-4.17.0-1001-azure.
Preparing to unpack 
linux-tools-4.17.0-1001-azure_4.17.0-1001.2~lp1794477_amd64.deb ...
Unpacking linux-tools-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
Setting up linux-azure-cloud-tools-4.17.0-1001 (4.17.0-1001.2~lp1794477) ...
dpkg: dependency problems prevent configuration of 
linux-azure-tools-4.17.0-1001:
 linux-azure-tools-4.17.0-1001 depends on libc6 (>= 2.28); however:
  Version of libc6:amd64 on system is 2.27-3ubuntu1.

dpkg: error processing package linux-azure-tools-4.17.0-1001 (--install):
 dependency problems - leaving unconfigured
Setting up linux-cloud-tools-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
dpkg: dependency problems prevent configuration of 
linux-headers-4.17.0-1001-azure:
 linux-headers-4.17.0-1001-azure depends on linux-azure-headers-4.17.0-1001; 
however:
  Package linux-azure-headers-4.17.0-1001 is not installed.

dpkg: error processing package linux-headers-4.17.0-1001-azure (--install):
 dependency problems - leaving unconfigured
Setting up linux-modules-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.17.0-1001-azure:
 linux-modules-extra-4.17.0-1001-azure depends on crda | wireless-crda; however:
  Package crda is not installed.
  Package wireless-crda is not installed.

dpkg: error processing package linux-modules-extra-4.17.0-1001-azure 
(--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of 
linux-tools-4.17.0-1001-azure:
 linux-tools-4.17.0-1001-azure depends on linux-azure-tools-4.17.0-1001; 
however:
  Package linux-azure-tools-4.17.0-1001 is not configured yet.

dpkg: error processing package linux-tools-4.17.0-1001-azure (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-unsigned-4.17.0-1001-azure (4.17.0-1001.2~lp1794477) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-4.17.0-1001-azure
I: /initrd.img is now a symlink to boot/initrd.img-4.17.0-1001-azure
Processing triggers for linux-image-unsigned-4.17.0-1001-azure 
(4.17.0-1001.2~lp1794477) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.17.0-1001-azure
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.17.0-1001-azure
Found initrd image: /boot/initrd.img-4.17.0-1001-azure
Found linux image: /boot/vmlinuz-4.15.0-1030-azure
Found initrd image: /boot/initrd.img-4.15.0-1030-azure
done
Errors were encountered while processing:
 linux-azure-tools-4.17.0-1001
 linux-headers-4.17.0-1001-azure
 linux-modules-extra-4.17.0-1001-azure
 linux-tools-4.17.0-1001-azure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
 

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
Hi David,

Before starting a bisect, we can try to narrow down the exact versions
first.  To start, I built a 4.17 kernel based on the azure tree.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1794477

Can you test this kernel and see if it exhibits this bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread David Coronel
Hi Chris. I spoke to Joseph and I think we have everything we need to
start the bisect. We'll get started and keep you posted.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread David Coronel
I can reproduce the issue in Azure with Ubuntu 18.04 and the kernel
linux-azure-edge 4.18.0.1004.5 from bionic-proposed.

I use an instance of type "Standard F4s_v2 (4 vcpus, 8 GB memory)"

I launch the instance and get the 4.15.0-1030-azure kernel:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

$ uname -a
Linux davecore-an 4.15.0-1030-azure #31-Ubuntu SMP Tue Oct 30 18:35:53 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep -i mella
[   27.398120] mlx4_core: Mellanox ConnectX core driver v4.0-0
[   27.425228]  mlx4_ib_add: mlx4_ib: Mellanox ConnectX InfiniBand 
driver v4.0-0
[   27.658916] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0

$ dpkg -l | grep linux-azure
ii  linux-azure 4.15.0.1030.30  
amd64Complete Linux kernel for Azure systems.
ii  linux-azure-cloud-tools-4.15.0-1030 4.15.0-1030.31  
amd64Linux kernel version specific cloud tools for version 
4.15.0-1030
ii  linux-azure-headers-4.15.0-1030 4.15.0-1030.31  
all  Header files related to Linux kernel version 4.15.0
ii  linux-azure-tools-4.15.0-1030   4.15.0-1030.31  
amd64Linux kernel version specific tools for version 4.15.0-1030

$ lsmod  | grep -i mlx
mlx4_en   114688  0

$ lspci
:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
:00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
:00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual 
VGA
0001:00:02.0 Ethernet controller: Mellanox Technologies MT27500/MT27520 Family 
[ConnectX-3/ConnectX-3 Pro Virtual Function]

I then enable bionic-proposed and install the linux-azure-edge kernel
and reboot. I can't see the Mellanox device anymore:

$ dmesg | grep -i mella

$ uname -a
Linux davecore-an 4.18.0-1004-azure #4~18.04.1-Ubuntu SMP Thu Oct 25 14:25:41 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l | grep linux-azure
ii  linux-azure  4.15.0.1030.30 
 amd64Complete Linux kernel for Azure systems.
ii  linux-azure-cloud-tools-4.15.0-1030  4.15.0-1030.31 
 amd64Linux kernel version specific cloud tools for version 
4.15.0-1030
ii  linux-azure-edge 4.18.0.1004.5  
 amd64Complete Linux kernel for Azure systems.
ii  linux-azure-edge-cloud-tools-4.18.0-1004 4.18.0-1004.4~18.04.1  
 amd64Linux kernel version specific cloud tools for version 
4.18.0-1004
ii  linux-azure-edge-tools-4.18.0-1004   4.18.0-1004.4~18.04.1  
 amd64Linux kernel version specific tools for version 
4.18.0-1004
ii  linux-azure-headers-4.15.0-1030  4.15.0-1030.31 
 all  Header files related to Linux kernel version 4.15.0
ii  linux-azure-headers-4.18.0-1004  4.18.0-1004.4~18.04.1  
 all  Header files related to Linux kernel version 4.18.0
ii  linux-azure-tools-4.15.0-10304.15.0-1030.31 
 amd64Linux kernel version specific tools for version 
4.15.0-1030

$ lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled) (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 

[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
Thanks for testing.  That's interesting because both of those kernels
are not the custom azure kernel and you say you don't see this bug on
the 4.15 azure kernel.  However, it is seen on the non-azure 4.15
kernel.

Can you see if this kernel exhibits the bug:
https://launchpad.net/ubuntu/+source/linux/4.15.0-20.21/+build/14791489

In parallel, I'm going to create an image on azure to see if I can
reproduce the bug as well.   Are there any particular options I should
pass to azure when creating the VM or just the default?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Chris Valean
"Just to confirm, the 4.18 kernel you see this bug in is the standard Ubuntu 
kernel?"
> A: this first was seen in the daily cosmic 18.10 images (before RTM), and 
> when azure-edge kernels were created we've seen this problem on those as well.
That being azure-edge for Bionic for example, not only Cosmic one.


Both kernels provided in comment #9 are having the issue - 4.15.0-29 and 
4.17.0-4.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
** Changed in: linux-azure (Ubuntu)
   Importance: High => Critical

** Changed in: linux (Ubuntu Cosmic)
   Importance: High => Critical

** Changed in: linux (Ubuntu)
   Importance: High => Critical

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
For 4.18 based azure images, there are two repos:

lp:~canonical-kernel/ubuntu/+source/linux-azure/+git/cosmic

or the azure-edge-next branch in the bionic azure tree.

I'm going to review both to see if the commits going from 4.15 to 4.18
are linear.  If they are, we may be able to bisect.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-20 Thread Joseph Salisbury
Just to confirm, the 4.18 kernel you see this bug in is the standard
Ubuntu kernel?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Joseph Salisbury
Also, the Ubuntu kernel trees are located at:

4.15:  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/
4.18:  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/cosmic/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Joseph Salisbury
Regarding my comment #9, I read your comment #7 incorrectly.  I
literally read you don't know how a bisect would work.  I understand
clearly now.

We still should be able to bisect using the azure tree.  I'll review the
commits between 4.15 and 4.18 and see if anything sticks out.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Joseph Salisbury
I can build you kernels for the bisect.  You test the kernel and post
back if it has the bug or not.  Then I will build the next kernel based
on your results.  Repeat.

To start a bisect, we first need to identify the last good kernel
version and the first bad one.  Can you test the following kernels:

4.15.0-29: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15137612
4.17.0-4: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/15068818


** Changed in: linux (Ubuntu Cosmic)
 Assignee: Marcelo Cerri (mhcerri) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Marcelo Cerri (mhcerri) => Joseph Salisbury (jsalisbury)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Chris Valean
If you can point me to the ubuntu kernel sources where we can see how
the 4.15 and 4.18 kernels are found then I can check if a bisect would
be possible as such.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Chris Valean
What I know is that this is working in azure kernels 4.15 series, but
not in 4.18 since we got the dailies with it for Cosmic.

>From the ubuntu kernel tree if these versions are separate branches then
I don't know how a bisect would work...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Joseph Salisbury
That is if this is a regression.  Was this working on a prior kernel
version?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-19 Thread Joseph Salisbury
Do you have a way to test some kernels out?  If so, we could perform a
kernel bisect to narrow down the commit that introduced this.

** Tags removed: kernel-da-key
** Tags added: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-15 Thread Joseph Salisbury
** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-azure (Ubuntu Cosmic)

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-azure (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** No longer affects: linux-azure (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Bionic)

** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-azure (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-11-12 Thread Joshua R. Poulson
This is a blocked for 4.18 in 18.04. This bug should be extended to
bionic "linux-azure"

-- 
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/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-10-26 Thread Chris Valean
Bug is now carried in linux-azure-edge kernels on the 4.18 tree, these
should not be published to release further from proposed.

-- 
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/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1794477] Re: Accelerated networking (SR-IOV VF) broken in 18.10 daily

2018-10-16 Thread Chris Valean
** Summary changed:

- [Azure] Accelerated networking broken in 18.10 daily
+ Accelerated networking (SR-IOV VF) broken in 18.10 daily

-- 
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/1794477

Title:
  Accelerated networking (SR-IOV VF) broken in 18.10 daily

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we 
discovered that accelerated networking wasn’t working inside the VM.
  No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in 
use.
  We tested the daily build on Hyper-V also, but there the Mellanox VF is 
functional, with the same mlx4 drivers.

  To give more details about this:
  • No mellanox logs are showing up in dmesg or syslog.
  • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as 
loaded, although Accelerated Networking is enabled for the Azure VM, so this 
should happen transparently.
  • Modprobe  -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but 
nothing really happens. And no Mellanox messages are logged in dmesg/syslog.
  - There are no entries in the logs to show anything about the drivers or 
netvsc/pci-hyperv that might relate to this issue.

  Kernel: 4.18.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp