Have had two or three more instances of this oom-killer behavior. Today
we also had an incident where the system really DID run out of memory,
but oom-killer did not kick in. I noticed the box being sluggish and
disk churning, so I started system monitor and watched it happen. One of
the firefox
No oom-killer event with v5.0 kernel.
Linux version 5.0.0-05rc1-generic (kernel@tangerine) (gcc version 8.2.0
(Ubuntu 8.2.0-12ubuntu1)) #201901062130 SMP Mon Jan 7 02:32:47 UTC 2019
Possible explanations:
Scenario #1) There was a kernel bug and it is fixed in v5.0. Or,
Scenario #2) Compiz r
So far, no oom-killer problems with Xenial HWE in production. Newer
kernel (Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18). Not sure if it
matters, but still using the proprietary Nvidia driver, but it may be a
newer version. Same version of compiz (0.9.12.3).
If you do not hear from us further,
Public bug reported:
This has happened five times in the past week (four times in the past
36 hours):
kernel: compiz invoked oom-killer:
There is plenty of free core memory and almost no swap in use when it
happens. This is Xenial with kernel version is 4.4.0-141, which
contains fix to previo
** Attachment added: "lspci-vvnn.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811093/+attachment/5227998/+files/lspci-vvnn.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/bu
** Attachment added: "syslog_snippets"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811093/+attachment/5227999/+files/syslog_snippets
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Package
compiz:
Installed: 1:0.9.12.3+16.04.20180221-0ubuntu1
--
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/1811093
Title:
Bogus "Out of Memory" compiz invoked oom-killer
Status in linux pac
Not sure when it started. I can only go by the logs I have, and they
only go back nine days. But the postgres job that I mentioned
previously, and which caused several oom-kill's in a row, was last run a
month and a half ago, and at that time it ran without any problems. But
it may have run witho
PID ACCESS COMMAND
/dev/snd/controlC0: craig 2953 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Jul 23 18:21:01 2014
HibernationDevice: RESUME=UUID=e9813637-6815-4ca0-916c-5d1c9f13b1d7
InstallationDate: Installed on 2013-12-02 (233 days ago)
InstallationMedia: Ubuntu-GNO
USERPID ACCESS COMMAND
/dev/snd/controlC0: craig 2953 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Jul 23 18:21:01 2014
HibernationDevice: RESUME=UUID=e9813637-6815-4ca0-916c-5d1c9f13b1d7
InstallationDate: Installed on 2013-12-02 (233 days ago)
InstallationMedia: U
USERPID ACCESS COMMAND
/dev/snd/controlC0: craig 2953 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Jul 23 18:21:01 2014
HibernationDevice: RESUME=UUID=e9813637-6815-4ca0-916c-5d1c9f13b1d7
InstallationDate: Installed on 2013-12-02 (233 days ago)
InstallationMedia:
I'm also having this problem and found a matching bug over on the kernel bug
tracker:
https://bugzilla.kernel.org/show_bug.cgi?id=72601
Emmanuel Grumbach (Intel wifi driver maintainer) is helping with the
issue.
** Bug watch added: Linux Kernel Bug Tracker #72601
http://bugzilla.kernel.org/sh
32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: craig 2953 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Jul 23 18:21:01
PID ACCESS COMMAND
- /dev/snd/controlC0: craig 2953 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: craig 2953 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Jul 23 18:21:01 2014
HibernationDevice: RESUME=UUID=e9813637-6815-4ca0-916c-5d1c9f13b1d7
Instal
eric x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F...
Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig
7-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F...
portVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] fail
ture: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig
inux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F.... pulseaudio
/dev/snd/controlC0: craig 3257 F pulseaudio
CRDA: Error: command [&#x
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Card0.
re: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: craig
inux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F pulseaudio
CRDA: Error: command ['
** Tags added: kernel-bug-exists-upstream
--
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/1253527
Title:
With Dell XPS 12 model 9Q33, touchpad gets detected as PS/2 Generic
Mouse
Statu
I have a Dell XPS 12 9Q33 (Haswell), BIOS A03.
With Precise (12.04) - no wifi, unable to drag and drop windows (window will
jump all over the screen, randomly. Touchpad doesn't appear to work correctly
with 2 fingers on the touchpad. It seems confused. No 2 finger scroll.)
xinput list
Currently unable to file a new report. The Dell XPS 12 does not have a
local network port, and the wifi does not work.
The wifi does work starting from 13.04. But there is still no 2 finger
scrolling.
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
2 finger scrolling does not work in the touchpad. Finger scrolling in
the touchscreen does not work either.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic 3.11.0-13.20
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux
7-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F pul
Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F pulseaudio
CRDA: Error: command ['iw', '
linux-image-3.2.0-37-generic 3.2.0-37.58
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCE
untu17.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 3257 F pulseaudio
/dev/snd/controlC0: craig 3257 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not
.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00
2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio chan
I get this bug on Ubuntu 18.10 with the kernel upgraded to 5.0.2 from the
ubuntu repository. My machine is an Acer Predator Helios 500 Ryzen.
acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first
instance was on PNP0C14:00)
--
You received this bug notification because
these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can&#
--
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
$ uname -a
Linu
n 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
$ uname -a
Linux craig
craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
$ uname -a
Linux craig-Predator-PH5
commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can&#
One does not simply close a bug report about a Radeon driver because
Christopher went out and got an Nvidia card.
--
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/1707695
Title:
radeon 000
One does not simply close a bug report about a Radeon driver because
Christopher went out and got an Nvidia card.
--
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/1707695
Title:
radeon 000
I believe this is solved by bug #1743529 backporting kexec-tools from
bionic. What's the right way to close this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1745492
Title:
Bac
Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio ch
craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
$ uname -a
Linux craig-Predator-PH5
iew things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517
things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kerne
to
view things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517
on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kerne
on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kerne
on 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access
vdagent virtio channel /dev/virtio-ports/com.redhat.
things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kerne
on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_cr
nd am able to
view things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 crai
to
view things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517
to
view things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517
things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kerne
to
view things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517
am able to
view things on screen.
Running these commands I get this information:
$ journalctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predato
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-0xdf778fff]
Jan
$ uname -a
Linux craig-Predator-PH517-61 5.0.0-05rc4-generic #201901272036 SMP Mon Jan
28 01:38:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Suspend to ram still results in gibberish on the screen with the latest
upstream kernel. Confirmed bug and added tag kernel-bug-exists-upstream.
Please
alctl -b -g suspend
Compiled without pattern matching support
$ journalctl -b -p3
-- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54
CST. --
Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't
request region for resource [mem 0xdf775000-
For the record:
I've tracked this down to a pair of commmits, the first of which landed
in -35 (released in -36) the second in -37.
The first:
https://lkml.org/lkml/2018/6/5/765
The second:
https://lkml.org/lkml/2018/6/24/161
In the interim state, it was casting a u64 to a u32, which truncates t
I can confirm the following fixed the no-sound issue on my UX533 per
buchovagabond's post above:
sudo ukuu --install v4.19.10
Cheers,
Craig
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Public bug reported:
I cannot see any bluetooth devices nearby or connect to them e.g. a
wireless loudspeaker.
Laptop is a Lenovo
Ubuntu 4.4.0-75.96-generic 4.4.59
This command did not return anything:
usb-devices | awk '/13d3/' RS=
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-i
No Joseph, it has always happened on the laptop since I installed Ubuntu
and did a few updates. I tried various things after seeing a similar bug
logged here and following the suggestions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Kai-Heng, no this did not work. I had previously turned these settings
on and off many times to test. Next job: try retesting with the newest
dev Linux kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
have no idea how.
Thanks
Craig
--
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/1686776
Title:
RTL8723BE Bluetooth drivers do not work
Status in linux package in Ubuntu:
Incomplete
Bug
Ok I tried two kernel packages both with and without nomodeset enabled
in the grub file, first tried the v4.11 image and specifically file
named linux-
image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb. This
gave me errors similar to the above including multiple "AMD-Vi:
Completion-W
added in the following link: https://bugs.freedesktop.org/show_bug.cgi?id=101029
Bug #101029
** Bug watch added: freedesktop.org Bugzilla #101029
https://bugs.freedesktop.org/show_bug.cgi?id=101029
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
thanks Timo and Paul
--
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/1683184
Title:
GPU problems on HP 15-ba009ng
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Triage
I experience the identical problem, but with TP-LINK TL-WN722N (Atheros)
WiFi USB stick.
--
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/1888385
Title:
FRITZ!WLAN USB Stick v2 (Product: F
I can confirm that Kernel 4.13 in ubuntu 17.10 beta 2 fixes this
problem. No work around is needed to boot into the system or live media.
--
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/1683
Public bug reported:
Debian bug #785714 is a fairly substantial one, as it causes unclean
shutdowns. In our case, KVM hosts with many guests will begin to
partially shutdown a couple before kexec jumps the gun and reboots the
machine. Without this fix, kexec is of only minimal use on Xenial
**
I can't progress this investigation without some help. Can someone tell
me how to clear out unwanted code from the "make" so I can make the new
RC kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
l for a brief time when the Windows machine is busy accessing the internet.
Routing stayed up all night when there was no Windows 10 internet routing
activity. Resuming activity in the morning caused a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
I haven't had any problems since upgrading to yakkety:
4.8.0-30-generic #32-Ubuntu
driver: iwlwifi
version: 4.8.0-30-generic
firmware-version: 22.361476.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bu
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Craig Magina (craig.magina)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Craig Magina (craig.magina)
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
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/1625222
Title:
d-i is missing usb support for platfor
I can now confirm that the patch provided in the
https://bugs.freedesktop.org/show_bug.cgi?id=101029 fixes my problem, i
was finally able to patch and compile the source code for the kernel and
was able to boot into the system without crashing. What is the process
now to get this patch applied in U
Executed "apport-collect 1695829" as root.
It took a long time to run, and I can't tell if it's done. The pop-up dialog
is gone.
This is what I see in the terminal window:
root@pluto:~# apport-collect 1695829
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=JCzPZ4NNj
l for a brief time when the Windows machine is busy accessing the internet.
Routing stayed up all night when there was no Windows 10 internet routing
activity. Resuming activity in the morning caused a quick routing failure.
+ ---
+ ApportVersion: 2.20.1-0ubuntu2.6
+ Architecture: amd64
+ A
ilure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
Hibernatio
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RE
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
ilure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=5967
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=5967
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RE
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RE
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice:
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=5967
d a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RE
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=5967
.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: craig 7726 F pulseaudio
/dev/snd/controlC0: craig 7726 F pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=5967ff24-0a8c-4a29-bd33-4
hine is busy accessing the internet.
Routing stayed up all night when there was no Windows 10 internet routing
activity. Resuming activity in the morning caused a quick routing failure.
---
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS C
I verified that the new drivers are in the trusty-proposed and the
yakkety netboot installers. Everything looks good.
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Looks like this has been corrected, from a recent c4.8xl launch:
--
[0.00] Linux version 3.13.0-71-generic (buildd@lgw01-09) (gcc version
4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015
(Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29)
[0.00] Command line:
m4.10xl also looks good:
[7399124.202570] lp1497428: module verification failed: signature and/or
required key missing - tainting kernel
[7399124.223762] pageblock_nr_pages 0x200
[7399124.226007] node 0 zone 0 info:
[7399124.227849] node 0 zone 0 provided page pfn 0xfff valid 1 present 1
[739912
** Description changed:
I recently replaced some Xenial servers, and started experiencing "Out
of memory" problems with the default kernel.
We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
e6b58e85, in ap-southeast-2, from https://cloud-
images.ubuntu.com/locator/e
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1458042
Title:
[SRU] xgene-enet: add SGMII based 1GbE support for
1 - 100 of 321 matches
Mail list logo
