So far I've tried with older kernels installed on my system. I'll try
with newer kernels later. And I incorrectly reported my Ubuntu version -
it's 14.04.4 now, and I think the error did not appear on 14.04.3.
3.13 and 3.19: the GL window freezes as described, but the i915 error is
not printed in
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592564/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592568/+files/PulseList.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/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592565/+files/ProcEnviron.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: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592558/+files/BootDmesg.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/
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592561/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592560/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592559/+files/CRDA.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/1554299
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592566/+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: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592571/+files/UdevLog.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/1554
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592562/+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/1554299
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592563/+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/1554299
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592567/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592569/+files/RfKill.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/1554299
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592572/+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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1554299/+attachment/4592570/+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/1554299
This is the result of my testing (I'll add appropriate tags):
3.13 OK
3.19 KO
4.2 KO
4.3 KO
4.4 OK
4.5 OK
OK means reported consumption 0 mW, KO means consumption 4-20 W.
** Description changed:
$ lsusb
Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications
Processor
Hmm, I feel it is probable that the i915 error and OpenGL freezes are
two separate issues. I tested with various kernels, and these are the
results:
GL bug:
3.13 KO
3.19 KO
4.2 KO
4.3 KO
4.4 KO
4.5 KO
i915 bug:
4.2 KO
4.3 OK
4.4 OK
So it seems 4.3 kernel has fixed the i915 issue, but the GL free
Oh, that's gonna take a while until I find the right time to do this
kind of experiment.
--
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/1554299
Title:
drm:intel_pipe_config_compare [i915
This still works fine with Linux 4.4.0-8, but fails on 4.4.0-10, so it's
a kernel regression.
This can be reproduced much simpler without LXC:
$ mkdir /tmp/lower /tmp/upper /tmp/work /tmp/merged
$ sudo mount -t overlay overlay
-olowerdir=/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/work /tmp/merg
Reproducer is available, not hw specific, so doesn’t need additional
logs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Nice work Seth, 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/1555997
Title:
overlay fs regression: chmod fails with "Operation not permitted" on
chowned files
Status in linu
There is no symptom or error description in your report at all. Dmesg
shows that the btrfs task is hung, but there's still not much to go
with.
** Summary changed:
- Systemd crash
+ task btrfs-transacti:1089 blocked for more than 120 seconds
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
I can confirm this bug is still present on MacBook Pro 11,1 and latest mainline
kernel 4.5.0,
tested on wily.
Disabling the XHC1 in /proc/acpi/wakeup does seem to prevent the immediate
wakeups
but this at the same time disables waking up on opening the lid for me (and
LID0 is still
enabled in /
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, w
Fwiw, there appears to be an upstream bug report at
https://bugzilla.kernel.org/show_bug.cgi?id=101681
** Bug watch added: Linux Kernel Bug Tracker #101681
http://bugzilla.kernel.org/show_bug.cgi?id=101681
--
You received this bug notification because you are a member of Kernel
Packages, whic
Public bug reported:
tested the latest xenial iso on a file server featuring an ARC-1882ix-24
RAID controller, and got weird timeout issues, followed by complete loss
of access to anything connected to the RAID controller. The timeouts
occur after a random amount of uptime (sometimes minutes, some
can't run apport-collect on the affected system because the filesystem
got ovverriden. the log lines posted in the original bug report are from
a remote rsyslog server capturing the event. the timeout bug in itself
is not new, it is a longstanding issue with that particular version of
the areca dri
** Package changed: systemd (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/1556433
Title:
Booting is taking too long to start from grub
Status in linux packag
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1549240
Title:
acer aspire 1
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1541151
Title:
16.04 PPC, un
I just tested this on 3 different computers using Ubuntu MATE 16.04 Beta
2, all were installed with full disk encryption.
* Thinkpad T43p (i386, Radeon)
* Thinkpad x201 (amd64, Intel IGP)
* Thinkpad T61s (amd64, nVidia)
In all cases I could not reproduce this issue. It works are intended.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1563095
Title:
Install boots
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1564046
Title:
New install b
This issue is a kernel bug. Patch is now available in the current
mainline since v4.6-rc1.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56dc66ff1c6d71f9a38c4a7c000b72b921fe4c89
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
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/1558275
Title:
wrong/missing permissions for device file /dev/prandom (prng
*** This bug is a duplicate of bug 1556228 ***
https://bugs.launchpad.net/bugs/1556228
Support for this codec was added in kernel v4.1
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6ffc0898b29a2811a6c0569c5dd9b581980110df
The strange sounds during reboot/shutdown
** This bug is no longer a duplicate of bug 1556228
HP Notebook Probook 440 G3 HDA Intel PCH horrible sounds while booting
--
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/1525554
Title:
** Package changed: systemd (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/1566828
Title:
Suspension does not work, freezes the pc
Status in linux package in
For the record, this "auto-destruct" behaviour with the xenial kernel
happens just by itself: reboot the instance, let it sit there for 15 or
60 minutes, then this kernel spew starts happening and it gets locked
up with losing network/ssh access. There was no actual payload on
these.
--
You rec
The kernel spews out some oopses
(https://launchpadlibrarian.net/234191094/CurrentDmesg.txt) About the
connection error, that is mostly tracked in bug 1502097, so let's devote
this to the kernel error.
** Summary changed:
- package systemd 225-1ubuntu4 failed to install/upgrade: subprocess instal
** Package changed: systemd (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/1551148
Title:
cfg80211 kernel module crashes
Status in linux package in Ubuntu:
The kernel issue still happens (see
http://autopkgtest.ubuntu.com/packages/u/udisks2/xenial/amd64/), so the
workaround needs to come back.
** Changed in: udisks2 (Ubuntu)
Status: Fix Released => In Progress
** Changed in: udisks2 (Ubuntu)
Milestone: ubuntu-15.01 => ubuntu-16.03
--
Yo
The workaround doesn't work any more, and the test does not actually
depend on ntfs-3g any more, so this must rather be fixed in our base
images.
** Changed in: udisks2 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: udisks2 (Ubuntu)
Milestone: ubuntu-16.03 => None
--
You
I re-tried with the current kernel 4.4.0-8, and merely booting a
pristine cloud image with "nova boot --poll --image ubuntu/ubuntu-
xenial-daily-arm64-server-20160227-uefi1.img --flavor m1.large" and
letting it sit there for some 20 minutes is still auto-destructing:
[2J[01;01H[=3h[2J[01;01H[2J[01
Booting with "debug=y" works better, as then the initramfs debug goes
right on the console, instead of /run/initramfs/initramfs.debug. This
shows that even the initrd starts after the error message, so this must
come from the kernel itself:
Loading Linux 4.4.0-8-generic ...
Loading initial ramdisk
Indeed the code in
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/hctosys.c
looks like it runs entirely "self-"triggered (late_initcall), not
triggered by an userspace call. This function tries to open the device
which simply isn't present (yet) at that time. So may
https://github.com/seccomp/libseccomp/pull/22 Thanks Andy!
** Changed in: libseccomp (Ubuntu)
Importance: High => Undecided
** Changed in: libseccomp (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: libseccomp (Ubuntu)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
there is no solution, most Fn keys don't work, I don't care, you don't have
the time. So stop this bug report from sending me stupid emails, shut this
down already. Don't think you can even bay this pis of shit computer new
anyway. The cpu is shit plus its nvidia, there is no point.
2016-01-10 9:3
I managed to get the 4x CPU instance into the same locked up state now,
so AFAICS the problem isn't fundamentally different between 4 and 8
cores.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Reducing the number of threads that Go uses seems to help a bit:
$ cat /etc/systemd/system/lxd.service.d/override.conf
[Service]
Environment=GOMAXPROCS=1
(GOMAXPROCS defaults to the number of CPUs). But Stéphane is still able
to lock up LXD pretty fast even with that.
--
You received this bug n
Confirming that 4.4.0-2 works fine on an arm64 box. 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/1533009
Title:
arm64: "unsupported RELA relocation"
Status in Linaro GCC:
Un
** Summary changed:
- lxd and other commands get stuck on arm64 kernel and multiple CPUs
+ [arm64] multithreaded processes get locked up in futexes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Some good news: With bug 1534545 fixed I was now able to upgrade to the
Xenial 4.4 kernel. On the 4x CPU instance two parallel adt-run loops
have now run for about two hours without any dmesg spew. Stéphane has
run "lxc-test-concurrent -j 16 -i 10" twice on the 8x CPU instance
successfully too.
Ba
Darn, I now get the "instance kills itself after some time" on the 4x
CPU as well. nova console-log shows the blurb below and ssh and lxd
ports are dead (so I can't learn anything further from the box than
console-log).
Ubuntu Xenial Xerus (development branch) lxd-armhf2 ttyAMA0
lxd-armhf2 login:
Public bug reported:
Running Ubunt 14.04.3 on a Dell XPS 15 9550.
After booting (successfully BTW) I see a number of errors in syslog. I
don't notice any errors which seem to indicate that something really is
broken, but, and I don't know if it's related, on multiple occasions I
had an issue duri
This only seems to happen while connected to an external monitor. It
happens between every <1s and 2 minutes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1542285
Title:
Xorg
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Suspend no longer works beta2 Not sure if bug or not
+ Suspend no longer works since 16.04 beta2
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of
Hello Thiago, or anyone else affected,
Accepted dpdk into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dpdk/2.2.0-0ubuntu8 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Public bug reported:
The kernel has been able to load firmware by itself for several years
now, and as a result the userspace loading of firmware got dropped in
udev three years ago
(https://github.com/systemd/systemd/commit/be2ea723b1d0).
But Ubuntu's kernels still enable CONFIG_FW_LOADER_USER_H
Oh, curious that CONFIG_DELL_RBU depends on the userspace firmware
helper (as a BIOS update sounds like the communication and request goes
from userspace to kernel, not the other way around?).
Anyway, this isn't urgent at all, so if it's not appropriate at that
time, please just close it.
** Chan
This is a syslog from one boot up to the point where I hard-rebooted the
instance because it was completely hanging. The kernel errors still
look by and large like the ones from the original report (in
JournalErrors.txt).
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/
Public bug reported:
Laptop: Dell XPS13 L321x
Trackpad: Cypress Trackpad / Clickpad
Problem appeared after update from 14.04 to 16.04
The touchpad is not listed under /proc/bus/input/devices altough it
shows up if using 14.04 via live usb
** Affects: linux (Ubuntu)
Importance: Undecided
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576196/+attachment/4650128/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576196/+attachment/4650129/+files/version.log
** Package changed: linux (Ubuntu) => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Attachment added: "devices"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576196/+attachment/4650127/+files/devices
--
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/1576196
Ti
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576196/+attachment/4650126/+files/dmesg
--
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/1576196
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1577810
Title:
Xbox 360 wire
Thanks, reassigning to the kernel then. Please run "apport-collect
1578015" to attach your hardware information. Also, please use "ubuntu-
bug" to file bugs so that this happens automatically in the future.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Yet another
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: bcmwl (Ubuntu Vivid)
Status: Fix Committed => Won't Fix
--
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: bcmwl (Ubuntu Vivid)
Status: Fix Committed => Won't Fix
--
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Tags removed: verification-needed
--
You received this bug notification becaus
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
The version of bcmwl in the proposed pocket of Vivid that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Kernel
Packages,
OK, I'll unsubscribe sponsors then. Please re-subscribe once there are
updated patches. Thank you!
--
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/1250109
Title:
Please use dpkg-triggers
Colin Ian King [2016-05-13 11:07 -]:
> Martin, I've going on a hunch, can you try the kernels to see if these
> help:
>
> http://kernel.ubuntu.com/~cking/lp1531768/
I installed that on two out of three lxd hosts. I'll watch the
notification emails of my watchdog and
@penalvch - I'm running this kernel, which I believe has your BYD patch
included.
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/
dmesg tells me the following:
[2.379157] mousedev: PS/2 mouse device common for all mice
[ 238.400656] psmouse serio1: byd: Unrecognized Z: p
I've installed the following Mainline PPA kernel on today's Ubuntu MATE
16.10
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc7-yakkety/
All screen flicker is gone. Just running Ubuntu MATE 16.10, without this
kernel upgrade, the flicker was still present.
--
You received this bug noti
My system:
Machine: System: Intel (portable) product: SharkBay Platform v: 0.1
Mobo: Topstar model: WhiteTip Mountain1 Fab2 v: Fab2
Bios: American Megatrends v: 5.6.5 date: 03/17/2015
CPU: Dual core Intel Core i3-5010U (-HT-MCP-) cache: 3072 KB
clock speed
Two boxes (lxd-armhf{1,2}) have been running for three days with cking's
kernel, 3 is running the standard xenial kernel. 1 and 3 don't respond
to ssh connections any more; 2 still does, but several processes are in
'D' state:
root47 0.0 0.0 0 0 ?DMay13 0:00 [fsnot
To fix your system locally you can set some custom names for these two
devices, or disable the ifnames schema completely. Please see
/usr/share/doc/udev/README.Debian.gz for details.
Can you please copy&paste the output of
SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id
/sys/class/net/eno1
After installing the 4.6 kernel and rebooting, lxd-bridge.service failed
the same way on two boxes:
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2112]: Failed to setup lxd-bridge.
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2129]: RTNETLINK answers: Operation
not supported
May 17 11:27:26 lxd-armh
> I now let one box run with 4.6.0, let's see how long it'll hold up.
Checking again, I got a dozen auto-reboots from the watchdog, and after
disabling the watchdog and inspecting the box after 4 hours I see
exactly the same symptoms.
--
You received this bug notification because you are a membe
I installed the debug kernel on one arm64 box last night, and it has now
run for 12 hours. lxd is still running, no hung processes, and dmesg
shows nothing unusual, i. e. no extra debug messages. Yay heisenbug?
The other box with the standard xenial kernel has locked up as always;
I'll install the
The verification of the Stable Release Update for linux-flo 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
One box completely froze again (ssh does not respond any more),
attaching dmesg. However, I'm not sure that this actually contains what
you were looking for -- there is a lot of the usual chatter from
starting/stopping containers, and then some traces about hung tasks when
trying to flush the file
FTR, I'm also having problems with the wily arm64 kernel on multi-CPU
machines. I filed that as bug 1531768 as the logs here look rather
different to mine. But maybe it's related.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Public bug reported:
I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
want to use for armhf autopkgtesting in LXD). I started with wily as
that has lxd available (it's not yet available in trusty nor the PPA for
arm64).
However, pretty much any LXD task that I do (I haven't
"reboot" also takes too long to be practical (I killed the instance
after waiting for 10 mins, as it didn't even begin to shut down).
--
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/1531768
I take that back. It does survive for much longer, but after some 15
minutes of running I again run into tons of
[ 2424.611668] INFO: task systemd-udevd:1320 blocked for more than 120 seconds.
[ 2424.613514] Tainted: GW 4.2.0-22-generic #27-Ubuntu
[ 2424.615183] "echo 0 > /proc
> Can you collect apport information from the host system as well?
Sorry, I can't. I can create Scalingstack instances, but I have no
access to the host systems. The IS team certainly can, though.
> Do you get the same effects with a single vCPU?
So far that test system is holding up and I haven
** Attachment added: "linux-image-3.19.0-43-generic.265328.crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532613/+attachment/4547634/+files/linux-image-3.19.0-43-generic.265328.crash
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
crash
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
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/1532613
Title:
NMI watchdog:
701 - 800 of 2221 matches
Mail list logo
