[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-07-06 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.0.0-4.6 --- linux (4.0.0-4.6) wily; urgency=low [ Andy Whitcroft ] * Release Tracking Bug - LP: #1470233 * rebase to mainline v4.0.7 [ Jay Vosburgh ] * SAUCE: fan: Proof of concept implementation (v2) - LP: #1439706 *

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-06-18 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New = Fix Released ** Changed in: linux (Ubuntu Vivid) Importance: Undecided = Medium ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) = Andy

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-04-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.13.0-51.84 --- linux (3.13.0-51.84) trusty; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1444141 * Merged back Ubuntu-3.13.0-49.83 security release linux (3.13.0-50.82) trusty; urgency=low [ Brad Figg ] *

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-04-29 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.16.0-36.48 --- linux (3.16.0-36.48) utopic; urgency=low [ Luis Henriques ] * Release Tracking Bug - LP: #1443946 * Merged back Ubuntu-3.16.0-34.47 security release linux (3.16.0-35.46) utopic; urgency=low [ Brad Figg ] *

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-04-28 Thread Luis Henriques
I've verified that the config files used to build the Utopic and Trusty kernels currently in proposed (3.16.0-36.48 and 3.13.0-51.84) contain CONFIG_DEFAULT_MMAP_MIN_ADDR set to 32768. I'm thus tagging this bug as verified. ** Tags removed: verification-needed-trusty verification-needed-utopic

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-04-17 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If verification is not done by 5 working days from

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-04-17 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- utopic' to 'verification-done-utopic'. If verification is not done by 5 working days from

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-04-01 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 3.19.0-11.11 --- linux (3.19.0-11.11) vivid; urgency=low [ Andy Whitcroft ] * [Config] add nvme to linux-virtual as this is now used in GCE to expose disks - LP: #1415580 * [Packaging] module-inclusion -- commonise copy code

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-03-31 Thread Brad Figg
** Changed in: linux (Ubuntu Trusty) Status: In Progress = Fix Committed ** Changed in: linux (Ubuntu Utopic) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-03-26 Thread Andy Whitcroft
** Changed in: linux (Ubuntu) Status: Confirmed = In Progress ** 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 Ubuntu

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-03-26 Thread Andy Whitcroft
** Description changed: Attempting to run 32bit binaries on arm64 triggers applications to be - Killed, as the CONFIG_DEFAULT_MMAP_MIN_ADDR used on arm64 is not valid - on armhf. While this can be overriden via sysctl, the default should be + Killed, as the CONFIG_DEFAULT_MMAP_MIN_ADDR used on

[Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu) Milestone: ubuntu-15.02 = ubuntu-15.03 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418140 Title: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64