The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
That kernel is still useless to me...
So I went looking a bit closer at your test kernels and it looks like
the problem is the config you're using, they simply lack PPPoE support
entirely...
root@sateda:~# grep -i pppoe /boot/config-3.7.0-030700rc5-generic
root@sateda:~# grep -i pppoe
That kernel still doesn't have PPPoE support in its config...
--
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/1251946
Title:
Network related kernel panic on Atom 64bit system using saucy
** Changed in: linux (Ubuntu)
Milestone: ubuntu-13.07 = ubuntu-13.09
--
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/1066435
Title:
powerpc: Fixing recursive fault but reboot is
Just reporting what I said on IRC, this kernel gives me a pretty similar
behaviour to the previous one, that's, it hangs at boot around the time
apparmor/networking loads and 1/3 times I get a kernel panic:
http://paste.ubuntu.com/6251449/
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Milestone: ubuntu-13.10 = saucy-updates
--
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/1066435
Title:
powerpc: Fixing recursive fault but reboot is
Yep, I'm fine with that. I had little hope this would be fixed for S and
I wasn't planning on running S for very long on that board anyway, so T
is fine for me.
** Also affects: linux (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance:
Public bug reported:
I can't report this through ubuntu-bug as the system is a firewall with
restricted connectivity and the kernel bug prevents me from using the
system for more than a couple minutes anyway.
I recently deployed the saucy kernel on that precise system, after the
first reboot
Moving to Confirmed to make the bot happy, I believe all immediately
useful information is above, let me know if you need more.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
I tried the current -proposed kernel which seems considerably more
reliable, instead of panicing within a couple of minutes from the boot
it now does within 30min or so, current panic message is:
[ 1407.957715] [ cut here ]
[ 1407.962346] Kernel BUG at 815e1310
And same thing reproduced after just a few seconds on the current 3.12
kernel:
[ 54.047386] [ cut here ]
[ 54.052018] Kernel BUG at 81607e40 [verbose debug info unavailable]
[ 54.058985] invalid opcode: [#1] SMP
[ 54.063118] Modules linked in:
Same thing on a 3.8 kernel:
[ 151.530274] [ cut here ]
[ 151.534897] Kernel BUG at 815be3a8 [verbose debug info unavailable]
[ 151.541849] invalid opcode: [#1] SMP
[ 151.545978] Modules linked in: authenc(F) esp6(F) xfrm6_mode_transport(F)
ipcomp6(F)
And just as I was typing that, Andy's kernel paniced, here's the dump:
[ 580.009012] [ cut here ]
[ 580.013637] kernel BUG at
/home/apw/build/ubuntu-saucy/ubuntu-saucy/net/core/skbuff.c:1059!
[ 580.021989] invalid opcode: [#1] SMP
[ 580.026133] Modules linked
I've been running the standard backported 3.5 kernel for an hour without
getting a panic.
I'm currently running a 3.11 debug kernel from Andy, once that one
panics (probably in the next hour), I'll then try the 3.6 and 3.7 you
linked above to try and figure out when the issue was introduced.
--
It's now been 45min without a panic using the 3.6 mainline build, so
considering that one good and moving on to 3.7.
--
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/1251946
Title:
And it's now been over 30 minutes on 3.7 mainline still without any
crash.
Now getting the 3.8 mainline to confirm that one gives the same panic as
the Ubuntu 3.8 did.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like the issue appeared with the 3.8 kernel, just a bit over two
minutes after booting the mainline 3.8 kernel:
[ 127.201762] [ cut here ]
[ 127.206379] Kernel BUG at 815cca98 [verbose debug info unavailable]
[ 127.213331] invalid opcode: [#1] SMP
[
rc4 is affected:
[ 76.048846] [ cut here ]
[ 76.053467] Kernel BUG at 815cf5b8 [verbose debug info unavailable]
[ 76.060419] invalid opcode: [#1] SMP
[ 76.064549] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6
xfrm6_tunnel tunnel6
and rc2 is also affected:
[ 60.661389] [ cut here ]
[ 60.666011] Kernel BUG at 815cc9e8 [verbose debug info unavailable]
[ 60.672961] invalid opcode: [#1] SMP
[ 60.677091] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6
xfrm6_tunnel
and same goes for rc1:
[ 80.428925] [ cut here ]
[ 80.433548] Kernel BUG at 815cc5d8 [verbose debug info unavailable]
[ 80.440501] invalid opcode: [#1] SMP
[ 80.444637] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6
xfrm6_tunnel tunnel6
That kernel panics:
[ 65.076034] [ cut here ]
[ 65.080663] Kernel BUG at 81604508 [verbose debug info unavailable]
No luck with that one either:
[ 136.619649] [ cut here ]
[ 136.624273] Kernel BUG at 81604508 [verbose debug info unavailable]
[ 136.631238] invalid opcode: [#1] SMP
[ 136.635382] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6
xfrm6_tunnel
Hmm, is there actually any difference between those two kernels? the
uname in the panic appears identical.
--
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/1251946
Title:
Network related
Public bug reported:
When booting under secureboot and using a signed kernel, it's expected
that all modules shipped alongside the kernel should validate and load
successfully without tainting the kernel.
Unfortunately it doesn't seem to always be the case. Looking through my
kernel logs, I see:
Attaching an older kernel log which contains the examples mentioned in
the report.
** Attachment added: kern.log.1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+attachment/3913419/+files/kern.log.1
--
You received this bug notification because you are a member of Kernel
Sorry I didn't get back to you earlier, I needed reliable internet the
past few days. I'm doing a test run now.
--
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/1251946
Title:
Network
Same thing as your previous kernel, PPPoE doesn't work so my machine is
essentially useless and the panicing code path doesn't get exercised. So
the result is no idea.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I've been trying to use the generic kernel with my wandboard (based on a
freescale imx6) as it's supposed to be working properly.
Using the Ubuntu generic kernel, I usually get a successful boot very shortly
followed by a hang.
The hang is: http://paste.ubuntu.com/6216221
There's no chance I can run apport on that machine since it hangs after
a few seconds, it's already a miracle I can get a shell to last long
enough to run dmesg :)
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member
That's a good question, I'll try a 3.8 generic kernel to see. AFAIK
that's the only other generic armhf kernel that we have around.
--
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/1237733
3.10 seems a bit better, at least the kernel loads and the initrd too,
though it appears unable to mount the sdcard and so ends up stuck in the
initrd after a bunch of mmc related printk.
So it looks like there's no Ubuntu kernel that works properly on this
board.
--
You received this bug
** Changed in: linux (Ubuntu)
Milestone: ubuntu-13.09 = ubuntu-13.10
--
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/1066435
Title:
powerpc: Fixing recursive fault but reboot is
The dtb comes from mmc, I'm currently using one coming from the Ubuntu
image for the wandboard linked from their website but I also tried the
one from the current upstream kernel without seeing any difference in
behaviour.
I didn't try any of those shipped with the 3.11 kernel since the imx6q-
Just did a quick test now, the board won't boot the kernel at all using
imx6q-sabrelite.dtb so it must be different enough from the wandboard
dtb to confuse the kernel very early on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
So just to sumarize our IRC discussion. The dtb looks good and works great with
the fedora kernel.
The kernel itself boots and gets me past the initrd but hangs randomly a bit
later on (around network initialization time).
--
You received this bug notification because you are a member of
Moved to linux, ifenslave only tells the kernel to create the bond, if
the reported speed is wrong, it's a kernel bug not a userspace one.
** Package changed: ifenslave (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is
It's related to the apparmor patch, the security team is aware of it and
I believe John has a 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/1308082
Title:
apparmor oops caused
The verification of the Stable Release Update for intel-gpu-tools has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Public bug reported:
Hello,
I pushed a fix to the mainline kernel which I believe will first be released in
3.16.
This change is required to make setting tc rules inside an unprivileged lxc
container (assuming the userns owns a netns).
Commit id is: 4e8bbb819d1594a01f91b1de83321f68d3e6e245
Serge, could we just have lxc-attach query lxc.arch using
get_config_item over the command interface and do the personality
mapping based on the running container config rather than the running
processes?
That should spare us the addition of a new command interface call and
the usual breakage we
** No longer affects: linux (Ubuntu)
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Utopic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The LXC change looks good, it's in line with what I was planning to push
upstream. Feel free to upload that directly to the archive and I'll do a
similar upstream change right around the same time so our PPA users
don't break, then shortly after that will tag 1.0.3 and get that into
trusty so we
Sorry for the delay, I just got back from a couple of weeks on another
continent so didn't feel like testing this remotely :)
I'll do a test run now. By the way, since I first reported this issue, I
managed to reproduce it on two more machines running the 3.11 kernel, it
seems to vary with the
That kernel panics:
[ 68.626968] [ cut here ]
[ 68.631590] kernel BUG at
/home/jsalisbury/bugs/lp1251946/linux-stable/net/core/skbuff.c:1040!
[ 68.640188] invalid opcode: [#1] SMP
[ 68.644324] Modules linked in: authenc esp6 xfrm6_mode_transport ipcomp6
To add to the list above, I also had him test the current 3.13.0-0 from
the kernel-team PPA, this one doesn't work either.
--
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/1265544
Title:
So to clarify based on IRC discussion:
- Current trusty (3.12.0-7) gives a blank screen from the start
- mainline drm-intel-nightly build 2013-12-10 does the same
- mainline drm-intel-nightly build 2013-12-11 and any further one works
works here refers to the screen lighting up at boot time
Hello Yingying, or anyone else affected,
Accepted linux-firmware into saucy-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/linux-
firmware/1.116.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
That kernel doesn't have PPPoE support so it's useless to me, I need a
distro kernel for those tests :)
--
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/1251946
Title:
Network related
://bugs.launchpad.net/bugs/1263738
Title:
login console 0 in user namespace container is not configured right
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263738/+subscriptions
--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
--
You
Marking as invalid for LXC since this is a kernel bug.
** Changed in: lxc (Ubuntu)
Status: Confirmed = 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/1196295
Title:
I'm closing the lxc task as there's nothing we can do in lxc itself to
avoid this, the upstart and kernel patches will solve this for us.
Btw, the branch proposed by James above does work fine for me and has
since been accepted upstream, the next upload should include this fix.
** Changed in:
root@lxc-dev:/# ls -lh /proc/sys/net/ipv4/ip_local_reserved_ports
ls: cannot access /proc/sys/net/ipv4/ip_local_reserved_ports: No such file or
directory
root@lxc-dev:/# uname -a
Linux lxc-dev 3.13.0-8-generic #27-Ubuntu SMP Fri Feb 7 02:01:37 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
So
Setting as confirmed since this is 100% reproducible on current kernel
and not a crash but just broken /proc/sys/net (missing entries) and
possibly broken netns (those should be ns-specific).
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
The audit problem with 3.14 is known and being looked at upstream I
believe.
--
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/1279041
Title:
/proc/sys/net/ipv4/ip_local_reserved_ports not
Public bug reported:
Hello,
We've just had a rather length chat in #ubuntu-touch about some problems
related to rtkit and pulseaudio on the phone and then on any trusty
machine.
It turns out that since we now put all users in their own cpu cgroup,
rt_runtime_us is set to 0 which prevents any of
Public bug reported:
The recent security update kernel broke nested unprivileged LXC containers as
those attempt to do the following:
access(/usr/lib/x86_64-linux-gnu/lxc/dev/console, F_OK) = 0
mount(/dev/console, /usr/lib/x86_64-linux-gnu/lxc/dev/console,
0x7fff406cd9e9, MS_BIND, NULL) = 0
root@qdisc:~# tc qdisc add dev eth0 root netem delay 50ms
root@qdisc:~# ping 10.0.3.1
PING 10.0.3.1 (10.0.3.1) 56(84) bytes of data.
64 bytes from 10.0.3.1: icmp_seq=1 ttl=64 time=50.3 ms
64 bytes from 10.0.3.1: icmp_seq=2 ttl=64 time=50.3 ms
^C
--- 10.0.3.1 ping statistics ---
2 packets
Public bug reported:
I've recently been getting a few kernel panics which I've tracked down
to having panic_on_oops set to 1 and which appear to be related to this
oops:
[ 2182.341680] general protection fault: [#1] SMP
[ 2182.341702] Modules linked in: xt_CHECKSUM esp6
Yes, this is 3.13 with btrfs on a single encrypted block device with
zlib compression.
The oops doesn't appear particularly armful now that I've turned off
panic_on_oops so it's not something I'm willing to sacrifice 2TB of free
space to workaround :)
--
You received this bug notification
I have since upgraded that server to the upcoming utopic backport (from
the kernel team PPA) and I haven't been able to reproduce this bug. So
it may well be that there are some btrfs bugfixes in 3.16 which haven't
made it to stable.
--
You received this bug notification because you are a member
Public bug reported:
So I just updated my home server to the 3.16 from the kernel team PPA
(3.16.0-23-generic #31-Ubuntu) and I'm now getting a ton of warnings
related to what looks like some kind of network hardware offloading.
A 10 minutes kernel.log sample is attached.
The server is a recent
Public bug reported:
I recently noticed a bunch of containers failing in a rather odd way
when running postfix.
The most visible example is when running mailq on an empty queue.
Without apparmor (unconfined container) I see that the queue is empty,
with apparmor, I get Permission denied.
That's
so I think it's some systemd handling which does that. LXC unshares the
mnt namespace which gets it a copy of the host's, then it's doing some
magic (rprivate I believe) to get things working under systemd, then
mounts what it needs, unmounts everything else and pivot_root.
lxc itself has no code
So the problem is that a force unmount of a bind-mount of a fuse
filesystem somehow gets the kernel to send the destroy command back to
the user space process running the filesystem. This behavior is clearly
wrong.
As an example, lets say that I'm running lxcfs as a fuse filesystem on
my system.
I don't have any good example in mind of fuse being used in that manner
(system wide user accessible filesystem) but if there was, this would be
a potential security issue against them. Once we figure out the root
cause of this and fix it, it may be worth considering this a security
fix.
--
You
Anything else that's special on that network, e.g. non-standard MTU?
--
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/1402763
Title:
Multicast traffic not propating correctly over linux
Hmm, I can reproduce the exact same thing even without allow_other.
Sure, my user is getting permission denied if it attempts to read from
the fs, but it can still bind-mount it and then cause it to die by doing
a force unmount.
--
You received this bug notification because you are a member of
So I came up with an alternate way around this which works for both
privileged and unprivileged containers and doesn't require an updated
apparmor. This uses seccomp to filter the umount2 call and return EACCES
when passed MNT_FORCE as second argument.
Code is at: http://paste.ubuntu.com/9568741/
SCMP_CMP_MASKED_EQ should be used to restrict MNT_FORCE regardless of
what other mntflags are passed, though I'm failing to find the right
syntax for it...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Might be worth mentioning that all affected hosts are x86 64bit Intel.
For those I've got access to, the issue happened on:
- 2x Xeon E3-1245v2
- 1x Xeon E5-2620v2
- 1x Atom C2750
- 1x Atom D2500
- 1x Core i5 750
All running on pretty standard Intel boards, so the usual set of Intel
Public bug reported:
After updating a dozen machines from 3.13.0-40 to 3.13.0-43, they all
kernel panic within the next 24 hours.
I managed to pull the console from one over an IP KVM and it shows a panic
related to IPv6 networking:
https://dl.stgraber.org/panic-3.13-43.png
All affected
** 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/1404558
Title:
IPv6 related kernel panic following upgrade to
Booted the new kernel and so far so good. Since there is no real
reproducer for this bug, I'll mark this as verification-done and will
come flip it back to verification-failed if the box panics by the time
you push this kernel to updates.
** Tags removed: verification-needed-trusty
** Tags added:
I don't have a reproducer other than install the kernel and wait 24h as
that's how long it took for some systems to panic...
From a very quick look, those kernels are mainline kernels,
unfortunately all my hosts are LXC hosts using unprivileged containers
with overlayfs, so I need kernels with
Rebooted the Xeon E5-2620v2 system on linux-image-3.13.0-44-generic now.
--
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/1404558
Title:
IPv6 related kernel panic following upgrade to
Reproduced the panic with -44, same stack trace, screenshot attached.
Booting the machine back on -40 now.
** Attachment added: Screenshot from 2015-01-05 16:40:16.png
Almost 24 hours and no kernel panic so far!
--
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/1404558
Title:
IPv6 related kernel panic following upgrade to 3.13.0-43
Status in linux
Still no panic after 48h, let's call it 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/1404558
Title:
IPv6 related kernel panic following upgrade to 3.13.0-43
Status in linux
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1426618
--
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/1404558
Title:
IPv6 related kernel panic following upgrade to 3.13.0-43
I can confirm that something's broken with the recent kernel update...
--
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/1404558
Title:
IPv6 related kernel panic following upgrade to
Let's file a new bug for that one.
--
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/1404558
Title:
IPv6 related kernel panic following upgrade to 3.13.0-43
Status in linux package in
Public bug reported:
Hello,
Pretty similar to what happened with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558 but this
time with the latest 3.13.0-46.
I've been getting about daily kernel panics (three times so far).
Screenshot attached. Another user also commented in bug
root@precise-gui:/# ls -lh /proc/sys/net/ipv4/ip_local_port_range
-rw-r--r-- 1 nobody nogroup 0 Nov 9 12:53
/proc/sys/net/ipv4/ip_local_port_range
root@precise-gui:/# uname -a
Linux precise-gui 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015
i686 i686 i386 GNU/Linux
So looks like
** No longer affects: lxc (Ubuntu)
--
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/1480411
Title:
rm -r * fails to delete directories when using overlayfs in a user-
namespace
Status
** Changed in: lxc (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/1471358
Title:
lxc-checkconfig shows Mainline PPA Wily-4.0.7 kernel
** No longer affects: lxc (Ubuntu)
--
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/1402763
Title:
Multicast traffic not propating correctly over linux bridge
Status in juju-core:
** No longer affects: lxc (Ubuntu)
--
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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux
** Changed in: lxc (Ubuntu)
Status: Fix Committed => 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/1409425
Title:
lxc-start-ephemeral stops working with kernel 3.18
** 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/1384711
Title:
btrfs oops on current 3.13
Status in linux package
** 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/1357588
Title:
3.13.0-24 broke nested unprivileged LXC
Status in
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello Andy, or anyone else affected,
Accepted lxc into precise-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/0.7.5-3ubuntu70 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
What I don't get is why the other tests aren't failing too, they all
start containers too and so should hit the exact same failure. Why one
of the last tests is the one hanging just doesn't make sense to me.
Anyway, looks like there's a way for us to reproduce this and look into
it. It may well
** Also 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-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1514785
Title:
kernel 3.16.0.52+53 - ip rule
** No longer affects: lxd (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1527374
Title:
privilege escalation on attach through ptrace
Status in linux package in
I unfortunately can't reproduce this on demand. I've had it happen to me
so far twice, both times immediately after resume, on two completely
different wifi networks, once on a mobile hotspot from my phone and
another time at a hotel in Brussels.
My best guess is that it's got to do with some
Very much looks like it's related to threading and futexes somehow.
Forcing golang to use a single thread rather than one per container made
things more stable using a very simple test (infinite loop of "lxc
list"), though starting containers then still caused the hang to happen.
I've seen a
Public bug reported:
After resume, wifi doesn't come back up, all wifi related commands take
a long time before failing with input/output error.
Kernel log only seems to show some slowpaths being hit, but wifi sure
isn't working here...
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package:
Unloading and loading iwlmvm and iwlwifi did the trick to fix this.
Last time I had that issue, I attempted to reload iwlmvm, but not
iwlwifi too, maybe that made a difference this time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** No longer affects: lxc
--
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/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
breakages
Status in juju-core:
1 - 100 of 255 matches
Mail list logo
