Public bug reported:
Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine
in an Intel NUC, part of a three-member LXD cluster. The other machines
do not show this crash and they are not running the lowlatency kernel,
but that might be incidental. I will swap out the generic kern
Just to confirm and still seeing this with today's -24 package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
Status
Hi Seth
I have been deploying charmed-kubernetes on a LXD cluster. I didn't
think the kernel crash was workload-specific, but of course it might be.
It looked more likely to be ZFS + lowlatency + snaps triggering the issue.
For now I have had to move to -generic on the machine which was causing
t
OK, will circle back to this bug in due course. From what you say it
might even be specific to that Nuc.
Mark
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliab
Fine-grained network security for snaps is going to be fantastic, but
it's also a rich area, and when networking policy stuff is done
simplistically it becomes awkward more than useful.
I'd suggest that we start now working up detailed design on the topic,
so that when we are ready to start implem
Public bug reported:
Hi folks, is there a reason we do not enable
CONFIG_NETWORK_PHY_TIMESTAMPING ? I'm not sure of the tradeoffs but I
think this config option is required for PTP time syncronization which
would be useful in telco and financial (and OCD :)) environments.
** Affects: linux (Ubunt
Thanks folks, looking forward to the results. I would have thought it
would noop where the feature was not in use; as far as I know it
requires explicit activation.
Mark
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Colin, thanks for the analysis.
No rush on the change.
Mark
--
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/1785816
Title:
Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING
Status in l
Hi Seth, 18.04 LTS is plenty for my purposes and for users wanting to
kick the tires on the functionality. No need for a backport on the
change at this stage.
Thank you!
Mark
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
Timestamping seems to be working. However there may be other networking
issues in -proposed that could be kernel related (captured in bug
#1818340) that might warrant a hold on promotion.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Public bug reported:
Hiya
I periodically do a full reinstall of all packages just to see what
breaks. Today it's the kernel :) Oddly I have reproduced this on several
machines. Simply fire up aptitude, go to "Installed" packages, hit
Shift-L to reinstall, then g and g again to kick it off. When I
apport information
** Tags added: apport-collected xenial
** Description changed:
Hiya
I periodically do a full reinstall of all packages just to see what
breaks. Today it's the kernel :) Oddly I have reproduced this on several
machines. Simply fire up aptitude, go to "Installed" pack
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583348/+files/ProcModules.txt
--
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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583349/+files/UdevDb.txt
--
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/1550755
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583346/+files/ProcCpuinfo.txt
--
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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583341/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583344/+files/Lspci.txt
--
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/1550755
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583343/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583345/+files/Lsusb.txt
--
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/1550755
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583347/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583342/+files/IwConfig.txt
--
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/15
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1550755/+attachment/4583350/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Thanks for the quick triage!
Mark
--
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/1550755
Title:
Reliably crash kernel 4.4.0.8-generic by reinstalling all packages and
waiting for bind
On 13/07/16 04:32, Uli Middelberg wrote:
>> @Uli, It's an automated dependency.
> I know.
>
> The question is: Should I modify /etc/network/fan if I'm using private
> IP addresses outside of 10.254/16, 172.16/12, 192.168/16, e.g. 10/24 ?
The key thing with the fan is that all the machines particip
Please bump up the importance of this issue. Thanks!
Mark
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1551747
Title:
ubuntu-fan causes issues during network configuration
Statu
Colin, Andy, thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1627909
Title:
[SRU] zfs-linux should be using python3 for python userspace tools
Status in zfs-linux package
Thanks guys, can't wait to see this in action :)
Mark
--
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/1611078
Title:
Support snaps inside of lxd containers
Status in lxd:
Unknown
Stat
I think it would be acceptable, for now, if (a) the zed init script
avoided starting in containers, and (b) there were an /etc/default/zed
which enabled one to disable zed altogether. Would that cause a problem
for people creating their first pool, where their docs expect zed to be
running?
Mark
Right, the only issue is how to address the legitimate concerns of
people not using ZFS. Ideally, we'd be:
* detecting the need for it on boot and starting it if relevant
* also starting it whenever a zpool is created
This way, it's there whenever you need it, otherwise not. I'm pretty
sure the
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1206961
Title:
Include rbd and kvm modules in the virtual package
Status in
30 matches
Mail list logo
