This still appears to be an issue. Events are listed in `perf list` but
not available for use by `perf record`
e.g.
$ sudo /usr/lib/linux-tools/6.2.0-39-generic/perf record -e
syscalls:sys_enter_fsync -ag
event syntax error: 'syscalls:sys_enter_fsync'
\___ unsupported tracep
Thanks for the update. I've just installed the suggested 17 series of
kernel packages on a test machine. It will probably take a day or so to
confirm the issue is gone, but as long as that patch is in there, I'm
pretty confident it will address the issue I was seeing. I'll update
again if I stil
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/2041668
Title:
Memory leak in 23.10 kernel (6.5.0-10)
Status i
FWIW, this appears to be an issue in the upstream 6.5 kernel. It's discussed
in more detail here:
https://lore.kernel.org/all/1694366...@msgid.manchmal.in-ulm.de/
A fix was applied to the mainline kernel here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3cec5049
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+attachment/5713765/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+attachment/5713766/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launch
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2041668/+attachment/5713764/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
There appears to be a memory 'leak' in the kernel of the latest Ubuntu release
(Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this
memory appears to be allocated but never used. The kernel's memory over-commit
mechanism seems to prevent this leak
Here are the binary dump of the smbios type 9 for one of the slots, as
well as the decoded information and the appropriate section in the spec.
I have also attached a copy of the spec in a previous comment.
--
You received this bug notification because you are a member of Kernel
Packages, which i
** Attachment added: "dmidecode-3.png"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651414/+files/dmidecode-3.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launch
** Attachment added: "dmidecode-2.png"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651413/+files/dmidecode-2.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launch
** Attachment added: "dmidecode-1.png"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651412/+files/dmidecode-1.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launch
HI Mauricio,
The following command did not work : sudo apt install --allow-downgrades
dmidecode/jammy-updates
I was able to download and install dmidecode 3.4 to my jammy instance. I
checked the version with dmidecode --v and it stated 3.4.
I uploaded my updates bios with slot information, slot
IS ther a way to test dmidecode 3.4 on Jammy?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/2004493
Title:
dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
Statu
I don't have access to Kinetic yet. Jammy is the latest available to my
team.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/2004493
Title:
dmidecode support for SMBIOS SPEC 3.5 for
Public bug reported:
For EDSFF slot type changes no longer indicate the PCIe Generation supported
nor do they indicate the full formfactor. To accomodate this severa sections
have been added in the spec as follows 7.10.10 System Slots — Slot Information
, 7.10.11 System Slots —Slot Physical Wid
Went through the URL below to identify if it's kernal related and after
implementing step 5 in Step by Step troubleshooting and no key press
event was made ("run sudo evtest, select your keyboard device, press the
broken keys, and note down their scan code (MSC_SCAN), current keycode
(KEY_*), and i
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634672/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634670/+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/1998711
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634671/+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/1998711
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634669/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634668/+files/ProcModules.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634667/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634666/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634665/+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: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634663/+files/Lsusb-v.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/1998
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634664/+files/PaInfo.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/1998711
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634662/+files/Lsusb-t.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/1998
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634661/+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/1998711
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634659/+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/1998711
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634660/+files/Lspci-vt.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/19
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634658/+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/19
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1998711/+attachment/5634657/+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
** Tags added: apport-collected wayland-session
** Description changed:
Upon research into several posted solutions the issue remains.
1.Ubuntu 22.04.1 LTS and GNOME tweaks 42.5 installed
2. Using apt-cache policy pkgname does not work in terminal
3. Left and right co
Ah, didn't realize Debian had a different limit. Thanks @juliank.
@anourzad, I'm not sure I would want to start adding custom steps to the
kernel update path. I'm much more inclined to add an /etc option for a
supported automatic mechanism, like compression or module selection.
@adrien-n, great n
Confirmed that reducing the size of the initrd.img slightly allowed my
machine to boot. I just enabled `COMPRESSLEVEL=19` with `COMPRESS=zstd`
(default on debian) in initramfs.conf. That reduced my initrd.img size
from 72MB to 62MB, which allowed my machine to boot.
Ultimately, I set `MODULES=dep`
I updated the firmware for this card from the 00157 to the 00288 version of
firmware:
https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1
and it seems to have fixed it but still I get:
ath10k_pci :3a:00.0: failed to install key for vdev 0 peer
MY_AP_MAC_ADDRESS: -110
in
** Attachment added: "lspci output"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1908800/+attachment/5547183/+files/ath10k-qca6174-lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
htt
I am on 21.04 (Linux XPS-13-9360 5.11.0-41-generic #45-Ubuntu SMP Fri
Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) and this is an
issue for me. I have to re-connect to my AP to get connected again.
My wireless card is: Qualcomm Atheros QCA6174 802.11ac Wireless Network
Adapter (rev 32)
I've never had this in Ubuntu 21.04 Hirsute. But after upgrading to
Ubuntu 21.10 Impish, I had it boot up without WiFi.
In 21.04 Hirsute, here is an example good boot from /var/log/syslog:
Oct 21 15:03:08 nary kernel: [2.596955] ath10k_pci :02:00.0: enabling
device ( -> 0002)
Oct 21
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 will have to read up on this, and I am in a situation where I have to
rely on this as my only computer for a while.
--
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/1882442
Title:
Upgrad
I already tried that, it V4.1.5 worked with both Ubuntu 18.04 and 20.04. I
put in an earlier comment about this.
On Wed, Jul 8, 2020 at 10:40 AM Kai-Heng Feng <1882...@bugs.launchpad.net>
wrote:
> Can you please test kernel v4.15, which is used by 18.04:
> https://kernel.ubuntu.com/~kernel-ppa/ma
Yes, it worked on 18.04. The problem came with the upgrade to 20.04.
--
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/1882442
Title:
Upgrade from 18.04 to 20.04 deactivates internal monito
The above did not work.
I edited grub to remove the amdgpu.dc=0 from the command line, ran update-grub
and rebooted. Essentially the same behavior as before.
I did notice some 'Tell Plymouth to write out...(something) in the boot
messages, but otherwise very similar.
--
You received this bug n
I got the files for the kernel and did this (many warnings, one error):
(base) david:new-kernel$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-5.8.0-050800.
(Reading database ... 454198 files and directories currently installed.)
Preparing to unpack
linux-headers-5.8.0-
I found a similar Fedora bug report, it is a kernel issue, and there is
a workaround. See: https://bugzilla.redhat.com/show_bug.cgi?id=1594488
Need to add 'amdgpu.dc=0' to the kernel command line in grub.cfg:
GRUB_CMDLINE_LINUX="amdgpu.dc=0"
then run grub-update
reboot
after booting to a versio
PARTIAL FIX: downgrade the kernel. I can confirm that everything seems to
return to normal if you use GRUB2 to select Linux 4.15.0-101-generic as the
kernel.
I edited /etc/default/grub to
- give a boot menu with a reasonable timeout
- use the last selected kernel as default
** Description cha
This seems to be a kernel issue: when I switched back to kernel 4.15 in
GRUB2, the problems seems to go away. Checking on it.
--
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/1882442
Title:
I left the machine on a while, and the internal monitor came on while I was
gone for about an hour.
???
--
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/1882442
Title:
Upgrade from 18.04
If the external HDMI is plugged in at power-on, a login window will show
up on the HDMI, and then I can choose gnome or gnome classic for the
session, log in, then right-click on the desktop, set the displays to
mirror, and get to the main panels or activities menu.
--
You received this bug noti
If I shutdown and unplug the external HDMI monitor, then power on, the
internal display only shows the initial UEFI message, the screen appears
grey, then it goes dark. If I then plug in the HDMI (not changing the
power state) I can get a tty with ctrl-alt-f1, login, and run startx.
MATE then appea
I also went in the dconf editor and changed some settings for laptop lid
behavior to 'nothing",
since the display settings show the internal monitor as a laptop monitor. No
effect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Public bug reported:
output of lsb_release -rd:
Description:Ubuntu 20.04 LTS
Release:20.04
I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade
was run my external
HDMI monitor was plugged in, after the update, when I reboot, the internal
monitor shows the b
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
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
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&#
.
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
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
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
--
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
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&#
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
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-
$ 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
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,
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
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
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
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
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
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
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
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
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
** 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
** 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
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
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
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 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
search for "r8168 for 4.15 kernel" and you will see problem from across
many linux distributions.
I am trying to follow
https://www.unixblogger.com/2016/08/11/how-to-get-your-realtek-
rtl8111rtl8168-working-updated-guide/
and change the "more stable" r8168. Neither the Ubuntu repo of r8168
nor
I've been having the same problem after resume. However, although de-
modprobe-ing and re-modprobe-ing enables the 'eth0' to be renamed as
'enp2s0', finally it fizzles out with
Jul 06 02:13:24 craig-desktop NetworkManager[5649]: [1530868404.9510]
device[
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 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
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
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
1 - 100 of 321 matches
Mail list logo
