I almost forgot about this; 4.17.19-041719-lowlatency has been running
fine now for 16 days. I'm going to switch to 4.18.0-13-lowlatency and
confirm the problem still exists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Just experienced the same symptom of a complete, silent, freeze with:
-- Logs begin at Sun 2018-04-01 13:42:23 BST, end at Wed 2018-11-28 10:33:23
GMT. --
Nov 20 10:48:10 T300CHI kernel: microcode: microcode updated early to revision
0x2b, date = 2018-03-22
Nov 20 10:48:10 T300CHI kernel: Linux
Five days running on 4.16.18-041618-lowlatency and had no problems so
I'm going to try the mainline build of v4.17.19.
--
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/1803960
Title:
This hang is affecting all mainline builds (from the kernel PPA) up to
and including 4.20-rc4.
The only version that doesn't appear to be affected is
4.15.0-38-lowlatency.
I'll start working backward from the 4.18* versions to try to narrow
where the apparent regression begins so that a bisect
I've been using the 4.18.0-12-lowlatency kernel from cosmic and not had
any freeze-ups in the last 48 hours. I'll continue monitoring and report
back after a few more days.
Because there are lots of reports of Intel Baytrail CPUs suffering
freezes due to c-states I want to make clear the CPU here
Public bug reported:
I've been using 18.04 on an Asus T300CHI without issue until I decided
to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency-
hwe-18.04-edge.
Since then the system randomly but regularly completely hangs. Only a
hard power-off resolves it.
Frustratingly there
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
** This bug has been marked a duplicate of bug 1542939
system freeze after vt switching
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
** This bug has been marked a duplicate of bug 1542939
system freeze after vt switching
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
** This bug has been marked a duplicate of bug 1542939
system freeze after vt switching
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
** This bug has been marked a duplicate of bug 1542939
system freeze after vt switching
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
** This bug has been marked a duplicate of bug 1542939
system freeze after vt switching
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This has *just* had a fix committed upstream and is hoped to be
available in v5.0. Could we get it backported to the LTS kernels?
commit ed20151a7699bb2c77eba3610199789a126940c4
Author: Ville Syrjälä
Date: Tue Nov 27 20:20:04 2018 +0200
drm/vblank: Allow dynamic per-crtc max_vblank_count
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
** This bug has been marked a duplicate of bug 1542939
system freeze after vt switching
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This has *just* had a fix committed upstream and is hoped to be
available in v5.0. Could we get it backported to the LTS kernels?
commit ed20151a7699bb2c77eba3610199789a126940c4
Author: Ville Syrjälä
Date: Tue Nov 27 20:20:04 2018 +0200
drm/vblank: Allow dynamic per-crtc max_vblank_count
*** This bug is a duplicate of bug 1542939 ***
https://bugs.launchpad.net/bugs/1542939
Based on the original report's JournalErrors.txt showing:
"vblank wait timed out on crtc 0"
marking this as a duplicate of the master bug #1542939
** This bug has been marked a duplicate of bug 1542939
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
Marking this as a duplicate of bug #1813745 since that already has a
test kernel build available which you should try, and if it solves the
issue, confirm on that bug.
** This bug has been marked a
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
** This bug is no longer a duplicate of bug 1813765
Regression/crash in i915 for 4.15.0-44.47
** This bug has been marked a duplicate of bug 1813745
ubuntu 18-04 hangs on graphical start with kernel
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
Upstream commit ID is be1c63c8017bb00a4
--
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/1813745
>From an initial reading of the commit history I suspect the issue may be
caused by e417085e79136d9f955 "drm/i915/dp: Send DPCD ON for MST before
phy_up" which deals with power transitions during monitor
connect/disconnect.
--
You received this bug notification because you are a member of Kernel
Initial summary of the changes affecting i915 specifically:
gitlog Ubuntu-4.15.0-43.46..Ubuntu-4.15.0-44.47 -- drivers/gpu/drm/i915
d2da7cbf2ae0 2019-01-14 09:28:55 + N Ville Syrjälä drm/i915: Fix PIPESTAT
irq ack on i965/g4x
e417085e7913 2019-01-14 09:28:55 + N Lyude Paul drm/i915/dp:
The 4.15.0-44 kernel in in the bionic-proposed pocket. Looks like we
need to pull it due to this regression until this is resolved.
--
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/1813765
Can we collect more information about the circumstances in which this
happens, since these can often be crucial in narrowing down the
possibilities and identifying a solution?
1. Does the problem occur if the system is completely powered off
between reboots (as opposed to what is called a 'warm'
15:38 TJ-, for a brief moment i saw 2-3 lines of text, first line
is "error: no video mode activated"
15:38 was unable to see more.
15:38 but this is a successful boot no purple screen this time
15:38 Jackneill: so, GRUB_TERMINAL=console was successfully booted to
desktop?
15:39
This looks to be related to LP: #829620 "intel-microcode on ASUS makes
kernel stuck during loading initramfs on bionic-updates, bionic-
security" which until now we thought only affected particular models.
Intel are aware, and this issue is being tracked in that bug.
--
You received this bug
Steve: Another possible system affected where disabling microcode
loading appears to have fixed it. I'll leave it to you to decide whether
that is a duplicate of this issue though:
LP: #1829402 "Purple screen hangup during boot"
Tom and myself have spent some considerable time with the affected
** Summary changed:
- Possible memory leak due to PCI AER faults even with pci=noaer
+ rtlwifi: aggresive memory leak
--
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/1831751
Title:
** Description changed:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1831751
Title:
rtlwifi: aggresive memory leak
Status in linux
Packages for 4.18.0-20.21-kmemleak are currently building in my bug-
fixes PPA. See
https://launchpad.net/~tj/+archive/ubuntu/bugfixes/+packages
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Description changed:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't
** Description changed:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't
** Attachment added: "dmesg after startup"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268933/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lspci -vvvnnk"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268932/+files/lspci-vvvnnk.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "kern.log OOM extract from earlier GUI-based boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268935/+files/kern.OOM.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Attachment added: "ps -efly at startup"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268936/+files/ps-efly.nogui-at-startup.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lspci -tvvvnn"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268931/+files/lspci-tvvvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
: (unassigned) => TJ (tj)
--
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/1831751
Title:
Possible memory leak due to PCI AER faults even with pci=noaer
Status in linux package in Ubunt
** Attachment added: "dmesg after leaving overnight"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268934/+files/dmesg.after-overnight.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "PCI AER error log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268930/+files/pci_aer.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't
The problem here is the installer failed to build/install initrd.img.
After installing into a LVM LV via libvirt and seeing the error I
mounted the disk image contained in the LV and explored:
$ sudo losetup -f --show -P /dev/VG02/lubuntu1910
/dev/loop5
$ sudo mount /dev/loop5p1 /mnt/target
$
It appears from the screenshot the panic is occurring because the
initramfs /init script is failing to find and mount the real root file-
system.
You can drop to a busybox shell in the initramfs by adding a kernel-
command line option manually in the GRUB boot menu.
Tap Esc key to get to the
After many hours diving down rabbit holes it turns out this is due to a
major change in the behaviour of update-initramfs introduced by Debian
in July 2018 which made its way into the Ubuntu archive end of april
2019.
01:02 Right! initramfs-tools had a MAJOR import from Debian with
The problem seems to be in the calamares configuration. The initramfs
task is being called before the target's live-* packages have been
removed. This is specifically warned about in the calamares initramfs
module but we see the timestamps of the initramfs task are before the
live-* packages are
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
We have a second bug that causes the call by update-
initramfs::get_sorted_versions() to report nothing when calling
(/usr/bin/) "linux-versions list".
This because the target root file-system is copied from the
filesystem.squashfs on the ISO which does NOT contain a
/boot/vmlinuz-$(uname -r).
I should have made clear, this 'second bug' is the only bug.
initrmafs-tools is in the clear - it wasn't finding a kernel image
because there wasn't one when update-initramfs was executed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Or is it? Actually I not, because the test in update-
initramfs::get_sorted_versions() expects an existing
initrd.img-$version:
get_sorted_versions()
{
version_list="$(
linux-version list |
while read -r version; do
test -e
** Summary changed:
- kernel bug causes i915 modesetting to not work
+ regression: between 4.15.0-45 and 4.15.0-50 - i915 vmalloc_fault
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like this is the likely candidate:
commit 7fa1a35564b270e940111c31828e553bff8f063b
Author: Gustavo A. R. Silva
Date: Thu Aug 2 22:40:19 2018 -0500
drm/i915/kvmgt: Fix potential Spectre v1
info.index can be indirectly controlled by user-space, hence leading
to a
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
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/1831751
Title:
rtlwifi: aggresive memory leak
Status in li
e. A short time after that I tried
to use that auto-mount directory again ("/home/tj/SourceCode") and the
shell hung. I tried from several more shells with different commands
with the same result.
Initially couldn't see any clues in the logs but after a while the
kernel dump
time after that I tried
to use that auto-mount directory again ("/home/tj/SourceCode") and the
shell hung. I tried from several more shells with different commands
with the same result.
Initially couldn't see any clues in the logs but after a while the
kernel dumped a couple of stack trace
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/1829620
Title:
cryptsetup stuck at loading initramfs
Status in cryptsetup package in Ubuntu:
New
Status in linux package in
Mark
I just realised your report isn't about cryptsetup being the problem and
you never reach the initialramfs shell.
Your report that the last thing you see is "my system gets stuck at
"Booting, Loading initramfs" tells us the kernel isn't starting. Those
messages come from GRUB when it loads
Mark:
With a LUKS encrypted system, when a new kernel is installed "update-
initramfs -u -k $KERNEL_VERSION" is executed.
As part of that cryptsetup hooks scripts are called. They examine
/etc/fstab and /etc/crypttabto determine if the root file-system, or
swap (which may be used for
Mark:
An additional kernel command-line option that might reveal more would be
remove "quiet splash" and add "debug early_print=XXX" where XXX is vga
for BIOS-mode or efi for UEFI mode boots.
You may find "earlycon" added into the mix may also add more early
messages.
See
** Changed in: linux (Ubuntu Disco)
Assignee: TJ (tj) => (unassigned)
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Upstream commit:
commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
Author: Larry Finger
Date: Sat Nov 17 20:55:03 2018 -0600
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO"), calling
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
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/1811869
Title:
Alienware m15 takes very long to boot Ubuntu
Sta
Request for cherry-pick sent to kernel-team mailing list 27 June 2019.
** Also affects: linux via
https://github.com/lwfinger/rtlwifi_new/issues/401
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is
Continuing issues up to and including 5.0.0-8. Experienced three lock-
ups today.
I strongly suspect the iwlwifi device but as the lock up is total and
silent there are zero clues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
On an 18.04 amd64 system dm-verity reports:
device-mapper: table: 253:20: verity: Invalid number of feature args
device-mapper: ioctl: error adding target to table
when trying to use "veritysetup" to create a previously formatted verity
device that uses FEC. Without FEC it
** Summary changed:
- dm-verity: Invalid number of feature args
+ "dm-verity: Invalid number of feature arg" with FEC due to "#
CONFIG_DM_VERITY_FEC is not set"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
On an 18.04 amd64 system dm-verity reports:
device-mapper: table: 253:20: verity: Invalid number of feature args
device-mapper: ioctl: error adding target to table
when trying to use "veritysetup" to create a previously formatted verity
device that uses
Could very likely be, or closely related to:
https://bugzilla.kernel.org/show_bug.cgi?id=199349
If the issue is RCU (Read-Copy-Update) or Memory-Management related and
specific to the AMD Turion X2 the most obvious suspect commits between
v4.6.2..v4.6.3 are:
$ gitlog v4.6.2..v4.6.3 -- mm/
The linked github repository doesn't break out whatever the fix is to
the rtsx_pci driver is. Therefore it is all but impossible to figure out
what was changed.
Another user reported this today with 5.0.0-27-generic where 64GB cards
are readable but 256GB cards are not. It isn't clear if the
Austin, thanks for confirming that repository solves the issue for you.
I'll try to make a diff of the original commit to that repository
against the Linux mainline driver at the same date, maybe we can be
lucky and it'll make the required change clear so we can test it in
Ubuntu and then get it
Just to be clear the device Austin is dealing with is:
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI
Express Card Reader [10ec:5227] (rev 01)
Subsystem: Hewlett-Packard Company RTS5227 PCI Express Card Reader
[103c:804e]
Kernel driver in use:
There are no logs required; this is a feature enhancement request
** 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.
Public bug reported:
Move "pci-hyperv.ko" to the primary kernel image package.
Whilst attempting a 20.04 install into a Microsoft Windows Hyper-V guest
that uses Discrete Device Assignment (DDA a.k.a. PCI pass-through) for
2x NVMe SSDs and Intel i350-T4 quad-port Gigabit Ethernet we found that
May be fixed by upstream commits:
7b7d897e8898 2020-07-24 12:34:42 +0200 N shirley her mmc: sdhci-pci-o2micro:
Add HW tuning for SDR104 mode
cdd2b769789a 2020-07-24 12:30:36 +0200 N shirley her mmc: sdhci-pci-o2micro:
Bug fix for O2 host controller Seabird1
--
You received this bug
Is part of the issue here that some (most) initramfs-tools created
images have an uncompressed early CPU microcode firmware prefixed ?
That is stored as ASCII CPIO which is why Con see's that reported by
'file' since that tool checks the magic signatures at start of a file.
binwalk reveals more
** Description changed:
This report is related to a problem reported in IRC #ubuntu whereby
(Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot
time but can later.
Appears to be a race condition between the wifi chipset setting up the
device and enabling the
Public bug reported:
This report is related to a problem reported in IRC #ubuntu whereby
(Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot
time but can later.
Appears to be a race condition between the wifi chipset setting up the
device and enabling the attached USB
User is long-gone after workaround solved their issue. This report is
FYI in case other users hit the same error messages.
--
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/1940332
Title:
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1574341/+attachment/5538304/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Although most other issues are solved there is still no multitouch for
this device with kernel v5.15 and xserver-xorg 1.20.13-1ubuntu1 using
Kubuntu 21.10.
# xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4
Recent kernels: 6.8.0-25 from Noble and the mainline kernel builds from
e.g:
https://kernel.ubuntu.com/mainline/v6.8/amd64/
Used for ensuring support for recent hardware.
If these will be rebuilt without module compression for LTS/HWE kernel
releases then this issue isn't so vital, but it will
Just for completeness,
I had this problem as well.
I did the steps mentiond:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
but It did not help. I noticed when i did sudo apt-get install -f
that I had kernel packages that wasn't needed so I followed the advice on the
screen
201 - 280 of 280 matches
Mail list logo
