This still happens with 8.10. I will post more details when I have them
but on resume from suspend my CPU is at 90% + with kacpi_notify and
kacpid spinning at 45% each.
--
kacpid constantly using 80-95% CPU on pentium D dual core
https://bugs.launchpad.net/bugs/82423
You received this bug
Public bug reported:
Binary package hint: gnome-panel
Launch Screens and Graphics from the System - Administration menu
fails.
ProblemType: Bug
Architecture: i386
Date: Mon Oct 1 11:10:43 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-panel
NonfreeKernelModules: vmnet vmblock
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/9622021/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/9622022/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/9622023/ProcStatus.txt
--
Trying to run
Public bug reported:
apt-get install lttng-tools
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: lttng-modules-dkms 2.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
NonfreeKernelModules: prl_fs_freeze prl_eth prl_fs
Public bug reported:
Trying to install perf.
sudo apt-get install linux-base linux-tools-common
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973590
Title:
package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/perf', which is also in package
Defintely concur with comment #3. I updated this morning, having left my
system alone for a few weeks, and immediately noticed this (broken)
behaviour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not noticed on other architectures as I am only testing against AArch64
at the moment. The failure was with the stock kernel that comes with the
vivid cloud image (3.19.0-9-generic). I had been building and using
3.19.1 on Trusty (AArch64 again) for about 3 days and hadn't noticed the
failure
I have seen this oops twice; I didn't report the issue first time round
as the machine I was using had been powered down and I was unable to
collect any logs. I happened to notice the stacktrace in my serial
console window so I tried again and saw the issue again (and raised this
bug). However, I
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348908/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348904/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348903/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348906/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348905/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348907/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
The appport-collect I just did was from the same machine, but a
different cloud image deployment (current/ 18-Mar-2015 06:05) . The
recent attachments may/may not be useful to the original bug report.
But if you look at the dmesg attachment you can see there is a different
(and new) stacktrace.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1433183/+attachment/4348909/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Tags added: apport-collected
** Description changed:
I was installing OpenStack using devstack/stack.sh and noticed that at
some point a `pip install' had failed. I later untarred
linux-3.19.1.tar.xz and get the same (or similar) kernel backtrace.
ProblemType:
Public bug reported:
I was installing OpenStack using devstack/stack.sh and noticed that at
some point a `pip install' had failed. I later untarred
linux-3.19.1.tar.xz and get the same (or similar) kernel backtrace.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package:
I will try and reproduce - but this machine is automatically deployed
and I have since destroyed it. Please bear with me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433183
Title:
Kernel oops
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380592/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446658
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380593/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380592/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Yes, the kernel is 3.19.2. I realised I was running a later version than
stock just after I submitted the report. I am deploying a fresh cloud
image onto a new machine and will double-check that it still happens
(but suspecting not). BTW: do you run the tests in a diferent way than
my 'for' loop?
I just installed the following cloud image onto an Applied Micro X-Gene
board:
http://cloud-images.ubuntu.com/trusty/20150420.1/trusty-server-
cloudimg-arm64-disk1.img
Running the tests in the same way:
# for i in /usr/bin/lxc-test-*; do $i || touch /tmp/$(basename
$i).failed; done
I see the
Public bug reported:
Running lxc-test-apparmor fails on aarch64 (arm64) systems.
The following files which are listed in files_to_deny[] in
src/tests/aa.c:
/sys/kernel/uevent_helper
/proc/sys/kernel/sysrq
are not denied, but should be.
Perhaps I should be changing the apparmor profile
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380593/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380595/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380594/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
Running lxc-test-apparmor fails on aarch64 (arm64) systems.
The following files which are listed in files_to_deny[] in
src/tests/aa.c:
/sys/kernel/uevent_helper
/proc/sys/kernel/sysrq
are not denied, but should be.
Perhaps I should be changing the apparmor profile
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380595/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446658
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1446658/+attachment/4380594/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at:
http://images.linuxcontainers.org/images/ubuntu/trusty/
I don't see a directory for arm64 (or aarch64) so that explains why lxc-
test-usernic fails -- there is no arm64 image to download.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And based on my comment in #14 the tests that I said currently fail:
lxc-test-unpriv
lxc-test-autostart
lxc-test-usernic
are also trying to download an arm64 image that, AFAICT at the time of
writing, does not exist.
So, given that lxc-test-apparmor does work on my trusty install:
Error output from the three tests that fail:
root@linaro-test:/tmp/lxc# id
uid=0(root) gid=0(root) groups=0(root)
root@linaro-test:/tmp/lxc# lxc-test-unpriv
Removing user `lxcunpriv' ...
Warning: group `lxcunpriv' has no
I also ran the tests using the debian/tests/exercise script:
SUMMARY: pass=21, fail=4, ignored=0
root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# ./exercise
PASS: lxc-tests: /usr/bin/lxc-test-apparmor
PASS: lxc-tests: /usr/bin/lxc-test-attach
FAIL: lxc-tests: /usr/bin/lxc-test-autostart
Regarding access to images.linuxcontainers.org - I believe I can see
this from my test machine:
root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# dig +short
images.linuxcontainers.org
rproxy.stgraber.org.
192.99.34.219
root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# dig +short -x
I believe there is also GPG connectivity:
root@linaro-test:/home/ubuntu/lxc-1.0.7/debian/tests# gpg --search-keys
andrew.iain.mcderm...@gmail.com
gpg: searching for andrew.iain.mcderm...@gmail.com from hkp server
keys.gnupg.net
(1) Andrew McDermott andrew.iain.mcderm...@gmail.com
Public bug reported:
Kernel crash whilst building new kernel:
Steps to reproduce:
wget https://www.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc2.tar.xz
tar xf linux-4.1-rc2.tar.xz
cd linux-4.1-rc2/
make mrproper
make olddefconfig
make -j20
I noticed that the output from the build had
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392220/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452293
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392221/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392219/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452293
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392240/+files/UdevDb.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392236/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452293
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/439/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452293
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392223/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452293
Title:
apport information
** Description changed:
Kernel crash whilst building new kernel:
Steps to reproduce:
wget https://www.kernel.org/pub/linux/kernel/v4.x/testing/linux-4.1-rc2.tar.xz
tar xf linux-4.1-rc2.tar.xz
cd linux-4.1-rc2/
make mrproper
make olddefconfig
make -j20
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392238/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452293
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1452293/+attachment/4392237/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was going straight from 3.19 (ie., vivid) to 4-1-rc2 so don't know if
it is applicable to just that version. I would be surprised if it was.
Regarding booting into utopic - I can try but it will be a while before
I can unload my machine to put utopic back.
--
You received this bug
This was crashing with 3.19 (i.e., vivid's kernel).
I wanted to pick up most of vivid's kernel config and initiated my build
on 3.19 with `make olddefconfig' .
I briefly tried with utopic and didn't see an issue - but take that with
a pinch of salt as I only did one run and wanted to report
Public bug reported:
I did a fresh install of a trusty cloud image to an applied micro X-Gene
today and post the installation (and login) I did:
apt-get update
apt-get dist-upgrade
and noticed the following:
ubuntu@linaro-test:devstack$ sudo apt-get dist-upgrade
Reading package lists... Done
This is no longer happening on stock kernels.
** Changed in: lxc (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/1446658
Title:
lxc-test-apparmor fails on
This is no longer happening on stock kernels.
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1446658
Title:
lxc-test-apparmor
** Changed in: juju-core
Milestone: None => 1.24.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
when
Pending RB: http://reviews.vapour.ws/r/3027/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
when deploying with
** Changed in: juju-core/1.25
Assignee: (unassigned) => Andrew McDermott (frobware)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully config
I can see this same issue on amd64.
ubuntu@maas-node2:~$ uname -a
Linux maas-node2 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@maas-node2:~$ lsb_release -cs
wily
And, having bootstrapped a node, I see the following:
ubuntu@maas-node2:~$
Will look at the patch. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
when deploying with wily 4.2 kernel
I see in comment #33 that the bug became invalid and reassigned.
However, it doesn't explain the behaviour I previously saw in comment
#15 where pinging a gateway interface appeared to lock up the machine -
there was no other changes made to /e/n/i in that case.
--
You received this bug
** Changed in: juju-core/1.25
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
** Changed in: juju-core
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1496972
Title:
juju bootstrap fails to successfully configure the bridge juju-br0
>From a Juju perspective we need this in trusty too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590104
Title:
network config from datasource overrides network config from system
To manage
I was trying to do something very similar for Juju - when the machine
boots we rewrite /etc/network/interfaces to add bridges for active
interfaces to support container networking.
Our sequence is:
$ ifdown -a
$ transform --in-place /etc/network/interfaces
$ ifup -a
and with bonds
If this is only happens with a bond then it's possible you are running
into:
https://bugs.launchpad.net/juju-core/+bug/1594855
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590052
Title:
juju
To clarify, my "transform" script just bridges active interfaces.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269921
Title:
networking services restart hangs due to missing
*** This bug is a duplicate of bug 1594855 ***
https://bugs.launchpad.net/bugs/1594855
Closing this as it is bond related and fixed by:
https://bugs.launchpad.net/juju-core/+bug/1594855
** This bug has been marked a duplicate of bug 1594855
MAAS provider bridge script on trusty does not
*** This bug is a duplicate of bug 1594855 ***
https://bugs.launchpad.net/bugs/1594855
The fix for:
https://bugs.launchpad.net/juju-core/+bug/1594855
will be in juju-2.0-beta10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this fix should be back ported to trusty so that we can
eventually install MAAS in a LXD environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518440
Title:
tgt fails to install in
I think this fix should be back ported to trusty so that we can
eventually install MAAS in a LXD environment.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1518440
Title:
tgt fails
The Juju bridge script, when creating the bridge device, generally
leaves all iface options as it found them.
For example:
auto eth1.16
iface eth1.16 inet static
address 10.245.184.100/24
vlan-raw-device eth1
mtu 1500
vlan_id 16
becomes the following:
iface eth1.16 inet manual
I tripped over this again today - will this be released or back-ported
to xenial soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590104
Title:
network config from datasource overrides network
3
> dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
> dmi.chassis.version: To Be Filled By O.E.M.
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:
> svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:
> rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:
&g
Amy update on when this will land in the archives?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574437
Title:
valgrind crashes on programs linked to openssl
To manage notifications about this
Public bug reported:
Since I started using IPv6 I noticed the following kernel error:
Thu Aug 18 15:05:01 2016] : hw csum failure
[Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P
OE 4.4.0-34-generic #53-Ubuntu
[Thu Aug 18 15:05:01 2016] Hardware name:
I mentioned that it repeats - here's the uptime to get a feeling of the
frequency:
$ uptime
13:51:59 up 1 day, 4:17, 2 users, load average: 0.40, 0.67, 0.71
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I only noticed because I had been experimenting with setting up IPv6
support for Juju. I enabled IPv6 on my router, then insisted that "eth0"
got an IP address in ENI and only then did I notice the messages. This
has only been a recent experiment so no evidence for whether this
happened as part of
Currently running:
$ uname -a
Linux spicy 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
Will report back tomorrow with a finding either way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And for completness:
https://github.com/dimitern/juju/commit/60e89f1d6cb02f3f0f9f36dbf8e3156ad4e9f7e8
that tree has, as a PoC, support for returning hostname that will work
with nss-juju.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@2-xtian - if you're testing on MAAS 2.0 then I suspect you're seeing
perfectly working DNS for hosts and their containers. Bootstrap across
AWS, GCE, and in particular Azure to see the issues on the public
clouds.
Note: we are also proposing to land the following as an additional
solution for
If we use manage_etc_hosts: "true" then we will get:
127.0.1.1 vmhost.home vmhost
(for example).
I'm concerned about how well charms would hold out if they were always
using localhost-esque addresses.
For the LXD container case also take a look at:
Running:
$ uname -a
Linux spicy 4.8.0-040800rc3-generic #201608212032 SMP Mon Aug 22 00:34:39 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
$ uptime
08:18:06 up 1 day, 15:40, 2 users, load average: 0.60, 0.80, 2.73
$ dmesg -T | grep 'hw csum failure' | wc -l
0
Marking this as fixed upstream.
**
82 matches
Mail list logo