The log excerpt is collected as part of an automated test run.
** 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/1261308
** Tags removed: ci
--
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/1261308
Title:
Intel ivy bridge crash on a CI machine executing autopilot tests
Status in “linux” package in Ubuntu:
Public bug reported:
This is the second time (unclear about a third one) I encounter this
crash and all I could do was power-cycling to reboot.
/var/crash is empty
/var/log/syslog and /var/log/kern.log don't contain any hint around the
crash time (the subsequent reboot is present though).
So I
Just occurred again and indeed that was when running 'juju destroy-
environment lxc --force'
The only thing that is not standard in my config is that I'm using an
existing 'br0' bridge in /etc/lxc/default.conf (lxc.network.link = br0)
and I disable /etc/default/lxc-net with
FTR, issuing 'juju destroy-environment lxc --force' after the reboot
completes.
--
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/1336859
Title:
crash without any trace in log files
I'm testing the kernel mentioned in bug #1314274 as this bug seems to be
a duplicate, will mark it as such if I don't get a crash in the next
days.
Note that I had to
http://www.ubuntuupdates.org/package/canonical_kernel_team/trusty/main/base
/linux-headers-3.13.0-31 in addition to the packages
Public bug reported:
https://wiki.canonical.com/UbuntuEngineering/CI/IncidentLog/2013-11-04
-otto-outage was filed when the issue was discovered
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1314274 ***
https://bugs.launchpad.net/bugs/1314274
@Christopher, sorry had a tab opened (but never came back to it) to
confirm I'm now running 3.13.0-32-generic #57-Ubuntu which includes the
fix and I didn't encounter the bug anymore (while still heavily
Happened today after the upgrade, lost wifi :-/
Linux pump 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
Happened today after the upgrade, lost wifi :-/
Linux pump 4.15.0-24-generic #26~16.04.1-Ubuntu SMP Fri Jun 15 14:35:08
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
rebooting with an older kernel worked around the issue:
Linux pump 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27
UTC
/me hugs apw
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1777646
Title:
bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe-
edge 4.15.0-23.25~16.04.1
Status in
> The proposed fix installed successfully and the problem is corrected.
\o/
Yet:
> I have run into a bug when installing the 4.15.0-29-generic kernel
today.
So can we have the -proposed fix landed ?
Pretty please ? With sugar on top ?
Is it a matter of changing one bug tag ?
Which one
Same here (broadcom-sta vs bcmwl).
Can a kind soul explains if one can be used instead of the other and
why/how they differ ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1757008
13 matches
Mail list logo
