[Kernel-packages] [Bug 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

I verified that the new drivers are in the trusty-proposed and the
yakkety netboot installers. Everything looks good.

** Tags removed: verification-needed
** Tags added: verification-done-trusty

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in debian-installer source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1625222/+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 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625222/+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 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Craig Magina (craig.magina)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625222/+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 1625232] Re: xgene i2c slimpro driver fails to load

[Craig Magina]

Verified that the X-Gene mailbox driver now loads.

[8.750686] xgene-slimpro-mbox 1054.slimpro-mbox: APM X-Gene SLIMpro 
MailBox registered
...
[8.819763] xgene-slimpro-i2c soc:i2cslimpro: Mailbox I2C Adapter registered

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  xgene i2c slimpro driver fails to load

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to 
communicate with the bmc, locally.

  [Test Case]
  Ensure the slimpro driver loads and that ipmitool can communicate with the 
bmc.

  [Regression Risk]
  The slimpro driver is a standalone, xgene driver, so any issues with it will 
only affect that platform. The patches were specified by APM as needed for 
local bmc access to work. Outside of the driver causing a crash, a regression 
in the driver itself would leave us in the same state we currently are, the 
driver not loading or no access to the bmc locally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625232/+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 1632739] Re: xgene merlin crashes when running as iperf server

[Craig Magina]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  xgene merlin crashes when running as iperf server

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The X-Gene Merlin board will hang and then crash.

  [Test Case]
  Have both the 1G and 10G interfaces connected, configured, and up. Bring down 
the 1G interface via 'ifconfig eth0 down'. Start the iperf server, i.e. iperf 
-s. From a separate system on the same 10G network, run the client, i.e. iperf 
-c <10G ip address for merlin board under test>.

  [Regression Risk]
  The patches are well tested, upstream and in yakkety, and only impacts the 
xgene enet driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632739/+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 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

** Summary changed:

- [SRU] [xenial] d-i is missing usb support for platforms that use the 
xhci-platform driver
+ d-i is missing usb support for platforms that use the xhci-platform driver

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625222/+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 1632739] Re: xgene merlin crashes when running as iperf server

[Craig Magina]

The backtrace was added at bug creation.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

Title:
  xgene merlin crashes when running as iperf server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  The X-Gene Merlin board will hang and then crash.

  [Test Case]
  Have both the 1G and 10G interfaces connected, configured, and up. Bring down 
the 1G interface via 'ifconfig eth0 down'. Start the iperf server, i.e. iperf 
-s. From a separate system on the same 10G network, run the client, i.e. iperf 
-c <10G ip address for merlin board under test>.

  [Regression Risk]
  The patches are well tested, upstream and in yakkety, and only impacts the 
xgene enet driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632739/+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 1632739] [NEW] xgene merlin crashes when running as iperf server

[Craig Magina]

Public bug reported:

[Impact]
The X-Gene Merlin board will hang and then crash.

[Test Case]
Have both the 1G and 10G interfaces connected, configured, and up. Bring down 
the 1G interface via 'ifconfig eth0 down'. Start the iperf server, i.e. iperf 
-s. From a separate system on the same 10G network, run the client, i.e. iperf 
-c <10G ip address for merlin board under test>.

[Regression Risk]
The patches are well tested, upstream and in yakkety, and only impacts the 
xgene enet driver.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Attachment added: "backtrace"
   
https://bugs.launchpad.net/bugs/1632739/+attachment/4759932/+files/ami_merlin_kernel_crash.log

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

Title:
  xgene merlin crashes when running as iperf server

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The X-Gene Merlin board will hang and then crash.

  [Test Case]
  Have both the 1G and 10G interfaces connected, configured, and up. Bring down 
the 1G interface via 'ifconfig eth0 down'. Start the iperf server, i.e. iperf 
-s. From a separate system on the same 10G network, run the client, i.e. iperf 
-c <10G ip address for merlin board under test>.

  [Regression Risk]
  The patches are well tested, upstream and in yakkety, and only impacts the 
xgene enet driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632739/+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 1625222] Re: [SRU] [xenial] d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

** Summary changed:

- d-i is missing usb support for platforms that use the xhci-platform driver
+ [SRU] [xenial] d-i is missing usb support for platforms that use the 
xhci-platform driver

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

Title:
  [SRU] [xenial] d-i is missing usb support for platforms that use the
  xhci-platform driver

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625222/+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 1625232] Re: [SRU] [xenial] xgene i2c slimpro driver fails to load

[Craig Magina]

** Summary changed:

- [xenial] xgene i2c slimpro driver fails to load
+ [SRU] [xenial] xgene i2c slimpro driver fails to load

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

Title:
  [SRU] [xenial] xgene i2c slimpro driver fails to load

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to 
communicate with the bmc, locally.

  [Test Case]
  Ensure the slimpro driver loads and that ipmitool can communicate with the 
bmc.

  [Regression Risk]
  The slimpro driver is a standalone, xgene driver, so any issues with it will 
only affect that platform. The patches were specified by APM as needed for 
local bmc access to work. Outside of the driver causing a crash, a regression 
in the driver itself would leave us in the same state we currently are, the 
driver not loading or no access to the bmc locally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625232/+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 1625232] [NEW] [xenial] xgene i2c slimpro driver fails to load

[Craig Magina]

Public bug reported:

[Impact]
The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to 
communicate with the bmc, locally.

[Test Case]
Ensure the slimpro driver loads and that ipmitool can communicate with the bmc.

[Regression Risk]
The slimpro driver is a standalone, xgene driver, so any issues with it will 
only affect that platform. The patches were specified by APM as needed for 
local bmc access to work. Outside of the driver causing a crash, a regression 
in the driver itself would leave us in the same state we currently are, the 
driver not loading or no access to the bmc locally.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Craig Magina (craig.magina)
 Status: In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

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

Title:
  [xenial] xgene i2c slimpro driver fails to load

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to 
communicate with the bmc, locally.

  [Test Case]
  Ensure the slimpro driver loads and that ipmitool can communicate with the 
bmc.

  [Regression Risk]
  The slimpro driver is a standalone, xgene driver, so any issues with it will 
only affect that platform. The patches were specified by APM as needed for 
local bmc access to work. Outside of the driver causing a crash, a regression 
in the driver itself would leave us in the same state we currently are, the 
driver not loading or no access to the bmc locally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625232/+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 1625222] Re: d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625222/+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 1625222] [NEW] d-i is missing usb support for platforms that use the xhci-platform driver

[Craig Magina]

Public bug reported:

[Impact]
Any platform that gets usb support from the xhci-platform driver does not have 
usb enabled in d-i.

[Test Case]
Boot into d-i and attempt to use a usb device, i.e. keyboard.

[Regression Risk]
Extremely low as this is a driver that is already present in the kernel.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  d-i is missing usb support for platforms that use the xhci-platform
  driver

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Any platform that gets usb support from the xhci-platform driver does not 
have usb enabled in d-i.

  [Test Case]
  Boot into d-i and attempt to use a usb device, i.e. keyboard.

  [Regression Risk]
  Extremely low as this is a driver that is already present in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625222/+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 1611399] Re: [SRU] xgene_enet: an extra interrupt may be pending for an interrupt controller that doesn't support irq_disable and hardware with level interrupt

[Craig Magina]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  [SRU] xgene_enet: an extra interrupt may be pending for an interrupt
  controller that doesn't support irq_disable and hardware with level
  interrupt

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  For interrupt controller that doesn't support irq_disable and hardware
  with level interrupt, an extra interrupt may be pending. This patch fixes
  the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
  as suggested by,

  'commit e9849777d0e2 ("genirq: Add flag to force mask in
   disable_irq[_nosync]()")'

  [Test Case]
  Run iperf on a merlin board to exercise the xgene_enet driver

  [Regression Risk]
  This commit only affects the xgene_enet driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611399/+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 1613157] Re: [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests

[Craig Magina]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  [Impact]
  During iperf testing of the xenial kernel, the line only achieves ~75% during 
multi-client testing. 

  [Test Case]
  Run iperf with multiple clients

  [Regression Risk]
  The patches changes only affect the xgene_enet driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613157/+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 1547047] Re: need arm64 acpi parking protocol support in xenial

[Craig Magina]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  need arm64 acpi parking protocol support in xenial

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  ARM64 systems that do not implement PSCI or are missing key parts of
  it need this patch to support things like kexec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547047/+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 1613157] [NEW] [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests

[Craig Magina]

Public bug reported:

[Impact]
During iperf testing of the xenial kernel, the line only achieves ~75% during 
multi-client testing. 

[Test Case]
Run iperf with multiple clients

[Regression Risk]
The patches changes only affect the xgene_enet driver

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Craig Magina (craig.magina)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

Title:
  [SRU] xgene_enet: 10g performance only hits ~75% on multi-client tests

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  During iperf testing of the xenial kernel, the line only achieves ~75% during 
multi-client testing. 

  [Test Case]
  Run iperf with multiple clients

  [Regression Risk]
  The patches changes only affect the xgene_enet driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613157/+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 1611399] Re: [SRU] xgene_enet: an extra interrupt may be pending for an interrupt controller that doesn't support irq_disable and hardware with level interrupt

[Craig Magina]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

Title:
  [SRU] xgene_enet: an extra interrupt may be pending for an interrupt
  controller that doesn't support irq_disable and hardware with level
  interrupt

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  For interrupt controller that doesn't support irq_disable and hardware
  with level interrupt, an extra interrupt may be pending. This patch fixes
  the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
  as suggested by,

  'commit e9849777d0e2 ("genirq: Add flag to force mask in
   disable_irq[_nosync]()")'

  [Test Case]
  Run iperf on a merlin board to exercise the xgene_enet driver

  [Regression Risk]
  This commit only affects the xgene_enet driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611399/+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 1611399] Re: [SRU] xgene_enet: an extra interrupt may be pending for an interrupt controller that doesn't support irq_disable and hardware with level interrupt

[Craig Magina]

The upstream commit that fixes this is:
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/net/ethernet/apm/xgene?id=b5d7a06906a4875524f5c61c0b312828bf6737de

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

Title:
  [SRU] xgene_enet: an extra interrupt may be pending for an interrupt
  controller that doesn't support irq_disable and hardware with level
  interrupt

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  For interrupt controller that doesn't support irq_disable and hardware
  with level interrupt, an extra interrupt may be pending. This patch fixes
  the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
  as suggested by,

  'commit e9849777d0e2 ("genirq: Add flag to force mask in
   disable_irq[_nosync]()")'

  [Test Case]
  Run iperf on a merlin board to exercise the xgene_enet driver

  [Regression Risk]
  This commit only affects the xgene_enet driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611399/+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 1611399] [NEW] [SRU] xgene_enet: an extra interrupt may be pending for an interrupt controller that doesn't support irq_disable and hardware with level interrupt

[Craig Magina]

Public bug reported:

[Impact]
For interrupt controller that doesn't support irq_disable and hardware
with level interrupt, an extra interrupt may be pending. This patch fixes
the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
as suggested by,

'commit e9849777d0e2 ("genirq: Add flag to force mask in
 disable_irq[_nosync]()")'

[Test Case]
Run iperf on a merlin board to exercise the xgene_enet driver

[Regression Risk]
This commit only affects the xgene_enet driver

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

Title:
  [SRU] xgene_enet: an extra interrupt may be pending for an interrupt
  controller that doesn't support irq_disable and hardware with level
  interrupt

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  For interrupt controller that doesn't support irq_disable and hardware
  with level interrupt, an extra interrupt may be pending. This patch fixes
  the issue by setting IRQ_DISABLE_UNLAZY flag for the interrupt line,
  as suggested by,

  'commit e9849777d0e2 ("genirq: Add flag to force mask in
   disable_irq[_nosync]()")'

  [Test Case]
  Run iperf on a merlin board to exercise the xgene_enet driver

  [Regression Risk]
  This commit only affects the xgene_enet driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611399/+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 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node

[Craig Magina]

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

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

Title:
  Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  [IMPACT]
  The value of the csr-mask of the SATA PHY clock DTS node has a
  wrong value resulting a kernel panic as the clock/reset is not
  proper for the PHY of the SATA host controller 1. This patch
  fixes the correct csr-mask value of the SATA PHY clock DTS node
  for the SATA Host controller 1.

  [TEST CASE]
  Attempt to boot from a disk attached to SATA Host controller 1.

  [Regression Potential]
  As the 'ok' is the default status of a device tree node, this patch
  removes the status of the PHY clock node of SATA Host Controller 1.
  The status of the clock node is handled from the firmware based on
  the controller enabled/disabled by the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+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 1359489] Re: Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node

[Craig Magina]

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

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

Title:
  Fix the csr-mask for APM X-Gene SoC AHCI SATA PHY clock DTS node

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  [IMPACT]
  The value of the csr-mask of the SATA PHY clock DTS node has a
  wrong value resulting a kernel panic as the clock/reset is not
  proper for the PHY of the SATA host controller 1. This patch
  fixes the correct csr-mask value of the SATA PHY clock DTS node
  for the SATA Host controller 1.

  [TEST CASE]
  Attempt to boot from a disk attached to SATA Host controller 1.

  [Regression Potential]
  As the 'ok' is the default status of a device tree node, this patch
  removes the status of the PHY clock node of SATA Host Controller 1.
  The status of the clock node is handled from the firmware based on
  the controller enabled/disabled by the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359489/+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 1561604] Re: x-gene2: add SoC v2 support to clock

[Craig Magina]

** Summary changed:

- x-gene2: fix rtc load error during kernel boot
+ x-gene2: add SoC v2 support to clock

** Description changed:

- This error "[ 0.981954] hctosys: unable to open rtc device (rtc0)" is
- seen while booting a new xgene2 board. This causes issues with any
- service (like MAAS) who tries to get the system time early in the
- booting process. The fix for this is two patches, one of which is
- already in the xenial kernel, the other is upstream in Linus's linux
- tree already, and changing a kernel module to be built-in for arm64.
+ Need an upstream patch to add support for the clock on the X-Gene 2
+ platform.

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

Title:
  x-gene2: add SoC v2 support to clock

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Need an upstream patch to add support for the clock on the X-Gene 2
  platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561604/+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 1561604] Re: x-gene2: fix rtc load error during kernel boot

[Craig Magina]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  x-gene2: fix rtc load error during kernel boot

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This error "[ 0.981954] hctosys: unable to open rtc device (rtc0)" is
  seen while booting a new xgene2 board. This causes issues with any
  service (like MAAS) who tries to get the system time early in the
  booting process. The fix for this is two patches, one of which is
  already in the xenial kernel, the other is upstream in Linus's linux
  tree already, and changing a kernel module to be built-in for arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561604/+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 1561604] [NEW] x-gene2: fix rtc load error during kernel boot

[Craig Magina]

Public bug reported:

This error "[ 0.981954] hctosys: unable to open rtc device (rtc0)" is
seen while booting a new xgene2 board. This causes issues with any
service (like MAAS) who tries to get the system time early in the
booting process. The fix for this is two patches, one of which is
already in the xenial kernel, the other is upstream in Linus's linux
tree already, and changing a kernel module to be built-in for arm64.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  x-gene2: fix rtc load error during kernel boot

Status in linux package in Ubuntu:
  New

Bug description:
  This error "[ 0.981954] hctosys: unable to open rtc device (rtc0)" is
  seen while booting a new xgene2 board. This causes issues with any
  service (like MAAS) who tries to get the system time early in the
  booting process. The fix for this is two patches, one of which is
  already in the xenial kernel, the other is upstream in Linus's linux
  tree already, and changing a kernel module to be built-in for arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1561604/+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 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port

[Craig Magina]

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

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

Title:
  [SRU] xgene-enet: add SGMII based 1GbE support for the second port

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+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 1547047] [NEW] need arm64 acpi parking protocol support in xenial

[Craig Magina]

Public bug reported:

ARM64 systems that do not implement PSCI or are missing key parts of it
need this patch to support things like kexec.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Craig Magina (craig.magina)
 Status: In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

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

Title:
  need arm64 acpi parking protocol support in xenial

Status in linux package in Ubuntu:
  In Progress

Bug description:
  ARM64 systems that do not implement PSCI or are missing key parts of
  it need this patch to support things like kexec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547047/+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 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port

[Craig Magina]

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

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

Title:
  [SRU] xgene-enet: add SGMII based 1GbE support for the second port

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+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 1514971] Re: [SRU trusty] arm64 USB support not enabled for APM Mustang

[Craig Magina]

Yes, and things seemed to work fine. However the same patch set caused
issues with wily on mcdivitt due to changes around the need for
CONFIG_DMA_CMA to be enabled. So, during investigations there,
additional patches were discovered as well as a bug fix for the dwc3
driver. The current patches in trusty proposed don't break anything,
they just aren't enough to get USB working completely on the mustang.

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

Title:
  [SRU trusty] arm64 USB support not enabled for APM Mustang

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

  [Test Case]
  Insert a USB device into an APM Mustang based platform.

  [Regression Risk]
  This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514971/+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 1514971] Re: [SRU trusty] arm64 USB support not enabled for APM Mustang

[Craig Magina]

The patches submitted for this bug turned out to not be the complete
picture. I have not hit any issues with these patches, but there are
additional patches that have been discovered recently as well as some
bug fixes that will need to be upstreamed around the dwc3 driver to
completely enable USB on the mustang platform. The current patch set
will not be changed, just additional patches will be added to the set.

** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty

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

Title:
  [SRU trusty] arm64 USB support not enabled for APM Mustang

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

  [Test Case]
  Insert a USB device into an APM Mustang based platform.

  [Regression Risk]
  This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514971/+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 1508471] Re: [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to dropped patch

[Craig Magina]

** Tags removed: verification-needed-wily
** Tags added: verification-done-wily

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

Title:
  [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to
  dropped patch

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Performance Regression.

  The copy_{to,from}_user implementations in the Ubuntu kernel are
  suboptimal. Optimized implementations have been accepted upstream and
  have shown a significant improvement in network performance. Previous
  Ubuntu releases included non-upstream versions of these patches, but
  they were dropped during the wily cycle.

  [Test Case]
  Generate traffic from one node to another using iperf.

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. However, it has been accepted by upstream 
after some cycles of review, and we have shipped earlier versions of it in 
every arm64 release prior to wily. The backported patches have also been tested 
on real arm64 hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508471/+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 1516682] Re: a trusty stable release patch breaks module loading on arm64

[Craig Magina]

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  a trusty stable release patch breaks module loading on arm64

Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  This upstream patch "arm64: errata: add module build workaround for
  erratum #843419" breaks module loading on arm64 and was pulled into
  trusty-proposed via stable release. The trusty master-next commit is:
  f869de1cf9b57d28dbba9f15569f5ae2c54c8724. Wily saw this as well, since
  it also carries the patch and the workaround used there was to disable
  CONFIG_ARM64_ERRATUM_843419.

  The issue was mentioned to upstream here:
  http://www.spinics.net/lists/arm-kernel/msg449982.html
  and a fix was proposed here: 
  http://www.spinics.net/lists/arm-kernel/msg450685.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516682/+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 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

** Tags removed: verification-needed-wily
** Tags added: verification-done-wily

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+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 1516682] Re: a trusty stable release patch breaks module loading on arm64

[Craig Magina]

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  a trusty stable release patch breaks module loading on arm64

Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  This upstream patch "arm64: errata: add module build workaround for
  erratum #843419" breaks module loading on arm64 and was pulled into
  trusty-proposed via stable release. The trusty master-next commit is:
  f869de1cf9b57d28dbba9f15569f5ae2c54c8724. Wily saw this as well, since
  it also carries the patch and the workaround used there was to disable
  CONFIG_ARM64_ERRATUM_843419.

  The issue was mentioned to upstream here:
  http://www.spinics.net/lists/arm-kernel/msg449982.html
  and a fix was proposed here: 
  http://www.spinics.net/lists/arm-kernel/msg450685.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516682/+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 1516682] Re: a trusty stable release patch breaks module loading on arm64

[Craig Magina]

Installed and verified each proposed kernel did not show the issue on a
mustang board.

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  a trusty stable release patch breaks module loading on arm64

Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  This upstream patch "arm64: errata: add module build workaround for
  erratum #843419" breaks module loading on arm64 and was pulled into
  trusty-proposed via stable release. The trusty master-next commit is:
  f869de1cf9b57d28dbba9f15569f5ae2c54c8724. Wily saw this as well, since
  it also carries the patch and the workaround used there was to disable
  CONFIG_ARM64_ERRATUM_843419.

  The issue was mentioned to upstream here:
  http://www.spinics.net/lists/arm-kernel/msg449982.html
  and a fix was proposed here: 
  http://www.spinics.net/lists/arm-kernel/msg450685.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516682/+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 1516682] [NEW] a trusty stable release patch breaks module loading on arm64

[Craig Magina]

Public bug reported:

This upstream patch "arm64: errata: add module build workaround for
erratum #843419" breaks module loading on arm64 and was pulled into
trusty-proposed via stable release. The trusty master-next commit is:
f869de1cf9b57d28dbba9f15569f5ae2c54c8724. Wily saw this as well, since
it also carries the patch and the workaround used there was to disable
CONFIG_ARM64_ERRATUM_843419.

The issue was mentioned to upstream here:
http://www.spinics.net/lists/arm-kernel/msg449982.html
and a fix was proposed here: 
http://www.spinics.net/lists/arm-kernel/msg450685.html

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: trusty

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

Title:
  a trusty stable release patch breaks module loading on arm64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This upstream patch "arm64: errata: add module build workaround for
  erratum #843419" breaks module loading on arm64 and was pulled into
  trusty-proposed via stable release. The trusty master-next commit is:
  f869de1cf9b57d28dbba9f15569f5ae2c54c8724. Wily saw this as well, since
  it also carries the patch and the workaround used there was to disable
  CONFIG_ARM64_ERRATUM_843419.

  The issue was mentioned to upstream here:
  http://www.spinics.net/lists/arm-kernel/msg449982.html
  and a fix was proposed here: 
  http://www.spinics.net/lists/arm-kernel/msg450685.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516682/+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 1514853] Re: Trusty update to 3.13.11-ckt29 stable release

[Craig Magina]

The commit for this change, "arm64: errata: add module build workaround
for erratum #843419" causes the kernel to fail on arm64. This issue was
seen with wily's kernel as well and was worked around by disabling
CONFIG_ARM64_ERRATUM_843419 in the kernel config. See LP#1502946
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946) for
additional information.

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

Title:
  Trusty update to 3.13.11-ckt29 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.13.11-ckt29 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.13.11-ckt29 stable release:

  sctp: donot reset the overall_error_count in SHUTDOWN_RECEIVE state
  KEYS: Fix race between key destruction and finding a keyring by name
  KEYS: Fix crash when attempt to garbage collect an uninstantiated keyring
  KEYS: Don't permit request_key() to construct a new keyring
  [stable-only] net: add length argument to skb_copy_and_csum_datagram_iovec
  spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
  spi: Fix documentation of spi_alloc_master()
  ARM: 8429/1: disable GCC SRA optimization
  powerpc/MSI: Fix race condition in tearing down MSI interrupts
  CIFS: fix type confusion in copy offload ioctl
  hwmon: (nct6775) Swap STEP_UP_TIME and STEP_DOWN_TIME registers for most chips
  USB: option: add ZTE PIDs
  x86/apic: Serialize LVTT and TSC_DEADLINE writes
  Btrfs: fix read corruption of compressed and shared extents
  btrfs: skip waiting on ordered range for special files
  arm64: head.S: initialise mdcr_el2 in el2_setup
  kvm: fix zero length mmio searching
  iser-target: remove command with state ISTATE_REMOVE
  ARM: fix Thumb2 signal handling when ARMv6 is enabled
  powerpc/mm: Recompute hash value after a failed update
  x86/platform: Fix Geode LX timekeeping in the generic x86 build
  arm64: compat: fix vfp save/restore across signal handlers in big-endian
  arm64: errata: add module build workaround for erratum #843419
  arm64: KVM: Disable virtual timer even if the guest is not using it
  arm: KVM: Disable virtual timer even if the guest is not using it
  KVM: x86: trap AMD MSRs for the TSeg base and mask
  usb: Use the USB_SS_MULT() macro to get the burst multiplier.
  xhci: give command abortion one more chance before killing xhci
  usb: xhci: Clear XHCI_STATE_DYING on start
  xhci: change xhci 1.0 only restrictions to support xhci 1.1
  disabling oplocks/leases via module parm enable_oplocks broken for SMB3
  cifs: use server timestamp for ntlmv2 authentication
  x86/paravirt: Replace the paravirt nop with a bona fide empty function
  x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
  ASoC: pxa: pxa2xx-ac97: fix dma requestor lines
  drm/qxl: only report first monitor as connected if we have no state
  PCI: Fix devfn for VPD access through function 0
  PCI: Use function 0 VPD for identical functions, regular VPD for others
  perf header: Fixup reading of HEADER_NRCPUS feature
  netfilter: nft_compat: skip family comparison in case of NFPROTO_UNSPEC
  ASoC: fix broken pxa SoC support
  ARM: dts: omap5-uevm.dts: fix i2c5 pinctrl offsets
  vxlan: set needed headroom correctly
  usbnet: Get EVENT_NO_RUNTIME_PM bit before it is cleared
  net/ipv6: Correct PIM6 mrt_lock handling
  netlink, mmap: transform mmap skb into full skb on taps
  openvswitch: Zero flows on allocation.
  fib_rules: fix fib rule dumps across multiple skbs
  Btrfs: update fix for read corruption of compressed and shared extents
  Linux 3.13.11-ckt29

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514853/+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 1514971] [NEW] [SRU trusty] arm64 USB support not enabled for APM Mustang

[Craig Magina]

Public bug reported:

[Impact]
Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

[Test Case]
Insert a USB device into an APM Mustang based platform.

[Regression Risk]
This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [SRU trusty] arm64 USB support not enabled for APM Mustang

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Currently USB is not enabled for arm64 platforms. The patches will enable USB 
for arm64 and for APM's Mustang platform. 

  [Test Case]
  Insert a USB device into an APM Mustang based platform.

  [Regression Risk]
  This patch set enables USB for all arm64 platforms, but they have all been 
accepted by upstream and have been tested on a couple Mustang platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514971/+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 1508471] Re: [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to dropped patch

[Craig Magina]

** Description changed:

- From trusty through to vivid there is a copy_to/from_user patch that
- improved performance on the m400. This patch was not pushed into wily's
- 4.2 kernel as a new one was nearing upstream acceptance. That patch has
- now landed in linux-next and needs to be backported to wily's 4.2
- kernel.
+ [Impact]
+ The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been accepted upstream and have shown a 
significant improvement in network performance.
+ 
+ [Test Case]
+ Generate traffic from one node to another using iperf.
+ 
+ [Regression Risk]
+ These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. However, it has been accepted by upstream 
after some cycles of review. The backported patches have also been tested on 
real arm64 hardware.

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

Title:
  [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to
  dropped patch

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Performance Regression.

  The copy_{to,from}_user implementations in the Ubuntu kernel are
  suboptimal. Optimized implementations have been accepted upstream and
  have shown a significant improvement in network performance. Previous
  Ubuntu releases included non-upstream versions of these patches, but
  they were dropped during the wily cycle.

  [Test Case]
  Generate traffic from one node to another using iperf.

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. However, it has been accepted by upstream 
after some cycles of review, and we have shipped earlier versions of it in 
every arm64 release prior to wily. The backported patches have also been tested 
on real arm64 hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508471/+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 1508471] [NEW] [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to dropped patch

[Craig Magina]

Public bug reported:

>From trusty through to vivid there is a copy_to/from_user patch that
improved performance on the m400. This patch was not pushed into wily's
4.2 kernel as a new one was nearing upstream acceptance. That patch has
now landed in linux-next and needs to be backported to wily's 4.2
kernel.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Craig Magina (craig.magina)
 Status: In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

** Summary changed:

- arm64 performance regression in wily 4.2 kernel on m400 due to dropped patch
+ [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to dropped 
patch

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

Title:
  [SRU] arm64 performance regression in wily 4.2 kernel on m400 due to
  dropped patch

Status in linux package in Ubuntu:
  In Progress

Bug description:
  From trusty through to vivid there is a copy_to/from_user patch that
  improved performance on the m400. This patch was not pushed into
  wily's 4.2 kernel as a new one was nearing upstream acceptance. That
  patch has now landed in linux-next and needs to be backported to
  wily's 4.2 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508471/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

[Craig Magina]

Vivid deployment succeeded with no issues.

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
  Confirmed
Status in curtin:
  New
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed
Status in cloud-init source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 1494357] Re: [SRU] Add X-Gene EDAC Driver

[Craig Magina]

I installed the vivid kernel on my m400 and verified the driver is
loaded and detected the hardware.

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  [SRU] Add X-Gene EDAC Driver

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  APM's X-Gene Mustang board supports EDAC, which is unsupported by all 
versions of Ubuntu prior to wily.

  [Test Case]
  Look in /var/log/kern.log for messages from the loading of the EDAC driver.

  [Regression Risk]
  The changes contain some core EDAC cleanup that affects all architectures, 
but not functionally, just build time and the X-Gene EDAC driver itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494357/+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 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

The crash does not reproduce when running with kernel 4.2.0-12.14 .

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+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 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

Here is a bit more of that code for context:

static int __init numa_register_memblks(struct numa_meminfo *mi)
{
unsigned long uninitialized_var(pfn_align);
int i, nid;

/* Account for nodes with cpus and no memory */
node_possible_map = numa_nodes_parsed;
numa_nodemask_from_meminfo(_possible_map, mi);
if (WARN_ON(nodes_empty(node_possible_map)))
return -EINVAL;

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+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 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

The dump stack comes from this according to the trace:
if (WARN_ON(nodes_empty(node_possible_map)))

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+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 1502946] Re: kernel crash on m400 arm64 server cartridge

[Craig Magina]

ARM64 NUMA was added and enabled in 4.2.0-13.15, which apparently breaks
on the m400.

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

Title:
  kernel crash on m400 arm64 server cartridge

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've made some progress on bug 1499869 , such that on Friday I actually had 
successful installs.
  An attempt at an install today shows a kernel stack trace early in the boot, 
then the initramfs not finding any network devices and thus failing to mount 
the iscsi root.

  The trace looks like this:
  [0.00] [ cut here ]
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-Nwr5zx/linux-4.2.0/arch/arm64/mm/numa.c:449 numa_init+0x90/0x398()
  [0.00] Modules linked in:
  [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.2.0-14-generic 
#16-Ubuntu
  [0.00] Hardware name: HP ProLiant m400 Server Cartridge (DT)
  [0.00] Call trace:
  [0.00] [] dump_backtrace+0x0/0x150
  [0.00] [] show_stack+0x20/0x30
  [0.00] [] dump_stack+0x7c/0x98
  [0.00] [] warn_slowpath_common+0xa0/0xe0
  [0.00] [] warn_slowpath_null+0x38/0x50
  [0.00] [] numa_init+0x8c/0x398
  [0.00] [] arm64_numa_init+0x30/0x40
  [0.00] [] bootmem_init+0x60/0x104
  [0.00] [] paging_init+0x198/0x224
  [0.00] [] setup_arch+0x274/0x5f8
  [0.00] [] start_kernel+0xdc/0x3f4
  [0.00] ---[ end trace f24b6c88ae00fa9a ]---
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   33.356615] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  ProcVersionSignature: User Name 3.13.0-63.103-generic 3.13.11-ckt25
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-63-generic N/A
   linux-backports-modules-3.13.0-63-generic  N/A
   linux-firmware 1.127.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-63-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502946/+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 1499869] Re: maas wily deployment to HP Proliant m400 fails

[Craig Magina]

Cloud-init is getting the wrong time because of this error:

[   14.726283] hctosys: unable to open rtc device (rtc0)

What that means is the RTC_DRV_XGENE kernel config option was changed to
'm', this needs to be built-in in order for the device to be available
for hctosys.

** Also affects: wily (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: wily (Ubuntu) => linux (Ubuntu)

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

Title:
  maas wily deployment to HP Proliant m400 fails

Status in cloud-init:
  New
Status in curtin:
  New
Status in MAAS:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 1494357] Re: [SRU] Add X-Gene EDAC Driver

[Craig Magina]

This bug is to fix the bug that EDAC does not currently work on the HP
Proliant m400 when running any release before wily.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Craig Magina (craig.magina)

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

Title:
  [SRU] Add X-Gene EDAC Driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  APM's X-Gene Mustang board supports EDAC, which is unsupported by all 
versions of Ubuntu prior to wily.

  [Test Case]
  Look in /var/log/kern.log for messages from the loading of the EDAC driver.

  [Regression Risk]
  The changes contain some core EDAC cleanup that affects all architectures, 
but not functionally, just build time and the X-Gene EDAC driver itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494357/+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 1494357] [NEW] [SRU] Add X-Gene EDAC Driver

[Craig Magina]

Public bug reported:

[Impact]
APM's X-Gene Mustang board supports EDAC, which is unsupported by all versions 
of Ubuntu prior to wily.

[Test Case]
Look in /var/log/kern.log for messages from the loading of the EDAC driver.

[Regression Risk]
The changes contain some core EDAC cleanup that affects all architectures, but 
not functionally, just build time and the X-Gene EDAC driver itself.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [SRU] Add X-Gene EDAC Driver

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  APM's X-Gene Mustang board supports EDAC, which is unsupported by all 
versions of Ubuntu prior to wily.

  [Test Case]
  Look in /var/log/kern.log for messages from the loading of the EDAC driver.

  [Regression Risk]
  The changes contain some core EDAC cleanup that affects all architectures, 
but not functionally, just build time and the X-Gene EDAC driver itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494357/+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 1474171] Re: Wily boot failure on HP proliant m400 server

[Craig Magina]

The latest wily linux-image-4.1.0-3-generic kernel (Full version:
4.1.0-3.3) boots on the HP Proliant m400 without issue.

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

Title:
  Wily boot failure on HP proliant m400 server

Status in linux package in Ubuntu:
  Triaged

Bug description:
  
  Looks kernel crashs inside mlx4_en_xmit() of mlx ethernet driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1474171/+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 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port

[Craig Magina]

ubuntu@am6:~$ uname -a  
Linux am6 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:31:00 UTC 2015 aarch64 
aarch64 aarch64 GNU/Linux
ubuntu@am6:~$ sudo ethtool eth2
Settings for eth2:
Supported ports: [ MII ]
Supported link modes:   1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Link detected: no

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

Title:
  [SRU] xgene-enet: add SGMII based 1GbE support for the second port

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+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 1455105] Re: [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400

[Craig Magina]

Verified with both a trusty and vivid base.

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown
  on HP Proliant m400

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to commit 
1972c97db5b, but is fixed by commit b90f8f22ed8.

  [Test Case]
  Login to the iLO-CM and issue 'set node power off shutdown c#n#'
  Check the console to ensure the node is shutting down.

  [Regression Risk]
  This re-enables a gpio driver on arm64 that was enabled on older versions of 
the kernel and is enabled for arm in general currently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455105/+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 1451593] Re: [SRU] Forward port XGene MSI-X driver to vivid

[Craig Magina]

Verified with a trusty and vivid base.

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  [SRU] Forward port XGene MSI-X driver to vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Without the MSI-X driver, network performance on the HP Proliant m400 will be 
degraded in vivid from what can be achieved in trusty and utopic.

  [Test Case]
  All commands work on the HP Proliant m400:

  'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry.
  'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... 
entries.

  [Regression Risk]
  This driver is self contained for the xgene1 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451593/+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 1455121] Re: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec

[Craig Magina]

** Tags removed: verification-verified-trusty
** Tags added: verification-done-trusty

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

Title:
  [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the
  firmware spec

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  On reboot, initialization commands can timeout causing the mellanox card to 
not initialize on boot.

  [Test Case]
  Reboot the system many, many times (this issue is rare).

  [Regression Risk]
  The fix comes from upstream and was submitted by Mellanox to bring the driver 
in-line with the way their firmware works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455121/+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 1455121] Re: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec

[Craig Magina]

Tested this on an HP Proliant m400 and verified the issue was not seen.

** Tags removed: verification-needed-trusty
** Tags added: verification-verified-trusty

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

Title:
  [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the
  firmware spec

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  On reboot, initialization commands can timeout causing the mellanox card to 
not initialize on boot.

  [Test Case]
  Reboot the system many, many times (this issue is rare).

  [Regression Risk]
  The fix comes from upstream and was submitted by Mellanox to bring the driver 
in-line with the way their firmware works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455121/+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 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port

[Craig Magina]

This patch set has been built on amd64 and arm64 to ensure no build
breakage. The arm64 kernel was tested on a Mustang board to verify it
worked properly and an HP Proliant m400 to ensure it did not cause
issues on an arm64 system that lacked the device.

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

Title:
  [SRU] xgene-enet: add SGMII based 1GbE support for the second port

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+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 1458042] [NEW] [trusty SRU] xgene-enet: add SGMII based 1GbE support for the second port

[Craig Magina]

Public bug reported:

[Impact]
APM's Mustang boards have a second SGMII based 1GbE interface that is currently 
unsupported by Ubuntu.

[Test Case]
Verify that the previously non-working SGMII based 1GbE interface now works.

[Regression Risk]
Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [trusty SRU] xgene-enet: add SGMII based 1GbE support for the second
  port

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+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 1458042] Re: [SRU] xgene-enet: add SGMII based 1GbE support for the second port

[Craig Magina]

** Summary changed:

- [trusty SRU] xgene-enet: add SGMII based 1GbE support for the second port
+ [SRU] xgene-enet: add SGMII based 1GbE support for the second port

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Craig Magina (craig.magina)

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

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

Title:
  [SRU] xgene-enet: add SGMII based 1GbE support for the second port

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  APM's Mustang boards have a second SGMII based 1GbE interface that is 
currently unsupported by Ubuntu.

  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.

  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE and first 
SGMII support, it is possible that that support has become impacted. The 
changes also impact drivers/of/of_net.c, which could impact other users of the 
interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458042/+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 1455105] Re: [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400

[Craig Magina]

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

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

Title:
  [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown
  on HP Proliant m400

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to commit 
1972c97db5b, but is fixed by commit b90f8f22ed8.

  [Test Case]
  Login to the iLO-CM and issue 'set node power off shutdown c#n#'
  Check the console to ensure the node is shutting down.

  [Regression Risk]
  This re-enables a gpio driver on arm64 that was enabled on older versions of 
the kernel and is enabled for arm in general currently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455105/+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 1455105] [NEW] [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400

[Craig Magina]

Public bug reported:

Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to
commit 1972c97db5b, but is fixed by commit b90f8f22ed8.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Craig Magina (craig.magina)
 Status: In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Craig Magina (craig.magina)

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

Title:
  [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown
  on HP Proliant m400

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to
  commit 1972c97db5b, but is fixed by commit b90f8f22ed8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455105/+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 1455105] Re: [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400

[Craig Magina]

** Description changed:

- Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to
- commit 1972c97db5b, but is fixed by commit b90f8f22ed8.
+ [Impact]
+ Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to commit 
1972c97db5b, but is fixed by commit b90f8f22ed8.
+ 
+ [Test Case]
+ Login to the iLO-CM and issue 'set node power off shutdown c#n#'
+ Check the console to ensure the node is shutting down.
+ 
+ [Regression Risk]
+ This re-enables a gpio driver on arm64 that was enabled on older versions of 
the kernel and is enabled for arm in general currently.

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

Title:
  [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown
  on HP Proliant m400

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to commit 
1972c97db5b, but is fixed by commit b90f8f22ed8.

  [Test Case]
  Login to the iLO-CM and issue 'set node power off shutdown c#n#'
  Check the console to ensure the node is shutting down.

  [Regression Risk]
  This re-enables a gpio driver on arm64 that was enabled on older versions of 
the kernel and is enabled for arm in general currently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455105/+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 1455121] [NEW] [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec

[Craig Magina]

Public bug reported:

[Impact]
On reboot, initialization commands can timeout causing the mellanox card to not 
initialize on boot.

[Test Case]
Reboot the system many, many times (this issue is rare).

[Regression Risk]
The fix comes from upstream and was submitted by Mellanox to bring the driver 
in-line with the way their firmware works.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Craig Magina (craig.magina)
 Status: In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Craig Magina (craig.magina)

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

Title:
  [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the
  firmware spec

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  On reboot, initialization commands can timeout causing the mellanox card to 
not initialize on boot.

  [Test Case]
  Reboot the system many, many times (this issue is rare).

  [Regression Risk]
  The fix comes from upstream and was submitted by Mellanox to bring the driver 
in-line with the way their firmware works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455121/+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 1451593] Re: [SRU] Forward port XGene MSI-X driver to vivid

[Craig Magina]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Craig Magina (craig.magina)

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

Title:
  [SRU] Forward port XGene MSI-X driver to vivid

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Without the MSI-X driver, network performance on the HP Proliant m400 will be 
degraded in vivid from what can be achieved in trusty and utopic.

  [Test Case]
  All commands work on the HP Proliant m400:

  'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry.
  'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... 
entries.

  [Regression Risk]
  This driver is self contained for the xgene1 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451593/+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 1451593] Re: [SRU] Forward port XGene MSI-X driver to vivid

[Craig Magina]

This bug is to forward port a driver from trusty/utopic to vivid.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Craig Magina (craig.magina)

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  [SRU] Forward port XGene MSI-X driver to vivid

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Without the MSI-X driver, network performance on the HP Proliant m400 will be 
degraded in vivid from what can be achieved in trusty and utopic.

  [Test Case]
  All commands work on the HP Proliant m400:

  'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry.
  'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... 
entries.

  [Regression Risk]
  This driver is self contained for the xgene1 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451593/+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 1451593] [NEW] [SRU] Forward port XGene MSI-X driver to vivid

[Craig Magina]

Public bug reported:

[Impact]
Without the MSI-X driver, network performance on the HP Proliant m400 will be 
degraded in vivid from what can be achieved in trusty and utopic.

[Test Case]
All commands work on the HP Proliant m400:

'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry.
'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... 
entries.

[Regression Risk]
This driver is self contained for the xgene1 platform.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [SRU] Forward port XGene MSI-X driver to vivid

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Without the MSI-X driver, network performance on the HP Proliant m400 will be 
degraded in vivid from what can be achieved in trusty and utopic.

  [Test Case]
  All commands work on the HP Proliant m400:

  'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry.
  'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... 
entries.

  [Regression Risk]
  This driver is self contained for the xgene1 platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451593/+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 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

[Craig Magina]

** Changed in: debian-installer (Ubuntu Vivid)
   Status: Confirmed = Fix Committed

** Changed in: linux (Ubuntu Vivid)
   Status: Confirmed = Fix Committed

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Linux Kernel:
  New
Status in debian-installer package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani ritesh.harj...@gmail.com
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1386490/+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 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

[Craig Magina]

Here is the patch set that fixes this issue:
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/log/?h=pci/iommushowmsg=1

I have tested them and they work when applied to the 3.19.0-10.10
kernel. The set of patches are from HEAD to pci/iommu.

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Linux Kernel:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani ritesh.harj...@gmail.com
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1386490/+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 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

[Craig Magina]

I have not been able to find a reliable way to reproduce this issue, but
the fix did not cause any issues in my testing.

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20:   feabe301 ffc0 feabe300 ffc0  
  fe40: c044fe70 ffc3 001b0a2c ffc0   ed3ea300 ffc3
  fe60: c044fe80 000b feabe300 ffc0 

[Kernel-packages] [Bug 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

[Craig Magina]

The upstream has merged a patch set into the iommu topic tree that
solves this issue for all platforms. I am currently testing that patch
set with the vivid 3.19 kernel.

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Linux Kernel:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani ritesh.harj...@gmail.com
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1386490/+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 1426043] Re: kernel 3.13.0-46.75 and 3.16.0-31.41 fails to boot on arm64

[Craig Magina]

** Summary changed:

- kernel 3.13.0-46.75 fails to boot on arm64
+ kernel 3.13.0-46.75 and 3.16.0-31.41 fails to boot on arm64

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

Title:
  kernel 3.13.0-46.75 and 3.16.0-31.41 fails to boot on arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Released

Bug description:
  The failure is:

  BUG: failure at
  
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!

  which comes from this code:

  static inline u64 arch_counter_get_cntpct(void)
  {
  /*
   * AArch64 kernel and user space mandate the use of CNTVCT.
   */
  BUG();
  return 0;
  }

  The -46 kernel includes commit 800a366 (corresponding to upstream
  commit 0b46b8a) clocksource: arch_timer: Fix code to use physical
  timers when requested. This was added to fix clock problems on certain
  ARMv7 systems. Unfortunately, it also appears to break ARMv8 systems.

  The upstream commit which fixes the ARMv8 breakage from commit 0b46b8a
  is d6ad369 clocksource: arch_timer: Only use the virtual counter
  (CNTVCT) on arm64. This commit appears not to have been backported to
  Trusty.

  Here is a full boot log of the failure:

  Starting kernel ...

  L3C: 8MB
  [ 0.00] Initializing cgroup subsys cpuset
  [ 0.00] Initializing cgroup subsys cpu
  [ 0.00] Initializing cgroup subsys cpuacct
  [ 0.00] Linux version 3.13.0-46-generic (buildd@templar) (gcc version 
4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #75-Ubuntu SMP Tue Feb 10 21:12:09 UTC 
2015 (Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15)
  [ 0.00] CPU: AArch64 Processor [500f0001] revision 1
  [ 0.00] bootconsole [earlycon0] enabled
  [ 0.00] On node 0 totalpages: 16777216
  [ 0.00] Normal zone: 229376 pages used for memmap
  [ 0.00] Normal zone: 16777216 pages, LIFO batch:31
  [ 0.00] PERCPU: Embedded 12 pages/cpu @ffc72000 s17088 r8192 
d23872 u49152
  [ 0.00] pcpu-alloc: s17088 r8192 d23872 u49152 alloc=12*4096
  [ 0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
  [ 0.00] Built 1 zonelists in Zone order, mobility grouping on. Total 
pages: 16547840
  [ 0.00] Kernel command line: console=ttyS0,9600n8r ro 
earlyprintk=uart8250-32bit,0x1c021000 debug
  [ 0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
  [ 0.00] Dentry cache hash table entries: 8388608 (order: 14, 67108864 
bytes)
  [ 0.00] Inode-cache hash table entries: 4194304 (order: 13, 33554432 
bytes)
  [ 0.00] software IO TLB [mem 0x4fbc80-0x4fc080] (64MB) mapped at 
[ffcfbc80-ffcfc07f]
  [ 0.00] Memory: 65994264K/67108864K available (5718K kernel code, 590K 
rwdata, 2536K rodata, 304K init, 538K bss, 1114600K reserved)
  [ 0.00] Virtual kernel memory layout:
  [ 0.00] vmalloc : 0xff80 - 0xffbb (245759 MB)
  [ 0.00] vmemmap : 0xffbce000 - 0xffbd1800 ( 896 MB)
  [ 0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB)
  [ 0.00] memory : 0xffc0 - 0xffd0 ( 65536 MB)
  [ 0.00] .init : 0xffc000891000 - 0xffc0008dd2c0 ( 305 kB)
  [ 0.00] .text : 0xffc8 - 0xffc0008909b4 ( 8259 kB)
  [ 0.00] .data : 0xffc0008de000 - 0xffc000971848 ( 591 kB)
  [ 0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
  [ 0.00] Hierarchical RCU implementation.
  [ 0.00] RCU dyntick-idle grace-period acceleration is enabled.
  [ 0.00] NR_IRQS:64 nr_irqs:64 0
  [ 0.00] Architected cp15 timer(s) running at 50.00MHz (phys).
  [ 0.00] BUG: failure at 
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!
  [ 0.00] Kernel panic - not syncing: BUG!
  [ 0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-46-generic 
#75-Ubuntu
  [ 0.00] Call trace:
  [ 0.00] [ffc8848c] dump_backtrace+0x0/0x16c
  [ 0.00] [ffc88608] show_stack+0x10/0x1c
  [ 0.00] [ffc000603e0c] dump_stack+0x74/0x94
  [ 0.00] [ffc0005fe040] panic+0xe0/0x20c
  [ 0.00] [ffc0004eb39c] arch_counter_get_cntpct+0x30/0x34
  [ 0.00] [ffc0008c28d4] arch_timer_common_init+0x1d4/0x244
  [ 0.00] [ffc0008c2b88] arch_timer_init+0x244/0x260
  [ 0.00] [ffc0008c26d8] clocksource_of_init+0x44/0x6c
  [ 0.00] [ffc000894b0c] time_init+0x8/0x38
  [ 0.00] [ffc000891694] start_kernel+0x200/0x360

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1426043/+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 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

[Craig Magina]

One final issue is the kernel version you used to test this fix contains
a bug that prevents it from booting on arm64 systems. The fix is in the
utopic-stable branch to be pulled into the next SRU cycle. The fix was
pushed into the latest trusty kernel for a one-off release,
3.13.0-46.76. You can read more about the issue here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1426043.

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 

[Kernel-packages] [Bug 1427243] [NEW] arm64 copy_to/from_user patch from trusty/utopic needs to be integrated with the vivid kernel tree

[Craig Magina]

Public bug reported:

This patch is an optimization and has yet to be accepted upstream, but
has been submitted and is present in our trusty and utopic kernels.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: hs-arm64

** Tags added: hs-arm64

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

Title:
  arm64 copy_to/from_user patch from trusty/utopic needs to be
  integrated with the vivid kernel tree

Status in linux package in Ubuntu:
  New

Bug description:
  This patch is an optimization and has yet to be accepted upstream, but
  has been submitted and is present in our trusty and utopic kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427243/+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 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

[Craig Magina]

I just looked at your packages and noticed they are for amd64, this
issue is an xgene (arm64) platform bug. If you give me the a point to
the git tree I can build the packages myself and test. Thanks.

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20:   feabe301 ffc0 feabe300 ffc0  
  fe40: c044fe70 ffc3 001b0a2c ffc0 

[Kernel-packages] [Bug 1426043] [NEW] kernel 3.13.0-46.75 fails to boot on arm64

[Craig Magina]

Public bug reported:

The failure is:

BUG: failure at
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!

which comes from this code:

static inline u64 arch_counter_get_cntpct(void)
{
/*
 * AArch64 kernel and user space mandate the use of CNTVCT.
 */
BUG();
return 0;
}

The -46 kernel includes commit 800a366 (corresponding to upstream commit
0b46b8a) clocksource: arch_timer: Fix code to use physical timers when
requested. This was added to fix clock problems on certain ARMv7
systems. Unfortunately, it also appears to break ARMv8 systems.

The upstream commit which fixes the ARMv8 breakage from commit 0b46b8a
is d6ad369 clocksource: arch_timer: Only use the virtual counter
(CNTVCT) on arm64. This commit appears not to have been backported to
Trusty.

Here is a full boot log of the failure:

Starting kernel ...

L3C: 8MB
[ 0.00] Initializing cgroup subsys cpuset
[ 0.00] Initializing cgroup subsys cpu
[ 0.00] Initializing cgroup subsys cpuacct
[ 0.00] Linux version 3.13.0-46-generic (buildd@templar) (gcc version 4.8.2 
(Ubuntu/Linaro 4.8.2-19ubuntu1) ) #75-Ubuntu SMP Tue Feb 10 21:12:09 UTC 2015 
(Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15)
[ 0.00] CPU: AArch64 Processor [500f0001] revision 1
[ 0.00] bootconsole [earlycon0] enabled
[ 0.00] On node 0 totalpages: 16777216
[ 0.00] Normal zone: 229376 pages used for memmap
[ 0.00] Normal zone: 16777216 pages, LIFO batch:31
[ 0.00] PERCPU: Embedded 12 pages/cpu @ffc72000 s17088 r8192 d23872 
u49152
[ 0.00] pcpu-alloc: s17088 r8192 d23872 u49152 alloc=12*4096
[ 0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[ 0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 
16547840
[ 0.00] Kernel command line: console=ttyS0,9600n8r ro 
earlyprintk=uart8250-32bit,0x1c021000 debug
[ 0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.00] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
[ 0.00] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
[ 0.00] software IO TLB [mem 0x4fbc80-0x4fc080] (64MB) mapped at 
[ffcfbc80-ffcfc07f]
[ 0.00] Memory: 65994264K/67108864K available (5718K kernel code, 590K 
rwdata, 2536K rodata, 304K init, 538K bss, 1114600K reserved)
[ 0.00] Virtual kernel memory layout:
[ 0.00] vmalloc : 0xff80 - 0xffbb (245759 MB)
[ 0.00] vmemmap : 0xffbce000 - 0xffbd1800 ( 896 MB)
[ 0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB)
[ 0.00] memory : 0xffc0 - 0xffd0 ( 65536 MB)
[ 0.00] .init : 0xffc000891000 - 0xffc0008dd2c0 ( 305 kB)
[ 0.00] .text : 0xffc8 - 0xffc0008909b4 ( 8259 kB)
[ 0.00] .data : 0xffc0008de000 - 0xffc000971848 ( 591 kB)
[ 0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.00] Hierarchical RCU implementation.
[ 0.00] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.00] NR_IRQS:64 nr_irqs:64 0
[ 0.00] Architected cp15 timer(s) running at 50.00MHz (phys).
[ 0.00] BUG: failure at 
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!
[ 0.00] Kernel panic - not syncing: BUG!
[ 0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-46-generic 
#75-Ubuntu
[ 0.00] Call trace:
[ 0.00] [ffc8848c] dump_backtrace+0x0/0x16c
[ 0.00] [ffc88608] show_stack+0x10/0x1c
[ 0.00] [ffc000603e0c] dump_stack+0x74/0x94
[ 0.00] [ffc0005fe040] panic+0xe0/0x20c
[ 0.00] [ffc0004eb39c] arch_counter_get_cntpct+0x30/0x34
[ 0.00] [ffc0008c28d4] arch_timer_common_init+0x1d4/0x244
[ 0.00] [ffc0008c2b88] arch_timer_init+0x244/0x260
[ 0.00] [ffc0008c26d8] clocksource_of_init+0x44/0x6c
[ 0.00] [ffc000894b0c] time_init+0x8/0x38
[ 0.00] [ffc000891694] start_kernel+0x200/0x360

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: Incomplete

** Affects: linux (Ubuntu Trusty)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: Incomplete


** Tags: trusty

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

Title:
  kernel 3.13.0-46.75 fails to boot on arm64

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete

Bug description:
  The failure is:

  BUG: failure at
  
/build/buildd/linux-3.13.0/arch/arm64/include/asm/arch_timer.h:143/arch_counter_get_cntpct()!

  which comes from this code:

  static inline u64 arch_counter_get_cntpct(void)
  {
  /*
   * AArch64 kernel and user space mandate the use of CNTVCT.
   

[Kernel-packages] [Bug 1425576] [NEW] Occasional crash in APM xgene enet driver on kernels prior to v3.19

[Craig Magina]

Public bug reported:

This crash was submitted upstream and a fix was already present, but it
didn't land until the 3.19 kernel. This bug is to track getting that fix
into trusty and utopic.

Unable to handle kernel NULL pointer dereference at virtual address 00c0
pgd = ffc3e639a000
[00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
Internal error: Oops: 9606 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
Hardware name: APM X-Gene Mustang board (DT)
task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
PC is at xgene_enet_process_ring+0x94/0x328
LR is at xgene_enet_process_ring+0x78/0x328
pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
sp : ffc3c044fa00
x29: ffc3c044fa00 x28: ffc0fe8aa218
x27:  x26: 
x25: ffc3ee2b7000 x24: 0040
x23: ffc0fe8aa418 x22: 01ff
x21: 0001 x20: ffc0ff058380
x19: 001c x18: 007f82d1c1f0
x17: 007f84afbc90 x16: ffc0001a6a8c
x15: 007f84b805a0 x14: 
x13: d0d03820 x12: 
x11: 0024 x10: d0d30a20
x9 : ffc00031da28 x8 : ffbdc000
x7 : ffc3cae0285e x6 : 0040fec0
x5 : 0c08100801400148 x4 : 0040ff00
x3 : 000200d1 x2 : 0066
x1 : 0043cae0285e x0 : ffc3ee2bb818

Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
Stack: (0xffc3c044fa00 to 0xffc3c045)
fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
fa80: fe8aa290 ffc0   0040  84b805a0 007f
faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
fb60:   2010 ff80 6145   
fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
fc60:     ae80   
fc80:   c7e8ed00 5df42439 001d  0092 
fca0:   001b    0092 
fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
fce0: 82d1c1f0 007f   fd024c90 ffc0  
fd00: feabe300 ffc0 ae80    011a 
fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
fdc0: edc06f70 ffc3 000b  ae80  0015 
fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
fe20:   feabe301 ffc0 feabe300 ffc0  
fe40: c044fe70 ffc3 001b0a2c ffc0   ed3ea300 ffc3
fe60: c044fe80 000b feabe300 ffc0 c044fe80 ffc3 001b0a80 ffc0
fe80: c044fe90 ffc3 001a6acc ffc0 82d1c600 007f 00086430 ffc0
fea0:   15b1cea0    84afbc9c 007f
fec0: 6000  0015  000b  ae80 
fee0:   ff80  82d1c700 007f 0001 
ff00:   c7e8ed00 5df42439 001d  0092 
ff20:   001b    0092 
ff40:   84b805a0 007f 008bc3d0  84afbc90 007f
ff60: 82d1c1f0 007f 0092  15b1cea0  

[Kernel-packages] [Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

[Craig Magina]

Here is a direct link to the upstream submission of the crash:

http://www.spinics.net/lists/arm-kernel/msg399023.html

The upstream commit that fixes it is:

commit ecf6ba83d76e0c78e89401750dc527008e14faa2
Author: Iyappan Subramanian isubramanian@xxx
Date:   Thu Jan 29 14:38:23 2015 -0800
drivers: net: xgene: fix: Out of order descriptor bytes read

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  New

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20:   feabe301 ffc0 feabe300 ffc0  
 

[Kernel-packages] [Bug 1423596] [NEW] kernel fails to build after enabling arm64 64k page support on Ubuntu-3.13.0-46.75

[Craig Magina]

Public bug reported:

Here is the failure:

In file included from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs.h:159:0,
 from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/../include/lustre_lib.h:49,
 from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:106:
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c: In 
function ‘loop_set_fd’:
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs_private.h:418:53:
 error: duplicate case
 value
 #define CLASSERT(cond) do {switch(42) {case (cond): case 0: break;}} while (0)
 ^
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:525:2: 
note: in expansion of macro ‘CLASSERT’
  CLASSERT(PAGE_CACHE_SIZE  (1  (sizeof(unsigned short) * 8)));
  ^
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs_private.h:418:40:
 error: previously use
d here
 #define CLASSERT(cond) do {switch(42) {case (cond): case 0: break;}} while (0)
^
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:525:2: 
note: in expansion of macro ‘CLASSERT’
  CLASSERT(PAGE_CACHE_SIZE  (1  (sizeof(unsigned short) * 8)));
  ^
make[7]: *** [drivers/staging/lustre/lustre/llite/lloop.o] Error 1
make[6]: *** [drivers/staging/lustre/lustre/llite] Error 2
make[5]: *** [drivers/staging/lustre/lustre] Error 2
make[4]: *** [drivers/staging/lustre] Error 2
make[3]: *** [drivers/staging] Error 2
make[3]: *** Waiting for unfinished jobs

A patch was submitted upstream, but it was not up to the standards required for 
acceptance.
https://lkml.org/lkml/2015/1/30/212

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  kernel fails to build after enabling arm64 64k page support on
  Ubuntu-3.13.0-46.75

Status in linux package in Ubuntu:
  New

Bug description:
  Here is the failure:

  In file included from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs.h:159:0,
   from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/../include/lustre_lib.h:49,
   from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:106:
  /home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c: In 
function ‘loop_set_fd’:
  
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs_private.h:418:53:
 error: duplicate case
   value
   #define CLASSERT(cond) do {switch(42) {case (cond): case 0: break;}} while 
(0)
   ^
  /home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:525:2: 
note: in expansion of macro ‘CLASSERT’
CLASSERT(PAGE_CACHE_SIZE  (1  (sizeof(unsigned short) * 8)));
^
  
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs_private.h:418:40:
 error: previously use
  d here
   #define CLASSERT(cond) do {switch(42) {case (cond): case 0: break;}} while 
(0)
  ^
  /home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:525:2: 
note: in expansion of macro ‘CLASSERT’
CLASSERT(PAGE_CACHE_SIZE  (1  (sizeof(unsigned short) * 8)));
^
  make[7]: *** [drivers/staging/lustre/lustre/llite/lloop.o] Error 1
  make[6]: *** [drivers/staging/lustre/lustre/llite] Error 2
  make[5]: *** [drivers/staging/lustre/lustre] Error 2
  make[4]: *** [drivers/staging/lustre] Error 2
  make[3]: *** [drivers/staging] Error 2
  make[3]: *** Waiting for unfinished jobs

  A patch was submitted upstream, but it was not up to the standards required 
for acceptance.
  https://lkml.org/lkml/2015/1/30/212

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423596/+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 1386490] Re: HP ProLiant m400 nic doesn't work after trusty

[Craig Magina]

** Changed in: santacruz
 Assignee: (unassigned) = Craig Magina (craig.magina)

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) = Craig Magina (craig.magina)

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Linux Kernel:
  New
Status in The Lomond project:
  New
Status in The Santacruz project:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani ritesh.harj...@gmail.com
  Date:   Wed Apr 23 06:29:46 2014 +0100

  arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core :01:00.0: command 0x23 timed out (go bit not 
cleared)
  [   18.710911] mlx4_core :01:00.0: Failed to initialize queue pair table, 
aborting

  
  There's an upstream discussion on the topic here:
http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1386490/+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 1423596] Re: kernel fails to build after enabling arm64 64k page support on Ubuntu-3.13.0-46.75

[Craig Magina]

This is a build failure and the build failure is included in the initial
description.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  kernel fails to build after enabling arm64 64k page support on
  Ubuntu-3.13.0-46.75

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Here is the failure:

  In file included from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs.h:159:0,
   from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/../include/lustre_lib.h:49,
   from 
/home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:106:
  /home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c: In 
function ‘loop_set_fd’:
  
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs_private.h:418:53:
 error: duplicate case
   value
   #define CLASSERT(cond) do {switch(42) {case (cond): case 0: break;}} while 
(0)
   ^
  /home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:525:2: 
note: in expansion of macro ‘CLASSERT’
CLASSERT(PAGE_CACHE_SIZE  (1  (sizeof(unsigned short) * 8)));
^
  
/home/ubuntu/trusty-xgene/drivers/staging/lustre/include/linux/libcfs/libcfs_private.h:418:40:
 error: previously use
  d here
   #define CLASSERT(cond) do {switch(42) {case (cond): case 0: break;}} while 
(0)
  ^
  /home/ubuntu/trusty-xgene/drivers/staging/lustre/lustre/llite/lloop.c:525:2: 
note: in expansion of macro ‘CLASSERT’
CLASSERT(PAGE_CACHE_SIZE  (1  (sizeof(unsigned short) * 8)));
^
  make[7]: *** [drivers/staging/lustre/lustre/llite/lloop.o] Error 1
  make[6]: *** [drivers/staging/lustre/lustre/llite] Error 2
  make[5]: *** [drivers/staging/lustre/lustre] Error 2
  make[4]: *** [drivers/staging/lustre] Error 2
  make[3]: *** [drivers/staging] Error 2
  make[3]: *** Waiting for unfinished jobs

  A patch was submitted upstream, but it was not up to the standards required 
for acceptance.
  https://lkml.org/lkml/2015/1/30/212

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423596/+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 1404335] Re: xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

[Craig Magina]

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404335/+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 1381084] Re: xgene-enet: add 10GbE support

[Craig Magina]

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  xgene-enet: add 10GbE support

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  APM's Mustang boards have a 10GbE interface that is currently unsupported by 
Ubuntu.
  [Test Case]
  Verify that the previously non-working 10GbE interface now works.
  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE support, it 
is possible that that support has become impacted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381084/+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 1404335] Re: xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

[Craig Magina]

** Tags added: hs-arm64

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404335/+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 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

[Craig Magina]

** Tags removed: verification-needed-trusty verification-needed-utopic
** Tags added: verification-done-trusty verification-done-utopic

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1404335] [NEW] xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

[Craig Magina]

Public bug reported:

[Impact]
Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

[Test Case]
The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

[Regression Potential]
These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404335/+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 1404335] Re: xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

[Craig Magina]

Here is an output from the console of a system experiencing this issue.

This bug occurs after executing sudo poweroff and sudo shutdown -h now This 
issue was found on trusty-updates and trusty-
proposed. It wasn't seen in the released version.

$ uname -a
Linux am5 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:32:32 UTC 2014 aarch64 
aarch64 aarch64 GNU/Linux

U-Boot 2013.04-mustang_sw_1.13.28-beta (Aug 25 2014 - 14:16:10)

ubuntu@am5:~$ sudo poweroff

Broadcast message from ubuntu@am5
 (/dev/ttyS0) at 17:33 ...

The system is going down for power off NOW!
ubuntwait-for-state stop/waiting
 * Stopping rsync daemon rsync [ OK ]
 * Asking all remaining processes to terminate... [ OK ]
 * All processes ended within 1 seconds... [ OK ]
 * Deactivating swap... [ OK ]
 * Unmounting local filesystems... [ OK ]
 * Will now halt
[22800.565563] reboot: System halted
[22828.004581] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[22856.004581] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[22884.004581] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22912.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22940.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22968.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[22996.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23024.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23052.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23080.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23108.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23136.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23164.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23192.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23220.004580] BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059]
[23248.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23276.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23304.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23332.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]
[23360.004580] BUG: soft lockup - CPU#0 stuck for 22s! [halt:2059]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  xgene: BUG: soft lockup - CPU#0 stuck for 23s! [halt:2059] on poweroff

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Fixes an issue where after the system halts the cpu starts to experience soft 
lockups.

  [Test Case]
  The most reliable means of reproducing this issue is to 'sudo poweroff' the 
system from the console.

  [Regression Potential]
  These patches are upstream patches that have been in the utopic kernel for 
quite a while and only affect the arm64 architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404335/+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 1400349] [NEW] [SRU] new arm64 optimized copy_to_user and copy_from_user assembly code

[Craig Magina]

Public bug reported:

[Impact]
The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been submitted upstream and have shown a 
significant improvement in network performance.

[Test Case]
Generate traffic from one node to another using iperf.

[Regression Risk]
These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. This risk is mitigated by using an 
implementation heavily based on the linaro string libraries (which are used in 
other places already, e.g. glibc), and through active testing of this patch on 
real hardware using a trusty-kernel base. The new patch will also undergo 
regression testing to ensure the memory corruption issue of the previous patch 
does not exist.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [SRU] new arm64 optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been submitted upstream and have shown a 
significant improvement in network performance.

  [Test Case]
  Generate traffic from one node to another using iperf.

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. This risk is mitigated by using an 
implementation heavily based on the linaro string libraries (which are used in 
other places already, e.g. glibc), and through active testing of this patch on 
real hardware using a trusty-kernel base. The new patch will also undergo 
regression testing to ensure the memory corruption issue of the previous patch 
does not exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400349/+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 1400349] Re: [SRU] new arm64 optimized copy_to_user and copy_from_user assembly code

[Craig Magina]

Here is a link to the original bug and fix that has since been reverted.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358949

This bug is for the new patch to fix the same issue.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion = Confirmed

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

Title:
  [SRU] new arm64 optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  The copy_{to,from}_user implementations in the Ubuntu kernel are suboptimal. 
Optimized implementations have been submitted upstream and have shown a 
significant improvement in network performance.

  [Test Case]
  Generate traffic from one node to another using iperf.

  [Regression Risk]
  These functions are obviously used heavily throughout the kernel, so a defect 
here could have significant impact. This risk is mitigated by using an 
implementation heavily based on the linaro string libraries (which are used in 
other places already, e.g. glibc), and through active testing of this patch on 
real hardware using a trusty-kernel base. The new patch will also undergo 
regression testing to ensure the memory corruption issue of the previous patch 
does not exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1400349/+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 1381216] Re: xgene-enet: add SGMII based 1GbE support

[Craig Magina]

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  xgene-enet: add SGMII based 1GbE support

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  APM's Mustang boards have an SGMII based 1GbE interface that is currently 
unsupported by Ubuntu.
  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.
  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE support, it 
is possible that that support has become impacted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381216/+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 1381084] Re: xgene-enet: add 10GbE support

[Craig Magina]

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  xgene-enet: add 10GbE support

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  APM's Mustang boards have a 10GbE interface that is currently unsupported by 
Ubuntu.
  [Test Case]
  Verify that the previously non-working 10GbE interface now works.
  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE support, it 
is possible that that support has become impacted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381084/+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 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

[Craig Magina]

Upstream already root caused the issue, so logs are not needed.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Utopic:
  New

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1381216] Re: xgene-enet: add SGMII based 1GbE support

[Craig Magina]

Trusty fails due to the patches that were missed in the pull.

** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty

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

Title:
  xgene-enet: add SGMII based 1GbE support

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  APM's Mustang boards have an SGMII based 1GbE interface that is currently 
unsupported by Ubuntu.
  [Test Case]
  Verify that the previously non-working SGMII based 1GbE interface now works.
  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE support, it 
is possible that that support has become impacted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381216/+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 1381084] Re: xgene-enet: add 10GbE support

[Craig Magina]

Trusty fails due to the patches that were missed in the pull.

** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty

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

Title:
  xgene-enet: add 10GbE support

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  APM's Mustang boards have a 10GbE interface that is currently unsupported by 
Ubuntu.
  [Test Case]
  Verify that the previously non-working 10GbE interface now works.
  [Regression Risk]
  Since the changes touch the driver that supports the existing GbE support, it 
is possible that that support has become impacted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381084/+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 1398596] [NEW] Revert arm64: optimized copy_to_user and copy_from_user assembly code

[Craig Magina]

Public bug reported:

The initial report of the issue can be found here:

http://www.spinics.net/lists/arm-kernel/msg381811.html

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Revert arm64: optimized copy_to_user and copy_from_user assembly code

Status in linux package in Ubuntu:
  New

Bug description:
  The initial report of the issue can be found here:

  http://www.spinics.net/lists/arm-kernel/msg381811.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1398596] Re: arm64: optimized copy_to_user and copy_from_user assembly code patch causing unhandled pagefaults

[Craig Magina]

Excerpt from the report:

The exact same fixup code is being used for copy_to_user and
copy_from_user.

For the copy_from_user case we want to zero the rest of the kernel
destination buffer when we hit a pagefault reading from user space.

However, for the copy_to_user case we most definitely don't want to
write zeros in the destination buffer when we hit a pagefault writing
to user space! I get unhandled pagefaults here, when copy_to_user is
called:

   0xffc00073c638 +8920:  strbwzr, [x6],#1
   0xffc00073c63c +8924:  subsx2, x2, #0x1
   0xffc00073c640 +8928:  b.ne0xffc00073c638 __hyp_text_end+8920
   0xffc00073c644 +8932:  ret

I would suggest re-working the fixup path and testing both fixup paths
thoroughly by placing the system under memory pressure and confirming
that they are both hit.

** Summary changed:

- arm64: optimized copy_to_user and copy_from_user assembly code patch causing 
unhandled pagefaults
+ Revert arm64: optimized copy_to_user and copy_from_user assembly code

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

Title:
  Revert arm64: optimized copy_to_user and copy_from_user assembly code

Status in linux package in Ubuntu:
  New

Bug description:
  The initial report of the issue can be found here:

  http://www.spinics.net/lists/arm-kernel/msg381811.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1398596] Re: Revert arm64: optimized copy_to_user and copy_from_user assembly code

[Craig Magina]

** Description changed:

- The initial report of the issue can be found here:
+ [Impact]
+ Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.
  
  http://www.spinics.net/lists/arm-kernel/msg381811.html
+ 
+ [Test Case]
+ Put the system under memory pressure.
+ 
+ [Regression Potential]
+ It will cause a performance regression on certain workloads on arm64 systems.

** Summary changed:

- Revert arm64: optimized copy_to_user and copy_from_user assembly code
+ [Revert] arm64: optimized copy_to_user and copy_from_user assembly code

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

Title:
  [Revert] arm64: optimized copy_to_user and copy_from_user assembly
  code

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Fixes an issue where the kernel hits unhandled pagefaults when copy_to_user 
is called.

  http://www.spinics.net/lists/arm-kernel/msg381811.html

  [Test Case]
  Put the system under memory pressure.

  [Regression Potential]
  It will cause a performance regression on certain workloads on arm64 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398596/+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 1386261] Re: xgene-pcie: Fix max payload size and phantom function configuration

[Craig Magina]

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  xgene-pcie: Fix max payload size and phantom function configuration

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  Systems under stress may encounter malformed TLP issues, which can result in 
networking dropping out after multiple hours.
  [Test Case]
  lspci -vvv output will show a MalfTLP+ in the Capabilities: [154 v2] 
Advanced Error Reporting section.
  [Regression Risk]
  Restricted to the xgene-pcie driver, so regression risk is restricted to the 
X-Gene platform, which has had many hours of testing with the proposed fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386261/+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 1382244] Re: HP ProLiant m400 nic fails to initialize when booted w/ debug

[Craig Magina]

Utopic kernel also tested in the same manner as the trusty kernel.

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  HP ProLiant m400 nic fails to initialize when booted w/ debug

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  On the majority of boots, the mlx4 driver will fail to initialize, resulting 
in no network connectivity. This only occurs if debug level
  logging to the serial console is enabled - which is not the default in Ubuntu.

  [Test Case]
  Enable debug logging:
$ echo 'setenv bootargs $bootargs debug'  
/etc/flash-kernel/ubootenv.d/debug
$ sudo flash-kernel
  And reboot.

  [Regression Risk]
  The MSI code being modified in question is only used on X-Gene systems, so 
risk to other systems is insignificant. In addition, the code being removed are 
just debug statements that aren't emitted by default today in Ubuntu, so even 
for X-Gene systems it is a minimal risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382244/+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 1382244] Re: HP ProLiant m400 nic fails to initialize when booted w/ debug

[Craig Magina]

Reproduced the bug with the current updates kernel, updated to the
proposed kernel and the bug was no longer reproducible.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  HP ProLiant m400 nic fails to initialize when booted w/ debug

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  On the majority of boots, the mlx4 driver will fail to initialize, resulting 
in no network connectivity. This only occurs if debug level
  logging to the serial console is enabled - which is not the default in Ubuntu.

  [Test Case]
  Enable debug logging:
$ echo 'setenv bootargs $bootargs debug'  
/etc/flash-kernel/ubootenv.d/debug
$ sudo flash-kernel
  And reboot.

  [Regression Risk]
  The MSI code being modified in question is only used on X-Gene systems, so 
risk to other systems is insignificant. In addition, the code being removed are 
just debug statements that aren't emitted by default today in Ubuntu, so even 
for X-Gene systems it is a minimal risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382244/+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 1386261] Re: xgene-pcie: Fix max payload size and phantom function configuration

[Craig Magina]

This fix was put under heavy stress for an extended period of time (72+
hours) on mutliple nodes and the issue was not seen.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  xgene-pcie: Fix max payload size and phantom function configuration

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  Systems under stress may encounter malformed TLP issues, which can result in 
networking dropping out after multiple hours.
  [Test Case]
  lspci -vvv output will show a MalfTLP+ in the Capabilities: [154 v2] 
Advanced Error Reporting section.
  [Regression Risk]
  Restricted to the xgene-pcie driver, so regression risk is restricted to the 
X-Gene platform, which has had many hours of testing with the proposed fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386261/+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 1354349] Re: The crash utility doesn't run in ARM64 based devices

[Craig Magina]

Verified on an arm64 system by running:
sudo crash /boot/System.map-3.13.0-36-generic 
/usr/lib/debug/boot/vmlinux-3.13.0-36-generic
Then from the 'crash' prompt, running 'dis sys_read' and getting the expected 
output.

** Changed in: crash (Ubuntu Trusty)
 Assignee: dann frazier (dannf) = Craig Magina (craig.magina)

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  The crash utility doesn't run in ARM64 based devices

Status in “crash” package in Ubuntu:
  Fix Released
Status in “crash” source package in Trusty:
  Fix Committed
Status in “crash” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Crash is useless on trusty/arm64

  [Test Case]
  BAD (today):
  dannf@mustang:~$ sudo crash /usr/lib/debug/boot/vmlinux-3.13.0-37-generic 

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   
  WARNING: arm64_verify_symbol: function not implemented
  WARNING: arm64_verify_symbol: function not implemented
 [repeats, ad nauseum]
  WARNING: arm64_verify_symbol: function not implemented
  WARNING: arm64_verify_symbol: function not implemented
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as aarch64-unknown-linux-gnu...

  crash: read error: kernel virtual address: ffc000612ce0  type: 
cpu_possible_mask
  dannf@mustang:~$

  
  GOOD:
  dannf@mustang:~$ sudo crash /usr/lib/debug/boot/vmlinux-3.13.0-37-generic 

  crash 7.0.3
  Copyright (C) 2002-2013  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter help copying to see the conditions.
  This program has absolutely no warranty.  Enter help warranty for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as aarch64-unknown-linux-gnu...

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-37-generic
  DUMPFILE: /dev/mem
  CPUS: 8
  DATE: Tue Sep 30 15:24:37 2014
UPTIME: 2 days, 05:04:47
  LOAD AVERAGE: 0.20, 0.59, 0.62
 TASKS: 150
  NODENAME: mustang
   RELEASE: 3.13.0-37-generic
   VERSION: #64-Ubuntu SMP Mon Sep 22 21:32:32 UTC 2014
   MACHINE: aarch64  (unknown Mhz)
MEMORY: 16 GB
   PID: 19911
   COMMAND: crash
  TASK: ffc21d18c200  [THREAD_INFO: ffc3e6978000]
   CPU: 3
 STATE: TASK_RUNNING (ACTIVE)

  crash dis sys_read
  0xffc0001a6bc0 SyS_read:  stp x29, x30, [sp,#-80]!
  0xffc0001a6bc4 sys_read+4:mov x29, sp
  0xffc0001a6bc8 sys_read+8:stp x19, x20, [sp,#16]
  0xffc0001a6bcc sys_read+12:   mov x20, x1
  0xffc0001a6bd0 sys_read+16:   add x1, x29, #0x48
  0xffc0001a6bd4 sys_read+20:   str x21, [sp,#32]
  0xffc0001a6bd8 sys_read+24:   str x2, [x29,#56]
  0xffc0001a6bdc sys_read+28:   bl  0xffc0001c1d4c 
fget_light
  0xffc0001a6be0 sys_read+32:   mov x19, x0
  0xffc0001a6be4 sys_read+36:   ldr w21, [x29,#72]
  0xffc0001a6be8 sys_read+40:   ldr x2, [x29,#56]
  0xffc0001a6bec sys_read+44:   cbz x0