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 in:
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:
Network
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.
https
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 xfrm4_m
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 tunne
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 t
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 k
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
Pac
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
Th
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
T
Just tried the latest 3.8 from raring-proposed. It won't boot at all, not
getting a single kernel entry on the serial console.
Now looking for a 3.10 kernel from earlier in the saucy cycle.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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 notifi
** 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 nee
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-
wan
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 in
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 Kernel
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 m
** 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 ne
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:
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 be
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
https://wiki.ubun
** 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
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/1402763
Title:
Multicast traffic not propating correctly over linux bridge
Status in juju-core:
Triag
** 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 mi
** 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 i
** 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 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/1384711
Title:
btrfs oops on current 3.13
Status in linux package i
** 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 li
** 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.
https://bugs.launchpad.net/b
** 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 repeats
Re-opening as until linux-kvm is deprecated or the CPC team moves over
to using linux-virtual for KVM images, this is the kernel we're dealing
with and that kernel should be functional.
** Changed in: linux-kvm (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification beca
** Package changed: lxd (Ubuntu) => linux-raspi (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1948573
Title:
Failure to start container “Failed to start device “eth0”: E
Moving over to the kernel as a userspace process shouldn't be able to
cause such a hang regardless of what it does so this looks like a kernel
bug (lock related by the looks of it).
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member
Closing the LXC side of this bug as there's nothing we can really do here.
It's either a kernel issue (needs support for their socket option within a
network namespace) or an open-iscsi issue where they could have some kind of
fallback mechanism.
** Changed in: lxc (Ubuntu)
Status: Confir
I think the strlcat thing is a red herring or an indication that the
test environment is somehow in a bad shape. This could be explained if
there was two versions of liblxc on the system for example.
Outside of that, I'm also seeing:
```
lxc-start tmp.KEpxw2rh0e 20220205081512.354 ERRORutils
** Changed in: lxc (Ubuntu)
Status: Incomplete => Invalid
** Changed in: lxc (Ubuntu Focal)
Status: Incomplete => Invalid
** No longer affects: lxc (Ubuntu)
** No longer affects: lxc (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages,
Closing the LXC task for now as that seems to be unrelated to a LXC
change (we haven't uploaded in a while) and not related to a new kernel
release which could actually cause such a change.
If you track this down to something other than an issue in your test
environment, please add lxc to this iss
Adding linux-kvm to the bug. It looks like if we can have the commit
above backported, it would take care of this issue for most users.
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu)
Status: New => Confirmed
--
You receiv
Public bug reported:
Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers
as they hit:
https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55
It looks like we need to get e90e51d5f01d included in those
Mar 25 16:18:30 abydos kernel: [ 1319.549186] [ cut here
]
Mar 25 16:18:30 abydos kernel: [ 1319.549191] WARNING: CPU: 12 PID: 15052 at
arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel]
Mar 25 16:18:30 abydos kernel: [ 1319.549213] Modules linked in: wi
This repeats in a loop and fills tens of GBs of space with kernel logs
in just a few minutes before crashing the entire 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/1966499
Title
Ah yeah, that could be. I figured I'd test what's in -proposed but if
-proposed is a security only fix on top of -37, that wouldn't help much.
It's a bit frustrating because users would have gotten the busted kernel
as part of -37 which includes a security fix but then the only real
option to get
** Package changed: zfs-linux (Ubuntu) => linux (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/1940083
Title:
zfs send encrypt causes kernel NULL pointer dereference
Status in
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1940083
Title:
zfs send encrypt causes kernel NULL pointer dereference
Stat
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
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/1063354
Title:
[Dell Studio XPS 1640] Sudden Read-Only Filesystems
St
Let's close this as our kernels pretty much all support ZFS and LXD is a
snap and therefore does not need additional userspace tools.
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
In my case I was constantly getting corruption of /etc/apparmor.d with
the matching zfs PANIC. I'd fix that directory and it'd break again on
next boot.
System is impish with 5.13 kernel (same on 5.11) using zfs encryption.
After fighting with this for over a day, I just gave the 2.1.0 dkms a go
Public bug reported:
Reported here: https://github.com/lxc/lxd/issues/8735
After investigation, the issue is:
```
# CONFIG_NFT_FIB_INET is not set
```
As found on current 5.11 raspberry pi kernel.
Generic Ubuntu kernel has:
```
CONFIG_NFT_FIB_INET=m
```
The rest of the config related to nft/n
This looks like a kernel regression to me.
** Package changed: lxd (Ubuntu) => linux (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/1921969
Title:
lxd 2.0.11-0ubuntu1~16.04.4 A
When a single test fails occasionally, it can be an issue with LXD or
with the test, but when a bugfix release of a stable kernel suddenly
causes one of the most trivial tests to fail on all architectures, this
strongly suggests that the kernel is the issue.
--
You received this bug notification
Confirmed that on a working system, just updating to the new kernel breaks it.
So that SRU kernel is definitely broken and should not be shipped.
[8.996651] BUG: unable to handle kernel NULL pointer dereference at
e12c1a77
[8.998738] IP: [] fuse_do_setattr+0x52/
Moving this bug to the kernel as investigation discovered a kernel regression
in overmounting protection behavior in 5.3 rc1.
So not a LXC bug but a kernel one.
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this b
Removing the LXD task as this isn't a LXD bug, the error is coming from
snapd when setting up the apparmor profiles. Most likely explanation is
that there's something pretty wrong going on with your /etc/apparmor.d
on your system. The errors indicate a variety of missing abstractions
files.
** Cha
Your `dmesg` output shows some serious kernel errors related to ZFS, I
bet that's the source of this.
--
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/1946437
Title:
snap install lxd fails
201 - 261 of 261 matches
Mail list logo
