[Kernel-packages] [Bug 1262901] [NEW] please include device-tree binaries for arm64
Public bug reported: The armhf images provides a number of dtb blobs under /lib/firmware/3.12.0-7-generic/device-tree. Can the same be done for the dts files in the upstream source (currently just 3). This would make it easier to e.g. create a boot image for the ARM fast model. ** 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/1262901 Title: please include device-tree binaries for arm64 Status in “linux” package in Ubuntu: Incomplete Bug description: The armhf images provides a number of dtb blobs under /lib/firmware/3.12.0-7-generic/device-tree. Can the same be done for the dts files in the upstream source (currently just 3). This would make it easier to e.g. create a boot image for the ARM fast model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1262901/+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 1234343] [NEW] FTBFS on arm64
Public bug reported:
libatasmart fails to build on arm64 due to outdated config.{sub,guess}
files.
** Affects: libatasmart (Ubuntu)
Importance: Undecided
Status: New
** Affects: libatasmart (Debian)
Importance: Unknown
Status: Unknown
** Attachment added: failed build log
https://bugs.launchpad.net/bugs/1234343/+attachment/3855880/+files/libatasmart.buildlog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1234343
Title:
FTBFS on arm64
Status in “libatasmart” package in Ubuntu:
New
Status in “libatasmart” package in Debian:
Unknown
Bug description:
libatasmart fails to build on arm64 due to outdated config.{sub,guess}
files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1234343/+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 1234343] Re: FTBFS on arm64
** Branch linked: lp:~dannf/ubuntu/saucy/libatasmart/lp1234343
** Bug watch added: Debian Bug tracker #725203
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725203
** Also affects: libatasmart (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725203
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1234343
Title:
FTBFS on arm64
Status in “libatasmart” package in Ubuntu:
New
Status in “libatasmart” package in Debian:
Unknown
Bug description:
libatasmart fails to build on arm64 due to outdated config.{sub,guess}
files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1234343/+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 1309221] Re: transparent hugepages flaky on arm64
dannf@mustang:~$ cat /proc/version Linux version 3.13.0-26-generic (buildd@magic) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #48-Ubuntu SMP Wed May 7 23:35:13 UTC 2014 dannf@mustang:~$ juju -h Juju -- devops distilled https://juju.ubuntu.com/ Juju provides easy, intelligent service orchestration on top of environments such as Amazon EC2, HP Cloud, OpenStack, MaaS, or your own local machine. Basic commands: juju init generate boilerplate configuration for juju environments juju bootstrapstart up an environment from scratch juju deploy deploy a new service juju add-relation add a relation between two services juju expose expose a service juju help bootstrap more help on e.g. bootstrap command juju help commandslist all commands juju help glossaryglossary of terms juju help topics list all help topics Provider information: juju help azure-provider use on Windows Azure juju help ec2-provider use on Amazon EC2 juju help hpcloud-provider use on HP Cloud juju help local-provider use on this computer juju help openstack-provider use on OpenStack ** 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/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to never until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+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 1309221] [NEW] transparent hugepages flaky on arm64
Public bug reported: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to never until we can fix this feature properly. ** 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/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: New Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to never until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+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 1334823] [NEW] please add xgene-gpio driver
Public bug reported: The X-Gene SoC contains a GPIO device for which there is currently no driver in Ubuntu. A driver has been posted and has gone through a series of review. These patches are available for trusty at: git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140626 ** 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/1334823 Title: please add xgene-gpio driver Status in “linux” package in Ubuntu: New Bug description: The X-Gene SoC contains a GPIO device for which there is currently no driver in Ubuntu. A driver has been posted and has gone through a series of review. These patches are available for trusty at: git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334823/+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 1334823] Re: please add xgene-gpio driver
** 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/1334823 Title: please add xgene-gpio driver Status in “linux” package in Ubuntu: Confirmed Bug description: The X-Gene SoC contains a GPIO device for which there is currently no driver in Ubuntu. A driver has been posted and has gone through a series of review. These patches are available for trusty at: git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334823/+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 1334823] Re: please add designware gpio support for x-gene
** Summary changed: - please add xgene-gpio driver + please add designware gpio support for x-gene ** Description changed: - The X-Gene SoC contains a GPIO device for which there is currently no driver in Ubuntu. A driver has been posted and has gone through a series of review. These patches are available for trusty at: - git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140626 + The X-Gene SoC contains a designware GPIO device that needs a driver backported from upstream. These patches are available for trusty at: + git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140628 -- 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/1334823 Title: please add designware gpio support for x-gene Status in “linux” package in Ubuntu: Confirmed Bug description: The X-Gene SoC contains a designware GPIO device that needs a driver backported from upstream. These patches are available for trusty at: git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140628 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334823/+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 1335636] [NEW] x-gene sata phy tuning varies across platforms
Public bug reported: The xgene-ahci driver sets sets the sata phy configuration, but this configuration can vary across platforms. Today the values we are using are optimal for the mustang development board, but suboptimal for other platforms. In general the recommendation is to move this into platform specific config in firmware - either by having firmware do the phy config, or by passing settings to the driver via device-tree config. But, that's a long term solution - in the short term, we can special case the Mustang board and use better default settings for other boards. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1335636 Title: x-gene sata phy tuning varies across platforms Status in “linux” package in Ubuntu: Incomplete Bug description: The xgene-ahci driver sets sets the sata phy configuration, but this configuration can vary across platforms. Today the values we are using are optimal for the mustang development board, but suboptimal for other platforms. In general the recommendation is to move this into platform specific config in firmware - either by having firmware do the phy config, or by passing settings to the driver via device-tree config. But, that's a long term solution - in the short term, we can special case the Mustang board and use better default settings for other boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335636/+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 1335636] Re: x-gene sata phy tuning varies across platforms
** 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/1335636 Title: x-gene sata phy tuning varies across platforms Status in “linux” package in Ubuntu: Confirmed Bug description: The xgene-ahci driver sets sets the sata phy configuration, but this configuration can vary across platforms. Today the values we are using are optimal for the mustang development board, but suboptimal for other platforms. In general the recommendation is to move this into platform specific config in firmware - either by having firmware do the phy config, or by passing settings to the driver via device-tree config. But, that's a long term solution - in the short term, we can special case the Mustang board and use better default settings for other boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335636/+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 1335645] [NEW] pending patch breaks xgene-ahci
Public bug reported: The following patch queued in trusty master-next introduces a regression in the xgene-ahci driver. commit 65e4c0de0b260fbd756d14f4df3bed694dcc52c0 Author: Dan Williams dan.j.willi...@intel.com Date: Thu Apr 17 11:48:21 2014 -0700 libata/ahci: accommodate tag ordered controllers BugLink: http://bugs.launchpad.net/bugs/1333837 commit 8a4aeec8d2d6a3edeffbdfae451cdf05cbf0fefd upstream. This issue is documented here: http://marc.info/?l=linux-kernelm=140195842716315w=2 There are patches in flight that resolve this problem - these are what I've been tested with. http://kernel.ubuntu.com/git?p=dannf/ubuntu-utopic-hyperscale.git;a=commit;h=bf8081785ddecfab928ced266cfb1092440da9c9 http://kernel.ubuntu.com/git?p=dannf/ubuntu-utopic-hyperscale.git;a=commit;h=9d182209b4c6be7cde703e235e99177215202366 These patches also resolve the issue - but they are not yet upstream, so I'm assuming that a revert for now is the more maintainable solution. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: hs-arm64 ** Changed in: linux (Ubuntu) Status: New = 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/1335645 Title: pending patch breaks xgene-ahci Status in “linux” package in Ubuntu: Confirmed Bug description: The following patch queued in trusty master-next introduces a regression in the xgene-ahci driver. commit 65e4c0de0b260fbd756d14f4df3bed694dcc52c0 Author: Dan Williams dan.j.willi...@intel.com Date: Thu Apr 17 11:48:21 2014 -0700 libata/ahci: accommodate tag ordered controllers BugLink: http://bugs.launchpad.net/bugs/1333837 commit 8a4aeec8d2d6a3edeffbdfae451cdf05cbf0fefd upstream. This issue is documented here: http://marc.info/?l=linux-kernelm=140195842716315w=2 There are patches in flight that resolve this problem - these are what I've been tested with. http://kernel.ubuntu.com/git?p=dannf/ubuntu-utopic-hyperscale.git;a=commit;h=bf8081785ddecfab928ced266cfb1092440da9c9 http://kernel.ubuntu.com/git?p=dannf/ubuntu-utopic-hyperscale.git;a=commit;h=9d182209b4c6be7cde703e235e99177215202366 These patches also resolve the issue - but they are not yet upstream, so I'm assuming that a revert for now is the more maintainable solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335645/+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 1335645] Re: pending patch breaks xgene-ahci
I can boot from disk, so yeah, it's good :) ** 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/1335645 Title: pending patch breaks xgene-ahci Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: The following patch queued in trusty master-next introduces a regression in the xgene-ahci driver. commit 65e4c0de0b260fbd756d14f4df3bed694dcc52c0 Author: Dan Williams dan.j.willi...@intel.com Date: Thu Apr 17 11:48:21 2014 -0700 libata/ahci: accommodate tag ordered controllers BugLink: http://bugs.launchpad.net/bugs/1333837 commit 8a4aeec8d2d6a3edeffbdfae451cdf05cbf0fefd upstream. This issue is documented here: http://marc.info/?l=linux-kernelm=140195842716315w=2 There are patches in flight that resolve this problem - these are what I've been tested with. http://kernel.ubuntu.com/git?p=dannf/ubuntu-utopic-hyperscale.git;a=commit;h=bf8081785ddecfab928ced266cfb1092440da9c9 http://kernel.ubuntu.com/git?p=dannf/ubuntu-utopic-hyperscale.git;a=commit;h=9d182209b4c6be7cde703e235e99177215202366 These patches also resolve the issue - but they are not yet upstream, so I'm assuming that a revert for now is the more maintainable solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335645/+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 1328295] Re: [serial] use hw flow control if supported
** 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/1328295 Title: [serial] use hw flow control if supported Status in “linux” package in Ubuntu: Fix Committed Status in “linux” source package in Trusty: Fix Committed Bug description: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328295/+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 1334823] Re: please add designware gpio support for x-gene
dannf@mustang:~$ lsmod | grep gpio gpio_dwapb 4990 0 gpio_generic4247 1 gpio_dwapb ** 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/1334823 Title: please add designware gpio support for x-gene 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: The X-Gene SoC contains a designware GPIO device that needs a driver backported from upstream. These patches are available for trusty at: git://kernel.ubuntu.com/dannf/trusty-xgene.git for-ubuntu-20140628 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334823/+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 1335636] Re: x-gene sata phy tuning varies across platforms
Verified on 2 platforms with different phy tunings. ** 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/1335636 Title: x-gene sata phy tuning varies across platforms 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: The xgene-ahci driver sets sets the sata phy configuration, but this configuration can vary across platforms. Today the values we are using are optimal for the mustang development board, but suboptimal for other platforms. In general the recommendation is to move this into platform specific config in firmware - either by having firmware do the phy config, or by passing settings to the driver via device-tree config. But, that's a long term solution - in the short term, we can special case the Mustang board and use better default settings for other boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335636/+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 1328295] [NEW] [serial] use hw flow control if supported
Public bug reported: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: hs-arm64 ** Attachment added: 0001-serial-uart-add-hw-flow-control-support-configuratio.patch https://bugs.launchpad.net/bugs/1328295/+attachment/4128491/+files/0001-serial-uart-add-hw-flow-control-support-configuratio.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/1328295 Title: [serial] use hw flow control if supported Status in “linux” package in Ubuntu: New Bug description: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328295/+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 1328295] Re: [serial] use hw flow control if supported
Marking confirmed; logs are unlikely to help with this issue. ** 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/1328295 Title: [serial] use hw flow control if supported Status in “linux” package in Ubuntu: Confirmed Bug description: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328295/+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
Re: [Kernel-packages] [Bug 1328295] Re: [serial] use hw flow control if supported
On Thu, Jun 12, 2014 at 11:31 AM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Also, do you have a way to test if I build a Trusty test kernel with this patch applied? Yes, though I've already done my own build/test. -- 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/1328295 Title: [serial] use hw flow control if supported Status in “linux” package in Ubuntu: Triaged Bug description: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328295/+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
Re: [Kernel-packages] [Bug 1328295] Re: [serial] use hw flow control if supported
On Thu, Jun 12, 2014 at 11:29 AM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Dann, Utopic will pick up commit 06aa82e automatically when it is re- based. Are you requesting this commit be included in any of the current stable releases? Just 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/1328295 Title: [serial] use hw flow control if supported Status in “linux” package in Ubuntu: Triaged Bug description: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328295/+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
Re: [Kernel-packages] [Bug 1328295] Re: [serial] use hw flow control if supported
On Fri, Jun 13, 2014 at 3:28 PM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Just to confirm this commit fixes this bug, I built a Trusty test kernel, which can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1328295/ Can you test this kernel to confirm it fixes this bug? My target platform is arm64 - if you can provide arm64 binaries, or the source, I could test it. Though, I have already tested a trusty kernel with this cherry-pick on the target platform. If it does, we can submit an SRU request to the kernel-team mailing list to have the commit included in Trusty. This commit is already in the master-next branch for trusty: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=commit;h=3545bd96109d76abb535f2751cb7162bc519a11a Based on this request: https://lists.ubuntu.com/archives/kernel-team/2014-June/043580.html Does that imply we're good? -- 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/1328295 Title: [serial] use hw flow control if supported Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Trusty: In Progress Bug description: HP Moonshot cartridges support hardware flow control, but right now only software assisted hw flow control is supported. This patch from upstream enables this functionality when exposed by firmware: commit 06aa82e498c144c7784a6f3d3b55458b272d6146 Author: Murali Karicheri m-kariche...@ti.com Date: Thu May 1 15:04:53 2014 -0400 serial: uart: add hw flow control support configuration 8250 uart driver currently supports only software assisted hw flow control. The software assisted hw flow control maintains a hw_stopped flag in the tty structure to stop and start transmission and use modem status interrupt for the event to drive the handshake signals. This is not needed if hw has flow control capabilities. This patch adds a DT attribute for enabling hw flow control for a uart port. Also skip stop and start if this flag is present in flag field of the port structure. Signed-off-by: Murali Karicheri m-kariche...@ti.com CC: Rob Herring robh...@kernel.org CC: Pawel Moll pawel.m...@arm.com CC: Mark Rutland mark.rutl...@arm.com CC: Ian Campbell ijc+devicet...@hellion.org.uk CC: Kumar Gala ga...@codeaurora.org CC: Randy Dunlap rdun...@infradead.org CC: Jiri Slaby jsl...@suse.cz CC: Santosh Shilimkar santosh.shilim...@ti.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328295/+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 1283165] Re: DI fails on arm64 with kernel Oops
This should be resolved now. In 3.13.0-11.31, the kernel was changed to link the IPMI modules statically. On probe, this causes the KCS driver to poke a well known address to look for a BMC - but on arm64, touching this address causes a fault. This change was reverted in subsequent uploads. ** Changed in: linux (Ubuntu) Status: Confirmed = 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/1283165 Title: DI fails on arm64 with kernel Oops Status in “linux” package in Ubuntu: Fix Released Bug description: DI fails on arm64 with kernel Oops: Using arm64 netboot install: http://ports.ubuntu.com/ubuntu-ports/dists/trusty/main/installer- arm64/20101020ubuntu300/images/generic/netboot/ and ARM fast model: FVP_Base_AEMv8A-AEMv8A_0.8_5311/models/Linux64_GCC-4.1 /FVP_Base_AEMv8A-AEMv8A model.conf: pctl.startup=0.0.0.0 bp.secure_memory=0 bp.flashloader0.fname=uefi_fvp-base.bin bp.secureflashloader.fname=bl1.bin bp.smsc_91c111.enabled=1 bp.hostbridge.userNetworking=1 bp.hostbridge.userNetPorts=8122=22 cluster0.NUM_CORES=1 cluster1.NUM_CORES=1 Screen dump: [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-11-generic (buildd@magic) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-16ubuntu1) ) #31-Ubuntu SMP Wed Feb 19 20:03:19 UTC 2014 (Ubuntu 3.13.0-11.31-generic 3.13.3) [0.00] CPU: AArch64 Processor [410fd0f0] revision 0 [0.00] bootconsole [earlycon0] enabled [0.00] On node 0 totalpages: 524288 [0.00] DMA32 zone: 7168 pages used for memmap [0.00] DMA32 zone: 0 pages reserved [0.00] DMA32 zone: 524288 pages, LIFO batch:31 [0.00] psci: probing function IDs from device-tree [0.00] PERCPU: Embedded 12 pages/cpu @ffc07ff87000 s17024 r8192 d23936 u49152 [0.00] pcpu-alloc: s17024 r8192 d23936 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: 517120 [0.00] Kernel command line: console=ttyAMA0 earlyprintk=pl011,0x1c09 debug user_debug=31 loglevel=9 root=/dev/vda2 [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.00] software IO TLB [mem 0xf9e0-0xfde0] (64MB) mapped at [ffc079e0-ffc07ddf] [0.00] Memory: 1980368K/2097152K available (5444K kernel code, 564K rwdata, 2380K rodata, 300K init, 544K bss, 116784K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbc01c0 - 0xffbc0380 ( 28 MB) [0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB) [0.00] memory : 0xffc0 - 0xffc08000 ( 2048 MB) [0.00] .init : 0xffc000826000 - 0xffc000871280 ( 301 kB) [0.00] .text : 0xffc8 - 0xffc000825344 ( 7829 kB) [0.00] .data : 0xffc000872000 - 0xffc0008ff180 ( 565 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 and mmio timer(s) running at 100.00MHz (phys/phys). [0.00] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 2748779069440ns [0.00] Console: colour dummy device 80x25 [0.00] allocated 8388608 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.002856] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=100) [0.002929] pid_max: default: 32768 minimum: 301 [0.003905] Security Framework initialized [0.004070] AppArmor: AppArmor initialized [0.004107] Yama: becoming mindful. [0.004612] Mount-cache hash table entries: 256 [0.017316] Initializing cgroup subsys memory [0.017450] Initializing cgroup subsys devices [0.017496] Initializing cgroup subsys freezer [0.017541] Initializing cgroup subsys blkio [0.017584] Initializing cgroup subsys perf_event [0.017702] Initializing cgroup subsys hugetlb [0.018662] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 9 counters available [0.028681]
[Kernel-packages] [Bug 1302245] [NEW] mmap_min_addr blocks armhf binary support on arm64
Public bug reported: As of linux 3.13.0_22.44, unprivileged armhf binaries will not run on a default arm64 Ubuntu install on hardware that supports ARMv7 instructions: $ LD_LIBRARY_PATH=/home/dannf/armhf/lib:/home/dannf/armhf/lib/arm-linux-gnueabihf /home/dannf/armhf/lib/ld-linux-armhf.so.3 /home/dannf/armhf/bin/true /home/dannf/armhf/bin/true: error while loading shared libraries: /home/dannf/armhf/bin/true: failed to map segment from shared object: Operation not permitted This appears to be because we set CONFIG_DEFAULT_MMAP_MIN_ADDR to 65536. If we lower this to 32768, these binaries work: $ echo 32768 | sudo tee /proc/sys/vm/mmap_min_addr 32768 $ LD_LIBRARY_PATH=/home/dannf/armhf/lib:/home/dannf/armhf/lib/arm-linux-gnueabihf /home/dannf/armhf/lib/ld-linux-armhf.so.3 /home/dannf/armhf/bin/true $ echo $? 0 Of course, lowering this default has some security implications - and it isn't clear how generally useful it is to have armhf compatibility support on arm64 systems. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: arm64 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/1302245 Title: mmap_min_addr blocks armhf binary support on arm64 Status in “linux” package in Ubuntu: Incomplete Bug description: As of linux 3.13.0_22.44, unprivileged armhf binaries will not run on a default arm64 Ubuntu install on hardware that supports ARMv7 instructions: $ LD_LIBRARY_PATH=/home/dannf/armhf/lib:/home/dannf/armhf/lib/arm-linux-gnueabihf /home/dannf/armhf/lib/ld-linux-armhf.so.3 /home/dannf/armhf/bin/true /home/dannf/armhf/bin/true: error while loading shared libraries: /home/dannf/armhf/bin/true: failed to map segment from shared object: Operation not permitted This appears to be because we set CONFIG_DEFAULT_MMAP_MIN_ADDR to 65536. If we lower this to 32768, these binaries work: $ echo 32768 | sudo tee /proc/sys/vm/mmap_min_addr 32768 $ LD_LIBRARY_PATH=/home/dannf/armhf/lib:/home/dannf/armhf/lib/arm-linux-gnueabihf /home/dannf/armhf/lib/ld-linux-armhf.so.3 /home/dannf/armhf/bin/true $ echo $? 0 Of course, lowering this default has some security implications - and it isn't clear how generally useful it is to have armhf compatibility support on arm64 systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302245/+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 1063895] Re: arm64 support to generate linux-source for crosstool bulds
We've had an arm64 kernel throughout the 14.04 cycle, so moving to fix- released. ** 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/1063895 Title: arm64 support to generate linux-source for crosstool bulds Status in “linux” package in Ubuntu: Fix Released Bug description: [Not sure If I've filed this aginst the right package. It should be linux-3.5.0, but that doesn't exist according to launchpad. ] Attached is a first-cut patch adding arm64 support to the linux-3.5.0 package so that it builds linux-source packages which can be used to build cross tools against. The arm64 support is just the core stuff so isn't much use for making binaries. It's also an unholy backport of 3.6/3.7 vintage stuff to 3.5 so it probably bust in important ways. However that's not relevant for the primiary purpose here of building cross-tools, which just needs a correct set of headers in linux-libc- dev, and arch/package machinery in linux-source. I'm not expecting this to be uploaded but wanted to put it somewhere public for anyone else to build with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063895/+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 1282329] [NEW] juju requires cpu-checker which is unavailable on arm64/ppc64el
Public bug reported: I'm testing out deploying charms to an arm64 target using the manual provider. After hacking juju to recognize the arch, and hacking in the necessary tools, I reach the following failure: dannf@laptop:~$ juju add-machine ssh:arm64.dannf -v verbose is deprecated with the current meaning, use show-log 2014-02-19 23:55:44 INFO juju api.go:231 connecting to API addresses: [bootstrap.dannf:17070] 2014-02-19 23:55:44 INFO juju apiclient.go:118 state/api: dialing wss://bootstrap.dannf:17070/ 2014-02-19 23:55:44 INFO juju apiclient.go:128 state/api: connection established 2014-02-19 23:55:44 INFO juju.environs.manual init.go:156 initialising arm64.dannf, user 2014-02-19 23:55:44 INFO juju.environs.manual init.go:167 ubuntu user is already initialised 2014-02-19 23:55:44 INFO juju.environs.manual provisioner.go:260 addresses for arm64.dannf: [192.168.1.117 public:arm64.dannf] 2014-02-19 23:55:44 INFO juju.environs.manual init.go:29 Checking if arm64.dannf is already provisioned 2014-02-19 23:55:44 INFO juju.environs.manual init.go:46 arm64.dannf is not provisioned 2014-02-19 23:55:44 INFO juju.environs.manual init.go:55 Detecting series and characteristics on arm64.dannf 2014-02-19 23:55:45 INFO juju.environs.manual init.go:118 series: trusty, characteristics: arch=arm64 cpu-cores=1 mem=16062M Logging to /var/log/cloud-init-output.log on remote host Running apt-get update Installing package: git Installing package: cpu-checker 2014-02-19 23:56:23 ERROR juju.environs.manual provisioner.go:78 provisioning failed, removing machine 2: exit status 1 2014-02-19 23:56:23 ERROR juju.cmd supercommand.go:294 exit status 1 The issue here is that cpu-checker is not available for arm64 (or ppc64el) in the archive. ** Affects: juju-core Importance: Undecided Status: New ** Affects: cpu-checker (Ubuntu) Importance: Undecided Status: New ** Tags: hs-arm64 ** Also affects: cpu-checker Importance: Undecided Status: New ** Project changed: cpu-checker = cpu-checker (Ubuntu) ** Branch linked: lp:~dannf/ubuntu/trusty/cpu-checker/arm64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to cpu-checker in Ubuntu. https://bugs.launchpad.net/bugs/1282329 Title: juju requires cpu-checker which is unavailable on arm64/ppc64el Status in juju-core: New Status in “cpu-checker” package in Ubuntu: New Bug description: I'm testing out deploying charms to an arm64 target using the manual provider. After hacking juju to recognize the arch, and hacking in the necessary tools, I reach the following failure: dannf@laptop:~$ juju add-machine ssh:arm64.dannf -v verbose is deprecated with the current meaning, use show-log 2014-02-19 23:55:44 INFO juju api.go:231 connecting to API addresses: [bootstrap.dannf:17070] 2014-02-19 23:55:44 INFO juju apiclient.go:118 state/api: dialing wss://bootstrap.dannf:17070/ 2014-02-19 23:55:44 INFO juju apiclient.go:128 state/api: connection established 2014-02-19 23:55:44 INFO juju.environs.manual init.go:156 initialising arm64.dannf, user 2014-02-19 23:55:44 INFO juju.environs.manual init.go:167 ubuntu user is already initialised 2014-02-19 23:55:44 INFO juju.environs.manual provisioner.go:260 addresses for arm64.dannf: [192.168.1.117 public:arm64.dannf] 2014-02-19 23:55:44 INFO juju.environs.manual init.go:29 Checking if arm64.dannf is already provisioned 2014-02-19 23:55:44 INFO juju.environs.manual init.go:46 arm64.dannf is not provisioned 2014-02-19 23:55:44 INFO juju.environs.manual init.go:55 Detecting series and characteristics on arm64.dannf 2014-02-19 23:55:45 INFO juju.environs.manual init.go:118 series: trusty, characteristics: arch=arm64 cpu-cores=1 mem=16062M Logging to /var/log/cloud-init-output.log on remote host Running apt-get update Installing package: git Installing package: cpu-checker 2014-02-19 23:56:23 ERROR juju.environs.manual provisioner.go:78 provisioning failed, removing machine 2: exit status 1 2014-02-19 23:56:23 ERROR juju.cmd supercommand.go:294 exit status 1 The issue here is that cpu-checker is not available for arm64 (or ppc64el) in the archive. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1282329/+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 1282329] Re: juju requires cpu-checker which is unavailable on arm64/ppc64el
One way to go about resolving this is to just make cpu-checker available on arm64/ppc64el. I've proposed such a change for arm64; I don't have access to ppc64el to test out an equivalent. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to cpu-checker in Ubuntu. https://bugs.launchpad.net/bugs/1282329 Title: juju requires cpu-checker which is unavailable on arm64/ppc64el Status in juju-core: New Status in “cpu-checker” package in Ubuntu: New Bug description: I'm testing out deploying charms to an arm64 target using the manual provider. After hacking juju to recognize the arch, and hacking in the necessary tools, I reach the following failure: dannf@laptop:~$ juju add-machine ssh:arm64.dannf -v verbose is deprecated with the current meaning, use show-log 2014-02-19 23:55:44 INFO juju api.go:231 connecting to API addresses: [bootstrap.dannf:17070] 2014-02-19 23:55:44 INFO juju apiclient.go:118 state/api: dialing wss://bootstrap.dannf:17070/ 2014-02-19 23:55:44 INFO juju apiclient.go:128 state/api: connection established 2014-02-19 23:55:44 INFO juju.environs.manual init.go:156 initialising arm64.dannf, user 2014-02-19 23:55:44 INFO juju.environs.manual init.go:167 ubuntu user is already initialised 2014-02-19 23:55:44 INFO juju.environs.manual provisioner.go:260 addresses for arm64.dannf: [192.168.1.117 public:arm64.dannf] 2014-02-19 23:55:44 INFO juju.environs.manual init.go:29 Checking if arm64.dannf is already provisioned 2014-02-19 23:55:44 INFO juju.environs.manual init.go:46 arm64.dannf is not provisioned 2014-02-19 23:55:44 INFO juju.environs.manual init.go:55 Detecting series and characteristics on arm64.dannf 2014-02-19 23:55:45 INFO juju.environs.manual init.go:118 series: trusty, characteristics: arch=arm64 cpu-cores=1 mem=16062M Logging to /var/log/cloud-init-output.log on remote host Running apt-get update Installing package: git Installing package: cpu-checker 2014-02-19 23:56:23 ERROR juju.environs.manual provisioner.go:78 provisioning failed, removing machine 2: exit status 1 2014-02-19 23:56:23 ERROR juju.cmd supercommand.go:294 exit status 1 The issue here is that cpu-checker is not available for arm64 (or ppc64el) in the archive. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1282329/+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 1350087] [NEW] ahci-xgene stability improvements
Public bug reported: Several issues have been discovered while testing the ahci-xgene driver. These include failures to discover certain disk types (SSDs), failure to discover disks on certain platforms due to phy tunings/timings, and disks disappearing during reboot loop testing. ** 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/1350087 Title: ahci-xgene stability improvements Status in “linux” package in Ubuntu: Incomplete Bug description: Several issues have been discovered while testing the ahci-xgene driver. These include failures to discover certain disk types (SSDs), failure to discover disks on certain platforms due to phy tunings/timings, and disks disappearing during reboot loop testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350087/+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 1350087] Re: ahci-xgene stability improvements
** 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/1350087 Title: ahci-xgene stability improvements Status in “linux” package in Ubuntu: Confirmed Bug description: Several issues have been discovered while testing the ahci-xgene driver. These include failures to discover certain disk types (SSDs), failure to discover disks on certain platforms due to phy tunings/timings, and disks disappearing during reboot loop testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350087/+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 1350087] Re: ahci-xgene stability improvements
This bug applies to the trusty, utopic and upstream kernels. Some of the patches are queued for 3.17, some others are still under discussion. I've sent out a pull request for this branch for trusty which resolves it: http://kernel.ubuntu.com/git?p=dannf/trusty-xgene.git;a=shortlog;h=refs/heads/for-ubuntu-20140729 As patches are accepted upstream, I'll do the same for utopic (providing backports to utopic's 3.16). ** Tags added: kernel-bug-exists-upstream -- 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/1350087 Title: ahci-xgene stability improvements Status in “linux” package in Ubuntu: Triaged Bug description: Several issues have been discovered while testing the ahci-xgene driver. These include failures to discover certain disk types (SSDs), failure to discover disks on certain platforms due to phy tunings/timings, and disks disappearing during reboot loop testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350087/+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 1357527] [NEW] [Trusty] support for X-Gene PMU in perf
Public bug reported: Trusty doesn't currently support the X-Gene PMU, which prevents perf from making use of hardware counters. ** 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/1357527 Title: [Trusty] support for X-Gene PMU in perf Status in “linux” package in Ubuntu: New Bug description: Trusty doesn't currently support the X-Gene PMU, which prevents perf from making use of hardware counters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357527/+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 1358498] Re: ahci-xgene falsely advertises NCQ support
This fix should flow naturally into utopic via stable. The driver isn't in upstream 3.13 stable, and the flag code has changed since, so trusty requires some backporting. -- 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/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: Incomplete Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1358498] [NEW] ahci-xgene falsely advertises NCQ support
Public bug reported: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. ** 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/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: Incomplete Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1358498] Re: ahci-xgene falsely advertises NCQ support
** Description changed: - ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA - failures that surface as a filesystem being remounted read-only due to - errors when using a disk that supports NCQ. + [IMPACT] + ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. + [TEST CASE] + Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. + [Regression Potential] + Minimal; we're turning off a feature that is known broken. -- 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/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: Incomplete Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1358498] Re: ahci-xgene falsely advertises NCQ support
** 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/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: Confirmed Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1358949] [NEW] arm64 iperf performance suboptimal
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.
Iperf performance increase:
-l (size) 1 core result
Optimized 64B 44-51Mb/s
1500B 4.9Gb/s
3B 16.2Gb/s
Original64B 34-50.7Mb/s
1500B 4.7Gb/s
3B 14.5Gb/s
[Test Case]
Generate traffic from one node to another using iperf (see above for config).
[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.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Patch added: optimized copy_to_user and copy_from_user for arm64
https://bugs.launchpad.net/bugs/1358949/+attachment/4181987/+files/0001-UBUNTU-SAUCE-no-up-arm64-optimized-copy_to_user-and-.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/1358949
Title:
arm64 iperf performance suboptimal
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.
Iperf performance increase:
-l (size) 1 core result
Optimized 64B 44-51Mb/s
1500B 4.9Gb/s
3B 16.2Gb/s
Original64B 34-50.7Mb/s
1500B 4.7Gb/s
3B 14.5Gb/s
[Test Case]
Generate traffic from one node to another using iperf (see above for config).
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358949/+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 1350087] Re: ahci-xgene stability improvements
** 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/1350087 Title: ahci-xgene stability improvements Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: Several issues have been discovered while testing the ahci-xgene driver. These include failures to discover certain disk types (SSDs), failure to discover disks on certain platforms due to phy tunings/timings, and disks disappearing during reboot loop testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350087/+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
Re: [Kernel-packages] [Bug 1358949] Re: arm64 iperf performance suboptimal
On Tue, Aug 19, 2014 at 4:56 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
Can you also send this patch to the Ubuntu kernel-team mailing list for
review?
https://lists.ubuntu.com/archives/kernel-team/2014-August/047895.html
--
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/1358949
Title:
arm64 iperf performance suboptimal
Status in “linux” package in Ubuntu:
Triaged
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.
Iperf performance increase:
-l (size) 1 core result
Optimized 64B 44-51Mb/s
1500B 4.9Gb/s
3B 16.2Gb/s
Original64B 34-50.7Mb/s
1500B 4.7Gb/s
3B 14.5Gb/s
[Test Case]
Generate traffic from one node to another using iperf (see above for config).
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358949/+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 1359501] Re: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware
** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- 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/1359501 Title: ahci_xgene: Skip the PHY and clock initialization if already configured by the firmware Status in “linux” package in Ubuntu: Invalid Bug description: This patch implements the feature to skip the PHY and clock initialization if it is already configured by the firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359501/+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 1344323] Re: Trusty kernel network performance regression
I'm seeing the expected performance with the SRU kernel (technically a different build with a couple of SATA patches required to boot) ** 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/1344323 Title: Trusty kernel network performance regression Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Bug description: SRU Justification: Impact: Reduced TCP/IP receive performance for network devices that do not split packet headers into skb linear area (e.g., mlx4). The trusty kernel has incorporated commit eff44f9cc9a02aad53d568d3ae5020b6792ae4f6 Author: Jerry Chu hk...@google.com Date: Wed Dec 11 20:53:45 2013 -0800 net-gro: Prepare GRO stack for the upcoming tunneling support which modifies the GRO frag0 optimization, but unfortunately for some cases results in calls to __skb_pull_tail for every packet being received via the GRO path. This causes a reduction in TCP receive performance (or, more accurately, an increase in CPU load for TCP receive processing, which will cause throughput reduction for CPU limited workloads). Fix: This has already been fixed in mainline in commit a50e233c50dbc881abaa0e4070789064e8d12d70 Author: Eric Dumazet eduma...@google.com Date: Sat Mar 29 21:28:21 2014 -0700 net-gro: restore frag0 optimization The fix has been backported to and verified on the trusty kernel using mlx4 devices and iperf; an increase from 7.5 to 8.5 Gb/sec was observed when adding the patch, and the relevant portion of perf captures show changes in the call paths from: 7.17%iperf [kernel.kallsyms] [k] __pskb_pull_tail | --- __pskb_pull_tail | |--48.03%-- tcp_gro_receive | tcp4_gro_receive | inet_gro_receive | dev_gro_receive | napi_gro_frags | mlx4_en_process_rx_cq | mlx4_en_poll_rx_cq | net_rx_action | __do_softirq [...] |--28.53%-- napi_gro_frags | mlx4_en_process_rx_cq | mlx4_en_poll_rx_cq | net_rx_action | __do_softirq [...] |--13.11%-- inet_gro_receive | dev_gro_receive | napi_gro_frags | mlx4_en_process_rx_cq | mlx4_en_poll_rx_cq | net_rx_action | __do_softirq to: 4.87% iperf [kernel.kallsyms] [k] skb_gro_receive | --- skb_gro_receive | |--98.13%-- tcp_gro_receive | tcp4_gro_receive | inet_gro_receive | dev_gro_receive | napi_gro_frags | mlx4_en_process_rx_cq | mlx4_en_poll_rx_cq | net_rx_action | __do_softirq Testcase: The fix was tested using mlx4 10Gb/sec network devices between two arm64 systems using iperf -s on one end and iperf -c on the other. The unmodified kernel reported approximately 7.5 Gb/sec throughput, the fixed kernel approximately 8.5 Gb/sec. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1344323/+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 1309221] Re: transparent hugepages flaky on arm64
** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = 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/1309221 Title: transparent hugepages flaky on arm64 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Fix Released Status in “linux” source package in Utopic: Confirmed Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to never until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+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 1365593] [NEW] No driver provided for X-Gene's hardware RNG
Public bug reported: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. ** 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/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: New Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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
Re: [Kernel-packages] [Bug 1365593] Re: No driver provided for X-Gene's hardware RNG
On Thu, Sep 4, 2014 at 11:13 AM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Is this an issue with all Ubuntu releases including Utopic? It impacts trusty and 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/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: Confirmed Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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 1365593] Re: No driver provided for X-Gene's hardware RNG
Pull requests: https://lists.ubuntu.com/archives/kernel-team/2014-September/048173.html https://lists.ubuntu.com/archives/kernel-team/2014-September/048174.html -- 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/1365593 Title: No driver provided for X-Gene's hardware RNG Status in “linux” package in Ubuntu: Confirmed Bug description: [Impact] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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 1366867] Re: PC is at ahci_enable_ahci+0x14/0x6c [libahci]
Hi, This is a known compatibility issue with u-boot versions earlier than 1.13.28. Please update u-boot and confirm. -- 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/1366867 Title: PC is at ahci_enable_ahci+0x14/0x6c [libahci] Status in “linux” package in Ubuntu: Incomplete Bug description: When attempting to use the 1.12.10 firmware with linux kernel versions 3.13.0-36.63 and above the system will not boot. SATA1 link 0 timeout SATA1 link 1 timeout AHCI1 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq pm only pmp fbss pio slum part ccc apst boh SATA2 spinup took 0 ms. SATA2 link 1 timeout AHCI2 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq pm only pmp fbss pio slum part ccc apst boh scanning bus for devices... Device 0: (4:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Found 1 device(s). 300 bytes read in 65 ms (3.9 KiB/s) ## Executing script at 400400 9361408 bytes read in 322 ms (27.7 MiB/s) 17697693 bytes read in 496 ms (34 MiB/s) 12756 bytes read in 53 ms (234.4 KiB/s) ## Booting kernel from Legacy Image at 400200 ... Image Name: kernel 3.13.0-36-generic Image Type: ARM Linux Kernel Image (uncompressed) Data Size:9361344 Bytes = 8.9 MiB Load Address: 0008 Entry Point: 0008 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 400400 ... Image Name: ramdisk 3.13.0-36-generic Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:17697629 Bytes = 16.9 MiB Load Address: Entry Point: Verifying Checksum ... OK ## Flattened Device Tree blob at 400300 Booting using the fdt blob at 0x00400300 Loading Kernel Image ... OK OK Loading Ramdisk to 43def1f000, end 43db5d ... OK Loading Device Tree to 004000ff9000, end 004000fff1d3 ... OK 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-36-generic (buildd@magic) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #63-Ubuntu SMP Wed Sep 3 21:33:11 UTC 2014 (Ubuntu 3.13.0-36.63-generic 3.13.11.6) [0.00] CPU: AArch64 Processor [500f] revision 0 [0.00] PERCPU: Embedded 12 pages/cpu @ffc3fff79000 s17024 r8192 d23936 u49152 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4136960 [0.00] Kernel command line: console=ttyS0,115200n8 ro [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) [0.00] software IO TLB [mem 0x43ec60-0x43f060] (64MB) mapped at [ffc3ec60-ffc3f05f] [0.00] Memory: 16429604K/16777216K available (5710K kernel code, 581K rwdata, 2536K rodata, 304K init, 538K bss, 347612K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbce000 - 0xffbcee00 ( 224 MB) [0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB) [0.00] memory : 0xffc0 - 0xffc4 ( 16384 MB) [0.00] .init : 0xffc00088f000 - 0xffc0008db280 ( 305 kB) [0.00] .text : 0xffc8 - 0xffc00088e984 ( 8251 kB) [0.00] .data : 0xffc0008dc000 - 0xffc00096d7c0 ( 582 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] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns [0.00] Console: colour dummy device 80x25 [0.00] allocated 67108864 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.003078] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50) [0.003083] pid_max: default: 32768 minimum: 301 [0.003125] Security Framework initialized [0.003160] AppArmor: AppArmor initialized [0.003163] Yama: becoming mindful. [0.003196] Mount-cache hash table entries: 32768 (order: 6,
[Kernel-packages] [Bug 1358498] Re: ahci-xgene falsely advertises NCQ support
ubuntu@am3:~$ dmesg | grep -i ncq [1.309746] xgene-ahci 1a80.sata: controller can't do NCQ, turning off CAP_NCQ [1.725691] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ubuntu@am3:~$ ** 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/1358498 Title: ahci-xgene falsely advertises NCQ support Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: In Progress Bug description: [IMPACT] ahci-xgene doesn't support NCQ but it sets this flag. This causes SATA failures that surface as a filesystem being remounted read-only due to errors when using a disk that supports NCQ. [TEST CASE] Do a network boot install on an X-Gene system with an SSD drive that supports NCQ. The install will fail and dmesg will show the filesystem being remounted read-only. [Regression Potential] Minimal; we're turning off a feature that is known broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358498/+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 1357527] Re: [Trusty] support for X-Gene PMU in perf
perf is working for me ** 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/1357527 Title: [Trusty] support for X-Gene PMU in perf 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: Trusty doesn't currently support the X-Gene PMU, which prevents perf from making use of hardware counters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357527/+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 1358949] Re: arm64 iperf performance suboptimal
I'm seeing reasonable performance with this.
** 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/1358949
Title:
arm64 iperf performance suboptimal
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]
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.
Iperf performance increase:
-l (size) 1 core result
Optimized 64B 44-51Mb/s
1500B 4.9Gb/s
3B 16.2Gb/s
Original64B 34-50.7Mb/s
1500B 4.7Gb/s
3B 14.5Gb/s
[Test Case]
Generate traffic from one node to another using iperf (see above for config).
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358949/+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 1366867] Re: PC is at ahci_enable_ahci+0x14/0x6c [libahci]
I updated the firmware on Michael's system and verified the firmware update resolves the problem. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- 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/1366867 Title: PC is at ahci_enable_ahci+0x14/0x6c [libahci] Status in “linux” package in Ubuntu: Invalid Bug description: When attempting to use the 1.12.10 firmware with linux kernel versions 3.13.0-36.63 and above the system will not boot. SATA1 link 0 timeout SATA1 link 1 timeout AHCI1 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq pm only pmp fbss pio slum part ccc apst boh SATA2 spinup took 0 ms. SATA2 link 1 timeout AHCI2 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq pm only pmp fbss pio slum part ccc apst boh scanning bus for devices... Device 0: (4:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Found 1 device(s). 300 bytes read in 65 ms (3.9 KiB/s) ## Executing script at 400400 9361408 bytes read in 322 ms (27.7 MiB/s) 17697693 bytes read in 496 ms (34 MiB/s) 12756 bytes read in 53 ms (234.4 KiB/s) ## Booting kernel from Legacy Image at 400200 ... Image Name: kernel 3.13.0-36-generic Image Type: ARM Linux Kernel Image (uncompressed) Data Size:9361344 Bytes = 8.9 MiB Load Address: 0008 Entry Point: 0008 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 400400 ... Image Name: ramdisk 3.13.0-36-generic Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:17697629 Bytes = 16.9 MiB Load Address: Entry Point: Verifying Checksum ... OK ## Flattened Device Tree blob at 400300 Booting using the fdt blob at 0x00400300 Loading Kernel Image ... OK OK Loading Ramdisk to 43def1f000, end 43db5d ... OK Loading Device Tree to 004000ff9000, end 004000fff1d3 ... OK 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-36-generic (buildd@magic) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #63-Ubuntu SMP Wed Sep 3 21:33:11 UTC 2014 (Ubuntu 3.13.0-36.63-generic 3.13.11.6) [0.00] CPU: AArch64 Processor [500f] revision 0 [0.00] PERCPU: Embedded 12 pages/cpu @ffc3fff79000 s17024 r8192 d23936 u49152 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4136960 [0.00] Kernel command line: console=ttyS0,115200n8 ro [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) [0.00] software IO TLB [mem 0x43ec60-0x43f060] (64MB) mapped at [ffc3ec60-ffc3f05f] [0.00] Memory: 16429604K/16777216K available (5710K kernel code, 581K rwdata, 2536K rodata, 304K init, 538K bss, 347612K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbce000 - 0xffbcee00 ( 224 MB) [0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB) [0.00] memory : 0xffc0 - 0xffc4 ( 16384 MB) [0.00] .init : 0xffc00088f000 - 0xffc0008db280 ( 305 kB) [0.00] .text : 0xffc8 - 0xffc00088e984 ( 8251 kB) [0.00] .data : 0xffc0008dc000 - 0xffc00096d7c0 ( 582 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] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns [0.00] Console: colour dummy device 80x25 [0.00] allocated 67108864 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.003078] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50) [0.003083] pid_max: default: 32768 minimum: 301 [0.003125] Security Framework initialized [0.003160] AppArmor: AppArmor initialized [0.003163] Yama: becoming mindful. [0.003196]
[Kernel-packages] [Bug 1365593] Re: No driver provided for X-Gene's hardware RNG
Verified: dannf@mustang:~$ cat /proc/version Linux version 3.13.0-37-generic (buildd@twombly) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:32:32 UTC 2014 dannf@mustang:~$ while :; do cat /proc/sys/kernel/random/entropy_avail; sleep 1; done [1] 2008 dannf@mustang:~$ 285 sudo a286 pt-get instal287 l rng-291 tools 170 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: rng-tools 0 upgraded, 1 newly installed, 0 to remove and 146 not upgraded. 180 Need to get 0 B/19.9 kB of archives. After this operation, 142 kB of additional disk space will be used. 193 205 Selecting previously unselected package rng-tools. 210ading database ... 65% 214ading database ... 75%70% 217ading database ... 85%80% 221ading database ... 95%90% (Reading database ... 119555 files and directories currently installed.) Preparing to unpack .../rng-tools_5-0ubuntu1_arm64.deb ... Unpacking rng-tools (5-0ubuntu1) ... 232 Processing triggers for ureadahead (0.100.0-16) ... ureadahead will be reprofiled on next reboot Processing triggers for man-db (2.6.7.1-1) ... 246 258 267 283 294 Setting up rng-tools (5-0ubuntu1) ... Starting Hardware RNG entropy gatherer daemon: rngd. 3075 dannf@mustang:~$ 3077 3078 ** 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/1365593 Title: No driver provided for X-Gene's hardware RNG 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] User has a system with a built-in random number generator that the OS cannot use. [Test Case] Make sure rng-tools is uninstalled. Reboot with this driver, verify that it is automatically loaded. Leave system idle for this test. In one terminal, run 'watch cat /proc/sys/kernel/random/entropy_avail', and note that the minor fluctuation in available entropy over time. Install rng-tools, and notice that entropy shoots up and grows at a faster rate than previously. [Regression Potential] If this driver is buggy it could cause e.g. an oops or a panic that would not otherwise have occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1365593/+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
** Changed in: crash (Ubuntu Utopic) Status: Triaged = Fix Released -- 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: Triaged Status in “crash” source package in Utopic: Fix Released Bug description: HOW TO REPRODUCE On an system that uses the ARM64 architecture, run the crash utility. ** EXPECTED BEHAVIOUR ** - The crash utility to work. ** REAL BEHAVIOUR ** - The crash utility doesn't work. PROPOSED FIX - To clean merge into Ubuntu the https://github.com/crash- utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 commit, which updates the ARM64 implementation to support Linux 3.13 and later. - Since the change only affects the ARM64 architecture, there is no potential regression. RELEVANT DETAILS - The package's affected versions are the 7.0.3 based. - Dave Anderson at http://people.redhat.com/anderson/crash.changelog.html said that some commands, most notably bt, don't work yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1354349/+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
** Description changed: - - HOW TO REPRODUCE - + [Impact] + Crash is useless on trusty/arm64 - On an system that uses the ARM64 architecture, run the crash utility. + [Test Case] + BAD (today): + dannf@mustang:~$ sudo crash /usr/lib/debug/boot/vmlinux-3.13.0-37-generic - ** - EXPECTED BEHAVIOUR - ** + 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... - - The crash utility to work. + crash: read error: kernel virtual address: ffc000612ce0 type: cpu_possible_mask + dannf@mustang:~$ - ** - REAL BEHAVIOUR - ** - - The crash utility doesn't work. + GOOD: + dannf@mustang:~$ sudo crash /usr/lib/debug/boot/vmlinux-3.13.0-37-generic - - PROPOSED FIX - + 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... - - To clean merge into Ubuntu the https://github.com/crash- - utility/crash/commit/0f6d989aa091a97e979ea01fb15e05cc22673de7 commit, - which updates the ARM64 implementation to support Linux 3.13 and later. + 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) - - Since the change only affects the ARM64 architecture, there is no - potential regression. + 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, 0xffc0001a6c48 sys_read+136 + 0xffc0001a6bf0 sys_read+48: ldr x4, [x0,#72] + 0xffc0001a6bf4
[Kernel-packages] [Bug 1354349] Re: The crash utility doesn't run in ARM64 based devices
** Changed in: crash (Ubuntu Trusty) Status: Triaged = In Progress ** Changed in: crash (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) -- 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: In Progress 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, 0xffc0001a6c48 sys_read+136 0xffc0001a6bf0 sys_read+48: ldr x4, [x0,#72] 0xffc0001a6bf4 sys_read+52: mov x1, x20 0xffc0001a6bf8 sys_read+56: add x3, x29, #0x48 0xffc0001a6bfc
[Kernel-packages] [Bug 1378856] [NEW] [highbank] Oops on boot loading bridge module
Public bug reported: [ 16.845971] Unable to handle kernel paging request at virtual address bf2c6a88 [ 16.853224] pgd = e76f15c0 [ 16.856108] [bf2c6a88] *pgd=2777a003, *pmd=2babb003, *pte=802753879f [ 16.862870] Internal error: Oops: a0f [#1] SMP ARM [ 16.867656] Modules linked in: bridge(+) stp llc iptable_filter ip_tables x_tables ib_iser[ 16.867695] CPU: 0 PID: 1126 Comm: modprobe Not tainted 3.16.0-21-generic-lpae #28-Ubuntu [ 16.867698] task: ec891a00 ti: e76a6000 task.ti: e76a6000 [ 16.867705] PC is at patch_text+0x4/0x10 [ 16.867713] LR is at __jump_label_update+0x64/0x6c [ 16.867716] pc : [c0a20494]lr : [c0434ffc]psr: 80070013 [ 16.867716] sp : e76a7d78 ip : 00019d80 fp : bf2d0888 [ 16.867718] r10: r9 : bf2d8000 r8 : [ 16.867721] r7 : 0001 r6 : c0f50458 r5 : bf2d0794 r4 : bf2d06f8 [ 16.867723] r3 : bf2c6a88 r2 : ea00 r1 : ea07 r0 : bf2c6a88 [ 16.867727] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 16.867730] Control: 30c5387d Table: 276f15c0 DAC: fffd [ 16.867732] Process modprobe (pid: 1126, stack limit = 0xe76a6250) [ 16.867734] Stack: (0xe76a7d78 to 0xe76a8000) [ 16.867737] 7d60: e7608040 c0f50458 [ 16.867741] 7d80: 0001 c0435054 c0f50458 0001 0007 c0e04920 [ 16.867744] 7da0: bf2d0600 c043517c bf2d0600 bf2d0620 0007 c095c62c c095c70c [ 16.867747] 7dc0: bf2d0a24 c0dff554 c0e04920 c0e04920 e7608b80 bf2d81a0 bf2d0a24 c092661c [ 16.867751] 7de0: c0dff554 bf2d8050 e76a6038 c0309740 0001 c04836e4 [ 16.867754] 7e00: e9ce6c40 e76b8080 8040003f 0001 c043d60c e9ce6c20 [ 16.867757] 7e20: 8040003f 80150014 c043f530 0001 [ 16.867760] 7e40: 0cab 8040003f e76b8080 f0c11000 0001 bd94282a e76a7f58 [ 16.867763] 7e60: bf2d0894 e76a6000 c0dff554 e76a7f58 bf2d0888 c03d55c4 [ 16.867767] 7e80: 8000 7fff c03d2374 ebad4188 b860d1c0 bf2d0894 040c bf2d1000 [ 16.867770] 7ea0: bf2d0894 b6fef398 c0dff554 e76a7f5c c049ef68 [ 16.867773] 7ec0: bf2cd024 0001 bf2cd02c 0002 [ 16.867776] 7ee0: 6e72656b 6c65 [ 16.867779] 7f00: [ 16.867783] 7f20: bd94282a 0120 b6fef398 017b c0320ec4 [ 16.867786] 7f40: e76a6000 b860d1c0 c03d5b90 00181088 f0c11000 0002391c [ 16.867789] 7f60: f0c33fe4 f0c27059 f0c2b378 00014000 00017190 bf2d0798 000a 0001 [ 16.867793] 7f80: 0039 003a 002e 0032 001a b6ff0608 b6ff0e18 [ 16.867796] 7fa0: b6ff0990 c0320d20 b6ff0608 b6ff0e18 b6fef398 b6ff0968 [ 16.867799] 7fc0: b6ff0608 b6ff0e18 b6ff0990 017b b8615288 b860d1c0 [ 16.867803] 7fe0: bef98a38 bef98a28 b6fe6177 b6f5b2b2 40010030 705f646e 696c6275 [ 16.867812] [c0a20494] (patch_text) from [c0434ffc] (__jump_label_update+0x64/0x6c) [ 16.867819] [c0434ffc] (__jump_label_update) from [c0435054] (jump_label_update+0x50/0x9c) [ 16.867826] [c0435054] (jump_label_update) from [c043517c] (static_key_slow_inc+0xdc/0xe0) [ 16.867835] [c043517c] (static_key_slow_inc) from [c095c62c] (nf_register_hook+0xc0/0xcc) [ 16.867842] [c095c62c] (nf_register_hook) from [c095c70c] (nf_register_hooks+0x38/0x78) [ 16.867861] [c095c70c] (nf_register_hooks) from [bf2d81a0] (br_netfilter_init+0x38/0xe98 [bridge]) [ 16.867895] [bf2d81a0] (br_netfilter_init [bridge]) from [bf2d8050] (br_init+0x50/0xd0 [bridge]) [ 16.867911] [bf2d8050] (br_init [bridge]) from [c0309740] (do_one_initcall+0xdc/0x20c) ** 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/1378856 Title: [highbank] Oops on boot loading bridge module Status in “linux” package in Ubuntu: Incomplete Bug description: [ 16.845971] Unable to handle kernel paging request at virtual address bf2c6a88 [ 16.853224] pgd = e76f15c0 [ 16.856108] [bf2c6a88] *pgd=2777a003, *pmd=2babb003, *pte=802753879f [ 16.862870] Internal error: Oops: a0f [#1] SMP ARM [ 16.867656] Modules linked in: bridge(+) stp llc iptable_filter ip_tables x_tables ib_iser[ 16.867695] CPU: 0 PID: 1126 Comm: modprobe Not tainted 3.16.0-21-generic-lpae #28-Ubuntu [ 16.867698] task: ec891a00 ti: e76a6000 task.ti: e76a6000 [ 16.867705] PC is at patch_text+0x4/0x10 [ 16.867713] LR is at __jump_label_update+0x64/0x6c [ 16.867716] pc : [c0a20494]lr : [c0434ffc]psr: 80070013 [
[Kernel-packages] [Bug 1378856] Re: [highbank] Oops on boot loading bridge module
** Attachment added: Full boot log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378856/+attachment/4228535/+files/console.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/1378856 Title: [highbank] Oops on boot loading bridge module Status in “linux” package in Ubuntu: Incomplete Bug description: [ 16.845971] Unable to handle kernel paging request at virtual address bf2c6a88 [ 16.853224] pgd = e76f15c0 [ 16.856108] [bf2c6a88] *pgd=2777a003, *pmd=2babb003, *pte=802753879f [ 16.862870] Internal error: Oops: a0f [#1] SMP ARM [ 16.867656] Modules linked in: bridge(+) stp llc iptable_filter ip_tables x_tables ib_iser[ 16.867695] CPU: 0 PID: 1126 Comm: modprobe Not tainted 3.16.0-21-generic-lpae #28-Ubuntu [ 16.867698] task: ec891a00 ti: e76a6000 task.ti: e76a6000 [ 16.867705] PC is at patch_text+0x4/0x10 [ 16.867713] LR is at __jump_label_update+0x64/0x6c [ 16.867716] pc : [c0a20494]lr : [c0434ffc]psr: 80070013 [ 16.867716] sp : e76a7d78 ip : 00019d80 fp : bf2d0888 [ 16.867718] r10: r9 : bf2d8000 r8 : [ 16.867721] r7 : 0001 r6 : c0f50458 r5 : bf2d0794 r4 : bf2d06f8 [ 16.867723] r3 : bf2c6a88 r2 : ea00 r1 : ea07 r0 : bf2c6a88 [ 16.867727] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 16.867730] Control: 30c5387d Table: 276f15c0 DAC: fffd [ 16.867732] Process modprobe (pid: 1126, stack limit = 0xe76a6250) [ 16.867734] Stack: (0xe76a7d78 to 0xe76a8000) [ 16.867737] 7d60: e7608040 c0f50458 [ 16.867741] 7d80: 0001 c0435054 c0f50458 0001 0007 c0e04920 [ 16.867744] 7da0: bf2d0600 c043517c bf2d0600 bf2d0620 0007 c095c62c c095c70c [ 16.867747] 7dc0: bf2d0a24 c0dff554 c0e04920 c0e04920 e7608b80 bf2d81a0 bf2d0a24 c092661c [ 16.867751] 7de0: c0dff554 bf2d8050 e76a6038 c0309740 0001 c04836e4 [ 16.867754] 7e00: e9ce6c40 e76b8080 8040003f 0001 c043d60c e9ce6c20 [ 16.867757] 7e20: 8040003f 80150014 c043f530 0001 [ 16.867760] 7e40: 0cab 8040003f e76b8080 f0c11000 0001 bd94282a e76a7f58 [ 16.867763] 7e60: bf2d0894 e76a6000 c0dff554 e76a7f58 bf2d0888 c03d55c4 [ 16.867767] 7e80: 8000 7fff c03d2374 ebad4188 b860d1c0 bf2d0894 040c bf2d1000 [ 16.867770] 7ea0: bf2d0894 b6fef398 c0dff554 e76a7f5c c049ef68 [ 16.867773] 7ec0: bf2cd024 0001 bf2cd02c 0002 [ 16.867776] 7ee0: 6e72656b 6c65 [ 16.867779] 7f00: [ 16.867783] 7f20: bd94282a 0120 b6fef398 017b c0320ec4 [ 16.867786] 7f40: e76a6000 b860d1c0 c03d5b90 00181088 f0c11000 0002391c [ 16.867789] 7f60: f0c33fe4 f0c27059 f0c2b378 00014000 00017190 bf2d0798 000a 0001 [ 16.867793] 7f80: 0039 003a 002e 0032 001a b6ff0608 b6ff0e18 [ 16.867796] 7fa0: b6ff0990 c0320d20 b6ff0608 b6ff0e18 b6fef398 b6ff0968 [ 16.867799] 7fc0: b6ff0608 b6ff0e18 b6ff0990 017b b8615288 b860d1c0 [ 16.867803] 7fe0: bef98a38 bef98a28 b6fe6177 b6f5b2b2 40010030 705f646e 696c6275 [ 16.867812] [c0a20494] (patch_text) from [c0434ffc] (__jump_label_update+0x64/0x6c) [ 16.867819] [c0434ffc] (__jump_label_update) from [c0435054] (jump_label_update+0x50/0x9c) [ 16.867826] [c0435054] (jump_label_update) from [c043517c] (static_key_slow_inc+0xdc/0xe0) [ 16.867835] [c043517c] (static_key_slow_inc) from [c095c62c] (nf_register_hook+0xc0/0xcc) [ 16.867842] [c095c62c] (nf_register_hook) from [c095c70c] (nf_register_hooks+0x38/0x78) [ 16.867861] [c095c70c] (nf_register_hooks) from [bf2d81a0] (br_netfilter_init+0x38/0xe98 [bridge]) [ 16.867895] [bf2d81a0] (br_netfilter_init [bridge]) from [bf2d8050] (br_init+0x50/0xd0 [bridge]) [ 16.867911] [bf2d8050] (br_init [bridge]) from [c0309740] (do_one_initcall+0xdc/0x20c) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378856/+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 1378856] Re: [highbank] Oops on boot loading bridge module
fyi, ps shows the following process which appears to be hung: root 1132 1065 0 01:48 ?00:00:00 brctl addbr lxcbr0 -- 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/1378856 Title: [highbank] Oops on boot loading bridge module Status in “linux” package in Ubuntu: Incomplete Bug description: [ 16.845971] Unable to handle kernel paging request at virtual address bf2c6a88 [ 16.853224] pgd = e76f15c0 [ 16.856108] [bf2c6a88] *pgd=2777a003, *pmd=2babb003, *pte=802753879f [ 16.862870] Internal error: Oops: a0f [#1] SMP ARM [ 16.867656] Modules linked in: bridge(+) stp llc iptable_filter ip_tables x_tables ib_iser[ 16.867695] CPU: 0 PID: 1126 Comm: modprobe Not tainted 3.16.0-21-generic-lpae #28-Ubuntu [ 16.867698] task: ec891a00 ti: e76a6000 task.ti: e76a6000 [ 16.867705] PC is at patch_text+0x4/0x10 [ 16.867713] LR is at __jump_label_update+0x64/0x6c [ 16.867716] pc : [c0a20494]lr : [c0434ffc]psr: 80070013 [ 16.867716] sp : e76a7d78 ip : 00019d80 fp : bf2d0888 [ 16.867718] r10: r9 : bf2d8000 r8 : [ 16.867721] r7 : 0001 r6 : c0f50458 r5 : bf2d0794 r4 : bf2d06f8 [ 16.867723] r3 : bf2c6a88 r2 : ea00 r1 : ea07 r0 : bf2c6a88 [ 16.867727] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 16.867730] Control: 30c5387d Table: 276f15c0 DAC: fffd [ 16.867732] Process modprobe (pid: 1126, stack limit = 0xe76a6250) [ 16.867734] Stack: (0xe76a7d78 to 0xe76a8000) [ 16.867737] 7d60: e7608040 c0f50458 [ 16.867741] 7d80: 0001 c0435054 c0f50458 0001 0007 c0e04920 [ 16.867744] 7da0: bf2d0600 c043517c bf2d0600 bf2d0620 0007 c095c62c c095c70c [ 16.867747] 7dc0: bf2d0a24 c0dff554 c0e04920 c0e04920 e7608b80 bf2d81a0 bf2d0a24 c092661c [ 16.867751] 7de0: c0dff554 bf2d8050 e76a6038 c0309740 0001 c04836e4 [ 16.867754] 7e00: e9ce6c40 e76b8080 8040003f 0001 c043d60c e9ce6c20 [ 16.867757] 7e20: 8040003f 80150014 c043f530 0001 [ 16.867760] 7e40: 0cab 8040003f e76b8080 f0c11000 0001 bd94282a e76a7f58 [ 16.867763] 7e60: bf2d0894 e76a6000 c0dff554 e76a7f58 bf2d0888 c03d55c4 [ 16.867767] 7e80: 8000 7fff c03d2374 ebad4188 b860d1c0 bf2d0894 040c bf2d1000 [ 16.867770] 7ea0: bf2d0894 b6fef398 c0dff554 e76a7f5c c049ef68 [ 16.867773] 7ec0: bf2cd024 0001 bf2cd02c 0002 [ 16.867776] 7ee0: 6e72656b 6c65 [ 16.867779] 7f00: [ 16.867783] 7f20: bd94282a 0120 b6fef398 017b c0320ec4 [ 16.867786] 7f40: e76a6000 b860d1c0 c03d5b90 00181088 f0c11000 0002391c [ 16.867789] 7f60: f0c33fe4 f0c27059 f0c2b378 00014000 00017190 bf2d0798 000a 0001 [ 16.867793] 7f80: 0039 003a 002e 0032 001a b6ff0608 b6ff0e18 [ 16.867796] 7fa0: b6ff0990 c0320d20 b6ff0608 b6ff0e18 b6fef398 b6ff0968 [ 16.867799] 7fc0: b6ff0608 b6ff0e18 b6ff0990 017b b8615288 b860d1c0 [ 16.867803] 7fe0: bef98a38 bef98a28 b6fe6177 b6f5b2b2 40010030 705f646e 696c6275 [ 16.867812] [c0a20494] (patch_text) from [c0434ffc] (__jump_label_update+0x64/0x6c) [ 16.867819] [c0434ffc] (__jump_label_update) from [c0435054] (jump_label_update+0x50/0x9c) [ 16.867826] [c0435054] (jump_label_update) from [c043517c] (static_key_slow_inc+0xdc/0xe0) [ 16.867835] [c043517c] (static_key_slow_inc) from [c095c62c] (nf_register_hook+0xc0/0xcc) [ 16.867842] [c095c62c] (nf_register_hook) from [c095c70c] (nf_register_hooks+0x38/0x78) [ 16.867861] [c095c70c] (nf_register_hooks) from [bf2d81a0] (br_netfilter_init+0x38/0xe98 [bridge]) [ 16.867895] [bf2d81a0] (br_netfilter_init [bridge]) from [bf2d8050] (br_init+0x50/0xd0 [bridge]) [ 16.867911] [bf2d8050] (br_init [bridge]) from [c0309740] (do_one_initcall+0xdc/0x20c) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378856/+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 1309221] Re: transparent hugepages flaky on arm64 and armhf
** Summary changed: - transparent hugepages flaky on arm64 + transparent hugepages flaky on arm64 and armhf -- 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/1309221 Title: transparent hugepages flaky on arm64 and armhf Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Fix Released Status in “linux” source package in Utopic: Confirmed Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to never until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+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
Re: [Kernel-packages] [Bug 1378856] Re: [highbank] Oops on boot loading bridge module
On Wed, Oct 8, 2014 at 8:56 AM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Which kernel version is causing this oops Full boot log is attached, version was: [0.00] Linux version 3.16.0-21-generic-lpae (buildd@kishi02) (gcc version 4.9.1 (Ubuntu/Linaro 4.9.1-16ubuntu4) ) #28-Ubuntu SMP Mon Oct 6 17:57:17 UTC 2014 (Ubuntu 3.16.0-21.28-generic-lpae 3.16.4) , and was there a prior kernel that did not? This is the first utopic kernel I've tried; but trusty did not exhibit this failure. -- 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/1378856 Title: [highbank] Oops on boot loading bridge module Status in “linux” package in Ubuntu: Confirmed Bug description: [ 16.845971] Unable to handle kernel paging request at virtual address bf2c6a88 [ 16.853224] pgd = e76f15c0 [ 16.856108] [bf2c6a88] *pgd=2777a003, *pmd=2babb003, *pte=802753879f [ 16.862870] Internal error: Oops: a0f [#1] SMP ARM [ 16.867656] Modules linked in: bridge(+) stp llc iptable_filter ip_tables x_tables ib_iser[ 16.867695] CPU: 0 PID: 1126 Comm: modprobe Not tainted 3.16.0-21-generic-lpae #28-Ubuntu [ 16.867698] task: ec891a00 ti: e76a6000 task.ti: e76a6000 [ 16.867705] PC is at patch_text+0x4/0x10 [ 16.867713] LR is at __jump_label_update+0x64/0x6c [ 16.867716] pc : [c0a20494]lr : [c0434ffc]psr: 80070013 [ 16.867716] sp : e76a7d78 ip : 00019d80 fp : bf2d0888 [ 16.867718] r10: r9 : bf2d8000 r8 : [ 16.867721] r7 : 0001 r6 : c0f50458 r5 : bf2d0794 r4 : bf2d06f8 [ 16.867723] r3 : bf2c6a88 r2 : ea00 r1 : ea07 r0 : bf2c6a88 [ 16.867727] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 16.867730] Control: 30c5387d Table: 276f15c0 DAC: fffd [ 16.867732] Process modprobe (pid: 1126, stack limit = 0xe76a6250) [ 16.867734] Stack: (0xe76a7d78 to 0xe76a8000) [ 16.867737] 7d60: e7608040 c0f50458 [ 16.867741] 7d80: 0001 c0435054 c0f50458 0001 0007 c0e04920 [ 16.867744] 7da0: bf2d0600 c043517c bf2d0600 bf2d0620 0007 c095c62c c095c70c [ 16.867747] 7dc0: bf2d0a24 c0dff554 c0e04920 c0e04920 e7608b80 bf2d81a0 bf2d0a24 c092661c [ 16.867751] 7de0: c0dff554 bf2d8050 e76a6038 c0309740 0001 c04836e4 [ 16.867754] 7e00: e9ce6c40 e76b8080 8040003f 0001 c043d60c e9ce6c20 [ 16.867757] 7e20: 8040003f 80150014 c043f530 0001 [ 16.867760] 7e40: 0cab 8040003f e76b8080 f0c11000 0001 bd94282a e76a7f58 [ 16.867763] 7e60: bf2d0894 e76a6000 c0dff554 e76a7f58 bf2d0888 c03d55c4 [ 16.867767] 7e80: 8000 7fff c03d2374 ebad4188 b860d1c0 bf2d0894 040c bf2d1000 [ 16.867770] 7ea0: bf2d0894 b6fef398 c0dff554 e76a7f5c c049ef68 [ 16.867773] 7ec0: bf2cd024 0001 bf2cd02c 0002 [ 16.867776] 7ee0: 6e72656b 6c65 [ 16.867779] 7f00: [ 16.867783] 7f20: bd94282a 0120 b6fef398 017b c0320ec4 [ 16.867786] 7f40: e76a6000 b860d1c0 c03d5b90 00181088 f0c11000 0002391c [ 16.867789] 7f60: f0c33fe4 f0c27059 f0c2b378 00014000 00017190 bf2d0798 000a 0001 [ 16.867793] 7f80: 0039 003a 002e 0032 001a b6ff0608 b6ff0e18 [ 16.867796] 7fa0: b6ff0990 c0320d20 b6ff0608 b6ff0e18 b6fef398 b6ff0968 [ 16.867799] 7fc0: b6ff0608 b6ff0e18 b6ff0990 017b b8615288 b860d1c0 [ 16.867803] 7fe0: bef98a38 bef98a28 b6fe6177 b6f5b2b2 40010030 705f646e 696c6275 [ 16.867812] [c0a20494] (patch_text) from [c0434ffc] (__jump_label_update+0x64/0x6c) [ 16.867819] [c0434ffc] (__jump_label_update) from [c0435054] (jump_label_update+0x50/0x9c) [ 16.867826] [c0435054] (jump_label_update) from [c043517c] (static_key_slow_inc+0xdc/0xe0) [ 16.867835] [c043517c] (static_key_slow_inc) from [c095c62c] (nf_register_hook+0xc0/0xcc) [ 16.867842] [c095c62c] (nf_register_hook) from [c095c70c] (nf_register_hooks+0x38/0x78) [ 16.867861] [c095c70c] (nf_register_hooks) from [bf2d81a0] (br_netfilter_init+0x38/0xe98 [bridge]) [ 16.867895] [bf2d81a0] (br_netfilter_init [bridge]) from [bf2d8050] (br_init+0x50/0xd0 [bridge]) [ 16.867911] [bf2d8050] (br_init [bridge]) from [c0309740] (do_one_initcall+0xdc/0x20c) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1309221] Re: transparent hugepages flaky on arm64 and armhf
** Changed in: linux (Ubuntu Utopic) Status: Confirmed = 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/1309221 Title: transparent hugepages flaky on arm64 and armhf Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Released Status in “linux” source package in Utopic: In Progress Bug description: linux 3.13.0-24.46 transparent hugepages, which are configured on by default in Ubuntu, are flaky on arm64. The most evident system is that go processes reliably hang or crash. This has been observed with both building juju-core with gccgo, and running the resulting juju binaries. The root cause of this is that get_user_pages_fast is not yet implemented on arm64 (and arm64). Patches are floating around, but haven't landed. http://comments.gmane.org/gmane.linux.ports.arm.kernel/299268 We've verified that either applying those patches, or disabling THP via sysfs, prevents the above issues. At minimum we should change the default boottime sysfs setting for THP to never until we can fix this feature properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309221/+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 1284433] Re: System can not reboot on APM X-Gene board
** Also affects: linux (Ubuntu Utopic) Importance: Medium Assignee: Ike Panhc (ikepanhc) Status: Fix Released ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: Fix Released = Confirmed ** Changed in: linux (Ubuntu Trusty) Status: New = Fix Released ** Changed in: linux (Ubuntu Utopic) Assignee: Ike Panhc (ikepanhc) = (unassigned) ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = Ike Panhc (ikepanhc) ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = Medium -- 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/1284433 Title: System can not reboot on APM X-Gene board Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Fix Released Status in “linux” source package in Utopic: Confirmed Bug description: * Stopping rsync daemon rsync [ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Deactivating swap... [ OK ] * Unmounting weak filesystems...[ OK ] * Unmounting local filesystems... [ OK ] * Will now restart [ 151.242953] reboot: Restarting system System hangs when rebooting, need drivers from http://www.spinics.net/lists/arm-kernel/msg303898.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284433/+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] [NEW] xgene-enet: add 10GbE support
Public bug reported: [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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) 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/1381084 Title: xgene-enet: add 10GbE support Status in “linux” package in Ubuntu: New Status in “linux” source package in Trusty: New Status in “linux” source package in Utopic: New 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 1381084] Re: xgene-enet: add 10GbE support
** Changed in: linux (Ubuntu Trusty) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu Utopic) 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/1381084 Title: xgene-enet: add 10GbE support Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “linux” source package in Utopic: Confirmed 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 1381216] [NEW] xgene-enet: add SGMII based 1GbE support
Public bug reported: [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. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Tags: hs-arm64 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Trusty) Status: New = 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/1381216 Title: xgene-enet: add SGMII based 1GbE support Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “linux” source package in Utopic: Confirmed 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 1382244] [NEW] HP ProLiant m400 nic fails to initialize when booted w/ debug
Public bug reported: [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. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: Confirmed ** Affects: linux (Ubuntu Trusty) Importance: Undecided Assignee: dann frazier (dannf) Status: Confirmed ** Affects: linux (Ubuntu Utopic) Importance: Undecided Assignee: dann frazier (dannf) Status: Confirmed ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Assignee: dann frazier (dannf) Status: Confirmed ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) -- 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: Confirmed Status in “linux” source package in Trusty: Confirmed Status in “linux” source package in Utopic: Confirmed 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
** Changed in: linux (Ubuntu Trusty) Status: Confirmed = Fix Committed ** Changed in: linux (Ubuntu Utopic) 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/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] [NEW] xgene-pcie: Fix max payload size and phantom function configuration[
Public bug reported: [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. ** Affects: linux (Ubuntu) Importance: High Assignee: dann frazier (dannf) Status: Confirmed ** Affects: linux (Ubuntu Trusty) Importance: High Assignee: dann frazier (dannf) Status: Confirmed ** Affects: linux (Ubuntu Utopic) Importance: High Assignee: dann frazier (dannf) Status: Confirmed ** Tags: hs-arm64 ** Attachment added: 0001-PCI-X-Gene-Fix-max-payload-size-and-phantom-function-conf.patch https://bugs.launchpad.net/bugs/1386261/+attachment/4246301/+files/0001-PCI-X-Gene-Fix-max-payload-size-and-phantom-function-conf.patch ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux (Ubuntu Utopic) Status: New = Confirmed ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = High ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = dann frazier (dannf) -- 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: Confirmed Status in “linux” source package in Utopic: Confirmed 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 1386261] Re: xgene-pcie: Fix max payload size and phantom function configuration
** Summary changed: - xgene-pcie: Fix max payload size and phantom function configuration[ + xgene-pcie: Fix max payload size and phantom function configuration -- 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: Confirmed Status in “linux” source package in Utopic: Confirmed 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 1386261] Re: xgene-pcie: Fix max payload size and phantom function configuration
** Changed in: linux (Ubuntu Utopic) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Trusty) Status: Confirmed = 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/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: In Progress Status in “linux” source package in Utopic: In Progress 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 1386490] [NEW] HP ProLiant m400 nic doesn't work after trusty
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Vivid) Importance: High Status: Confirmed ** Tags: hs-arm64 ** Attachment added: boot log demonstrating problem https://bugs.launchpad.net/bugs/1386490/+attachment/4246707/+files/boot.log ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: High Status: 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/1386490 Title: HP ProLiant m400 nic doesn't work after trusty Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: New 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/ubuntu/+source/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
** Changed in: linux (Ubuntu Utopic) Status: New = Confirmed ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = High -- 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 “linux” package in Ubuntu: Confirmed Status in “linux” source package in Utopic: 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/ubuntu/+source/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 1388952] [NEW] CONFIG_IPMI_SI_PROBE_DEFAULTS should be disabled on ARM
Public bug reported: [Impact] Causes fault which can lead to a hang or crash on ARM systems when loading the ipmi_si module. The ipmi_si driver includes code that probes into iospace for a KCS interface. This is to support platforms that don't expose this interface in SMBIOS/ACPI tables, and this is a defined discovery mechanism as per the IPMI Spec (v2.0r1, section 9.5). However, this assumption is x86-centric. It is not safe to blindly probe I/O space on ARM platforms. [Test Case] sudo modprobe ipmi_si This should discover an IPMI system interface if present, or fail to load otherwise. But it should not cause a hang, a synchronous external abort, or other kernel failure. [Regression Risk] The proposed fix is only to the ARM config, so the risk to other architectures is negligible. There is a risk that there exists some system out there where this probing works - but I'm highly confident no such system exists. Existing ARM systems supported by Ubuntu either describe their IPMI/KCS interface using device-tree or do not provide one. ** Affects: linux (Ubuntu) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Trusty) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Utopic) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Vivid) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Tags: hs-arm64 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: High Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: New = In Progress ** Changed in: linux (Ubuntu Trusty) Status: New = In Progress ** Changed in: linux (Ubuntu Utopic) Importance: Undecided = High ** Changed in: linux (Ubuntu Trusty) Importance: Undecided = High ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = dann frazier (dannf) ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) -- 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/1388952 Title: CONFIG_IPMI_SI_PROBE_DEFAULTS should be disabled on ARM Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress Status in “linux” source package in Vivid: In Progress Bug description: [Impact] Causes fault which can lead to a hang or crash on ARM systems when loading the ipmi_si module. The ipmi_si driver includes code that probes into iospace for a KCS interface. This is to support platforms that don't expose this interface in SMBIOS/ACPI tables, and this is a defined discovery mechanism as per the IPMI Spec (v2.0r1, section 9.5). However, this assumption is x86-centric. It is not safe to blindly probe I/O space on ARM platforms. [Test Case] sudo modprobe ipmi_si This should discover an IPMI system interface if present, or fail to load otherwise. But it should not cause a hang, a synchronous external abort, or other kernel failure. [Regression Risk] The proposed fix is only to the ARM config, so the risk to other architectures is negligible. There is a risk that there exists some system out there where this probing works - but I'm highly confident no such system exists. Existing ARM systems supported by Ubuntu either describe their IPMI/KCS interface using device-tree or do not provide one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388952/+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 1388952] Re: CONFIG_IPMI_SI_PROBE_DEFAULTS should be disabled on ARM
Trusty verified: dannf@mustang:~$ cat /proc/version Linux version 3.13.0-40-generic (buildd@auburn) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #68-Ubuntu SMP4 dannf@mustang:~$ sudo modprobe ipmi_si modprobe: ERROR: could not insert 'ipmi_si': No such device ** 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/1388952 Title: CONFIG_IPMI_SI_PROBE_DEFAULTS should be disabled on ARM 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 Status in “linux” source package in Vivid: Fix Committed Bug description: [Impact] Causes fault which can lead to a hang or crash on ARM systems when loading the ipmi_si module. The ipmi_si driver includes code that probes into iospace for a KCS interface. This is to support platforms that don't expose this interface in SMBIOS/ACPI tables, and this is a defined discovery mechanism as per the IPMI Spec (v2.0r1, section 9.5). However, this assumption is x86-centric. It is not safe to blindly probe I/O space on ARM platforms. [Test Case] sudo modprobe ipmi_si This should discover an IPMI system interface if present, or fail to load otherwise. But it should not cause a hang, a synchronous external abort, or other kernel failure. [Regression Risk] The proposed fix is only to the ARM config, so the risk to other architectures is negligible. There is a risk that there exists some system out there where this probing works - but I'm highly confident no such system exists. Existing ARM systems supported by Ubuntu either describe their IPMI/KCS interface using device-tree or do not provide one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388952/+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 1388952] Re: CONFIG_IPMI_SI_PROBE_DEFAULTS should be disabled on ARM
Utopic verified: dannf@mustang:~$ cat /proc/version Linux version 3.16.0-25-generic (buildd@beebe) (gcc version 4.9.1 (Ubuntu/Linaro 4.9.1-16ubuntu6) ) #33-Ubuntu SMP 4 dannf@mustang:~$ sudo modprobe ipmi_si modprobe: ERROR: could not insert 'ipmi_si': No such device dannf@mustang:~$ ** 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/1388952 Title: CONFIG_IPMI_SI_PROBE_DEFAULTS should be disabled on ARM 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 Status in “linux” source package in Vivid: Fix Committed Bug description: [Impact] Causes fault which can lead to a hang or crash on ARM systems when loading the ipmi_si module. The ipmi_si driver includes code that probes into iospace for a KCS interface. This is to support platforms that don't expose this interface in SMBIOS/ACPI tables, and this is a defined discovery mechanism as per the IPMI Spec (v2.0r1, section 9.5). However, this assumption is x86-centric. It is not safe to blindly probe I/O space on ARM platforms. [Test Case] sudo modprobe ipmi_si This should discover an IPMI system interface if present, or fail to load otherwise. But it should not cause a hang, a synchronous external abort, or other kernel failure. [Regression Risk] The proposed fix is only to the ARM config, so the risk to other architectures is negligible. There is a risk that there exists some system out there where this probing works - but I'm highly confident no such system exists. Existing ARM systems supported by Ubuntu either describe their IPMI/KCS interface using device-tree or do not provide one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388952/+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
** Changed in: linux (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Utopic) Status: Confirmed = 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/1381216 Title: xgene-enet: add SGMII based 1GbE support Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress 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
** Changed in: linux (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Utopic) Status: Confirmed = 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/1381084 Title: xgene-enet: add 10GbE support Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Trusty: In Progress Status in “linux” source package in Utopic: In Progress 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 1382244] Re: HP ProLiant m400 nic fails to initialize when booted w/ debug
** Changed in: linux (Ubuntu Trusty) Assignee: dann frazier (dannf) = Craig Magina (craig.magina) ** Changed in: linux (Ubuntu Utopic) Assignee: dann frazier (dannf) = 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/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
Re: [Kernel-packages] [Bug 1386490] Re: HP ProLiant m400 nic doesn't work after trusty
On Thu, Nov 27, 2014 at 8:17 PM, Ming Lei 1386...@bugs.launchpad.net wrote: From ARM64 maintainer's viewpoint: http://marc.info/?l=linux-arm-kernelm=141708838404470w=2 Either way, I don't think it's a problem for the kernel. We just need to change the default DMA ops to coherent when booting with ACPI (using non-coherent ops for a coherent device is not safe as the CPU can corrupt cache lines written by the device). So I suggest to revert c7a4a7658d689f6 for utopic since utopic ships APM's non-upstreamed PCI implementation, and APM's ARM64 Soc is coherent arch. Dann, what do you think about it? Ming, Thanks for looking into this. I'm not sure I follow the relevancy of a couple things: - The upstream discussion seems to have gotten rerouted to solving the problem for ACPI, but this issue is regarding device-tree (as was your patch), since that is what Ubuntu/m400 uses. I'm having trouble seeing how the ACPI solution helps us. - I'm confident I reproduced this problem with all upstream bits after PCI was merged. Therefore my assumption was that this issue is independent of PCI stack choice. Do you believe that the solution for the upstream PCI stack is different than the solution for the APM PCI stack? In general I'm OK with a revert of c7a4a7658d689f6 for utopic, as long as we have a plan for an upstream answer for vivid and beyond (= 3.19). I don't think the kernel team would support a plan that involves carrying this revert indefinitely (if that's what you're suggesting, I'm not sure it is). -dann Thanks, ** Changed in: linux (Ubuntu Utopic) Assignee: (unassigned) = Ming Lei (tom-leiming) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1386490 Title: HP ProLiant m400 nic doesn't work after trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386490/+subscriptions -- 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 linux package in Ubuntu: Confirmed Status in linux source package in Utopic: 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/ubuntu/+source/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 1398596] Re: [Revert] arm64: optimized copy_to_user and copy_from_user assembly code
** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) 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: Incomplete 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 1381084] Re: xgene-enet: add 10GbE support
This is not fixed in trusty - note that verification failed. ** Changed in: linux (Ubuntu Trusty) Status: Fix Released = 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/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 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 1433290] [NEW] xgene-enet: doesn't work at 100Mbit
Public bug reported: I hooked a mustang board up to a 100Mbit switch, and it fails to communicate. I've tried a couple switches, one a pretty common WRT54GL running Tomato firmware. The system fails to DHCP or ping if manually configured. I've verified the port/cable are ok with other devices. ** 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/1433290 Title: xgene-enet: doesn't work at 100Mbit Status in linux package in Ubuntu: New Bug description: I hooked a mustang board up to a 100Mbit switch, and it fails to communicate. I've tried a couple switches, one a pretty common WRT54GL running Tomato firmware. The system fails to DHCP or ping if manually configured. I've verified the port/cable are ok with other devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1433290/+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 1438318] Re: [arm64] tg3 NIC causing kernel stack trace
** Summary changed: - tg3 NIC causing kernel stack trace + [arm64] tg3 NIC causing kernel stack trace -- 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/1438318 Title: [arm64] tg3 NIC causing kernel stack trace Status in linux package in Ubuntu: Incomplete Bug description: Below is the relevant output from u-boot (arm64) loading the kernel (I believe it has all pertinent information). It should also be noted that when we pulled the tg3 NIC out of the machine, it booted up fine and there was no longer any issues: ## Booting kernel from Legacy Image at 400200 ... Image Name: kernel 3.16.0-33-generic Image Type: ARM Linux Kernel Image (uncompressed) Data Size:11536696 Bytes = 11 MiB Load Address: 0008 Entry Point: 0008 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 400400 ... Image Name: ramdisk 3.16.0-33-generic Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:24313751 Bytes = 23.2 MiB Load Address: Entry Point: Verifying Checksum ... OK ## Flattened Device Tree blob at 400300 Booting using the fdt blob at 0x00400300 Loading Kernel Image ... OK OK Loading Ramdisk to 43de8d, end 43df97 ... OK Loading Device Tree to 004000ff9000, end 004000fff838 ... OK Fix up GIC node for non-secure access 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.16.0-33-generic (buildd@templar) (gcc version 4.9.1 (Ubuntu/Linaro 4.9.1-16ubuntu6) ) #44-Ubuntu SMP Thu Mar 12 12:25:12 UTC 2015 (Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7) [0.00] CPU: AArch64 Processor [500f] revision 0 [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: UEFI not found. [0.00] PERCPU: Embedded 12 pages/cpu @ffc3fff59000 s19520 r8192 d21440 u49152 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4136960 [0.00] Kernel command line: nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-arm64-xgene-uboot-mustang-utopic-daily iscsi_target_ip=10.228.12.173 iscsi_target_port=3260 iscsi_initiator=hidden-chicken ip=hidden-chicken:BOOTIF ro root=/dev/disk/by-path/ip-10.228.12.173:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-arm64-xgene-uboot-mustang-utopic-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://10.228.12.173/MAAS/metadata/latest/by-id/node-4a600b98-d370-11e4-a434-00163e634f88/?op=get_preseed log_host=10.228.12.173 log_port=514 xx console=ttyS0,115200 BOOTIF=01-00-01-73-02-08-25 [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) [0.00] Memory: 16486692K/16777216K available (6935K kernel code, 754K rwdata, 3016K rodata, 555K init, 757K bss, 290524K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbce000 - 0xffbcee00 ( 224 MB) [0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB) [0.00] memory : 0xffc0 - 0xffc4 ( 16384 MB) [0.00] .init : 0xffc000a39000 - 0xffc000ac3c40 ( 556 kB) [0.00] .text : 0xffc8 - 0xffc000a38dc4 ( 9956 kB) [0.00] .data : 0xffc000ac4000 - 0xffc000b80938 ( 755 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.02] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns [0.69] Console: colour dummy device 80x25 [0.003113] allocated 67108864 bytes of page_cgroup [0.003116] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.003125] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50) [0.003129] pid_max: default: 32768 minimum: 301 [0.003167] Security Framework initialized [0.003203] AppArmor: AppArmor initialized [0.003205] Yama: becoming mindful. [0.003266] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes) [0.003270] Mountpoint-cache
[Kernel-packages] [Bug 1426043] Re: kernel 3.13.0-46.75 fails to boot on arm64
Fix verified on a mustang board. 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/1426043
Title:
kernel 3.13.0-46.75 fails to boot on arm64
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
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 : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194
Diagnosing further, I've found that this happens when accessing a certain file: dannf@mustang:~$ ls -l /usr/bin/qemu-system-aarch64 -rwxr-xr-x 1 root root 4998496 Mar 12 21:17 /usr/bin/qemu-system-aarch64 dannf@mustang:~$ ls -l /usr/lib/python2.7/six.pyc [ 3586.472110] Unable to handle kernel paging request at virtual address 3c [ 3586.479819] pgd = ffc0fdebf000 [ 3586.483237] [3c] *pgd=0040fde7d003, *pud=0040fde7d003, *pmd= [ 3586.492027] Internal error: Oops: 9604 [#13] SMP [ 3586.496965] Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6t [ 3586.539676] CPU: 5 PID: 1932 Comm: ls Tainted: G D 3.19.0-12-generic #12-Ubuntu [ 3586.547982] Hardware name: APM X-Gene Mustang board (DT) [ 3586.553266] task: ffc3e8a38c40 ti: ffc0fc68c000 task.ti: ffc0fc68c000 [ 3586.560712] PC is at __d_lookup_rcu+0x80/0x17c [ 3586.565133] LR is at lookup_fast+0x4c/0x2f0 [ 3586.569293] pc : [ffc000229eec] lr : [ffc00021ce68] pstate: 0145 [ 3586.576648] sp : ffc0fc68fb40 [ 3586.579942] x29: ffc0fc68fb40 x28: ffc0fc68c000 [ 3586.585245] x27: x26: 0007 [ 3586.590546] x25: ffc3ed26a033 x24: ffc0fc68fd20 [ 3586.595848] x23: 000725cabf8e x22: ffc0fc68fbfc [ 3586.601150] x21: ffc3ed53b780 x20: 0038 [ 3586.606451] x19: 0040 x18: [ 3586.611754] x17: 004292d0 x16: ffc000215d3c [ 3586.617057] x15: x14: 007faf35c16c [ 3586.622360] x13: x12: 0010 [ 3586.627662] x11: x10: fefefefefefefeff [ 3586.632965] x9 : 007fca1ade6c x8 : 535f474458006379 [ 3586.638268] x7 : x6 : 0020 [ 3586.643571] x5 : x4 : ffc000b64f60 [ 3586.648872] x3 : 0015 x2 : ffc3eec0 [ 3586.654174] x1 : 000b x0 : 001ed681 [ 3586.659475] [ 3586.660956] Process ls (pid: 1932, stack limit = 0xffc0fc68c058) [ 3586.667275] Stack: (0xffc0fc68fb40 to 0xffc0fc69) [ 3586.672991] fb40: fc68fba0 ffc0 0021ce68 ffc0 fc68fd10 ffc0 [ 3586.681126] fb60: fc68fc70 ffc0 fc68fc60 ffc0 dfa06020 ffc3 ed53b780 ffc3 [ 3586.689260] fb80: 011a 004f 00b6e000 ffc0 c3e4c240 ffbe [ 3586.697395] fba0: fc68fc00 ffc0 0021f578 ffc0 fc68fd10 ffc0 [ 3586.705529] fbc0: 0040 ed26a020 ffc3 ff9c 0015 [ 3586.713663] fbe0: 011a ed26a020 ffc3 ff9c 000994ec ffc0 [ 3586.721798] fc00: fc68fc90 ffc0 0021fbe4 ffc0 ed26a000 ffc3 fc68fd10 ffc0 [ 3586.729932] fc20: ed26a000 ffc3 ff9c 0015 [ 3586.738066] fc40: 011a 004f 00b6e000 ffc0 ca1ade4c 007f [ 3586.746201] fc60: fc68fe20 ffc0 0015 [ 3586.754335] fc80: fc68fcd0 ffc0 0022133c ffc0 fc68fcd0 ffc0 00221360 ffc0 [ 3586.762469] fca0: ed26a000 ffc3 ff9c [ 3586.770604] fcc0: fc68fe20 ffc0 00b6fc10 ffc0 fc68fdb0 ffc0 002213f0 ffc0 [ 3586.778738] fce0: ff9c ca1ade4c 007f fc68fe20 ffc0 [ 3586.786872] fd00: fc68fe68 ffc0 00129750 ffc0 dfa06020 ffc3 ed53b780 ffc3 [ 3586.795007] fd20: 25cabf8e 0007 ed26a033 ffc3 dfa06020 ffc3 ed5da180 ffc3 [ 3586.803141] fd40: ff659c88 ffc0 0040 0002 0536 [ 3586.811275] fd60: 0012a07c ffc0 0001 [ 3586.819410] fd80: 0081 af49e770 007f 7fff 0003 [ 3586.827544] fda0: 0062 fc68fde0 ffc0 002157b0 ffc0 [ 3586.835678] fdc0: ff9c ca1ade4c 007f [ 3586.843813] fde0: fc68fe30 ffc0 00215d78 ffc0 ff9c ca1ade4c 007f [ 3586.851947] fe00: 0100 22811c90 8000 001d468c [ 3586.860081] fe20: ca1ad0a0 007f 0008609c ffc0 ca1ace20 007f 000863f0 ffc0 [ 3586.868216] fe40: 22811c90 af41614c 007f [ 3586.876350] fe60: ca1ace00 007f 000863f0 ffc0 af37c140 007f [ 3586.884484] fe80: af2aa05c 007f 2000 0015 [ 3586.892619] fea0: 011a 0062 ca1acc90 007f 000863f0 ffc0 [ 3586.900753] fec0: 0015 ff9c ca1ade4c 007f [ 3586.908887] fee0: 22811c90 0100
[Kernel-packages] [Bug 1448811] Re: Internal error: Oops: 9600004f [#41] SMP leaks unkillable processes
@Dave: Can you provide instructions on obtaining/executing runtest.exe so I can attempt to reproduce it on another system? -- 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/1448811 Title: Internal error: Oops: 964f [#41] SMP leaks unkillable processes Status in linux package in Ubuntu: Incomplete Bug description: We have an arm64 xgene system running 14.04.1 which leaks processes when the kernel oopses [928109.838289] Unable to handle kernel paging request at virtual address 42083b48a0 [928109.845776] pgd = ffc00a50b000 [928109.849254] [42083b48a0] *pgd=00420bb45003, *pmd=0042dd0fb003, *pte=00a000407272ffd3 [928109.857788] Internal error: Oops: 964f [#42] SMP [928109.862815] Modules linked in: 8021q garp stp mrp llc gpio_dwapb gpio_generic xgene_rng uio_pdrv_genirq uio ahci_xgene ahci_platform libahci xgene_enet [928109.876569] CPU: 5 PID: 11728 Comm: runtest.exe Tainted: G D 3.13.0-37-generic #64-Ubuntu [928109.885743] task: ffc2b013ac00 ti: ffc001884000 task.ti: ffc001884000 [928109.893281] PC is at __hyp_text_end+0x2230/0x3180 [928109.898052] LR is at pipe_read+0x23c/0x4d4 [928109.902219] pc : [ffc00060d230] lr : [ffc0001aea20] pstate: 2145 [928109.909672] sp : ffc001887cf0 [928109.913058] x29: ffc001887cf0 x28: ffc2c56a9000 [928109.918451] x27: ffc001887dc8 x26: 1000 [928109.923842] x25: ffc2c56a9000 x24: ffc001884000 [928109.929244] x23: 0001 x22: ffc0006269d8 [928109.934636] x21: ffc219e81cc0 x20: ffc001971518 [928109.940029] x19: x18: [928109.945420] x17: 003ce8e0 x16: 0001f4b0 [928109.950810] x15: x14: 65757274202c3130 [928109.956205] x13: 303030303030 x12: 66377830 [928109.961599] x11: 202c313137323030 x10: 3030 [928109.966993] x9 : 66377830202c6665 x8 : 38643078 [928109.972385] x7 : 302d202c30303030 x6 : 0042083b48a0 [928109.98] x5 : 1000 x4 : [928109.983174] x3 : 1d365e9f x2 : 1000 [928109.988566] x1 : ffc2c56a9030 x0 : 1000 [928109.993954] [928109.995527] Process runtest.exe (pid: 11728, stack limit = 0xffc001884058) [928110.002800] Stack: (0xffc001887cf0 to 0xffc001888000) [928110.008606] 7ce0: 01887da0 ffc0 001a5b50 ffc0 [928110.016829] 7d00: 01887dd8 ffc0 01887ec8 ffc0 01887ec8 ffc0 083b48c0 0042 [928110.025051] 7d20: 6000 0015 0112 003f [928110.033275] 7d40: 008ec000 ffc0 01884000 ffc0 6000 1000 [928110.041499] 7d60: 19e81d38 ffc2 19e81ce8 ffc2 d695cc00 ffc3 01884000 0007 [928110.049722] 7d80: 0001 9540 1000 01887dc8 ffc0 [928110.057946] 7da0: 01887e30 ffc0 001a6110 ffc0 d695cc00 ffc3 01884000 ffc0 [928110.066170] 7dc0: 083b48c0 0042 9540 d695cc00 ffc3 [928110.074393] 7de0: b013ac00 ffc2 [928110.082616] 7e00: 9540 [928110.090840] 7e20: 01887e80 ffc0 001a6c04 ffc0 [928110.099064] 7e40: d695cc00 ffc3 083b48c0 0042 0001 001467d8 [928110.107287] 7e60: 6000 0015 d695cc00 ffc3 [928110.115509] 7e80: 000849ec ffc0 [928110.123730] 7ea0: 000849ec ffc0 9540 [928110.131951] 7ec0: 000e2920 0010 083b48c0 0042 [928110.140172] 7ee0: 9540 [928110.148394] 7f00: 9540 0802a4e8 0042 003f 00053a08 [928110.156618] 7f20: 0801a000 0042 00324160 00324160 0010 [928110.164841] 7f40: 0a3f13d0 000a 0004f570 00277ff0 [928110.173071] 7f60: 08119490 0042 [928110.181302] 7f80: [928110.189527] 7fa0: 00324508 080bbcc0 0042 [928110.197756] 7fc0: 001467b8 08312c40 0042 001467d8 6000 [928110.205982] 7fe0: 0010 003f [928110.214204] Call trace: [928110.216736]
[Kernel-packages] [Bug 1441291] Re: support EFI rtc on arm64
Verified using tianocore/qemu (search for rtc below): Booting a command list EFI stub: Booting Linux Kernel... [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-53-generic (buildd@auburn) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #87-Ubuntu SMP Thu May 7 14:43:55 UTC 2015 (Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19) [0.00] CPU: AArch64 Processor [500f] revision 0 [0.00] No earlyprintk arguments passed. [0.00] efi: Getting parameters from FDT: [0.00] EFI v2.40 by EDK II [0.00] efi: [0.00] psci: probing function IDs from device-tree [0.00] PERCPU: Embedded 11 pages/cpu @ffc03f9bb000 s16192 r8192 d20672 u45056 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258560 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=1aaf7ff5-f468-46de-bca4-960eaf01a7b4 ro earlyprintk console=ttyAMA0 [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [0.00] software IO TLB [mem 0x73098000-0x77098000] (64MB) mapped at [ffc033098000-ffc037097fff] [0.00] Memory: 901200K/1048576K available (5750K kernel code, 587K rwdata, 2548K rodata, 315K init, 542K bss, 147376K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbc00e0 - 0xffbc01c0 (14 MB) [0.00] modules : 0xffbffc00 - 0xffc0 (64 MB) [0.00] memory : 0xffc0 - 0xffc04000 ( 1024 MB) [0.00] .init : 0xffc00089c000 - 0xffc0008eaf40 ( 316 kB) [0.00] .text : 0xffc8 - 0xffc00089b9b4 ( 8303 kB) [0.00] .data : 0xffc0008eb000 - 0xffc00097df68 ( 588 kB) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] RCU dyntick-idle grace-period acceleration is enabled. [0.00] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1. [0.00] NR_IRQS:64 nr_irqs:64 0 [0.00] Architected cp15 timer(s) running at 50.00MHz (virt). [0.00] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns [0.00] Console: colour dummy device 80x25 [0.00] allocated 4194304 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.001040] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50) [0.001045] pid_max: default: 32768 minimum: 301 [0.001091] Security Framework initialized [0.001122] AppArmor: AppArmor initialized [0.001125] Yama: becoming mindful. [0.001153] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) [0.001156] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes) [0.001687] Initializing cgroup subsys memory [0.001697] Initializing cgroup subsys devices [0.001700] Initializing cgroup subsys freezer [0.001703] Initializing cgroup subsys blkio [0.001705] Initializing cgroup subsys perf_event [0.001710] Initializing cgroup subsys hugetlb [0.001827] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available [0.001838] Remapping and enabling EFI services. [0.026754] Freed 0x202c000 bytes of EFI boot services memory [0.027456] Brought up 1 CPUs [0.027460] SMP: Total of 1 processors activated. [0.027684] devtmpfs: initialized [0.029312] EVM: security.selinux [0.029315] EVM: security.SMACK64 [0.029317] EVM: security.ima [0.029318] EVM: security.capability [0.029600] atomic64 test passed [0.029686] regulator-dummy: no parameters [0.029778] NET: Registered protocol family 16 [0.031266] vdso: 2 pages (1 code, 1 data) at base ffc0008f1000 [0.031297] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [0.031373] Serial: AMBA PL011 UART driver [0.031426] 900.pl011: ttyAMA0 at MMIO 0x900 (irq = 33, base_baud = 0) is a PL011 rev1 [0.231224] console [ttyAMA0] enabled [0.234092] bio: create slab bio-0 at 0 [0.237192] vgaarb: loaded [0.239349] SCSI subsystem initialized [0.242252] NetLabel: Initializing [0.244336] NetLabel: domain hash size = 128 [0.247118] NetLabel: protocols = UNLABELED CIPSOv4 [0.250335] NetLabel: unlabeled traffic allowed by default [0.254016] Switched to clocksource arch_sys_counter [0.260738] AppArmor: AppArmor Filesystem Enabled [0.265693]
[Kernel-packages] [Bug 1441876] Re: arm64 efi stub support
I've verified that I can successfully boot a trusty cloud image in an EFI VM by upgrading it to proposed and manually adding console=ttyAMA0 to the kernel commandline (a separate issue): EFI stub: Booting Linux Kernel... [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-53-generic (buildd@auburn) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #87-Ubuntu SMP Thu May 7 14:43:55 UTC 2015 (Ubuntu 3.13.0-53.87-generic 3.13.11-ckt19) [0.00] CPU: AArch64 Processor [500f] revision 0 [0.00] No earlyprintk arguments passed. [0.00] efi: Getting parameters from FDT: [0.00] EFI v2.40 by EDK II [0.00] efi: [0.00] psci: probing function IDs from device-tree [0.00] PERCPU: Embedded 11 pages/cpu @ffc03f9bb000 s16192 r8192 d20672 u45056 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258560 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=1aaf7ff5-f468-46de-bca4-960eaf01a7b4 ro earlyprintk console=ttyAMA0 [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.00] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) [0.00] software IO TLB [mem 0x73098000-0x77098000] (64MB) mapped at [ffc033098000-ffc037097fff] [0.00] Memory: 901200K/1048576K available (5750K kernel code, 587K rwdata, 2548K rodata, 315K init, 542K bss, 147376K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbc00e0 - 0xffbc01c0 (14 MB) [0.00] modules : 0xffbffc00 - 0xffc0 (64 MB) [0.00] memory : 0xffc0 - 0xffc04000 ( 1024 MB) [0.00] .init : 0xffc00089c000 - 0xffc0008eaf40 ( 316 kB) [0.00] .text : 0xffc8 - 0xffc00089b9b4 ( 8303 kB) [0.00] .data : 0xffc0008eb000 - 0xffc00097df68 ( 588 kB) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Hierarchical RCU implementation. [0.00] RCU dyntick-idle grace-period acceleration is enabled. [0.00] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1. [0.00] NR_IRQS:64 nr_irqs:64 0 [0.00] Architected cp15 timer(s) running at 50.00MHz (virt). [0.00] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns [0.00] Console: colour dummy device 80x25 [0.00] allocated 4194304 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.001040] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50) [0.001045] pid_max: default: 32768 minimum: 301 [0.001091] Security Framework initialized [0.001122] AppArmor: AppArmor initialized [0.001125] Yama: becoming mindful. [0.001153] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) [0.001156] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes) [0.001687] Initializing cgroup subsys memory [0.001697] Initializing cgroup subsys devices [0.001700] Initializing cgroup subsys freezer [0.001703] Initializing cgroup subsys blkio [0.001705] Initializing cgroup subsys perf_event [0.001710] Initializing cgroup subsys hugetlb [0.001827] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 1 counters available [0.001838] Remapping and enabling EFI services. [0.026754] Freed 0x202c000 bytes of EFI boot services memory [0.027456] Brought up 1 CPUs [0.027460] SMP: Total of 1 processors activated. [0.027684] devtmpfs: initialized [0.029312] EVM: security.selinux [0.029315] EVM: security.SMACK64 [0.029317] EVM: security.ima [0.029318] EVM: security.capability [0.029600] atomic64 test passed [0.029686] regulator-dummy: no parameters [0.029778] NET: Registered protocol family 16 [0.031266] vdso: 2 pages (1 code, 1 data) at base ffc0008f1000 [0.031297] hw-breakpoint: found 4 breakpoint and 4 watchpoint registers. [0.031373] Serial: AMBA PL011 UART driver [0.031426] 900.pl011: ttyAMA0 at MMIO 0x900 (irq = 33, base_baud = 0) is a PL011 rev1 [0.231224] console [ttyAMA0] enabled [0.234092] bio: create slab bio-0 at 0 [0.237192] vgaarb: loaded [0.239349] SCSI subsystem initialized [0.242252] NetLabel: Initializing [0.244336] NetLabel: domain hash size = 128 [0.247118] NetLabel: protocols = UNLABELED CIPSOv4 [0.250335] NetLabel: unlabeled traffic allowed by default [0.254016]
[Kernel-packages] [Bug 1448811] Re: Internal error: Oops: 9600004f [#41] SMP leaks unkillable processes
** Changed in: linux (Ubuntu) Status: Confirmed = 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/1448811 Title: Internal error: Oops: 964f [#41] SMP leaks unkillable processes Status in linux package in Ubuntu: Fix Released Bug description: We have an arm64 xgene system running 14.04.1 which leaks processes when the kernel oopses [928109.838289] Unable to handle kernel paging request at virtual address 42083b48a0 [928109.845776] pgd = ffc00a50b000 [928109.849254] [42083b48a0] *pgd=00420bb45003, *pmd=0042dd0fb003, *pte=00a000407272ffd3 [928109.857788] Internal error: Oops: 964f [#42] SMP [928109.862815] Modules linked in: 8021q garp stp mrp llc gpio_dwapb gpio_generic xgene_rng uio_pdrv_genirq uio ahci_xgene ahci_platform libahci xgene_enet [928109.876569] CPU: 5 PID: 11728 Comm: runtest.exe Tainted: G D 3.13.0-37-generic #64-Ubuntu [928109.885743] task: ffc2b013ac00 ti: ffc001884000 task.ti: ffc001884000 [928109.893281] PC is at __hyp_text_end+0x2230/0x3180 [928109.898052] LR is at pipe_read+0x23c/0x4d4 [928109.902219] pc : [ffc00060d230] lr : [ffc0001aea20] pstate: 2145 [928109.909672] sp : ffc001887cf0 [928109.913058] x29: ffc001887cf0 x28: ffc2c56a9000 [928109.918451] x27: ffc001887dc8 x26: 1000 [928109.923842] x25: ffc2c56a9000 x24: ffc001884000 [928109.929244] x23: 0001 x22: ffc0006269d8 [928109.934636] x21: ffc219e81cc0 x20: ffc001971518 [928109.940029] x19: x18: [928109.945420] x17: 003ce8e0 x16: 0001f4b0 [928109.950810] x15: x14: 65757274202c3130 [928109.956205] x13: 303030303030 x12: 66377830 [928109.961599] x11: 202c313137323030 x10: 3030 [928109.966993] x9 : 66377830202c6665 x8 : 38643078 [928109.972385] x7 : 302d202c30303030 x6 : 0042083b48a0 [928109.98] x5 : 1000 x4 : [928109.983174] x3 : 1d365e9f x2 : 1000 [928109.988566] x1 : ffc2c56a9030 x0 : 1000 [928109.993954] [928109.995527] Process runtest.exe (pid: 11728, stack limit = 0xffc001884058) [928110.002800] Stack: (0xffc001887cf0 to 0xffc001888000) [928110.008606] 7ce0: 01887da0 ffc0 001a5b50 ffc0 [928110.016829] 7d00: 01887dd8 ffc0 01887ec8 ffc0 01887ec8 ffc0 083b48c0 0042 [928110.025051] 7d20: 6000 0015 0112 003f [928110.033275] 7d40: 008ec000 ffc0 01884000 ffc0 6000 1000 [928110.041499] 7d60: 19e81d38 ffc2 19e81ce8 ffc2 d695cc00 ffc3 01884000 0007 [928110.049722] 7d80: 0001 9540 1000 01887dc8 ffc0 [928110.057946] 7da0: 01887e30 ffc0 001a6110 ffc0 d695cc00 ffc3 01884000 ffc0 [928110.066170] 7dc0: 083b48c0 0042 9540 d695cc00 ffc3 [928110.074393] 7de0: b013ac00 ffc2 [928110.082616] 7e00: 9540 [928110.090840] 7e20: 01887e80 ffc0 001a6c04 ffc0 [928110.099064] 7e40: d695cc00 ffc3 083b48c0 0042 0001 001467d8 [928110.107287] 7e60: 6000 0015 d695cc00 ffc3 [928110.115509] 7e80: 000849ec ffc0 [928110.123730] 7ea0: 000849ec ffc0 9540 [928110.131951] 7ec0: 000e2920 0010 083b48c0 0042 [928110.140172] 7ee0: 9540 [928110.148394] 7f00: 9540 0802a4e8 0042 003f 00053a08 [928110.156618] 7f20: 0801a000 0042 00324160 00324160 0010 [928110.164841] 7f40: 0a3f13d0 000a 0004f570 00277ff0 [928110.173071] 7f60: 08119490 0042 [928110.181302] 7f80: [928110.189527] 7fa0: 00324508 080bbcc0 0042 [928110.197756] 7fc0: 001467b8 08312c40 0042 001467d8 6000 [928110.205982] 7fe0: 0010 003f [928110.214204] Call trace: [928110.216736] [ffc00060d230] __hyp_text_end+0x2230/0x3180
[Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194
I'm going to mark this as invalid for the following reasons: - I reinstalled the system and the issue persisted. - I was unable to reproduce on another, identically configured system. - After removing one of the two DIMMs, the system is no longer seeing the problem. This all points to a localized hardware failure. ** Changed in: linux (Ubuntu) Status: Triaged = Invalid ** Changed in: linux (Ubuntu Vivid) Status: Triaged = Invalid -- 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in The Linux Kernel: Unknown Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Invalid Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1440536/+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 1411294] Re: kernel panic during MAAS fastpath install of Vivid images
I'm working on MAAS enablement for a system that will require a = 3.18 kernel and I've hit this issue in trusty. I'm obviously using custom images since trusty doesn't include a newer kernel - but I wonder if this won't be a problem with hwe-v images starting in 14.04.3. ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cloud-initramfs-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: cloud-initramfs-tools (Ubuntu Trusty) Status: New = 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/1411294 Title: kernel panic during MAAS fastpath install of Vivid images Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cloud-initramfs-tools source package in Trusty: Confirmed Status in linux source package in Trusty: Invalid Bug description: There appears to be an issue with the use of overlayfs in the image. See the attached screenshot for details. Immediately after that overlayfs error the kernel panics. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1411294/+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 1440536] Re: Oops __d_lookup+0x88/0x194
https://bugzilla.kernel.org/show_bug.cgi?id=96641 ** Bug watch added: Linux Kernel Bug Tracker #96641 http://bugzilla.kernel.org/show_bug.cgi?id=96641 ** Changed in: linux (Ubuntu Vivid) 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in The Linux Kernel: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1440536/+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 1438585] Re: no console when starting VM from cloud image
** Summary changed: - no console when starting VM from utopic cloud image + no console when starting VM from cloud image -- 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/1438585 Title: no console when starting VM from cloud image Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: In current arm64 utopic cloud image, the 'console=' parameter has been removed from grub config, and always resort to 'stdout' DT property which is setup from QEMU. Unfortunately parsing 'stdout' DT property is just merged to 3.19 kernel, so there is no console usable any more for arm64 utopic VM when booting via uefi/grub. SRU Justification: Impact: No console if arm64 Utopic based VM is booted from the cloud image. Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are cherry picked from 3.19 to Utopic, and the other one is backported by just dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can be booted with console. Testcase: Boot one arm64 Utopic VM via uefi/grub. 5ba2ee8 of: support passing console options with stdout-path 5c64126 of: add optional options parameter to of_find_node_by_path() 7507839 of: Add bindings for chosen node, stdout-path 54e15d7 of: correct of_console_check()'s return value 4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path a699dfd of: Create of_console_check() for selecting a console specified in /chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438585/+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 1366867] Re: PC is at ahci_enable_ahci+0x14/0x6c [libahci]
Sorry for the late reply, I wasn't subscribed to this bug. For firmware updates, you need to have a MyAPM account: https://myapm.apm.com/ If you have problems getting an account approved, feel free to contact me at dann.fraz...@canonical.com and I'll see if I can help out. -- 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/1366867 Title: PC is at ahci_enable_ahci+0x14/0x6c [libahci] Status in linux package in Ubuntu: Invalid Bug description: When attempting to use the 1.12.10 firmware with linux kernel versions 3.13.0-36.63 and above the system will not boot. SATA1 link 0 timeout SATA1 link 1 timeout AHCI1 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq pm only pmp fbss pio slum part ccc apst boh SATA2 spinup took 0 ms. SATA2 link 1 timeout AHCI2 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode flags: 64bit ncq pm only pmp fbss pio slum part ccc apst boh scanning bus for devices... Device 0: (4:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Found 1 device(s). 300 bytes read in 65 ms (3.9 KiB/s) ## Executing script at 400400 9361408 bytes read in 322 ms (27.7 MiB/s) 17697693 bytes read in 496 ms (34 MiB/s) 12756 bytes read in 53 ms (234.4 KiB/s) ## Booting kernel from Legacy Image at 400200 ... Image Name: kernel 3.13.0-36-generic Image Type: ARM Linux Kernel Image (uncompressed) Data Size:9361344 Bytes = 8.9 MiB Load Address: 0008 Entry Point: 0008 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 400400 ... Image Name: ramdisk 3.13.0-36-generic Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:17697629 Bytes = 16.9 MiB Load Address: Entry Point: Verifying Checksum ... OK ## Flattened Device Tree blob at 400300 Booting using the fdt blob at 0x00400300 Loading Kernel Image ... OK OK Loading Ramdisk to 43def1f000, end 43db5d ... OK Loading Device Tree to 004000ff9000, end 004000fff1d3 ... OK 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-36-generic (buildd@magic) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) ) #63-Ubuntu SMP Wed Sep 3 21:33:11 UTC 2014 (Ubuntu 3.13.0-36.63-generic 3.13.11.6) [0.00] CPU: AArch64 Processor [500f] revision 0 [0.00] PERCPU: Embedded 12 pages/cpu @ffc3fff79000 s17024 r8192 d23936 u49152 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4136960 [0.00] Kernel command line: console=ttyS0,115200n8 ro [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) [0.00] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) [0.00] software IO TLB [mem 0x43ec60-0x43f060] (64MB) mapped at [ffc3ec60-ffc3f05f] [0.00] Memory: 16429604K/16777216K available (5710K kernel code, 581K rwdata, 2536K rodata, 304K init, 538K bss, 347612K reserved) [0.00] Virtual kernel memory layout: [0.00] vmalloc : 0xff80 - 0xffbb (245759 MB) [0.00] vmemmap : 0xffbce000 - 0xffbcee00 ( 224 MB) [0.00] modules : 0xffbffc00 - 0xffc0 ( 64 MB) [0.00] memory : 0xffc0 - 0xffc4 ( 16384 MB) [0.00] .init : 0xffc00088f000 - 0xffc0008db280 ( 305 kB) [0.00] .text : 0xffc8 - 0xffc00088e984 ( 8251 kB) [0.00] .data : 0xffc0008dc000 - 0xffc00096d7c0 ( 582 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] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps every 2748779069440ns [0.00] Console: colour dummy device 80x25 [0.00] allocated 67108864 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.003078] Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50) [0.003083] pid_max: default: 32768 minimum: 301 [0.003125] Security Framework initialized
[Kernel-packages] [Bug 1441291] Re: support EFI rtc on arm64
** Changed in: linux (Ubuntu Trusty) Status: Confirmed = In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) = dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1441291 Title: support EFI rtc on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux source package in Trusty: In Progress Status in linux-lts-utopic source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux-lts-utopic source package in Utopic: Invalid Bug description: [Impact] ARM64 EFI platforms have no real time clock support. This can leave a system with a very out-of-date system clock. It can be somewhat mitigated by using NTP, but that still leaves issues in early boot (inaccurate last mount times, etc). [Test Case] if dmesg | grep -q 'rtc-efi: setting system clock'; then PASS else FAIL fi [Regression Risk] This enables a new driver only on ARM64, so the risk should be low to other platforms. The upstream patches do refactor the rtc-efi driver but, that driver was previously only compilable on ia64, which isn't supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441291/+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 1438585] Re: no console when starting VM from cloud image
** Attachment added: dmesg from verified utopic kernel https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438585/+attachment/4379116/+files/dmesg-utopic-verified.txt ** 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/1438585 Title: no console when starting VM from cloud image Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: In current arm64 utopic cloud image, the 'console=' parameter has been removed from grub config, and always resort to 'stdout' DT property which is setup from QEMU. Unfortunately parsing 'stdout' DT property is just merged to 3.19 kernel, so there is no console usable any more for arm64 utopic VM when booting via uefi/grub. SRU Justification: Impact: No console if arm64 Utopic based VM is booted from the cloud image. Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are cherry picked from 3.19 to Utopic, and the other one is backported by just dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can be booted with console. Testcase: Boot one arm64 Utopic VM via uefi/grub. 5ba2ee8 of: support passing console options with stdout-path 5c64126 of: add optional options parameter to of_find_node_by_path() 7507839 of: Add bindings for chosen node, stdout-path 54e15d7 of: correct of_console_check()'s return value 4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path a699dfd of: Create of_console_check() for selecting a console specified in /chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438585/+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 1441291] Re: support EFI rtc on arm64
dannf@ubuntu:~$ cat /proc/version Linux version 3.16.0-36-generic (buildd@beebe) (gcc version 4.9.1 (Ubuntu/Linaro 4.9.1-16ubuntu6) ) #48-Ubuntu SMP Tue Apr 14 20:18:23 UTC 2015 dannf@ubuntu:~$ if dmesg | grep -q 'rtc-efi: setting system clock'; then echo PASS; else echo FAIL; fi PASS ** 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/1441291 Title: support EFI rtc on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux source package in Trusty: In Progress Status in linux-lts-utopic source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux-lts-utopic source package in Utopic: Invalid Bug description: [Impact] ARM64 EFI platforms have no real time clock support. This can leave a system with a very out-of-date system clock. It can be somewhat mitigated by using NTP, but that still leaves issues in early boot (inaccurate last mount times, etc). [Test Case] if dmesg | grep -q 'rtc-efi: setting system clock'; then PASS else FAIL fi [Regression Risk] This enables a new driver only on ARM64, so the risk should be low to other platforms. The upstream patches do refactor the rtc-efi driver but, that driver was previously only compilable on ia64, which isn't supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441291/+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 1440536] Re: Oops __d_lookup+0x88/0x194
Tested w/ 4.0, still exists. -- 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in The Linux Kernel: Incomplete Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1440536/+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 1440536] Re: Oops __d_lookup+0x88/0x194
It seems like a corruption issue. The machine is sometimes usable for short periods after this errors occurs, but is otherwise deadlocked. I did go back to 3.19.0-4.4, and the problem is persisting. I also tried building a kernel from Linus' git tree and the problem is still there. My guess is that something changed outside of the kernel that is now triggering this bug. Perhaps it was the switch to systemd, or perhaps it is that I have a juju local provider deployment going on this system now - or a combination of the two. ** 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in linux package in Ubuntu: Confirmed Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440536/+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
Re: [Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194
On Mon, Apr 6, 2015 at 6:26 AM, Tim Gardner tim.gard...@canonical.com wrote: From what version did you upgrade ? It looks like 3.19.0-4.4. I'll downgrade to see if going back resolves the issue and, if so, try and bisect it down. -- 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in linux package in Ubuntu: Confirmed Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440536/+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 1441291] [NEW] support EFI rtc on arm64
Public bug reported: [Impact] ARM64 EFI platforms have no real time clock support. This can leave a system with a very out-of-date system clock. It can be somewhat mitigated by using NTP, but that still leaves issues in early boot (inaccurate last mount times, etc). [Test Case] if dmesg | grep -q 'rtc-efi: setting system clock'; then PASS else FAIL fi [Regression Risk] This enables a new driver only on ARM64, so the risk should be low to other platforms. The upstream patches do refactor the rtc-efi driver but, that driver was previously only compilable on ia64, which isn't supported by Ubuntu. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Affects: linux-lts-utopic (Ubuntu Utopic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released ** Changed in: linux (Ubuntu Utopic) Status: New = Confirmed ** Changed in: linux (Ubuntu Trusty) Status: New = Confirmed ** Also affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New = Confirmed ** Changed in: linux-lts-utopic (Ubuntu Utopic) Status: New = Invalid -- 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/1441291 Title: support EFI rtc on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: New Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in linux-lts-utopic source package in Utopic: Invalid Bug description: [Impact] ARM64 EFI platforms have no real time clock support. This can leave a system with a very out-of-date system clock. It can be somewhat mitigated by using NTP, but that still leaves issues in early boot (inaccurate last mount times, etc). [Test Case] if dmesg | grep -q 'rtc-efi: setting system clock'; then PASS else FAIL fi [Regression Risk] This enables a new driver only on ARM64, so the risk should be low to other platforms. The upstream patches do refactor the rtc-efi driver but, that driver was previously only compilable on ia64, which isn't supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441291/+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 1440536] [NEW] Oops __d_lookup+0x88/0x194
Public bug reported: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 third-party-packages 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in linux package in Ubuntu: New Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440536/+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 1438585] Re: no console when starting VM from utopic cloud image
** Changed in: linux (Ubuntu Trusty) Status: New = 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/1438585 Title: no console when starting VM from utopic cloud image Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: In current arm64 utopic cloud image, the 'console=' parameter has been removed from grub config, and always resort to 'stdout' DT property which is setup from QEMU. Unfortunately parsing 'stdout' DT property is just merged to 3.19 kernel, so there is no console usable any more for arm64 utopic VM when booting via uefi/grub. SRU Justification: Impact: No console if arm64 Utopic based VM is booted from the cloud image. Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are cherry picked from 3.19 to Utopic, and the other one is backported by just dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can be booted with console. Testcase: Boot one arm64 Utopic VM via uefi/grub. 5ba2ee8 of: support passing console options with stdout-path 5c64126 of: add optional options parameter to of_find_node_by_path() 7507839 of: Add bindings for chosen node, stdout-path 54e15d7 of: correct of_console_check()'s return value 4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path a699dfd of: Create of_console_check() for selecting a console specified in /chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438585/+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 1438585] Re: no console when starting VM from utopic cloud image
** Also affects: linux (Ubuntu Trusty) 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/1438585 Title: no console when starting VM from utopic cloud image Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: In current arm64 utopic cloud image, the 'console=' parameter has been removed from grub config, and always resort to 'stdout' DT property which is setup from QEMU. Unfortunately parsing 'stdout' DT property is just merged to 3.19 kernel, so there is no console usable any more for arm64 utopic VM when booting via uefi/grub. SRU Justification: Impact: No console if arm64 Utopic based VM is booted from the cloud image. Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are cherry picked from 3.19 to Utopic, and the other one is backported by just dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can be booted with console. Testcase: Boot one arm64 Utopic VM via uefi/grub. 5ba2ee8 of: support passing console options with stdout-path 5c64126 of: add optional options parameter to of_find_node_by_path() 7507839 of: Add bindings for chosen node, stdout-path 54e15d7 of: correct of_console_check()'s return value 4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path a699dfd of: Create of_console_check() for selecting a console specified in /chosen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438585/+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
