** Changed in: libdebian-installer (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To manage notifications
** Changed in: libdebian-installer (Ubuntu Utopic)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To manage notifications
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438318
Title:
[arm64] tg3 NIC causing kernel
On Thu, Mar 26, 2015 at 11:42 AM, Brian Murray br...@ubuntu.com wrote:
Which efibootmgr SRU is this blocked on?
0.5.4-7ubuntu1.1:
http://launchpadlibrarian.net/201094067/efibootmgr_0.5.4-7ubuntu1_0.5.4-7ubuntu1.1.diff.gz
-dann
--
You received this bug notification because you are a member
I've prepared a git branch against Debian's mysql-5.6 tree w/ fixes that pass
my test on ARM64:
https://github.com/dannf/mysql-5.6.git
I should note that this was really a mechanical port w/ blackbox
testing. I'm not an expert in the semantics at this level - and the code
here had diverged
I've prepared a git branch against Debian's mysql-5.6 tree w/ fixes that pass
my test on ARM64:
https://github.com/dannf/mysql-5.6.git
I should note that this was really a mechanical port w/ blackbox
testing. I'm not an expert in the semantics at this level - and the code
here had diverged
Upstream bug: https://github.com/go-yaml/yaml/issues/85
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431850
Title:
test failures on arm64, ppc64el and powerpc
To manage notifications about this
Public bug reported:
I've verified that the following MariaDB issue also impacts MySQL:
https://mariadb.atlassian.net/browse/MDEV-6615
[Impact]
Data corruption on arm64 (and maybe ppc64el?)
[Test Case]
Reproducibility varies across SoCs but, at least on one SoC, it reliably fails
within
** Patch added: mysql-5.6-vivid.patch
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+attachment/4332652/+files/mysql-5.6-vivid.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I've verified that the following MariaDB issue also impacts MySQL:
https://mariadb.atlassian.net/browse/MDEV-6615
[Impact]
Data corruption on arm64 (and maybe ppc64el?)
[Test Case]
Reproducibility varies across SoCs but, at least on one SoC, it reliably fails
within
** Patch added: mysql-5.6-vivid.patch
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/+attachment/4332652/+files/mysql-5.6-vivid.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Also affects: mysql-5.6 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: mysql-5.6 (Ubuntu Vivid)
Importance: Critical
Status: Confirmed
** Also affects: mysql-5.6 (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: mysql-5.6
** Also affects: mysql-5.6 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: mysql-5.6 (Ubuntu Vivid)
Importance: Critical
Status: Confirmed
** Also affects: mysql-5.6 (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: mysql-5.6
** Bug watch added: MySQL Bug System #76135
http://bugs.mysql.com/bug.php?id=76135
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=76135
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Bug watch added: MySQL Bug System #76135
http://bugs.mysql.com/bug.php?id=76135
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=76135
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: mariadb-5.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mariadb-10.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: mariadb-5.5 (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
** Also affects: mariadb-5.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mariadb-10.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently the fix I've proposed here caused regressions in MariaDB and was
reworked:
https://mariadb.atlassian.net/browse/MDEV-7026
Unfortunately, the reworking reintroduces the problem on arm64:
https://mariadb.atlassian.net/browse/MDEV-7658
--
You received this bug notification because
Apparently the fix I've proposed here caused regressions in MariaDB and was
reworked:
https://mariadb.atlassian.net/browse/MDEV-7026
Unfortunately, the reworking reintroduces the problem on arm64:
https://mariadb.atlassian.net/browse/MDEV-7658
--
You received this bug notification because
You do, thanks.
** Changed in: vnc4 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425753
Title:
freeze exception to fix FTBFS on arm64, powerpc ppc64el
To
Public bug reported:
I'm requesting a freeze exception for vnc4 4.1.1+xorg4.3.0-37.3ubuntu2 to:
1) Fix a FTBFS on existing supported architecture powerpc
2) Introduce support for arm64 (tested) and ppc64el (untested)
3) Support using a URI (debbugs #769891)
4) Fix broken alternatives handling
Fix verified on a mustang board. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426043
Title:
kernel 3.13.0-46.75 fails to boot on arm64
To manage notifications about this bug go to:
** No longer affects: mariadb-5.5 (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage notifications about this bug go
** No longer affects: mariadb-5.5 (Ubuntu Vivid)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage notifications about this bug go to:
On Thu, Mar 26, 2015 at 12:06 PM, Brian Murray br...@ubuntu.com wrote:
On Thu, Mar 26, 2015 at 05:54:09PM -, dann frazier wrote:
On Thu, Mar 26, 2015 at 11:42 AM, Brian Murray br...@ubuntu.com wrote:
Which efibootmgr SRU is this blocked on?
0.5.4-7ubuntu1.1:
http
** Changed in: efibootmgr (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To manage notifications about this bug
-efi (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: efibootmgr (Ubuntu Trusty)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Triaged
** Affects: grub-installer (Ubuntu Trusty)
Importance: Undecided
Assignee: dann frazier
** Changed in: partman-efi (Ubuntu Trusty)
Status: Confirmed = In Progress
** Changed in: partman-efi (Ubuntu Utopic)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding a proposed backport patch for grub2. Note that this is blocked on
the efibootmgr SRU, otherwise it would make grub-efi-arm64-bin
uninstallable.
** Patch added: proposed patch for grub2
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
[
am running Lubuntu.
Yours sincerely,
Brandon Camilleri
*Linked* in Profile http://mt.linkedin.com/in/brandonleecamilleri
On 25 April 2015 at 16:32, dann frazier dann.fraz...@canonical.com
wrote:
@Brandon: would you mind checking your sed binary and doing a memory
test (https
@Brandon: would you mind checking your sed binary and doing a memory
test (https://help.ubuntu.com/community/MemoryTest) and reporting back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447295
I'm unable to reproduce. From the terminal log, I see that it is
reporting an illegal instruction in sed:
/var/lib/dpkg/info/grub-pc.postinst: line 368: 22257 Illegal instruction
sed -i -e 's/^\(GRUB_TIMEOUT=\)\([0-9][0-9]*\)/\1\2/'
$tmp_default_grub
Which is strange indeed. Is this
** Changed in: grub2 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447295
Title:
package grub-pc 2.02~beta2-9ubuntu1.1 failed to install/upgrade:
Thanks for testing and catching this Sven! I've uploaded an updated
grub2-signed, would you mind testing it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448811
Title:
Internal
@Brandon: Would you mind opening a terminal and running md5sum /bin/sed and
providing the output here?
Also - can you confirm whether or not this problem persists? Does dist-upgrade
continue to report this error?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
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
I am changing this back to verification-done even though bug 1447295
has not yet been root caused. My justification is:
1) I attempted and failed to reproduce the possible regression reported in
bug 1447295.
2) The failure mode in 1447295 looks more consistent with a bug in sed or
(more
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448811
Title:
Internal error: Oops: 964f [#41] SMP leaks unkillable
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
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438585
Title:
no console
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** 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
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
** Tags removed: verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To manage
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
Tested w/ 4.0, still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440536
Title:
Oops __d_lookup+0x88/0x194
To manage notifications about this bug go to:
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
** Changed in: grub2 (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To manage notifications about this bug go
** Tags removed: verification-needed
** Tags added: verification-done-utopic verification-needed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435663
Title:
arm64/efi support
To manage
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
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 |
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
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438585
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438585
Title:
no console when starting VM from utopic cloud image
To manage
Assignee: dann frazier (dannf)
Status: Confirmed
** Tags: hs-arm64
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New = Confirmed
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441876
Title:
arm64 efi stub support
To manage notifications about this
** Description changed:
- 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.
+ [Impact]
+ overlayfs support doesn't work with kernels 3.18 which will, for example,
break MAAS
** Description changed:
- 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.
+ [Impact]
+ overlayfs support doesn't work with kernels 3.18 which will, for example,
break MAAS
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: cloud-initramfs-tools (Ubuntu Trusty)
Assignee: (unassigned) = dann frazier (dannf
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: cloud-initramfs-tools (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: cloud-initramfs-tools (Ubuntu Trusty)
Assignee: (unassigned) = dann frazier (dannf
I've pushed changes for the grub2 package here:
git://git.launchpad.net/~dannf/grub2
I've pushed changes for the grub2-signed package to
lp:~dannf/ubuntu/wily/grub2-signed/arm64-support.
** Changed in: grub2-signed (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug
Public bug reported:
I'd like to request that Ubuntu start producing an arm64 signed GRUB
binary, like we currently do for x86. While the securemode EFI story
isn't completely fleshed out for ARM systems yet - we don't know what
keys will be shipped by OEMS for example, an Ubuntu-signed GRUB
Public bug reported:
[Impact]
* The reboot command fails to reboot the system. Instead it hangs
here:
[ OK ] Stopped Remount Root and Kernel File Systems.
Stopping Remount Root and Kernel File Systems...
[ OK ] Reached target Shutdown.
[ 38.876665] reboot: Restarting system
*
Reopening as this has now been seen on 2 other systems.
** Changed in: linux (Ubuntu Vivid)
Status: Invalid = Confirmed
** Changed in: linux (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- mustang board doesn't shutdown/reboot
+ mustang board doesn't reboot
** Description changed:
[Impact]
- * The reboot command fails to reboot the system. Instead it hangs
+ * The reboot command fails to reboot the system. Instead it hangs
here:
[ OK ]
Restricting to just the reboot issue as it is more pressing, and
because poweroff will take a longer time to verify (needs fw update).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463211
Title:
** Description changed:
- We need to add support to curtin for supporting UEFI-based ARM64
- systems.
+ [Impact]
+ Curtin doesn't support UEFI-based ARM64 systems.
+
+ [Test Case]
+ Use Curtin to install an ARM64-UEFI system. We did this testing with MAAS
incorporating this MP:
+
** Description changed:
- We need to add support to curtin for supporting UEFI-based ARM64
- systems.
+ [Impact]
+ Curtin doesn't support UEFI-based ARM64 systems.
+
+ [Test Case]
+ Use Curtin to install an ARM64-UEFI system. We did this testing with MAAS
incorporating this MP:
+
** Changed in: crash (Ubuntu Trusty)
Status: New = In Progress
** Changed in: crash (Ubuntu Utopic)
Status: New = In Progress
** Changed in: crash (Ubuntu Vivid)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
- This crash was submitted upstream and a fix was already present, but it
- didn't land until the 3.19 kernel. This bug is to track getting that fix
- into trusty and utopic.
+ [Impact]
+ System panics every few hours under constant network load
- Unable to handle
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Assignee: Craig Magina (craig.magina)
Status: In Progress
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After testing with the proposed backport[1], I was able to run the iperf
test overnight on a trusty kernel w/o any crashes.
[1]http://kernel.ubuntu.com/git/ming/ubuntu-utopic.git/commit/?h=arm64
-net-backportid=d46456e3ed9153e743f2add6e01d06c56eb2ceb7
** Changed in: linux (Ubuntu Trusty)
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433290
Title:
xgene-enet: doesn't work at 100Mbit
To manage notifications about this
I am unable to reproduce - see attached console log. Note that I am running the
latest ROM version available from HP:
http://h17007.www1.hp.com/us/en/enterprise/servers/products/moonshot/component-pack/index.aspx
I suggest upgrading your firmware, as I believe there are changes to the
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463211
Title:
mustang board doesn't reboot
To manage notifications
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1468215
Title:
Kernel boot stuck on ARMv8 Moonshot after update kernel
** Also affects: crash (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: crash (Ubuntu Trusty)
Status: New = In Progress
** Changed in: crash (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Patch added: trusty debdiff
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1460941/+attachment/4418859/+files/crash-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460941
** Patch added: utopic debdiff
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1460941/+attachment/4418860/+files/crash-utopic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460941
** Patch added: vivid debdiff
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1460941/+attachment/4418861/+files/crash-vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460941
** Patch added: proposed trusty SRU debdiff
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1466686/+attachment/4418862/+files/crash-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mysql-5.6 (Ubuntu Vivid)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Also affects: crash (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: crash (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: crash (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: crash (Ubuntu Vivid)
** Also affects: crash (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: crash (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: crash (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: crash (Ubuntu Utopic)
** Changed in: mysql-5.6 (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Changed in: mysql-5.6 (Ubuntu Trusty)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage notifications about
** Changed in: mysql-5.6 (Ubuntu Utopic)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage
** Changed in: mysql-5.6 (Ubuntu Utopic)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage notifications about this
I can't confirm that this is 100% the same issue since the backtrace
isn't identical, but I was able to hit the following panic on trusty's
3.13 just by running iperf to another system for a few hours:
[ 2613.269450] BUG: Bad page state in process iperf pfn:41d5c57
[ 2613.275172]
Resolved for wily w/ Debian sync of upstream 7.1.1.
** Changed in: crash (Ubuntu Wily)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460942
Title:
crash:
Resolved for wily w/ Debian sync of upstream 7.1.1.
** Changed in: crash (Ubuntu Wily)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460941
Title:
arm64: crash:
** Also affects: mysql-5.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427406
Title:
data corruption on arm64
To manage notifications about
501 - 600 of 3498 matches
Mail list logo
