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
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
** 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
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
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
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
**
** 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
** 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
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
** 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
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
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
** 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
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
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.
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
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
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
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
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
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.
**
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
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.
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
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
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:
** 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”
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:
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
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.
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
** 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
** 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
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)
** 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
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
** 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
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
** 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
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
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
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.
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
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
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]
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
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.
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
** 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
** 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
** 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
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:
** 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.
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
** 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
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) )
** 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
** 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
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
** 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.
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
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
** 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.
]
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
** 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.
** 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.
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
** 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.
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
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:
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:
** 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.
** 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.
** 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
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
** 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.
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.
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.
** 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
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:
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
[
@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:
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
** 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
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
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
** 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:
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 Kernel
Packages, which is subscribed to linux-lts-utopic
** 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
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
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
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
** 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
** 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
1 - 100 of 1616 matches
Mail list logo
