[Kernel-packages] [Bug 989191] Re: Asus Zenbook UX31E powers off on plugin in/out AC adapter
** 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/989191 Title: Asus Zenbook UX31E powers off on plugin in/out AC adapter Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: When I have logged in to Unity and plug in or out AC adapter to Asus Zenbook UX31E, computer powers off. Sometimes this needs couple of tries (waiting or not waiting in between) when plugin in or out AC adapter. This problem doesn't occur when I have switched to console or when in LightDM login screen. Problem doesn't happen with MS Windows either. And yes, there's enough power in my battery too, I can boot up and use the computer without AC adapter. syslog prints these lines to stdout in console, when plugin AC adapter first out and then in: [ 869.521396] asus_wmi: Unknown key 57 pressed [ 874.704525] asus_wmi: Unknown key 58 pressed [ 876.993295] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id What you also need: 1) lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 2) I could guess kernel, but it happens _only_ when I have logged in to Unity (or Unity 2D)... 3) I expect that my computer doesn't power off. 4) Computer powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/989191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1437988] Re: 10ec:8179 wireless network and browser issues
** 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/1437988 Title: 10ec:8179 wireless network and browser issues Status in linux package in Ubuntu: In Progress Bug description: My wireless adapter connecting to my Linsksys wrt120N (firmware version 1.0.07) that constantly drops, only when running Ubuntu. Also no matter which browser I use it will arbitrarily max out the CPU usage and lock me up at times. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karl 2708 F pulseaudio /dev/snd/controlC1: karl 2708 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 29 22:45:34 2015 HibernationDevice: RESUME=UUID=e720cd76-77cb-4087-bfcc-876f10ecb858 InstallationDate: Installed on 2015-02-13 (44 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 0c45:6516 Microdia Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic.efi.signed root=UUID=fd43416e-9f3d-47f8-826d-37ffc7fdf565 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8014 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.02 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd08/25/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn8014:rvr10.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437988/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1356526] Re: [HP Elitebook 755] wifi not working in 14.04 LTS
** 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/1356526 Title: [HP Elitebook 755] wifi not working in 14.04 LTS Status in linux package in Ubuntu: In Progress Bug description: For the HP Elitebook 755 (SKU "J0X38AW#ABD" with BIOS Version "M84 Ver. 01.01") I found the following kernel parameters were needed to make the wireless controller work properly: "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" intremap=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1356526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Thanks Mathew. One note: I edited the SRU template to correct my name.
It is just "Tj" (pronounced Teej) not initials T.J.
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very long
command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution either.
- Thankfully, T.J. did some debugging of the root cause in comment #20
- [1], and found the issue occurs because of memcmp() in
- include/linux/fortify-string.h detecting an attempted out-of-bounds read
- when comparing buf and aliases[i].alias.
+ Thankfully, Tj did some debugging of the root cause in comment #20 [1],
+ and found the issue occurs because of memcmp() in include/linux/fortify-
+ string.h detecting an attempted out-of-bounds read when comparing buf
+ and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
- I know SAUCE patches are to be avoided if possible, but T.J's solution
- is minimal and fixes the root cause without the regression risk of
- backporting the entire mini C runtime, so I suggest we go with T.J's
+ I know SAUCE patches are to be avoided if possible, but Tj's solution is
+ minimal and fixes the root cause without the regression risk of
+ backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 board with Noble, running 6.8.
2) Edit /boot/grub/grub.cfg and add the following param to any boot entry with
Linux 6.8
testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5732f126a62b4232
3) Reboot the machine and select the boot entry in grub with the testparam as
above.
4) Observe kernel never boots.
[Where problems could occur]
We are changing command line parsing on ARM64 systems, such that we only
do a memcmp() with aliased entries if the parameter we are parsing has
the same length as an aliased entry. This really sh
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
@Shantur I also tested with your specific parameter in case it contained something to trigger this but it works fine: (initramfs) uname -a; cat /proc/cmdline Linux (none) 6.8.0-39-generic #39+TEST2069534v20240727b1-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 27 aarch64 GNU/Linux debug testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 I have a suspicion you've got the wrong kernel! There's a 6.8.0-39 in Noble -updates|-security and I would not be surprised if that is what your system actually booted. -- 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
@Shantur I confirm your results trying to boot that kernel image in QEMU and unfortunately there does not appear to be a debug symbols package generated so I cannot debug 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
I don't use Ubuntu kernels; build my own mainline but work on kernel
issues in mainline and Debian. I tested 144..157 length (interestingly
although arm64 professes to support 2048 characters the kernel messages
are truncated at around 1000 so don't show the entire thing
$ qemu-system-aarch64 -machine virt,gic-version=3 -cpu max,pauth-impdef=on -smp
2 -m 4096 -nographic -kernel
/srv/NAS/Sunny/SourceCode/builds/linux-aarch64/arch/arm64/boot/Image -append
"debug $( for l in {144..157}; do echo -n param$l=$(pwgen $((l-9)) 1)' '; done
)" -initrd rootfs/boot/initrd.img-6.8.12-arm64-debug
[0.00] Booting Linux on physical CPU 0x00 [0x000f0510]
[0.00] Linux version 6.8.12 (li...@iam.tj) (aarch64-linux-gnu-gcc
(Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #10 SMP Fri
Jul 26 13:57:53 BST 2024
[0.00] random: crng init done
[0.00] Machine model: linux,dummy-virt
...
[0.00] Kernel command line: debug
param144=aixootoo9ii0dieghaem2eehahqu9Aejeuka3ui8chain9ief3Ooth9lahgeiyiew3dio3PhahpeiShoh1ootoch2rae9quushei9yu4ge5uasi9peizooT8JohjieMuGh7ohs7
param145=noohieL5DaeghaeGh4nueQuugoowohj6fa0Jaive7meaghukoog8tho6De6ahga7sheighah2Raing9eitai3eeHi4Ahr7aixaiLoh3cheeG
hosa9eR4sohkajahwe1tha9aotha
param146=taesaekie3Vaiv2Neejohph0ozeile5daemu8beepha9Ojae8niev8nepaidaemu9uphaah4bongeiRahM5eichahTah6aegob8edee2xah6UaxahThee2puePua5ahchoqueixee
param147=ahZai6EeW1EejaGh6hen6eu6oov6wo3ooph5theide6OhGh5oog2Iel8oong1ighooboo7ohthoh2le5eeloog1agha0phaid5enaeQuohfoo3EijaemeiZ
9ohG5aichoo9shuiFee
param148=ieT6oogat5sheng9aeteigh4poohoongul5za7Eich5Abo2Aeraec0eingah5ahsh4Ooth9Phaithai3gethoo4piphie0zieHieYahngahbiitheingooshau4
chaepee2zeeWei5a
param149=eenga3ku8deongie7Oovahsoo7ao1zail8remu2ieshai6haemee2eingoophev6eeY5KeeChiemeu2Eaquuqu8ahk3oohovoh6vaijaexoodeesoetuucie7geeba
h5cad5aikoh6mo
param150=oopaiCh0thu1ioneed3apee9igieT7OaWedeemoop4izex9gaeRaequai6aavaephua4ahlooThaiquie4Gu8Eiyo8ohmai1aiye
...
[3.045515] Run /init as init process
[3.045717] with arguments:
[3.045852] /init
[3.045962] with environment:
[3.046098] HOME=/
[3.046206] TERM=linux
[3.046320]
param144=aixootoo9ii0dieghaem2eehahqu9Aejeuka3ui8chain9ief3Ooth9lahgeiyiew3dio3PhahpeiShoh1ootoch2rae9quushei9yu4ge5uasi9peizooT8Johj
ieMuGh7ohs7
[3.046913]
param145=noohieL5DaeghaeGh4nueQuugoowohj6fa0Jaive7meaghukoog8tho6De6ahga7sheighah2Raing9eitai3eeHi4Ahr7aixaiLoh3cheeGhosa9eR4sohkajah
we1tha9aotha
[3.047481]
param146=taesaekie3Vaiv2Neejohph0ozeile5daemu8beepha9Ojae8niev8nepaidaemu9uphaah4bongeiRahM5eichahTah6aegob8edee2xah6UaxahThee2puePua
5ahchoqueixee
[3.047963]
param147=ahZai6EeW1EejaGh6hen6eu6oov6wo3ooph5theide6OhGh5oog2Iel8oong1ighooboo7ohthoh2le5eeloog1agha0phaid5enaeQuohfoo3EijaemeiZ9ohG5
aichoo9shuiFee
[3.048466]
param148=ieT6oogat5sheng9aeteigh4poohoongul5za7Eich5Abo2Aeraec0eingah5ahsh4Ooth9Phaithai3gethoo4piphie0zieHieYahngahbiitheingooshau4c
haepee2zeeWei5a
[3.048992]
param149=eenga3ku8deongie7Oovahsoo7ao1zail8remu2ieshai6haemee2eingoophev6eeY5KeeChiemeu2Eaquuqu8ahk3oohovoh6vaijaexoodeesoetuucie7gee
bah5cad5aikoh6mo
[3.049508]
param150=oopaiCh0thu1ioneed3apee9igieT7OaWedeemoop4izex9gaeRaequai6aavaephua4ahlooThaiquie4Gu8Eiyo8ohmai1aiyeib9ahkaifeh3ahqu5joutugh
1hee7ShiePhieThai
[3.050024]
param151=aiVeiT2Aw0EenaizeeKaezei8eigei2Luov0ohdeeng6miekooZuD9ieci3oph6pahs9upid6Aesou6uiboongei7aVie2ushai8iex3quahzieH5eingaengao2
OhsheiHoo4Hiehei6N
[3.050564]
param152=eivohroQui8quoh5jeizoo1ook6toothahchei3Iethee6au6irae3quee8AhLae9FaceuZahsahqueig9iec1jae9fier9Ohmaengohpheing4eimaipah3pahs
h4uo1Eefauroong1hiz
[3.051316]
param153=juh6ahbu2raena5uocejaqueeduyohB6uasiex5ahtaiTieK3Ruol1ceijin4quah3Fee7ahthaiphoo8piaghaegomeez3aichee4doreiloh6dieL5chae0oor
ahth1shoz7cheesarood
[3.051860]
param154=ainaa7XahH8phoobeefaebaepaivee9kierohse7OopooshahphiengogahThood6qua3woh5aiziungae1sai6ao7phahW0Ooph6fahk0uph3wieghai1ootoh4
Oogei6Jaeboupheehepho
[3.052373]
param155=zienga1nee1CaiFeiv7Kae8ohma2ceejeif3pung2zi2shoigohn6choh6Oon7iaxie1Kua2waFoophier0uaf9aivoh1cee9chooha1phughohx8Abei9de9lai
kuaz6pheeD3pohbeic7sah
[3.052903]
param156=aiyahy5ieghoo5eenaipethei7chebi4thaek5iqu5eelah5au3Eishil5Aichae3guqueiPei2ahdeeghiteequeichooWah2othee1thee4Zohgo5deem9aigh
0eef2sha2wei0sed8aiquoo
[3.053432]
param157=iiph5iewudai5SahbiY4holoos3nis2Caeheibav0eu9EijaebahzeBuathei7xohngah
...
BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) cat /proc/cmdline
debug
param144=aixootoo9ii0dieghaem2eehahqu9Aejeuka3ui8chain9ief3Ooth9lahgeiyiew3dio3PhahpeiShoh1ootoch2rae9quushei9yu4ge5uasi9peizooT8JohjieMuGh7ohs7
param145=noohieL5DaeghaeGh4nueQuugoowohj6fa0Jaive7meaghukoog8tho6De6ahga7sheighah2Raing9eitai3eeHi4Ahr7aixaiLoh3cheeGhosa9eR4sohkajahwe1tha9aotha
param146=taesaekie3Vaiv2Neejohph0ozeile5daem
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
@Chris: no idea - someone in the Canonical kernel team needs to deal with 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
Upstream stable tree patch submission: https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_- PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u -- 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
My hunch about the length of struct aliases was correct; when a
parameter that is longer than the *entire* aliases struct element (146
characters) is compared the call to memcmp() is redirected to
"include/linux/fortify-string.h" [0] where checks are done to ensure
there are no out-of-bounds reads.
Because the 'buf' parameter is 146 characters long the call looks like:
memcmp("param146=...", aliases[i].alias, len + 1)
where 'len' is 146 and so 147 gets passed in. That triggers:
if (p_size < size || q_size < size)
fortify_panic(__func__);
because 'size' (from 'len + 1') is 147 and q_size is 146 ( size_t q_size
= __struct_size(q) )
('p' is `buf`, 'q' is 'aliases[i].alias' )
So, with a guard case to avoid calling memcmp() at all unless the
lengths match it works. I'll send the patch to the v6.8 stable tree
upstream.
$ qemu-system-aarch64 -machine virt,gic-version=3 -cpu max,pauth-impdef=on -smp
2 -m 4096 -nographic -kernel
/srv/NAS/Sunny/SourceCode/builds/linux-aarch64/arch/arm64/boot/Image -append
"debug
param146=ni4ohneo0oothieyeef9vo4ieth4yeiz6ohsiemae6aoy2asu9xei5eethoh0igaitha7laeghoot
haeph9xai7kier3aib7aejaengahghan2zojeebai3kad9meesh6eichaey2"
[0.00] Booting Linux on physical CPU 0x00 [0x000f0510]
[0.00] Linux version 6.8.12 (li...@iam.tj) (aarch64-linux-gnu-gcc
(Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #10 SMP Fri
Jul 26 13:57:53 BST 2024
[0.00] random: crng init done
[0.00] Machine model: linux,dummy-virt
...
[0.00] Kernel command line: debug
param146=ni4ohneo0oothieyeef9vo4ieth4yeiz6ohsiemae6aoy2asu9xei5eethoh0igaitha7laeghoothaeph9xai7kier3aib7aejae
ngahghan2zojeebai3kad9meesh6eichaey2
[0.00] Unknown kernel command line parameters
"param146=ni4ohneo0oothieyeef9vo4ieth4yeiz6ohsiemae6aoy2asu9xei5eethoh0igaitha7laeghoothaeph9xai7k
ier3aib7aejaengahghan2zojeebai3kad9meesh6eichaey2", will be passed to user
space.
[0]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/fortify-string.h?h=v6.8#n659
--
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/2069534
Title:
linux 6.8 fails to boot on arm64 if any param is more than 140 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Confirmed
Bug description:
Hi,
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 140 characters.
Test Machine
=
Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI
mode booting grubaa64.efi
Reproduced on
==
Ubuntu 22.04.4 with Linux HWE Proposed 6.8
Ubuntu 24.04 with Linux 6.8
Works on
=
Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9
Steps to reproduce
1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or
Ubuntu 22.04.4 install Linux HWE 6.8 from
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/proposed?field.series_filter=jammy
2. Edit /boot/grub/grub.cfg and add the following param to any boot
entry with Linux 6.8
testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5
3. Reboot the machine and select the boot entry in grub with the
testparam as above.
4. Observe kernel never boots.
Cause
After bisecting the kernel, I found that the bug was introduced in
Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
arm64: idreg-override: Avoid parameq() and parameqn()
This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
arm64: idreg-override: Move to early mini C runtime
That got merged to Linux 6.9-rc1 with commit
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Fix Options
=
Option 1.
For Linux 6.8 the safest fix would be to revert
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
arm64: idreg-override: Avoid parameq() and parameqn()
Option 2.
Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework
to Linux 6.8 with
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Merge tag 'arm64-upstream
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
My aim is not to revert a commit but to discover what the actual bug is and get it fixed in upstream stable 6.8 tree. I've isolated it to kernel-only by eliminating both firmware (UEFI) and boot-loader (GRUB) from the equation with: qemu-system-aarch64 -machine virt,gic-version=3 -cpu max,pauth-impdef=on -smp 2 -m 4096 -nographic -kernel ./vmlinuz-6.8.12-arm64-debug -append "debug param146=ni4ohneo0oothieyeef9vo4ieth4yeiz6ohsiemae6aoy2asu9xei5eethoh0igaitha7laeghoothaeph9xai7kier3aib7aejaengahghan2zojeebai3kad9meesh6eichaey2" This will hang. Removing one character from param146= so it is actually 145 characters and the kernel will start. Now I have a minimal reproducer I can attach gdb and debug 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
This was brought to my attention by Chris; looking at the code in commit dc3f5aae0638 parsing of an individual parameter will terminate prematurely if it is more than 255 characters and it will not be recognised as expected, with the remaining characters being parsed as an additional parameter. For aarch64 the default command-line length is 2048 characters. Having seem some examples of actual command-lines I'm not yet convinced this commit is the cause - I'm currently building a reproducer to test some ideas. One such is, looking at the Ubuntu 6.8 git commits, there's a patch from upstream that fixes a command-line overflow: commit 4e38935f02fa0 "init/main.c: Fix potential static_command_line memory overflow" ( upstream commit 46dad3c1e57897) We really need to see a complete kernel log capture using options "earlyprintk debug" to see at what stage it breaks (and what the kernel reports as the cmdline, and what exact kernel version it is); currently I'm not convinced its the kernel failing here, but rather, the initialramfs processing (since most of the kernel command-line arguments shown are not kernel parameters at all; root= is but the 'squash:' type prefix isn't handled by the kernel's init/ code.). I haven't looked at MAAS but the command lines indicate it may be adding scripts into the initialramfs that read the command-line. -- 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
With pr_debug() added into __parse_cmdline() there are no reports; last message is as always: EFI stub: Exiting boot services... -- 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
I think the cause here is staring us in the face; we have a do { ... }
while(1) loop wrapping this code. The only escape are the 2 return
statements. If neither trigger it'll spin, which is what the symptoms
seem to indicate.
1) "-- " as a parameter
2) !len (in other words, len==0)
In the first call to __parse_cmdline() bool parse_aliases == true so the
re-entrant call into itself with parse_aliases == false should be done
if the memcmp() finds any of the alises[i].alias in the current option.
Now, in the example command lines I've seen, none of the aliases is
present.
It surely cannot be coincidence though that we have:
#define FTR_ALIAS_NAME_LEN 30
#define FTR_ALIAS_OPTION_LEN 116
...
static const struct {
char alias[FTR_ALIAS_NAME_LEN];
char feature[FTR_ALIAS_OPTION_LEN];
} aliases[]
that means each element is 146 characters long - the length at which I
can trigger the bug.
--
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/2069534
Title:
linux 6.8 fails to boot on arm64 if any param is more than 140 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Confirmed
Bug description:
Hi,
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 140 characters.
Test Machine
=
Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI
mode booting grubaa64.efi
Reproduced on
==
Ubuntu 22.04.4 with Linux HWE Proposed 6.8
Ubuntu 24.04 with Linux 6.8
Works on
=
Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9
Steps to reproduce
1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or
Ubuntu 22.04.4 install Linux HWE 6.8 from
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/proposed?field.series_filter=jammy
2. Edit /boot/grub/grub.cfg and add the following param to any boot
entry with Linux 6.8
testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5
3. Reboot the machine and select the boot entry in grub with the
testparam as above.
4. Observe kernel never boots.
Cause
After bisecting the kernel, I found that the bug was introduced in
Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
arm64: idreg-override: Avoid parameq() and parameqn()
This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
arm64: idreg-override: Move to early mini C runtime
That got merged to Linux 6.9-rc1 with commit
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Fix Options
=
Option 1.
For Linux 6.8 the safest fix would be to revert
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
arm64: idreg-override: Avoid parameq() and parameqn()
Option 2.
Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework
to Linux 6.8 with
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Please revert the change in Linux 6.8
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: linux 6.8 fails to boot on arm64 if any param is more than 140 chars
I can reproduce the issue in a QEMU aarch64 virtual machine with both Ubuntu and Debian v6.8* kernels booting in EFI mode via GRUB, but here the length of the parameter that triggers it is 146 characters; eg: linux /boot/vmlinuz-6.8.12-arm64 root=uuid=06bc9a44-31ef-41b1-bfe1-e6383822dccd ro console=earlycon efi=debug debug earlyprintk param146=ni4ohneo0oothieyeef9vo4ieth4yeiz6ohsiemae6aoy2asu9xei5eethoh0igaitha7laeghoothaeph9xai7kier3aib7aejaengahghan2zojeebai3kad9meesh6eichaey2 And the kernel hangs in the EFI libstub just after exiting boot services. I'm instrumenting the code to get to the root cause. -- 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/2069534 Title: linux 6.8 fails to boot on arm64 if any param is more than 140 chars Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Bug description: Hi, Linux 6.8 kernel fails to boot on ARM64 when any Linux command line param is more than 140 characters. Test Machine = Rockchip RK3399 based RockPro64 with latest u-boot 2024.07-rc3 in EFI mode booting grubaa64.efi Reproduced on == Ubuntu 22.04.4 with Linux HWE Proposed 6.8 Ubuntu 24.04 with Linux 6.8 Works on = Ubuntu 22.04.4 with Linux 5.15, 6.6, 6.7, 6.9 Steps to reproduce 1. Install Ubuntu 24.04 which comes with Linux 6.8 by default or Ubuntu 22.04.4 install Linux HWE 6.8 from https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/proposed?field.series_filter=jammy 2. Edit /boot/grub/grub.cfg and add the following param to any boot entry with Linux 6.8 testparam=f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b54edcba27e5f790d47911a4cc3e726d8d256878d3df9175c020e0f081c381e7b5 3. Reboot the machine and select the boot entry in grub with the testparam as above. 4. Observe kernel never boots. Cause After bisecting the kernel, I found that the bug was introduced in Linux 6.8-rc1 ( and released in Linux 6.8 ) with commit commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() This got fixed with Linux 6.9-rc1 and released in Linux 6.9 as part of rework commit e223a449125571daa62debd8249fa4fc2da0a961 Author: Ard Biesheuvel Date: Wed Feb 14 13:28:50 2024 +0100 arm64: idreg-override: Move to early mini C runtime That got merged to Linux 6.9-rc1 with commit commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Fix Options = Option 1. For Linux 6.8 the safest fix would be to revert commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9 Author: Ard Biesheuvel Date: Wed Nov 29 12:16:12 2023 +0100 arm64: idreg-override: Avoid parameq() and parameqn() Option 2. Unless Ubuntu Team is interested in bringing the whole Mini C Runtime rework to Linux 6.8 with commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b Merge: fe46a7dd189e 1ef21fcd6a50 Author: Linus Torvalds Date: Thu Mar 14 15:35:42 2024 -0700 Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux Please revert the change in Linux 6.8 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed
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 make testing a recent kernel (often asked for when hitting hardware/kernel issues) extremely challenging and for most non-technical operators, impossible. On balance I'd think adding those two wildcards is a win. -- 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/2057808 Title: [LTS] cryptsetup-initramfs fails when kernel modules are compressed Status in cryptsetup package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in cryptsetup source package in Jammy: New Status in linux source package in Jammy: Incomplete Bug description: This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules" https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120 where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines. It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_* I think the fix needs cherry-picking into LTS release(s). https://salsa.debian.org/cryptsetup- team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750 At boot-time it results in the cryptic (pun intended) messages: device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch
** 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. https://bugs.launchpad.net/bugs/1574341 Title: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in xinput package in Ubuntu: Triaged Bug description: This is a related but separate issue to bug #1480673 "Asus T300 CHI bluetooth Touchpad is recognized incorrectly". Affecting this digitizer is also bug #1574028 "Asus T300 CHI: touchscreen digitiser missing at boot". Using 16.04 amd64 Ubuntu (unity). In this case the USB-attached "Synaptics Touch Digitizer V04" fails to provide any multitouch functionality. 'evtest' shows multitouch events happening. $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 06cb:11ef Synaptics, Inc. Bus 001 Device 005: ID 04f2:b3d5 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ASUS T300CHI DOCKING id=9[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=11 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ USB2.0 HD UVC WebCam id=10 [slave keyboard (3)] ↳ Asus WMI hotkeys id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ ASUS T300CHI DOCKING id=15 [slave keyboard (3)] $ ll /sys/bus/hid/drivers/hid-multitouch/ total 0 drwxr-xr-x 2 root root0 Apr 24 18:12 ./ drwxr-xr-x 4 root root0 Apr 24 18:12 ../ lrwxrwxrwx 1 root root0 Apr 24 18:12 0003:06CB:11EF.0003 -> ../../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11EF.0003/ --w--- 1 root root 4096 Apr 24 18:12 bind lrwxrwxrwx 1 root root0 Apr 24 18:12 module -> ../../../../module/hid_multitouch/ --w--- 1 root root 4096 Apr 24 18:12 new_id --w--- 1 root root 4096 Apr 24 18:12 uevent --w--- 1 root root 4096 Apr 24 18:12 unbind To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1574341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574341] Re: [Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch
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[slave pointer (2)]
⎜ ↳ Asus TouchPad id=10 [slave pointer (2)]
⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Mouse id=15 [slave pointer
(2)]
⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=16 [slave pointer (2)]
⎜ ↳ BT5.0 Mouse id=20 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ Power Button id=6[slave keyboard (3)]
↳ Asus Wireless Radio Control id=7[slave keyboard (3)]
↳ Video Bus id=8[slave keyboard (3)]
↳ Sleep Button id=9[slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=11 [slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=12 [slave keyboard (3)]
↳ ASUS T300CHI DOCKING id=13 [slave keyboard (3)]
↳ USB2.0 HD UVC WebCam: USB2.0 HD id=14 [slave keyboard (3)]
↳ SYNAPTICS Synaptics Touch Digitizer V04 Stylusid=17 [slave
keyboard (3)]
↳ Asus WMI hotkeys id=18 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=19 [slave keyboard (3)]
# for id in {15..17}; do xinput --list $id; done
SYNAPTICS Synaptics Touch Digitizer V04 Mouse id=15 [slave pointer (2)]
Reporting 7 classes:
Class originated from: 15. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right"
Button state:
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 15. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 15.00
flags: 0x0
Class originated from: 15. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 15.00
flags: 0x0
SYNAPTICS Synaptics Touch Digitizer V04 id=16 [slave pointer (2)]
Reporting 6 classes:
Class originated from: 16. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right"
"Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz
Wheel Right"
Button state:
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 0:
Label: Abs MT Position X
Range: 0.00 - 65535.00
Resolution: 0 units/m
Mode: absolute
Current value: 44291.812165
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 1:
Label: Abs MT Position Y
Range: 0.00 - 65535.00
Resolution: 0 units/m
Mode: absolute
Current value: 39378.849306
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.00 - -1.00
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 3:
[Kernel-packages] [Bug 1940332] Re: hci0: Failed to send firmware data (-38)
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: hci0: Failed to send firmware data (-38) Status in linux package in Ubuntu: Confirmed Bug description: 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 interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem. The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() and/or https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 as the result of the calls: err = wait_event_interruptible_timeout(...) since only these are followed by calls to net/bluetooth/lib.c::bt_to_errno() and that is the only function that can return -ENOSYS (-38) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 default: return ENOSYS; } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940332] Re: hci0: Failed to send firmware data (-38)
** 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 attached USB interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. - Reporting user tells us this works around the problem + Reporting user tells us this works around the problem. + + The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() + and/or + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 + + as the result of the calls: + + err = wait_event_interruptible_timeout(...) + + since only these are followed by calls to + net/bluetooth/lib.c::bt_to_errno() and that is the only function that + can return -ENOSYS (-38) + + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 + + default: + return ENOSYS; + } -- 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: hci0: Failed to send firmware data (-38) Status in linux package in Ubuntu: Confirmed Bug description: 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 interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem. The code responsible is net/bluetooth/hci_request.c::__hci_cmd_sync_ev() and/or https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n147 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/hci_request.c#n234 as the result of the calls: err = wait_event_interruptible_timeout(...) since only these are followed by calls to net/bluetooth/lib.c::bt_to_errno() and that is the only function that can return -ENOSYS (-38) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/lib.c#n132 default: return ENOSYS; } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940332] [NEW] hci0: Failed to send firmware data (-38)
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 interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "Kernel Log" https://bugs.launchpad.net/bugs/1940332/+attachment/5518599/+files/kernel.log ** Changed in: linux (Ubuntu) Status: New => 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/1940332 Title: hci0: Failed to send firmware data (-38) Status in linux package in Ubuntu: Confirmed Bug description: 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 interface to the Bluetooth device fully. Bluetooth: hci0: Failed to send firmware data (-38) Bluetooth: hci0: Intel reset sent to retry FW download The solution is to introduce a delay in loading the 'btusb' module: echo "install btusb /usr/bin/sleep 2; /usr/sbin/modprobe --ignore- install btusb" | sudo tee -a /etc/modprobe.d/btusb.conf This imposes a 2 second delay before the 'btusb' module is loaded. Reporting user tells us this works around the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490347] Re: [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes
Another follow-up. Had the same problem with 20.04 amd64. My solution detailed above would not work when using the GUI where the Blueman bluetooth applet was in the notification area. Eventually I found it worked from a real tty console (switched from GUI to tty2 with Ctrl+Alt+F2) and running the bluetoothctl sequence as detailed. ** Summary changed: - [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes + [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490347 Title: [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes Status in Bluez Utilities: New Status in bluez package in Ubuntu: Triaged Status in bluez source package in Wily: Triaged Status in bluez source package in Xenial: Confirmed Bug description: Bluez 5.3 does not have support for pairing with devices (such as keyboards) that use a PIN code for pairing. A mouse pairs correctly. From my research it seems as if the ChromeOS project developed patches to fix this and they are supposed to have been included in Bluez 5.4 (that statement dated April 2013) but I've not yet identified them. "The agent's implementation in bt_console/bluetoothctl upstream is incomplete, missing some functions like DisplayPincode." https://code.google.com/p/chromium/issues/detail?id=222661 Along with the loss of Headset profiles meaning VoIP applications can no longer use HSP/HFP profiles (requiring functionality yet to land in Ofono) this cripples the use of Bluetooth for much else than A2DP or mouse input. Attempting to pair with, for example, an Apple Wireless Keyboard that pairs and works correctly with 14.04 LTS, fails totally on 15.10. The mouse shown below is already paired, connected, and working. $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48 [bluetooth]# pair 00:0A:95:4B:BD:C2 Attempting to pair with 00:0A:95:4B:BD:C2 >>> at this point nothing is happening >>> so I press Enter on the keyboard and... [agent] PIN code: 791166 >>> I type 791166 Enter and ... [agent] PIN code: 237744 >>> I type 237744 Enter and... [agent] PIN code: 358866 >>> I type 358866 Enter and... Request PIN code [agent] Enter PIN code: 1234 >>> I type 1234 Enter on the keyboard and 1234 at the prompt... Failed to pair: org.bluez.Error.AuthenticationFailed This cycle repeats in various permuations. Sometimes the final "Request PIN code" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules
** 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/1906131
Title:
No rule to make target 'scripts/module.lds' while building out-of-tree
modules
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild:
preprocess module linker script" ) that affects where and how
scripts/module.lds is used and causes external modules to fail to
build since that linker script is not shipped in the
linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today
installed v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
See the LKML discussion:
https://lkml.org/lkml/2020/8/31/455
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
make[3]: *** Waiting for unfinished jobs
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1703: modules] Error 2
make[1]: Leaving directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906131/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906131] [NEW] No rule to make target 'scripts/module.lds' while building out-of-tree modules
Public bug reported:
kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
module linker script" ) that affects where and how scripts/module.lds is
used and causes external modules to fail to build since that linker
script is not shipped in the linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today installed
v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
See the LKML discussion:
https://lkml.org/lkml/2020/8/31/455
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
make[3]: *** Waiting for unfinished jobs
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1703: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #975571
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571
** Also affects: linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571
Importance: Unknown
Status: Unknown
** Description changed:
- kernel v5.10-rc1 introduced a change that affects where and how
- scripts/module.lds is used and causes external modules to fail to build
- since that linker script is not shipped in the linux-{image,header}
- packages.
+ kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
+ module linker script" ) that affects where and how scripts/module.lds is
+ used and causes external modules to fail to build since that linker
+ script is not shipped in the linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today installed
v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
-
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
- CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
- MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
+ CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
+ MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
make[3]: *** Waiting for unfinished jobs
- CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
+ CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.mod.o
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1703: modules] Error 2
make[1]: Leaving directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
** Description changed:
kernel v5.10-rc1 introduced a change ( 596b0474d3d9 "kbuild: preprocess
module linker script" ) that affects where and how scripts/module.lds is
used and causes external modules to fail to build since that linker
script is not shipped in the linux-{image,header} packages.
I've been testing the mainline PPA kernel v5.10-rc5 and today installed
v4l2loopback-dkms and hit this issue.
It will affect all DKMS packages. Ubuntu carries 39 DKMS packages.
+
+ See the LKML discussion:
+
+ https://lkml.org/lkml/2020/8/31/455
+
DKMS make.log for v4l2loopback-0.12.3 for kernel 5.10.0-051000rc5-lowlatency
(x86_64)
Sun 29 Nov 02:48:58 GMT 2020
Building v4l2-loopback driver...
make -C /lib/modules/5.10.0-051000rc5-lowlatency/build
M=/var/lib/dkms/v4l2loopback/0.12.3/build modules
make[1]: Entering directory
'/usr/src/linux-headers-5.10.0-051000rc5-lowlatency'
CC [M] /var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.o
MODPOST /var/lib/dkms/v4l2loopback/0.12.3/build/Module.symvers
make[3]: *** No rule to make target 'scripts/module.lds', needed by
'/var/lib/dkms/v4l2loopback/0.12.3/build/v4l2loopback.ko'. Stop.
[Kernel-packages] [Bug 1905993] Re: Actual kernel don't want to make more than 64 cpus available
** Project changed: launchpad => 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/1905993 Title: Actual kernel don't want to make more than 64 cpus available Status in linux package in Ubuntu: New Bug description: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901401] Re: SD card does not work on linux, but window (O2Micro)
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 notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901401 Title: SD card does not work on linux, but window (O2Micro) Status in linux package in Ubuntu: Confirmed Bug description: I try to use a micro SD card (256GB, connected via microSD-to-SD adapter) on my laptop. I could not ... - ...mount my (micro) SD card - ...format with gparted - ...format with "disks" disks error: --- Error wiping device: failed to probe the device "/dev/mmcblk0" (udisks error-quark,0) gparted error: --- "Input/output error during read on /dev/mmcblk0" `lspci -nn` shows: --- SD Host controller [0805]: O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01) Output of `journalctl -f` when inserting - 10月 25 20:21:08 myuser kernel: mmc0: new ultra high speed SDR104 SDXC card at address 59b4 10月 25 20:21:08 myuser kernel: mmcblk0: mmc0:59b4 EE4S5 239 GiB 10月 25 20:21:08 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:08 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:09 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:09 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:09 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:09 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:09 myuser kernel: ldm_validate_partition_table(): Disk read failed. 10月 25 20:21:09 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:09 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:10 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:10 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:10 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: Dev mmcblk0: unable to read RDB block 0 10月 25 20:21:11 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:11 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:11 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:11 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:11 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:11 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 3, async page read 10月 25 20:21:12 myuser kernel: mmcblk0: unable to read partition table 10月 25 20:21:13 myuser fwupd[19538]: 11:21:13:0166 FuEngine failed to add udev device /sys/devices/pci:00/:00:1d.0/:03:00.0/mmc_host/mmc0/mmc0:59b4/block/mmcblk0: failed get ffu_capable for (null) I tried: - - Another micoSD-SD adapter: No change - Rebooting: No change I can do: --- - Use the card under Win 10: Same reader, same adapter, same card - Use other SD/microSD cards with the same reader under Linux lsb_release -rd -- Description: Ubuntu 20.04 Release: 20.04 and Description: Ubuntu 20.10 Release: 20.10 digging in `journalctl -b 0` --- xhci_hcd :00:14.0: xHCI Host Controller xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: xHCI H
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
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 detail. -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859212] Re: Move pci-hyperv.ko from linux-modules-extra to support installation to Hyper-V using DDA
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.
https://bugs.launchpad.net/bugs/1859212
Title:
Move pci-hyperv.ko from linux-modules-extra to support installation to
Hyper-V using DDA
Status in linux package in Ubuntu:
Confirmed
Bug description:
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 the installer kernel (ubuntu-server) does not include
the "drivers/pci/controller/pci-hyperv.ko" module that is required for
Linux to discover the Hyper-V para-virtualised PCI bus.
Eventually discovered the module in the installer ISO's
/pool/main/l/linux/linux-modules-extra-`uname-r`_amd64.deb and were
able to manually install it with:
# udpkg --unpack /cdrom/pool/main/l/linux/linux-modules-extra-`uname
-r`_amd64.deb
# depmod
After which it could be loaded ("pci-hyperv-intf.ko" is already
installed):
# modprobe pci-hyperv-intf
# modprobe pci-hyperv
At this point it is possible to use the NVMe devices.
We used 'mdadm' to create a RAID-1 mirror and then returned to the
installer and were able to use the partitioner to install the root
file-system to NVMe, although it is worth noting that GRUB has to be
installed to a Hyper-V virtual storage device (a Hyper-V file on NTFS)
in order to boot since the guest UEFI nor GRUB can 'see' any PCI
devices without help from a para-virtualisation driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859212/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859212] [NEW] Move pci-hyperv.ko from linux-modules-extra to support installation to Hyper-V using DDA
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
the installer kernel (ubuntu-server) does not include the
"drivers/pci/controller/pci-hyperv.ko" module that is required for Linux
to discover the Hyper-V para-virtualised PCI bus.
Eventually discovered the module in the installer ISO's
/pool/main/l/linux/linux-modules-extra-`uname-r`_amd64.deb and were able
to manually install it with:
# udpkg --unpack /cdrom/pool/main/l/linux/linux-modules-extra-`uname
-r`_amd64.deb
# depmod
After which it could be loaded ("pci-hyperv-intf.ko" is already
installed):
# modprobe pci-hyperv-intf
# modprobe pci-hyperv
At this point it is possible to use the NVMe devices.
We used 'mdadm' to create a RAID-1 mirror and then returned to the
installer and were able to use the partitioner to install the root file-
system to NVMe, although it is worth noting that GRUB has to be
installed to a Hyper-V virtual storage device (a Hyper-V file on NTFS)
in order to boot since the guest UEFI nor GRUB can 'see' any PCI devices
without help from a para-virtualisation driver.
** 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/1859212
Title:
Move pci-hyperv.ko from linux-modules-extra to support installation to
Hyper-V using DDA
Status in linux package in Ubuntu:
New
Bug description:
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 the installer kernel (ubuntu-server) does not include
the "drivers/pci/controller/pci-hyperv.ko" module that is required for
Linux to discover the Hyper-V para-virtualised PCI bus.
Eventually discovered the module in the installer ISO's
/pool/main/l/linux/linux-modules-extra-`uname-r`_amd64.deb and were
able to manually install it with:
# udpkg --unpack /cdrom/pool/main/l/linux/linux-modules-extra-`uname
-r`_amd64.deb
# depmod
After which it could be loaded ("pci-hyperv-intf.ko" is already
installed):
# modprobe pci-hyperv-intf
# modprobe pci-hyperv
At this point it is possible to use the NVMe devices.
We used 'mdadm' to create a RAID-1 mirror and then returned to the
installer and were able to use the partitioner to install the root
file-system to NVMe, although it is worth noting that GRUB has to be
installed to a Hyper-V virtual storage device (a Hyper-V file on NTFS)
in order to boot since the guest UEFI nor GRUB can 'see' any PCI
devices without help from a para-virtualisation driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859212/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735099] Re: Realtek Card Reader not working (kernel driver)
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: rtsx_pci Kernel modules: rtsx_pci -- 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/1735099 Title: Realtek Card Reader not working (kernel driver) Status in linux package in Ubuntu: Triaged Bug description: This is the situation if I use the normal 4.13 kernel driver [ 1899.245301] mmc0: cannot verify signal voltage switch [ 1899.377540] mmc0: new ultra high speed SDR104 SDXC card at address e624 [ 1899.401829] mmcblk0: mmc0:e624 AGGCE 59.5 GiB [ 1899.404700] mmcblk0: p1 [ 1899.620084] mmcblk0: error -110 sending status command, retrying [ 1899.620231] mmcblk0: error -22 sending status command, retrying [ 1899.620419] mmcblk0: error -22 sending status command, aborting [ 1899.905535] mmc0: cannot verify signal voltage switch [ 1900.136253] mmcblk0: error -22 sending status command, retrying [ 1900.136396] mmcblk0: error -22 sending status command, retrying [ 1900.240070] mmcblk0: error -110 sending status command, aborting [ 1900.240084] print_req_error: I/O error, dev mmcblk0, sector 8 but it works perfectly if I use the patched driver on kernel 4.4-4.7 this one https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel the problem is that I can't compile it on 4.13 and anyway this affects a lot of systems using 5229/5227 many laptops use this. any solution?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735099] Re: Realtek Card Reader not working (kernel driver)
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 into mainline kernel. Please keep a watch on this report for updates. -- 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/1735099 Title: Realtek Card Reader not working (kernel driver) Status in linux package in Ubuntu: Triaged Bug description: This is the situation if I use the normal 4.13 kernel driver [ 1899.245301] mmc0: cannot verify signal voltage switch [ 1899.377540] mmc0: new ultra high speed SDR104 SDXC card at address e624 [ 1899.401829] mmcblk0: mmc0:e624 AGGCE 59.5 GiB [ 1899.404700] mmcblk0: p1 [ 1899.620084] mmcblk0: error -110 sending status command, retrying [ 1899.620231] mmcblk0: error -22 sending status command, retrying [ 1899.620419] mmcblk0: error -22 sending status command, aborting [ 1899.905535] mmc0: cannot verify signal voltage switch [ 1900.136253] mmcblk0: error -22 sending status command, retrying [ 1900.136396] mmcblk0: error -22 sending status command, retrying [ 1900.240070] mmcblk0: error -110 sending status command, aborting [ 1900.240084] print_req_error: I/O error, dev mmcblk0, sector 8 but it works perfectly if I use the patched driver on kernel 4.4-4.7 this one https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel the problem is that I can't compile it on 4.13 and anyway this affects a lot of systems using 5229/5227 many laptops use this. any solution?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735099] Re: Realtek Card Reader not working (kernel driver)
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 power- signalling errors are critical or incidental: Sep 15 11:55:59 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:56:00 kubuntu-laptop kernel: mmc0: new ultra high speed SDR104 SDXC card at address 0001 Sep 15 11:56:00 kubuntu-laptop kernel: mmcblk0: mmc0:0001 GC2QT 59.6 GiB Sep 15 11:56:00 kubuntu-laptop kernel: mmcblk0: p1 Sep 15 11:57:06 kubuntu-laptop kernel: mmc0: card 0001 removed Sep 15 11:57:14 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:57:14 kubuntu-laptop kernel: mmc0: tuning execution failed: -22 Sep 15 11:57:14 kubuntu-laptop kernel: mmc0: error -22 whilst initialising SD card Sep 15 11:57:15 kubuntu-laptop kernel: mmc0: error -110 whilst initialising SD card Sep 15 11:57:17 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:57:17 kubuntu-laptop kernel: mmc0: tuning execution failed: -22 Sep 15 11:57:17 kubuntu-laptop kernel: mmc0: error -22 whilst initialising SD card Sep 15 11:58:08 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:58:08 kubuntu-laptop kernel: mmc0: new ultra high speed SDR104 SDXC card at address 0001 Sep 15 11:58:08 kubuntu-laptop kernel: mmcblk0: mmc0:0001 GC2QT 59.6 GiB Sep 15 11:58:08 kubuntu-laptop kernel: mmcblk0: p1 Sep 15 11:58:46 kubuntu-laptop kernel: mmc0: card 0001 removed -- 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/1735099 Title: Realtek Card Reader not working (kernel driver) Status in linux package in Ubuntu: Triaged Bug description: This is the situation if I use the normal 4.13 kernel driver [ 1899.245301] mmc0: cannot verify signal voltage switch [ 1899.377540] mmc0: new ultra high speed SDR104 SDXC card at address e624 [ 1899.401829] mmcblk0: mmc0:e624 AGGCE 59.5 GiB [ 1899.404700] mmcblk0: p1 [ 1899.620084] mmcblk0: error -110 sending status command, retrying [ 1899.620231] mmcblk0: error -22 sending status command, retrying [ 1899.620419] mmcblk0: error -22 sending status command, aborting [ 1899.905535] mmc0: cannot verify signal voltage switch [ 1900.136253] mmcblk0: error -22 sending status command, retrying [ 1900.136396] mmcblk0: error -22 sending status command, retrying [ 1900.240070] mmcblk0: error -110 sending status command, aborting [ 1900.240084] print_req_error: I/O error, dev mmcblk0, sector 8 but it works perfectly if I use the patched driver on kernel 4.4-4.7 this one https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel the problem is that I can't compile it on 4.13 and anyway this affects a lot of systems using 5229/5227 many laptops use this. any solution?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839707] Re: System does not shutdown with any kernel >= v4.6.3
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/ a5f09a92b7ec 2016-06-24 10:22:04 -0700 N Gerald Schaefer mm: thp: broken page count after commit aa88b68c3b1d 50c596c23c08 2016-06-24 10:22:03 -0700 N Tejun Heo memcg: add RCU locking around css_for_each_descendant_pre() in memcg_offline_kmem() ** Bug watch added: Linux Kernel Bug Tracker #199349 https://bugzilla.kernel.org/show_bug.cgi?id=199349 -- 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/1839707 Title: System does not shutdown with any kernel >= v4.6.3 Status in linux package in Ubuntu: Confirmed Bug description: System hangs on shutdown at "Target Poweroff" since updating from 16.04LTS to 18.04LTS. I have since tried cosmic and now disco with the same results. Using ukuu I have diagnosed the issue to a change between linux 4.6.2 and 4.6.3 Any linux version 4.6.3=> will hang at shutdown. Both full installations and live images have the same result, I also have two devices with the same issue. In addition I should mention I have tried many workarounds suggested on forums and in IRC. This includes but not confined to running with:- noapic nolapic and both Windows and Linux acpi_osi ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: MATE Date: Sat Aug 10 10:54:17 2019 HibernationDevice: RESUME=UUID=3149be45-ddfc-461d-b629-f14840f86784 InstallationDate: Installed on 2017-04-13 (848 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. MachineType: Dell Inc. Inspiron 1501 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=976abfe1-4322-487d-bead-8edf85051221 ro dell_smm_hwmon=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-31 (9 days ago) dmi.bios.date: 08/23/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0UW744 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd08/23/2006:svnDellInc.:pnInspiron1501:pvrNotSpecified:rvnDellInc.:rn0UW744:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 1501 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838844] Re: "dm-verity: Invalid number of feature arg" with FEC due to "# CONFIG_DM_VERITY_FEC is not set"
** 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.
https://bugs.launchpad.net/bugs/1838844
Title:
"dm-verity: Invalid number of feature arg" with FEC due to "#
CONFIG_DM_VERITY_FEC is not set"
Status in linux package in Ubuntu:
Incomplete
Bug description:
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 succeeds.
After writing this report I thought to check the kernel compilation
options and discovered the cause:
$ sudo grep VERITY /boot/config-$(uname -r)
CONFIG_DM_VERITY=m
# CONFIG_DM_VERITY_FEC is not set
It would be very useful to enable this unless there's a specific
reason not to.
I'm working (with the Lubuntu team) on introducing verity/FEC for the
live-build tooling so that all Ubuntu ISO images can have integral
verification with FEC available.
--- additional data ---
$ uname -r
4.15.0-56-lowlatency
$ sudo dmsetup targets | grep verity
verity v1.3.0
$ lsmod | grep verity
dm_verity 20480 0
dm_bufio 28672 1 dm_verity
$ modinfo dm-verity
filename:
/lib/modules/4.15.0-56-lowlatency/kernel/drivers/md/dm-verity.ko
...
depends:dm-bufio
retpoline: Y
intree: Y
name: dm_verity
vermagic: 4.15.0-56-lowlatency SMP preempt mod_unload
signat: PKCS#7
...
sig_hashalgo: md4
parm: prefetch_cluster:uint
$ sudo losetup /dev/loop3 Downloads/lubuntu-desktop-amd64.1910.iso
$ sudo mkdir -p /mnt/live/verity
$ sudo veritysetup format --fec-device=/mnt/live/verity/iso-fec.verity
/dev/loop3 /mnt/live/verity/iso-hash.verity
VERITY header information for /mnt/live/verity/iso-hash.verity
UUID: fa07efe8-e4a6-4968-abce-779f2d5674ce
Hash type: 1
Data blocks:412080
Data block size:4096
Hash block size:4096
Hash algorithm:
sha256
Salt:
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b
Root hash:
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
$ ls -la /mnt/live/verity/
total 26136
drwxr-xr-x 2 root root 4096 Aug 3 13:21 .
drwxr-xr-x 5 root root 4096 Aug 3 13:19 ..
-rw--- 1 root root 13451264 Aug 3 13:23 iso-fec.verity
-rw--- 1 root root 13303808 Aug 3 13:23 iso-hash.verity
Using strace I'm able to capture the table definition veritysetup is
trying to use:
$ sudo strace -v -s 256 -f -o /tmp/veritysetup.strace veritysetup -v
--fec-device=/mnt/live/verity/iso-fec.verity create live-iso /
dev/loop3 /mnt/live/verity/iso-hash.verity
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
device-mapper: reload ioctl on failed: Invalid argument
Command failed with code -1 (wrong or missing parameters).
28809 ioctl(5, DM_DEV_CREATE, {version=4.0.0, data_size=16384,
name="live-iso", uuid="CRYPT-VERITY-fa07efe8e4a64968abce779f2d5674ce-live-iso
", flags=DM_EXISTS_FLAG} => {version=4.37.0, data_size=305, dev=makedev(253,
20), name="live-iso", uuid="CRYPT-VERITY-fa07efe8e4a64968abce77
9f2d5674ce-live-iso", target_count=0, open_count=0, event_nr=0,
flags=DM_EXISTS_FLAG}) = 0
28809 ioctl(5, DM_TABLE_LOAD, {version=4.0.0, data_size=16384,
data_start=312, name="live-iso", target_count=1, flags=DM_READONLY_FLAG|DM_EX
ISTS_FLAG|DM_SECURE_DATA_FLAG, {sector_start=0, length=3296640,
target_type="verity", string="1 /dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots 2"}},
0x560977ffe210) = -1 EINVAL (Invalid argument)
So the table is:
1 /dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots
2
Manually attempting the command also fails (/dev/loop3 remains):
$ SIZE=$(blockdev --getsz /dev/loop3)
$ sudo losetup /dev/loop4 /mnt/live/verity/iso-hash.verity
$ sudo losetup /dev/loop5 /mnt/live/verity/iso-fec.verity
$ sudo dmsetup -vv create live-iso -r --table "0 $SIZE verity 1
/dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c
[Kernel-packages] [Bug 1838844] Re: dm-verity: Invalid number of feature args
** 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 FEC. Without FEC it succeeds.
+
+ After writing this report I thought to check the kernel compilation
+ options and discovered the cause:
+
+ $ sudo grep VERITY /boot/config-$(uname -r)
+ CONFIG_DM_VERITY=m
+ # CONFIG_DM_VERITY_FEC is not set
+
+ It would be very useful to enable this unless there's a specific reason
+ not to.
+
+ I'm working (with the Lubuntu team) on introducing verity/FEC for the
+ live-build tooling so that all Ubuntu ISO images can have integral
+ verification with FEC available.
+
+ --- additional data ---
$ uname -r
4.15.0-56-lowlatency
$ sudo dmsetup targets | grep verity
verity v1.3.0
$ lsmod | grep verity
dm_verity 20480 0
dm_bufio 28672 1 dm_verity
$ modinfo dm-verity
filename:
/lib/modules/4.15.0-56-lowlatency/kernel/drivers/md/dm-verity.ko
...
depends:dm-bufio
retpoline: Y
intree: Y
name: dm_verity
vermagic: 4.15.0-56-lowlatency SMP preempt mod_unload
signat: PKCS#7
...
sig_hashalgo: md4
parm: prefetch_cluster:uint
$ sudo losetup /dev/loop3 Downloads/lubuntu-desktop-amd64.1910.iso
$ sudo mkdir -p /mnt/live/verity
$ sudo veritysetup format --fec-device=/mnt/live/verity/iso-fec.verity
/dev/loop3 /mnt/live/verity/iso-hash.verity
VERITY header information for /mnt/live/verity/iso-hash.verity
UUID: fa07efe8-e4a6-4968-abce-779f2d5674ce
Hash type: 1
Data blocks:412080
Data block size:4096
Hash block size:4096
Hash algorithm:
sha256
Salt:
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b
Root hash:
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
$ ls -la /mnt/live/verity/
total 26136
drwxr-xr-x 2 root root 4096 Aug 3 13:21 .
drwxr-xr-x 5 root root 4096 Aug 3 13:19 ..
-rw--- 1 root root 13451264 Aug 3 13:23 iso-fec.verity
-rw--- 1 root root 13303808 Aug 3 13:23 iso-hash.verity
Using strace I'm able to capture the table definition veritysetup is
trying to use:
$ sudo strace -v -s 256 -f -o /tmp/veritysetup.strace veritysetup -v
--fec-device=/mnt/live/verity/iso-fec.verity create live-iso /
dev/loop3 /mnt/live/verity/iso-hash.verity
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
device-mapper: reload ioctl on failed: Invalid argument
Command failed with code -1 (wrong or missing parameters).
28809 ioctl(5, DM_DEV_CREATE, {version=4.0.0, data_size=16384,
name="live-iso", uuid="CRYPT-VERITY-fa07efe8e4a64968abce779f2d5674ce-live-iso
", flags=DM_EXISTS_FLAG} => {version=4.37.0, data_size=305, dev=makedev(253,
20), name="live-iso", uuid="CRYPT-VERITY-fa07efe8e4a64968abce77
9f2d5674ce-live-iso", target_count=0, open_count=0, event_nr=0,
flags=DM_EXISTS_FLAG}) = 0
28809 ioctl(5, DM_TABLE_LOAD, {version=4.0.0, data_size=16384,
data_start=312, name="live-iso", target_count=1, flags=DM_READONLY_FLAG|DM_EX
ISTS_FLAG|DM_SECURE_DATA_FLAG, {sector_start=0, length=3296640,
target_type="verity", string="1 /dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots 2"}},
0x560977ffe210) = -1 EINVAL (Invalid argument)
So the table is:
1 /dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots 2
Manually attempting the command also fails (/dev/loop3 remains):
$ SIZE=$(blockdev --getsz /dev/loop3)
$ sudo losetup /dev/loop4 /mnt/live/verity/iso-hash.verity
$ sudo losetup /dev/loop5 /mnt/live/verity/iso-fec.verity
$ sudo dmsetup -vv create live-iso -r --table "0 $SIZE verity 1
/dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots
2"
dm version [ opencount flush ] [16384] (*1)
Udev cookie 0xd4d119f (semid 819203) created
Udev cookie 0xd4d119f (semid 819203) incremented to 1
Udev cookie 0xd4d119f (semid 819203) incremented to 2
Udev cookie 0xd4d119f (semid 819203) assig
[Kernel-packages] [Bug 1838844] [NEW] dm-verity: Invalid number of feature args
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 succeeds.
$ uname -r
4.15.0-56-lowlatency
$ sudo dmsetup targets | grep verity
verity v1.3.0
$ lsmod | grep verity
dm_verity 20480 0
dm_bufio 28672 1 dm_verity
$ modinfo dm-verity
filename: /lib/modules/4.15.0-56-lowlatency/kernel/drivers/md/dm-verity.ko
...
depends:dm-bufio
retpoline: Y
intree: Y
name: dm_verity
vermagic: 4.15.0-56-lowlatency SMP preempt mod_unload
signat: PKCS#7
...
sig_hashalgo: md4
parm: prefetch_cluster:uint
$ sudo losetup /dev/loop3 Downloads/lubuntu-desktop-amd64.1910.iso
$ sudo mkdir -p /mnt/live/verity
$ sudo veritysetup format --fec-device=/mnt/live/verity/iso-fec.verity
/dev/loop3 /mnt/live/verity/iso-hash.verity
VERITY header information for /mnt/live/verity/iso-hash.verity
UUID: fa07efe8-e4a6-4968-abce-779f2d5674ce
Hash type: 1
Data blocks:412080
Data block size:4096
Hash block size:4096
Hash algorithm:
sha256
Salt:
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b
Root hash:
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
$ ls -la /mnt/live/verity/
total 26136
drwxr-xr-x 2 root root 4096 Aug 3 13:21 .
drwxr-xr-x 5 root root 4096 Aug 3 13:19 ..
-rw--- 1 root root 13451264 Aug 3 13:23 iso-fec.verity
-rw--- 1 root root 13303808 Aug 3 13:23 iso-hash.verity
Using strace I'm able to capture the table definition veritysetup is
trying to use:
$ sudo strace -v -s 256 -f -o /tmp/veritysetup.strace veritysetup -v
--fec-device=/mnt/live/verity/iso-fec.verity create live-iso /
dev/loop3 /mnt/live/verity/iso-hash.verity
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
device-mapper: reload ioctl on failed: Invalid argument
Command failed with code -1 (wrong or missing parameters).
28809 ioctl(5, DM_DEV_CREATE, {version=4.0.0, data_size=16384, name="live-iso",
uuid="CRYPT-VERITY-fa07efe8e4a64968abce779f2d5674ce-live-iso
", flags=DM_EXISTS_FLAG} => {version=4.37.0, data_size=305, dev=makedev(253,
20), name="live-iso", uuid="CRYPT-VERITY-fa07efe8e4a64968abce77
9f2d5674ce-live-iso", target_count=0, open_count=0, event_nr=0,
flags=DM_EXISTS_FLAG}) = 0
28809 ioctl(5, DM_TABLE_LOAD, {version=4.0.0, data_size=16384, data_start=312,
name="live-iso", target_count=1, flags=DM_READONLY_FLAG|DM_EX
ISTS_FLAG|DM_SECURE_DATA_FLAG, {sector_start=0, length=3296640,
target_type="verity", string="1 /dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots 2"}},
0x560977ffe210) = -1 EINVAL (Invalid argument)
So the table is:
1 /dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots 2
Manually attempting the command also fails (/dev/loop3 remains):
$ SIZE=$(blockdev --getsz /dev/loop3)
$ sudo losetup /dev/loop4 /mnt/live/verity/iso-hash.verity
$ sudo losetup /dev/loop5 /mnt/live/verity/iso-fec.verity
$ sudo dmsetup -vv create live-iso -r --table "0 $SIZE verity 1
/dev/loop3 /dev/loop4 4096 4096 412080 1 sha256
500f659e52b62e0efabe1eae2b2fac34c12522acc372e80e5d375be252c51931
fa93e8fdeb55acf548adf8812d6748c789b620c22338579def0bc01e65726a7b 8
use_fec_from_device /dev/loop5 fec_start 0 fec_blocks 415327 fec_roots
2"
dm version [ opencount flush ] [16384] (*1)
Udev cookie 0xd4d119f (semid 819203) created
Udev cookie 0xd4d119f (semid 819203) incremented to 1
Udev cookie 0xd4d119f (semid 819203) incremented to 2
Udev cookie 0xd4d119f (semid 819203) assigned to CREATE task(0) with flags
DISABLE_LIBRARY_FALLBACK (0x20)
dm create live-iso [ opencount flush ] [16384] (*1)
dm reload live-iso [ opencount flush readonly ] [16384] (*1)
device-mapper: reload ioctl on live-iso failed: Invalid argument
Udev cookie 0xd4d119f (semid 819203) decremented to 1
Udev cookie 0xd4d119f (semid 819203) incremented to 2
Udev cookie 0xd4d119f (semid 819203) assigned to REMOVE task(2) with flags
DISABLE_LIBRARY_FALLBACK (0x20)
dm remove live-iso [ opencount flush readonly ] [16384] (*1)
Udev cookie 0xd4d119f (semid 819203) decremented to 1
Udev cookie 0xd4d119f (semid 819203) waiting for zero
Udev cookie 0xd4d119f (semid 819203)
[Kernel-packages] [Bug 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
** 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.launchpad.net/bugs/1811815 Title: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: === SRU Justification === [Impact] Lenovo ideapad 330-15ICH Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === The issue here is that the drivers/platform/x86/ideapad_laptop.c module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill switch, reads the I/O port for its state, gets a zero, and therefore reports to the kernel that RFkill is hard-blocked. The current workaround is to blacklist the module to stop it being loaded. I've attached a simple patch for the module that teaches it that this model does not have a hardware RF kill switch. Original Report - Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggressive memory leak
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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831751
Title:
rtlwifi: aggressive memory leak
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Bug description:
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 have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
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 rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
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 rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
** Summary changed:
- rtlwifi: aggresive memory leak
+ rtlwifi: aggressive 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:
rtlwifi: aggressive memory leak
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Bug description:
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 have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
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 rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811869] Re: Alienware m15 takes very long to boot Ubuntu
** 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 Status in linux package in Ubuntu: Fix Released Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 2452 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d InstallationDate: Installed on 2018-12-25 (21 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) IwConfig: wlp112s0 no wireless extensions. enp111s0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware m15 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 Tags: xenial Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.3 dmi.board.name: 0CNR45 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware m15 dmi.product.version: 1.3.3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834177] Re: regression: between 4.15.0-45 and 4.15.0-50 - i915 vmalloc_fault
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 potential exploitation of the Spectre variant 1 vulnerability. This issue was detected with the help of Smatch: drivers/gpu/drm/i915/gvt/kvmgt.c:1232 intel_vgpu_ioctl() warn: potential spectre issue 'vgpu->vdev.region' [r] Fix this by sanitizing info.index before indirectly using it to index vgpu->vdev.region Notice that given that speculation windows are large, the policy is to kill the speculation on the first load and not worry if it can be completed with a dependent load/store [1]. [1] https://marc.info/?l=linux-kernel&m=152449131114778&w=2 Cc: sta...@vger.kernel.org Signed-off-by: Gustavo A. R. Silva Signed-off-by: Zhenyu Wang CVE-2017-5753 (cherry picked from commit de5372da605d3bca46e3102bab51b7e1c0e0a6f6) Signed-off-by: Juerg Haefliger Acked-by: Stefan Bader Acked-by: Kleber Sacilotto de Souza Signed-off-by: Stefan Bader ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5753 -- 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/1834177 Title: regression: between 4.15.0-45 and 4.15.0-50 - i915 vmalloc_fault Status in linux package in Ubuntu: Confirmed Bug description: From the logs: Jun 25 11:14:21 machine-name kernel: [ cut here ] Jun 25 11:14:21 machine-name kernel: kernel BUG at /build/linux-H3Eec1/linux-4.15.0/arch/x86/mm/fault.c:268! Jun 25 11:14:21 machine-name kernel: invalid opcode: [#1] SMP PTI Jun 25 11:14:21 machine-name kernel: Modules linked in: i915(+) video i2c_algo_bit crc32_pclmul drm_kms_helper syscopyarea sysfillrect psmouse ahci sysimgblt e1000e fb_sys_fops libahci drm ptp pps_core wmi Jun 25 11:14:21 machine-name kernel: CPU: 1 PID: 168 Comm: systemd-udevd Not tainted 4.15.0-52-generic #56-Ubuntu Jun 25 11:14:21 machine-name kernel: Hardware name: Hewlett-Packard HP Compaq 8200 Elite SFF PC/1495, BIOS J01 v02.15 11/10/2011 Jun 25 11:14:21 machine-name kernel: EIP: vmalloc_fault+0x229/0x240 Jun 25 11:14:21 machine-name kernel: EFLAGS: 00010086 CPU: 1 Jun 25 11:14:21 machine-name kernel: EAX: 027b EBX: c5e20e28 ECX: fef3 EDX: Jun 25 11:14:21 machine-name kernel: ESI: f8a78000 EDI: fe00 EBP: f550fc08 ESP: f550fbec Jun 25 11:14:21 machine-name kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Jun 25 11:14:21 machine-name kernel: CR0: 80050033 CR2: f8a78000 CR3: 356b2000 CR4: 000406f0 Jun 25 11:14:21 machine-name kernel: Call Trace: Jun 25 11:14:21 machine-name kernel: ? __do_page_fault+0x510/0x510 Jun 25 11:14:21 machine-name kernel: __do_page_fault+0x39d/0x510 Jun 25 11:14:21 machine-name kernel: ? __do_page_fault+0x510/0x510 Jun 25 11:14:21 machine-name kernel: do_page_fault+0x27/0xf0 Jun 25 11:14:21 machine-name kernel: ? __do_page_fault+0x510/0x510 Jun 25 11:14:21 machine-name kernel: common_exception+0x130/0x136 Jun 25 11:14:21 machine-name kernel: EIP: i915_check_vgpu+0x11/0xb0 [i915] Jun 25 11:14:21 machine-name kernel: EFLAGS: 00010286 CPU: 1 Jun 25 11:14:21 machine-name kernel: EAX: f57d8000 EBX: f57d8000 ECX: f550fcb4 EDX: f8a0 Jun 25 11:14:21 machine-name kernel: ESI: EDI: f57d83f8 EBP: f550fcb8 ESP: f550fcac Jun 25 11:14:21 machine-name kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Jun 25 11:14:21 machine-name kernel: ? pci_conf1_read+0xbb/0xf0 Jun 25 11:14:21 machine-name kernel: intel_uncore_init+0x15/0x5c0 [i915] Jun 25 11:14:21 machine-name kernel: i915_driver_load+0x456/0xcc0 [i915] Jun 25 11:14:21 machine-name kernel: ? acpi_dev_found+0x6c/0x80 Jun 25 11:14:21 machine-name kernel: ? i915_pci_remove+0x20/0x20 [i915] Jun 25 11:14:21 machine-name kernel: i915_pci_probe+0x3a/0x70 [i915] Jun 25 11:14:21 machine-name kernel: pci_device_probe+0xc7/0x160 Jun 25 11:14:21 machine-name kernel: driver_probe_device+0x2af/0x440 Jun 25 11:14:21 machine-name kernel: __driver_attach+0x99/0xe0 Jun 25 11:14:21 machine-name kernel: ? driver_probe_device+0x440/0x440 Jun 25 11:14:21 machine-name kernel: bus_for_each_dev+0x5a/0xa0 Jun 25 11:14:21 machine-name kernel: driver_attach+0x19/0x20 Jun 25 11:14:21 machine-name kernel: ? driver_probe_device+0x440/0x440 Jun 25 11:14:21 machine-name kernel: bus_add_driver+0x187/0x230 Jun 25 11:14:21 machine-name kernel: ? 0xf8951000 Jun 25 11:14:21 machine-name kernel: driver_register+0x56/0xd0 Jun 25 11:14:21 machine-name kernel: ? 0xf8951000 Jun 25 11:14:21 machine-name kernel: __pci_register_driver+0x3a/0x40 Jun 25 11:14:21
[Kernel-packages] [Bug 1834177] Re: regression: between 4.15.0-45 and 4.15.0-50 - i915 vmalloc_fault
** 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. https://bugs.launchpad.net/bugs/1834177 Title: regression: between 4.15.0-45 and 4.15.0-50 - i915 vmalloc_fault Status in linux package in Ubuntu: Confirmed Bug description: From the logs: Jun 25 11:14:21 machine-name kernel: [ cut here ] Jun 25 11:14:21 machine-name kernel: kernel BUG at /build/linux-H3Eec1/linux-4.15.0/arch/x86/mm/fault.c:268! Jun 25 11:14:21 machine-name kernel: invalid opcode: [#1] SMP PTI Jun 25 11:14:21 machine-name kernel: Modules linked in: i915(+) video i2c_algo_bit crc32_pclmul drm_kms_helper syscopyarea sysfillrect psmouse ahci sysimgblt e1000e fb_sys_fops libahci drm ptp pps_core wmi Jun 25 11:14:21 machine-name kernel: CPU: 1 PID: 168 Comm: systemd-udevd Not tainted 4.15.0-52-generic #56-Ubuntu Jun 25 11:14:21 machine-name kernel: Hardware name: Hewlett-Packard HP Compaq 8200 Elite SFF PC/1495, BIOS J01 v02.15 11/10/2011 Jun 25 11:14:21 machine-name kernel: EIP: vmalloc_fault+0x229/0x240 Jun 25 11:14:21 machine-name kernel: EFLAGS: 00010086 CPU: 1 Jun 25 11:14:21 machine-name kernel: EAX: 027b EBX: c5e20e28 ECX: fef3 EDX: Jun 25 11:14:21 machine-name kernel: ESI: f8a78000 EDI: fe00 EBP: f550fc08 ESP: f550fbec Jun 25 11:14:21 machine-name kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Jun 25 11:14:21 machine-name kernel: CR0: 80050033 CR2: f8a78000 CR3: 356b2000 CR4: 000406f0 Jun 25 11:14:21 machine-name kernel: Call Trace: Jun 25 11:14:21 machine-name kernel: ? __do_page_fault+0x510/0x510 Jun 25 11:14:21 machine-name kernel: __do_page_fault+0x39d/0x510 Jun 25 11:14:21 machine-name kernel: ? __do_page_fault+0x510/0x510 Jun 25 11:14:21 machine-name kernel: do_page_fault+0x27/0xf0 Jun 25 11:14:21 machine-name kernel: ? __do_page_fault+0x510/0x510 Jun 25 11:14:21 machine-name kernel: common_exception+0x130/0x136 Jun 25 11:14:21 machine-name kernel: EIP: i915_check_vgpu+0x11/0xb0 [i915] Jun 25 11:14:21 machine-name kernel: EFLAGS: 00010286 CPU: 1 Jun 25 11:14:21 machine-name kernel: EAX: f57d8000 EBX: f57d8000 ECX: f550fcb4 EDX: f8a0 Jun 25 11:14:21 machine-name kernel: ESI: EDI: f57d83f8 EBP: f550fcb8 ESP: f550fcac Jun 25 11:14:21 machine-name kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Jun 25 11:14:21 machine-name kernel: ? pci_conf1_read+0xbb/0xf0 Jun 25 11:14:21 machine-name kernel: intel_uncore_init+0x15/0x5c0 [i915] Jun 25 11:14:21 machine-name kernel: i915_driver_load+0x456/0xcc0 [i915] Jun 25 11:14:21 machine-name kernel: ? acpi_dev_found+0x6c/0x80 Jun 25 11:14:21 machine-name kernel: ? i915_pci_remove+0x20/0x20 [i915] Jun 25 11:14:21 machine-name kernel: i915_pci_probe+0x3a/0x70 [i915] Jun 25 11:14:21 machine-name kernel: pci_device_probe+0xc7/0x160 Jun 25 11:14:21 machine-name kernel: driver_probe_device+0x2af/0x440 Jun 25 11:14:21 machine-name kernel: __driver_attach+0x99/0xe0 Jun 25 11:14:21 machine-name kernel: ? driver_probe_device+0x440/0x440 Jun 25 11:14:21 machine-name kernel: bus_for_each_dev+0x5a/0xa0 Jun 25 11:14:21 machine-name kernel: driver_attach+0x19/0x20 Jun 25 11:14:21 machine-name kernel: ? driver_probe_device+0x440/0x440 Jun 25 11:14:21 machine-name kernel: bus_add_driver+0x187/0x230 Jun 25 11:14:21 machine-name kernel: ? 0xf8951000 Jun 25 11:14:21 machine-name kernel: driver_register+0x56/0xd0 Jun 25 11:14:21 machine-name kernel: ? 0xf8951000 Jun 25 11:14:21 machine-name kernel: __pci_register_driver+0x3a/0x40 Jun 25 11:14:21 machine-name kernel: i915_init+0x51/0x56 [i915] Jun 25 11:14:21 machine-name kernel: do_one_initcall+0x49/0x174 Jun 25 11:14:21 machine-name kernel: ? _cond_resched+0x17/0x40 Jun 25 11:14:21 machine-name kernel: ? kmem_cache_alloc_trace+0x165/0x1d0 Jun 25 11:14:21 machine-name kernel: ? do_init_module+0x21/0x1ec Jun 25 11:14:21 machine-name kernel: ? do_init_module+0x21/0x1ec Jun 25 11:14:21 machine-name kernel: do_init_module+0x50/0x1ec Jun 25 11:14:21 machine-name kernel: load_module+0x1588/0x1ab0 Jun 25 11:14:21 machine-name kernel: ? ima_post_read_file+0xb4/0xc0 Jun 25 11:14:21 machine-name kernel: ? security_kernel_post_read_file+0x62/0x70 Jun 25 11:14:21 machine-name kernel: SyS_finit_module+0x8a/0xe0 Jun 25 11:14:21 machine-name kernel: do_fast_syscall_32+0x7f/0x200 Jun 25 11:14:21 machine-name kernel: entry_SYSENTER_32+0x6b/0xbe Jun 25 11:14:21 machine-name kernel: EIP: 0xb7f4bd09 Jun 25 11:14:21 machine-name kernel: EFLAGS: 0296 CPU: 1 Jun 25 11:14:21 machine-name kernel: EAX: ffda EBX: 0013 ECX: b7d5da15 EDX: Jun 25 11:14:21 machine-name kernel: ESI: 01f2c530 EDI: 01f17d50 EBP: 01f11800
[Kernel-packages] [Bug 1834003] Re: autofs4 hangs waiting to mount local file-system
** Description changed:
18.04 amd64, 4.15.0-50-lowlatency.
The system has a number of local autofs mounts created and managed by
systemd through .automount units.
Earlier today I had finished working on one such ("SourceCode") and it
had auto-unmounted after the idle time. 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 dumped a couple of stack traces of which I include the first
here.
After the stack-traces appeared the shell was able to report an error
for other auto-mounts that haven't hung but trying to access the
problematic "/home/tj/SourceCode" still hangs the shell, and trying to
manually mount the affected file-system to the same location also hangs
but works for another mount-point:
ls: cannot access '/home/tj/Projects/': Host is down
+
+ In trying to clean up I manually stopped all the systemd
+ .mount/.automount units. As soon as I stopped the home-tj-
+ SourceCode.automount unit the mount succeeded and the shells un-hung.
+
+ Not sure if this is caused by the systemd autofs handling or there was
+ some race condition behind it, but it seems to have recovered.
Jun 24 11:01:02 T300CHI kernel: INFO: task ls:29630 blocked for more than 120
seconds.
Jun 24 11:01:02 T300CHI kernel: Tainted: G OE
4.15.0-50-lowlatency #54-Ubuntu
Jun 24 11:01:02 T300CHI kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 24 11:01:02 T300CHI kernel: Call Trace:
Jun 24 11:01:02 T300CHI kernel: __schedule+0x293/0x8a0
Jun 24 11:01:02 T300CHI kernel: schedule+0x33/0x90
Jun 24 11:01:02 T300CHI kernel: schedule_timeout+0x1e6/0x380
Jun 24 11:01:02 T300CHI kernel: ? autofs4_wait+0x451/0x870 [autofs4]
Jun 24 11:01:02 T300CHI kernel: wait_for_completion+0xac/0x130
Jun 24 11:01:02 T300CHI kernel: ? wake_up_q+0x80/0x80
Jun 24 11:01:02 T300CHI kernel: autofs4_expire_wait+0xa0/0x160 [autofs4]
Jun 24 11:01:02 T300CHI kernel: do_expire_wait+0x155/0x210 [autofs4]
Jun 24 11:01:02 T300CHI kernel: ? __d_alloc+0x122/0x1d0
Jun 24 11:01:02 T300CHI kernel: autofs4_d_manage+0x76/0x1a0 [autofs4]
Jun 24 11:01:02 T300CHI kernel: follow_managed+0xce/0x310
Jun 24 11:01:02 T300CHI kernel: lookup_fast+0x115/0x340
Jun 24 11:01:02 T300CHI kernel: walk_component+0x49/0x470
Jun 24 11:01:02 T300CHI kernel: path_lookupat+0x84/0x1f0
Jun 24 11:01:02 T300CHI kernel: filename_lookup+0xb6/0x190
Jun 24 11:01:02 T300CHI kernel: ? mem_cgroup_commit_charge+0x82/0x520
Jun 24 11:01:02 T300CHI kernel: ? __check_object_size+0xaf/0x1b0
Jun 24 11:01:02 T300CHI kernel: ? strncpy_from_user+0x4d/0x170
Jun 24 11:01:02 T300CHI kernel: user_path_at_empty+0x36/0x40
Jun 24 11:01:02 T300CHI kernel: ? user_path_at_empty+0x36/0x40
Jun 24 11:01:02 T300CHI kernel: vfs_statx+0x76/0xe0
Jun 24 11:01:02 T300CHI kernel: SYSC_newstat+0x3d/0x70
Jun 24 11:01:02 T300CHI kernel: ? __do_page_fault+0x292/0x520
Jun 24 11:01:02 T300CHI kernel: SyS_newstat+0xe/0x10
Jun 24 11:01:02 T300CHI kernel: do_syscall_64+0x73/0x130
Jun 24 11:01:02 T300CHI kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jun 24 11:01:02 T300CHI kernel: RIP: 0033:0x7f4a02814775
Jun 24 11:01:02 T300CHI kernel: RSP: 002b:7fff7c274b98 EFLAGS: 0246
ORIG_RAX: 0004
Jun 24 11:01:02 T300CHI kernel: RAX: ffda RBX: 55fb8dd08640
RCX: 7f4a02814775
Jun 24 11:01:02 T300CHI kernel: RDX: 55fb8dd08658 RSI: 55fb8dd08658
RDI: 7fff7c276d68
Jun 24 11:01:02 T300CHI kernel: RBP: 7fff7c274f40 R08:
R09: 7fff7c276d72
Jun 24 11:01:02 T300CHI kernel: R10: 7c276d00 R11: 0246
R12: 7fff7c276d68
Jun 24 11:01:02 T300CHI kernel: R13: 0001 R14:
R15: 55fb8dd08658
--
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/1834003
Title:
autofs4 hangs waiting to mount local file-system
Status in linux package in Ubuntu:
Incomplete
Bug description:
18.04 amd64, 4.15.0-50-lowlatency.
The system has a number of local autofs mounts created and managed by
systemd through .automount units.
Earlier today I had finished working on one such ("SourceCode") and it
had auto-unmounted after the idle time. 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 dumped a couple of stack traces of wh
[Kernel-packages] [Bug 1834003] [NEW] autofs4 hangs waiting to mount local file-system
Public bug reported:
18.04 amd64, 4.15.0-50-lowlatency.
The system has a number of local autofs mounts created and managed by
systemd through .automount units.
Earlier today I had finished working on one such ("SourceCode") and it
had auto-unmounted after the idle time. 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 dumped a couple of stack traces of which I include the first
here.
After the stack-traces appeared the shell was able to report an error
for other auto-mounts that haven't hung but trying to access the
problematic "/home/tj/SourceCode" still hangs the shell, and trying to
manually mount the affected file-system to the same location also hangs
but works for another mount-point:
ls: cannot access '/home/tj/Projects/': Host is down
In trying to clean up I manually stopped all the systemd
.mount/.automount units. As soon as I stopped the home-tj-
SourceCode.automount unit the mount succeeded and the shells un-hung.
Not sure if this is caused by the systemd autofs handling or there was
some race condition behind it, but it seems to have recovered.
Jun 24 11:01:02 T300CHI kernel: INFO: task ls:29630 blocked for more than 120
seconds.
Jun 24 11:01:02 T300CHI kernel: Tainted: G OE
4.15.0-50-lowlatency #54-Ubuntu
Jun 24 11:01:02 T300CHI kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 24 11:01:02 T300CHI kernel: Call Trace:
Jun 24 11:01:02 T300CHI kernel: __schedule+0x293/0x8a0
Jun 24 11:01:02 T300CHI kernel: schedule+0x33/0x90
Jun 24 11:01:02 T300CHI kernel: schedule_timeout+0x1e6/0x380
Jun 24 11:01:02 T300CHI kernel: ? autofs4_wait+0x451/0x870 [autofs4]
Jun 24 11:01:02 T300CHI kernel: wait_for_completion+0xac/0x130
Jun 24 11:01:02 T300CHI kernel: ? wake_up_q+0x80/0x80
Jun 24 11:01:02 T300CHI kernel: autofs4_expire_wait+0xa0/0x160 [autofs4]
Jun 24 11:01:02 T300CHI kernel: do_expire_wait+0x155/0x210 [autofs4]
Jun 24 11:01:02 T300CHI kernel: ? __d_alloc+0x122/0x1d0
Jun 24 11:01:02 T300CHI kernel: autofs4_d_manage+0x76/0x1a0 [autofs4]
Jun 24 11:01:02 T300CHI kernel: follow_managed+0xce/0x310
Jun 24 11:01:02 T300CHI kernel: lookup_fast+0x115/0x340
Jun 24 11:01:02 T300CHI kernel: walk_component+0x49/0x470
Jun 24 11:01:02 T300CHI kernel: path_lookupat+0x84/0x1f0
Jun 24 11:01:02 T300CHI kernel: filename_lookup+0xb6/0x190
Jun 24 11:01:02 T300CHI kernel: ? mem_cgroup_commit_charge+0x82/0x520
Jun 24 11:01:02 T300CHI kernel: ? __check_object_size+0xaf/0x1b0
Jun 24 11:01:02 T300CHI kernel: ? strncpy_from_user+0x4d/0x170
Jun 24 11:01:02 T300CHI kernel: user_path_at_empty+0x36/0x40
Jun 24 11:01:02 T300CHI kernel: ? user_path_at_empty+0x36/0x40
Jun 24 11:01:02 T300CHI kernel: vfs_statx+0x76/0xe0
Jun 24 11:01:02 T300CHI kernel: SYSC_newstat+0x3d/0x70
Jun 24 11:01:02 T300CHI kernel: ? __do_page_fault+0x292/0x520
Jun 24 11:01:02 T300CHI kernel: SyS_newstat+0xe/0x10
Jun 24 11:01:02 T300CHI kernel: do_syscall_64+0x73/0x130
Jun 24 11:01:02 T300CHI kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jun 24 11:01:02 T300CHI kernel: RIP: 0033:0x7f4a02814775
Jun 24 11:01:02 T300CHI kernel: RSP: 002b:7fff7c274b98 EFLAGS: 0246
ORIG_RAX: 0004
Jun 24 11:01:02 T300CHI kernel: RAX: ffda RBX: 55fb8dd08640
RCX: 7f4a02814775
Jun 24 11:01:02 T300CHI kernel: RDX: 55fb8dd08658 RSI: 55fb8dd08658
RDI: 7fff7c276d68
Jun 24 11:01:02 T300CHI kernel: RBP: 7fff7c274f40 R08:
R09: 7fff7c276d72
Jun 24 11:01:02 T300CHI kernel: R10: 7c276d00 R11: 0246
R12: 7fff7c276d68
Jun 24 11:01:02 T300CHI kernel: R13: 0001 R14:
R15: 55fb8dd08658
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: bionic
--
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/1834003
Title:
autofs4 hangs waiting to mount local file-system
Status in linux package in Ubuntu:
Incomplete
Bug description:
18.04 amd64, 4.15.0-50-lowlatency.
The system has a number of local autofs mounts created and managed by
systemd through .automount units.
Earlier today I had finished working on one such ("SourceCode") and it
had auto-unmounted after the idle time. 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 dumped a couple of stack traces of which I include the first
here.
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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). calamares has a job to copy the /cdrom/casper/vmlinuz into the target and name it correctly. The job is contextualprocess@before_bootloader_mkdirs but it is listed after the "initramfs" job so there is no kernel image to get the version string from when "initramfs" executes. "before_bootloader_mkdirs" needs moving to before "initramfs". -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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 "${BOOTDIR}/initrd.img-$version" && echo
"$version"
done |
linux-version sort --reverse
)"
verbose "Available versions: ${version_list}"
}
I confused myself because I'd added a workaround for this in calamares by
executing a shell
"touch /boot/initrd.img-$(uname -r)"
and forgotten it was there whilst chasing the missing kernel!
--
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/1829805
Title:
Lubuntu Eoan Daily Image fails to boot after install on KVM
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Invalid
Bug description:
Context: The live environment appears to function properly and install
proceeds as expected with no noticeable errors.
Expected results: After a system reboot the virtual machine enters the
graphical environment
Actual Results: After rebooting the virtual machine a kernel panic
error screen appears. I will attempt to attach the screenshot after
submitting this bug report.
The collected data is from the live environment as the installed
environment will not boot.
lubuntu@lubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
lubuntu@lubuntu:~$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
2.02+dfsg1-12ubuntu2 500
500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519)
eoan/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.407
CurrentDesktop: LXQt
Date: Tue May 21 00:30:39 2019
LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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 "initramfs-tools (0.133ubuntu1)" April 29th; I've worked back through the changes by Debian to "initramfs-tools (0.132) unstable" of 26th July 2018, which contains "[f39625a] update-initramfs: Make "-k all" take over other initramfs images" and looking at that commit seems to indicate it is the cause https://salsa.debian.org/kernel-team/initramfs- tools/commit/f39625afd6ba6c1aa2027286dc3ef1c933da14e0 Running the script with shell logging shows that when Calamares initramfs module calls with: # update-initramfs -k all -c -t We get: ... + break + [ 0 -ne 0 ] + [ -z c ] + [ all = all ] + get_sorted_versions + linux-version list + linux-version sort --reverse + read -r version + test -e /boot/initrd.img-5.0.0-17-generic + read -r version + version_list= + verbose Available versions: + [ 0 = 1 ] + [ -z ] + verbose Nothing to do, exiting. + [ 0 = 1 ] + exit 0 Because there is currently no /boot/initrd.img-$VERSION the version_list is empty. This shouldn't be a concern when we're using the "-c" create option so it looks to be a bug in the logic. The workaround for Lubuntu calamares installer configuration is to make the file exist before calling it: touch /boot/initrd.img-$(uname -r) Until initramfs-tools is fixed. -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
** 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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 removed:
# in the live system
root@lubuntu:/usr/lib/x86_64-linux-gnu/calamares/modules/initramfs# cat
README.md
## initramfs module
This module is specific to Debian based distros. Post installation on Debian
the initramfs needs to be updated so as to not interrupt the boot process
with a error about fsck.ext4 not being found.
## Debian specific notes
If you're using live-build to build your ISO and setup the runtime env
make sure that you purge the live-\* packages on the target system
before running this module, since live-config dpkg-diverts update-initramfs
and can cause all sorts of fun issues.
#
# chroot to the installed target
#
root@lubuntu:/# grep -n initramfs /var/log/installer/debug
81: "/etc/calamares/modules/initramfscfg.conf"
82: "/usr/share/calamares/modules/initramfscfg.conf"
84: "/etc/calamares/modules/initramfs.conf"
85: "/usr/share/calamares/modules/initramfs.conf"
313:2019-06-18 - 21:25:43 [6]: Starting job "initramfscfg"
316:2019-06-18 - 21:25:43 [6]: Job file
"/usr/lib/x86_64-linux-gnu/calamares/modules/initramfscfg/main.py"
317:2019-06-18 - 21:25:43 [6]: Job description from pretty_name "initramfscfg"
= "Configuring initramfs."
318:2019-06-18 - 21:25:43 [6]: Starting job "initramfs"
321:2019-06-18 - 21:25:43 [6]: Job file
"/usr/lib/x86_64-linux-gnu/calamares/modules/initramfs/main.py"
322:2019-06-18 - 21:25:43 [6]: Job description from pretty_name "initramfs" =
"Creating initramfs."
323:2019-06-18 - 21:25:43 [6]: Running "chroot"
("/tmp/calamares-root-kp3scv8s", "update-initramfs", "-k", "all", "-c", "-t")
root@lubuntu:/# cat /var/log/apt/history..log
...
Start-Date: 2019-06-18 21:26:38
Commandline: apt-get --purge -q -y remove ^live-* calamares-settings-lubuntu
calamares hunspell-en-us zram-config cifs-utils
Purge: hunspell-en-us:amd64 (1:2018.04.16-1), calamares-settings-lubuntu:amd64
(1:19.10.1), casper:amd64 (1.408), lupin-casper:amd64 (0.57build1),
calamares:amd64 (3.2.7-0ubuntu1), cifs-utils:amd64 (2:6.8-2),
calamares-settings-ubuntu-common:amd64 (1:19.10.1), zram-config:amd64 (0.5)
End-Date: 2019-06-18 21:26:48
--
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/1829805
Title:
Lubuntu Eoan Daily Image fails to boot after install on KVM
Status in linux package in Ubuntu:
Confirmed
Bug description:
Context: The live environment appears to function properly and install
proceeds as expected with no noticeable errors.
Expected results: After a system reboot the virtual machine enters the
graphical environment
Actual Results: After rebooting the virtual machine a kernel panic
error screen appears. I will attempt to attach the screenshot after
submitting this bug report.
The collected data is from the live environment as the installed
environment will not boot.
lubuntu@lubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
lubuntu@lubuntu:~$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
2.02+dfsg1-12ubuntu2 500
500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519)
eoan/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.407
CurrentDesktop: LXQt
Date: Tue May 21 00:30:39 2019
LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829805/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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
$ sudo TERM=screen chroot /mnt/target
# ls -l /boot/
total 13548
-rw-r--r-- 1 root root 224306 Jun 4 16:22 config-5.0.0-17-generic
drwxr-xr-x 5 root root4096 Jun 18 20:50 grub
lrwxrwxrwx 1 root root 27 Jun 18 17:41 initrd.img ->
initrd.img-5.0.0-17-generic
lrwxrwxrwx 1 root root 27 Jun 18 17:41 initrd.img.old ->
initrd.img-5.0.0-17-generic
-rw-r--r-- 1 root root 182704 Jan 28 2016 memtest86+.bin
-rw-r--r-- 1 root root 184380 Jan 28 2016 memtest86+.elf
-rw-r--r-- 1 root root 184840 Jan 28 2016 memtest86+_multiboot.bin
-rw--- 1 root root 4378278 Jun 4 16:22 System.map-5.0.0-17-generic
lrwxrwxrwx 1 root root 24 Jun 18 17:41 vmlinuz -> vmlinuz-5.0.0-17-generic
-r--r--r-- 1 root root 8703736 Jun 18 20:50 vmlinuz-5.0.0-17-generic
lrwxrwxrwx 1 root root 24 Jun 18 17:41 vmlinuz.old ->
vmlinuz-5.0.0-17-generic
Notice the symlinks from initrd.img{,.old} point to non-existent
initrd.img-5.0.0-17-generic,
--
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/1829805
Title:
Lubuntu Eoan Daily Image fails to boot after install on KVM
Status in linux package in Ubuntu:
Confirmed
Bug description:
Context: The live environment appears to function properly and install
proceeds as expected with no noticeable errors.
Expected results: After a system reboot the virtual machine enters the
graphical environment
Actual Results: After rebooting the virtual machine a kernel panic
error screen appears. I will attempt to attach the screenshot after
submitting this bug report.
The collected data is from the live environment as the installed
environment will not boot.
lubuntu@lubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
Codename: eoan
lubuntu@lubuntu:~$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 2.02+dfsg1-12ubuntu2
Version table:
2.02+dfsg1-12ubuntu2 500
500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519)
eoan/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.407
CurrentDesktop: LXQt
Date: Tue May 21 00:30:39 2019
LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829805/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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 GRUB menu, highlight the default entry, press 'e' to edit it, navigate down to the line beginning "linux ..." and add the option "break=premount" then press Ctrl+X (or F10) to immediately boot with this change. This should drop you into the busbyox initramfs shell so you can investigate where the root-fs is. Start with "cat /proc/cmdline" and then verify the root= device actually exists. There are other points to break= at; On an working system identify them with: grep maybe_break /usr/share/initramfs-tools/init -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in linux package in Ubuntu: Confirmed Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
** 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 linux package in Ubuntu:
Confirmed
Bug description:
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 have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
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 rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
** 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 package in Ubuntu:
Confirmed
Bug description:
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 have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
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 rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
** 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. --- Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly disabled to capture the AERs. Memory seems to be consumed (~6 GB of 8GB) just by leaving PC overnight booted just to console (systemd.unit=multi-user.target). The memory leak doesn't affect Windows but owner is going to check Windows Event Log for signs of AERs being logged. --- - ## AERs (repeated several times per second) + Original suspect of AER is not guilty. - [ 34.978011] pcieport :00:1d.0: device [8086:9d1b] error status/mask=0001/2000 - [ 34.978013] pcieport :00:1d.0:[ 0] Receiver Error (First) - [ 34.978038] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 - [ 34.978042] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) + This turns out to be a bug in the rtlwifi driver where in some rare + circumstances it fails to free an sk_buf. - ## PCI device + Reporter has been testing a DKMS build of rtlwfi with the fix applied + and confirms it solves the issue. - +-1d.0-[04]00.0 Realtek Semiconductor Co., Ltd. RTL8723BE PCIe - Wireless Network Adapter [10ec:b723] + Upstream has the commit. Can we get this cherry-picked into all + releases? - 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1) (prog-if 00 [Normal decode]) - Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ - Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- - PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- - Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 - DevCap: MaxPayload 128 bytes, PhantFunc 0 - ExtTag- RBE+ - DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- - RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- - MaxPayload 128 bytes, MaxReadReq 128 bytes - DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- - LnkCap: Port #12, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us - ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ - LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ - ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- - LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- - SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- - Slot #11, PowerLimit 10.000W; Interlock- NoCompl+ - SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- - Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- - SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- - Changed: MRL- PresDet- LinkState+ - RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- - RootCap: CRSVisible- - RootSta: PME ReqID , PMEStatus- PMEPending- - DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+ - DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- - LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- -Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- -Compliance De-emphasis: -6dB - LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- -EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- - Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- - Address: fee002d8 Data: - Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:820a] - Capabilities: [a0] Power Management version 3 - Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) - Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- - Capabilities: [100 v1] Advanced Error Reporting - UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- -
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
** 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: rtlwifi: aggresive memory leak Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. --- Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly disabled to capture the AERs. Memory seems to be consumed (~6 GB of 8GB) just by leaving PC overnight booted just to console (systemd.unit=multi-user.target). The memory leak doesn't affect Windows but owner is going to check Windows Event Log for signs of AERs being logged. --- ## AERs (repeated several times per second) [ 34.978011] pcieport :00:1d.0: device [8086:9d1b] error status/mask=0001/2000 [ 34.978013] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 34.978038] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 [ 34.978042] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) ## PCI device +-1d.0-[04]00.0 Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #12, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #11, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee002d8 Data: Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:820a] Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
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/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. --- Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly disabled to capture the AERs. Memory seems to be consumed (~6 GB of 8GB) just by leaving PC overnight booted just to console (systemd.unit=multi-user.target). The memory leak doesn't affect Windows but owner is going to check Windows Event Log for signs of AERs being logged. --- ## AERs (repeated several times per second) [ 34.978011] pcieport :00:1d.0: device [8086:9d1b] error status/mask=0001/2000 [ 34.978013] pcieport :00:1d.0:[ 0] Receiver Error (First) [ 34.978038] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 [ 34.978042] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) ## PCI device +-1d.0-[04]00.0 Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #12, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #11, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee002d8 Data: Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:820a] Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Advanced Error Reporting UESta:
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. + + --- + Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly disabled to capture the AERs. + + Memory seems to be consumed (~6 GB of 8GB) just by leaving PC overnight + booted just to console (systemd.unit=multi-user.target). + + The memory leak doesn't affect Windows but owner is going to check + Windows Event Log for signs of AERs being logged. + + --- + + ## AERs (repeated several times per second) + + [ 34.978011] pcieport :00:1d.0: device [8086:9d1b] error status/mask=0001/2000 + [ 34.978013] pcieport :00:1d.0:[ 0] Receiver Error (First) + [ 34.978038] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 + [ 34.978042] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) + + ## PCI device + + +-1d.0-[04]00.0 Realtek Semiconductor Co., Ltd. RTL8723BE PCIe + Wireless Network Adapter [10ec:b723] + + 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d1b] (rev f1) (prog-if 00 [Normal decode]) + Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- + PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- + Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 + DevCap: MaxPayload 128 bytes, PhantFunc 0 + ExtTag- RBE+ + DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- + RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- + MaxPayload 128 bytes, MaxReadReq 128 bytes + DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- + LnkCap: Port #12, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <16us + ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ + LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ + ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- + LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- + SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- + Slot #11, PowerLimit 10.000W; Interlock- NoCompl+ + SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- + Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- + SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- + Changed: MRL- PresDet- LinkState+ + RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- + RootCap: CRSVisible- + RootSta: PME ReqID , PMEStatus- PMEPending- + DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Not Supported ARIFwd+ + DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- + LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- +Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- +Compliance De-emphasis: -6dB + LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- +EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- + Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- + Address: fee002d8 Data: + Capabilities: [90] Subsystem: Hewlett-Packard Company Device [103c:820a] + Capabilities: [a0] Power Management version 3 + Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) + Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- + Capabilities: [100 v1] Advanced Error Reporting + UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- + UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- + UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- + CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- + CEMsk: RxErr- BadTLP- BadDL
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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 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 Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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. https://bugs.launchpad.net/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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. https://bugs.launchpad.net/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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. https://bugs.launchpad.net/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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. https://bugs.launchpad.net/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** Attachment added: "ps -efly after overnight" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+attachment/5268937/+files/ps-efly.after-overnight.txt ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (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 Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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. https://bugs.launchpad.net/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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. https://bugs.launchpad.net/bugs/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: In Progress Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. + + # nogui boot, free memory reported at startup: + totalusedfree shared buff/cache available + 8055940 239824 73357923256 480324 7567576 + 2097148 0 2097148 + # after leaving overnight (user used 'free -m') + 78676836 230 3 800 763 + 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev-tools/kmemleak.html for how to make use of 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/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: Incomplete Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. # nogui boot, free memory reported at startup: totalusedfree shared buff/cache available 8055940 239824 73357923256 480324 7567576 2097148 0 2097148 # after leaving overnight (user used 'free -m') 78676836 230 3 800 763 2047 02047 This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: Possible memory leak due to PCI AER faults even with pci=noaer
** 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. + + This will likely need a custom kernel build that enables DEBUG_MEMLEAK, + see https://www.kernel.org/doc/html/v4.18/dev-tools/kmemleak.html for + how to make use of 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/1831751 Title: Possible memory leak due to PCI AER faults even with pci=noaer Status in linux package in Ubuntu: New Bug description: 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 have this problem on Ubuntu 17.10 but i was still flooded with message about pci aer taking lots of disk space in the logs, but pci=noaer fixed this problem and i had no memory leak. The computer is a common laptop: HP Pavilion. This will likely need a custom kernel build that enables DEBUG_MEMLEAK, see https://www.kernel.org/doc/html/v4.18/dev- tools/kmemleak.html for how to make use of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829402] Re: Purple screen hangup during boot
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 notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829402 Title: Purple screen hangup during boot Status in linux package in Ubuntu: Confirmed Bug description: Specs: Ubuntu 19.04 fresh install, everything updated Firmware is latest (Bios version 300) Asus vivobook s14 LVM disk encryption Steps to reproduce: - Install ubuntu 19.04/18.10 - Reboot - Purple screen indefinitely Setting kernel cmdline args only to ro nomodeset seems solves it. After some debugging session with #ubuntu with different cmdline args, it seems now the default one works too. I have not edited anything, but now i am unable to reproduce it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: markbartos 1778 F pulseaudio Date: Thu May 16 17:15:07 2019 InstallationDate: Installed on 2019-05-16 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3526 IMC Networks Bus 001 Device 002: ID 13d3:56c1 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430FA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX430FA.300:bd11/22/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
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 user on IRC testing permutations so I'm confident it is the same issue. -- 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: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpa
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
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 https://www.kernel.org/doc/html/latest/admin-guide/kernel- parameters.html -- 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: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with newer (Kaby lake) Intel CPU, intel-microcode WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/List
[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs
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 the kernel and initrd.img into memory. I'm wondering if the recent Intel microcode updates and related kernel patches could be responsible? Can you tell us what CPU the system has? $ cat /proc/cpuinfo -- 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 Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs
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 Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs
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 hibernation) are encrypted. If so cryptsetup and its supporting libraries and scripts are copied into the initrd.img-$KERNEL_VERSION file that is being built. Additionally, the /etc/crypttab entry for the root file-system device is added to the initialramfs's /conf/conf.d/cryptroot. At boot-time the initialramfs cryptsetup scripts read this file and should unlock the LUKS container. As that is not happening you should, when dropped at the initialramfs shell, check for the existence of the config and the tooling: # ls -l /conf/conf.d/cryptroot /bin/cryptroot-unlock /sbin/cryptsetup /lib/cryptsetup/askpass If they are present you can manually unlock using: # cryptsetup open /dev/sdXY sdXY_crypt Note: identify the LUKS container using: # blkid | grep crypt_LUKS and replace my example 'sdXY' with your device name. After a successful unlock scan for LVM volumes: # vgchange -ay Then let the init system resume operations by pressing Ctrl+D or typing: # exit If you're not in the initramfs but are looking at the broken system's file system from a LiveISO or similar you can check whether the cryptsetup tools are included in the initrd.img file using this command: # sudo ls -l /boot/initrd.img* # sudo lsinitramfs /boot/initrd.img-$KERNEL_VERSION | grep crypt cryptroot-keyfiles cryptroot-keyfiles/cryptswap1.key cryptroot-keyfiles/LUKS_VG02.key sbin/cryptsetup usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 conf/conf.d/cryptroot bin/cryptroot-unlock lib/cryptsetup lib/cryptsetup/askpass lib/x86_64-linux-gnu/libgcrypt.so.20.2.1 lib/x86_64-linux-gnu/libcryptsetup.so.12 lib/x86_64-linux-gnu/libgcrypt.so.20 lib/x86_64-linux-gnu/libcryptsetup.so.12.2.0 lib/modules/5.1.0-050100-lowlatency/kernel/crypto lib/modules/5.1.0-050100-lowlatency/kernel/crypto/crypto_simd.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/xor.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/cryptd.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/ecdh_generic.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_tx.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_memcpy.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_raid6_recov.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_pq.ko lib/modules/5.1.0-050100-lowlatency/kernel/crypto/async_tx/async_xor.ko lib/modules/5.1.0-050100-lowlatency/kernel/drivers/md/dm-crypt.ko lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto/glue_helper.ko lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto/aes-x86_64.ko lib/modules/5.1.0-050100-lowlatency/kernel/arch/x86/crypto/aesni-intel.ko scripts/local-bottom/cryptopensc scripts/local-block/cryptroot scripts/local-top/cryptroot scripts/local-top/cryptopensc -- 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 Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth
[Kernel-packages] [Bug 1829402] Re: Purple screen hangup during boot
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 TJ-, yes, but its non-determinitsitc so its hard to tell
15:39 if the error still exists or not
15:39 requires many boots.
...
15:43 TJ-, i got a bad boot this time.
15:43 TJ-, hanging black screen with 2 lines: first is what i said
above, second: 'error: can't find command `hwmatch`'
15:45 Jackneill: the fact you can see the text is a good thing, as it may
point to the issue not being video at all, but possibly something else that is
hanging the entire system
...
15:49 Jackneill: "hwmatch" is part of the GRUB boot-loader, and (is
supposed) to be executed by GRUB at boot-time to check if the GPU is included
in a blacklist: "/boot/grub/grub.cfg:122:if hwmatch
${prefix}/gfxblacklist.txt 3; then ..." - so it appears the hand-over from GRUB
to Linux kernel is failing
So, in GRUB GFX mode, which sets the background colour to the Ubuntu
themed 'purple' mentioned in this bug, the display is cleared when GRUB
hands over to the Linux kernel. If the kernel is not starting for some
reason that purple screen is all the user will see.
With GRUB_TERMINAL=console the display is not in a GFX mode, but text
only, so we get to see some clue at least!
--
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/1829402
Title:
Purple screen hangup during boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
Specs:
Ubuntu 19.04 fresh install, everything updated
Firmware is latest (Bios version 300)
Asus vivobook s14
LVM disk encryption
Steps to reproduce:
- Install ubuntu 19.04/18.10
- Reboot
- Purple screen indefinitely
Setting kernel cmdline args only to ro nomodeset seems solves it.
After some debugging session with #ubuntu with different cmdline args,
it seems now the default one works too. I have not edited anything,
but now i am unable to reproduce it.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: markbartos 1778 F pulseaudio
Date: Thu May 16 17:15:07 2019
InstallationDate: Installed on 2019-05-16 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:3526 IMC Networks
Bus 001 Device 002: ID 13d3:56c1 IMC Networks
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.0.0-15-generic N/A
linux-backports-modules-5.0.0-15-generic N/A
linux-firmware1.178.1
SourcePackage: linux
StagingDrivers: r8822be
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X430FA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X430FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrX430FA.300:bd11/22/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829402] Re: Purple screen hangup during boot
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' reboot) ? 2. Can 'journalctl --list-boots' be used to identify logs of a *failed* boot and use 'journalctl -b X' to grab the log file of the failed boot? 3. has 'GRUB_TERMINAL=console' in /etc/default/grub been tried (edit file to include that string without a leading # [comment prefix] then "sudo update-grub" and reboot to test) -- 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/1829402 Title: Purple screen hangup during boot Status in linux package in Ubuntu: Confirmed Bug description: Specs: Ubuntu 19.04 fresh install, everything updated Firmware is latest (Bios version 300) Asus vivobook s14 LVM disk encryption Steps to reproduce: - Install ubuntu 19.04/18.10 - Reboot - Purple screen indefinitely Setting kernel cmdline args only to ro nomodeset seems solves it. After some debugging session with #ubuntu with different cmdline args, it seems now the default one works too. I have not edited anything, but now i am unable to reproduce it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: markbartos 1778 F pulseaudio Date: Thu May 16 17:15:07 2019 InstallationDate: Installed on 2019-05-16 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3526 IMC Networks Bus 001 Device 002: ID 13d3:56c1 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430FA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX430FA.300:bd11/22/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803960] Re: 4.18.0 kernels hang system randomly
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 Ubuntu. https://bugs.launchpad.net/bugs/1803960 Title: 4.18.0 kernels hang system randomly Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: 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 are never any clues in the kernel logs so it is very difficult to point to anything that might cause it; there is never any obvious pattern in the workload, the user interaction, or state of the PC when the hang occurs. A week ago I switched to the Ubuntu mainline v4.19 builds and that resolved the issue. I was reminded of it again today when it hung a few minutes ago. After the reboot I checked the previous boot log and realised the PC had accidentally been booted with the default v4.18 kernel rather than v4.19. I don't think this report can be debugged but it is worth having a tracking bug in case other people experience the same issue with v4.18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813745] Re: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44
*** 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 Title: ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44 Status in linux package in Ubuntu: Confirmed Bug description: I updated my machine's kernel to 4.15.0-44. After a restart the whole machine was messed up. The machine starts regularly up to the point, where the graphical interface would appear (rough guess). The monitor gets black (normal) to change the screen resolution. Unfortunately, the monitor never comes back to life. Nothing useful is displayed anymore and my input devices are non-functional. I cannot change to any tty not change the state of the Num-Lock-LED on the keyboard. 4.15.0-43 kernel boots fine from grub-menu. From there, demsg shows a crash in Intel video driver: [ 47.320244] [ cut here ] [ 47.320245] Unknown pixelformat 0x [ 47.320267] WARNING: CPU: 2 PID: 3603 at /build/linux-vxxS7y/linux-4.15.0/drivers/media/v4l2-core/v4l2-ioctl.c:1291 v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320267] Modules linked in: rfcomm hid_generic uhid algif_hash algif_skcipher af_alg thunderbolt xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 cdc_ether usbnet iptable_nat nf_nat_ipv4 nf_nat ipheth r8152 mii snd_usb_audio snd_usbmidi_lib msr nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp cmac bridge stp llc bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 btusb btrtl btbcm btintel bluetooth ecdh_generic ebtable_filter ebtables devlink ip6table_filter ip6_tables pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) iptable_filter vboxdrv(O) snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek dell_laptop snd_hda_codec_generic snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp [ 47.320292] snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine intel_rapl x86_pkg_temp_thermal intel_powerclamp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf binfmt_misc kvm_intel kvm irqbypass joydev input_leds nls_iso8859_1 serio_raw snd_hda_intel dell_wmi snd_hda_codec dell_smbios dcdbas snd_hda_core dell_wmi_descriptor snd_hwdep wmi_bmof intel_wmi_thunderbolt snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ath10k_pci ath10k_core ath mac80211 idma64 virt_dma cfg80211 rtsx_pci_ms memstick mei_me intel_lpss_pci processor_thermal_device shpchp mei intel_lpss intel_soc_dts_iosf intel_pch_thermal int3403_thermal int340x_thermal_zone [ 47.320325] intel_hid int3400_thermal mac_hid acpi_thermal_rel acpi_pad sparse_keymap sch_fq_codel coretemp parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt nvme fb_sys_fops i2c_i801 nvme_core drm rtsx_pci i2c_hid wmi hid video pinctrl_sunrisepoint [ 47.320346] CPU: 2 PID: 3603 Comm: AudioThread Tainted: G O 4.15.0-43-generic #46-Ubuntu [ 47.320347] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018 [ 47.320350] RIP: 0010:v4l_fill_fmtdesc+0xf41/0x1250 [videodev] [ 47.320350] RSP: 0018:a8cc4530bc30 EFLAGS: 00010282 [ 47.320351] RAX: RBX: a8cc4530bd68 RCX: 0006 [ 47.320352] RDX: 0007 RSI: 0086 RDI: 8c8d6e496490 [ 47.320352] RBP: a8cc4530bc40 R08: 0001 R09: 04c7 [ 47.320353] R10: 8c8d5abe2d00 R11: R12: 8c8cda86c500 [ 47.320353] R13: c11bc900 R14: 8c8d5abe2d80 R15: 8c8cda86c500 [ 47.320354] FS: 7f9ad4ff9700() GS:8c8d6e48() knlGS: [ 47.320355] CS: 0010 DS: ES: CR0: 80050033 [ 47.320355] CR2: 7ff9f0083905 CR3: 00043fd80006 CR4: 003606e0 [ 47.320356] Call Trace: [ 47.320360] v4l_enum_fmt+0x74/0x110 [videodev] [ 47.320362] __video_do_ioctl+0x370/0x380 [videodev] [ 47.320364] ? terminate_walk+0x8e/0xf0 [ 47.320366] ? aa_path_perm+0xe2/0x130 [ 47.320367] ? aa_path_perm+0xf6/0x130 [ 47.320370] video_usercopy+0x24d/0x640 [videodev] [ 47.320372] ? video_ioctl2+0x20/0x20 [videodev] [ 47.320374] video_ioctl2+0x15/0x20 [videodev] [ 47.320376] v4l2_ioctl+0xc8/0xf0 [videodev] [ 47.320378] do_vfs_ioctl+0xa8/0x630 [ 47.320380] ? kmem_cache_free+0x1b3/0x1e0 [ 47.32038
[Kernel-packages] [Bug 1813769] Re: System crash with dual monitor setup
*** 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 4-15-0-44 -- 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/1813769 Title: System crash with dual monitor setup Status in linux package in Ubuntu: New Bug description: Laptop crashes after successfully login with 2nd monitor attached. If I attach the monitor after login system crashes when changing display settings , e.g. monitor positions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: b 1883 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 15:32:04 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-30 (90 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20JWS09Q00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=9354306a-00ba-43a3-85ce-209a58d47604 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET45W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JWS09Q00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET45W(1.35):bd07/12/2018:svnLENOVO:pn20JWS09Q00:pvrThinkPadT570W10DG:rvnLENOVO:rn20JWS09Q00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T570 W10DG dmi.product.name: 20JWS09Q00 dmi.product.version: ThinkPad T570 W10DG dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813765] Re: Regression/crash in i915 for 4.15.0-44.47
*** 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 duplicate of bug 1813745 ubuntu 18-04 hangs on graphical start with kernel 4-15-0-44 -- 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 Title: Regression/crash in i915 for 4.15.0-44.47 Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo T470s laptop with a Thinkpad Ultra dock. After upgrading kernel to 4.15.0-44, the system freeze and has to be hard reset (hold power button for 7 seconds) when booting, unlocking or changing display configuration when in dock. I downgraded the kernel to 4.15.0-43 and the problem went away. (The system information is collected after downgraded the kernel to 4.15.0-43 and removing 4.15.0-44.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaelstaldal 2219 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 29 13:20:45 2019 HibernationDevice: RESUME=UUID=3c08f9f9-c1a9-43fa-97c9-5dc4873f87d9 InstallationDate: Installed on 2018-10-12 (108 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004UMX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET25W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004UMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HF004UMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004UMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004UMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813765] Re: Regression/crash in i915 for 4.15.0-44.47
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 Title: Regression/crash in i915 for 4.15.0-44.47 Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo T470s laptop with a Thinkpad Ultra dock. After upgrading kernel to 4.15.0-44, the system freeze and has to be hard reset (hold power button for 7 seconds) when booting, unlocking or changing display configuration when in dock. I downgraded the kernel to 4.15.0-43 and the problem went away. (The system information is collected after downgraded the kernel to 4.15.0-43 and removing 4.15.0-44.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaelstaldal 2219 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 29 13:20:45 2019 HibernationDevice: RESUME=UUID=3c08f9f9-c1a9-43fa-97c9-5dc4873f87d9 InstallationDate: Installed on 2018-10-12 (108 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004UMX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET25W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004UMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HF004UMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004UMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004UMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813765] Re: Regression/crash in i915 for 4.15.0-44.47
>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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813765 Title: Regression/crash in i915 for 4.15.0-44.47 Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo T470s laptop with a Thinkpad Ultra dock. After upgrading kernel to 4.15.0-44, the system freeze and has to be hard reset (hold power button for 7 seconds) when booting, unlocking or changing display configuration when in dock. I downgraded the kernel to 4.15.0-43 and the problem went away. (The system information is collected after downgraded the kernel to 4.15.0-43 and removing 4.15.0-44.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaelstaldal 2219 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 29 13:20:45 2019 HibernationDevice: RESUME=UUID=3c08f9f9-c1a9-43fa-97c9-5dc4873f87d9 InstallationDate: Installed on 2018-10-12 (108 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004UMX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET25W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004UMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HF004UMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004UMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004UMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813765] Re: Regression/crash in i915 for 4.15.0-44.47
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: Send DPCD ON for MST before phy_up 0f5eea60a4f8 2019-01-14 09:28:55 + N Kenneth Graunke drm/i915: Enable provoking vertex fix on Gen9 systems. ** Summary changed: - Freeze on Lenovo laptop in dock station + Regression/crash in i915 for 4.15.0-44.47 -- 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 Title: Regression/crash in i915 for 4.15.0-44.47 Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo T470s laptop with a Thinkpad Ultra dock. After upgrading kernel to 4.15.0-44, the system freeze and has to be hard reset (hold power button for 7 seconds) when booting, unlocking or changing display configuration when in dock. I downgraded the kernel to 4.15.0-43 and the problem went away. (The system information is collected after downgraded the kernel to 4.15.0-43 and removing 4.15.0-44.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikaelstaldal 2219 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 29 13:20:45 2019 HibernationDevice: RESUME=UUID=3c08f9f9-c1a9-43fa-97c9-5dc4873f87d9 InstallationDate: Installed on 2018-10-12 (108 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004UMX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET25W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004UMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HF004UMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004UMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004UMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637347] Re: Xubuntu 16.10: drm errors causing slow boot
*** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1637347 Title: Xubuntu 16.10: drm errors causing slow boot Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: I have been getting drm errors since updating to 16.10 causing slow boot times. Ex: 3.830465] jhm-Inspiron-1520 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 13.792249] jhm-Inspiron-1520 kernel: [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out There is ten second gap in the above adjacent lines. I have a few of these in the journal log. These errors also cause Xorg to stall during mode setting also, as seen in the adjacent Xorg.0.log file. [55.988] (II) modeset(0): Output VGA-1 has no monitor section [66.615] (II) modeset(0): Output SVIDEO-1 has no monitor section Using the Ubuntu test kernels, the best result I have gotten is from kernel 4.5.6. At 4.6.0 the wheels start to come off the wagon. At 4.9.0 rc1 the boot stopped at the busybox initrd shell. 4.8.0 fails decompressing the hibernate image as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jhm1262 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 27 17:02:19 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=bd7562ce-d720-4e95-995e-48f0ec1a77aa InstallationDate: Installed on 2016-10-12 (15 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Inspiron 1520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=5dc9cf92-93d8-4e84-826d-6b4d5f6e1c0d ro plymouth:debug=1 vesafb.invalid=1 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-15 (12 days ago) dmi.bios.date: 02/03/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0KY767 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY767:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 DistroRelease: Ubuntu 16.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-12 (15 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: yakkety Uname: Linux 4.6.0-040600rc1-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to yakkety on 2016-10-15 (12 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1637347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1621719] Re: Black screen when resuming laptop from sleep
*** 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 system freeze after vt switching -- 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/1621719 Title: Black screen when resuming laptop from sleep Status in elementary OS: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid and sleep it overnight 2. Open lid and see lock screen 3. Enter password at lock screen 4. Get a black screen with on the cursor Expected results: See the Elementary desktop Hardware: Lenovo Thinkpad x220 ProblemType: Bug DistroRelease: elementary 0.4 Package: elementary-desktop 1.414+469+r1~daily~ubuntu0.4.1 [origin: LP-PPA-elementary-os-daily] ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: elementary_meta CurrentDesktop: Pantheon Date: Thu Sep 8 20:44:28 2016 InstallationDate: Installed on 2016-09-08 (0 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160716) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: elementary-meta SuspiciousXErrors: ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1621719/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
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 commit 32db0b6501d97b09e92e70caefc74fa35aa9a8d6 Author: Ville Syrjälä Date: Tue Nov 27 22:05:50 2018 +0200 drm/i915: Don't try to use the hardware frame counter with i965gm TV output -- 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/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-lts-xenial package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-lts-xenial source package in Xenial: In Progress Status in Fedora: Confirmed Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
*** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1785326
Title:
The booting is too long with drm_atomic_helper_wait_for_dependencies
errors (xenial+hwe,bionic).
Status in linux package in Ubuntu:
Confirmed
Bug description:
1,2) Please see the apport attachments
3) Fast booting without errors as with xenial non-hwe kernels
4) The booting is too long
The errors are similar to this:
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[CRTC:41:pipe B] flip_done timed out
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[PLANE:35:plane B] flip_done timed out
The errors appears on Toshiba Satellite L300-11Q.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: LXDE
Date: Fri Aug 3 20:34:23 2018
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-20-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lubuntu1707 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x9430 irq 26'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1179ff64,0013
HDA:11c11040,11790001,00100200'
Controls : 20
Simple ctrls : 9
CasperVersion: 1.394
CurrentDesktop: LXDE
DistroRelease: Ubuntu 18.04
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: TOSHIBA Satellite L300
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=ru
keyboard-configuration/layoutcode?=ru
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
linux-restricted-modules-4.15.0-20-generic N/A
linux-backports-modules-4.15.0-20-generic N/A
linux-firmware 1.173
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/10/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.50
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: Satellite L300
dmi.product.version: PSLB0E-014012RU
dmi.sys.vendor: TOSHIBA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789258] Re: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out
*** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1789258 Title: drm:drm_atomic_helper_wait_for_dependencies flip_done timed out Status in linux package in Ubuntu: Confirmed Bug description: every now an then the system freezes but eventually comes back to life. the boot process is especially slow, login greeter takes ages to come up and then, while there, needs some extra time to unfreeze and actually allow typing in the password. the freeze can be easily reproduced each time when switching from graphics to console (with ctrl-alt-fN) and back. each time the dmesg gets also gets appended with the error messages that can be found in the attached text file. is the workaround really to uninstall intel's xorg drivers? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-intel1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Aug 27 20:03:14 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (primary) [17aa:383e] Subsystem: Lenovo Mobile GM965/GL960 Integrated Graphics Controller (secondary) [17aa:383e] InstallationDate: Installed on 2018-08-24 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 0769BJG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=5c1b96ff-002e-4358-bf56-8dd74e76584d ro dis_ucode_ldr SourcePackage: libdrm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769BJG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Lenovo dmi.product.name: 0769BJG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
*** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux
[Kernel-packages] [Bug 1767808] Re: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15
*** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1767808 Title: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15 Status in linux package in Ubuntu: Confirmed Bug description: With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 Integrated Graphics (driver i915). In total it is 198 seconds that are lost in these timeouts during boot, more than 3 minutes! Regression is present since linux kernel 4.8 (with Ubuntu 16.04). To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. 1/ sudo gedit /etc/default/grub 2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line 3/ sudo update-grub After applying this, the system boots up much faster, there are no "drm ... timed out" messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774845] Re: [Dell Inspiron 1525] Booting takes a couple more minutes than normal
*** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1774845 Title: [Dell Inspiron 1525] Booting takes a couple more minutes than normal Status in linux package in Ubuntu: Incomplete Bug description: Booting into a installed environment takes a few more minutes than normal. WORKAROUND: Use kernel parameter: video=SVIDEO-1:d --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rose 1084 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=f871d5a4-72c8-4c2b-b9a2-17f18a8ae520 InstallationDate: Installed on 2018-05-07 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 1525 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=903c6b4d-dc72-4b1e-ad11-fc1ac80687ea ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637347] Re: Xubuntu 16.10: drm errors causing slow boot
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 commit 32db0b6501d97b09e92e70caefc74fa35aa9a8d6 Author: Ville Syrjälä Date: Tue Nov 27 22:05:50 2018 +0200 drm/i915: Don't try to use the hardware frame counter with i965gm TV output ** Bug watch added: freedesktop.org Bugzilla #93782 https://bugs.freedesktop.org/show_bug.cgi?id=93782 ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=93782 Importance: Unknown Status: Unknown -- 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/1637347 Title: Xubuntu 16.10: drm errors causing slow boot Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: I have been getting drm errors since updating to 16.10 causing slow boot times. Ex: 3.830465] jhm-Inspiron-1520 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 13.792249] jhm-Inspiron-1520 kernel: [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR* [CRTC:26:pipe A] flip_done timed out There is ten second gap in the above adjacent lines. I have a few of these in the journal log. These errors also cause Xorg to stall during mode setting also, as seen in the adjacent Xorg.0.log file. [55.988] (II) modeset(0): Output VGA-1 has no monitor section [66.615] (II) modeset(0): Output SVIDEO-1 has no monitor section Using the Ubuntu test kernels, the best result I have gotten is from kernel 4.5.6. At 4.6.0 the wheels start to come off the wagon. At 4.9.0 rc1 the boot stopped at the busybox initrd shell. 4.8.0 fails decompressing the hibernate image as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-26-generic 4.8.0-26.28 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jhm1262 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 27 17:02:19 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=bd7562ce-d720-4e95-995e-48f0ec1a77aa InstallationDate: Installed on 2016-10-12 (15 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Inspiron 1520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=5dc9cf92-93d8-4e84-826d-6b4d5f6e1c0d ro plymouth:debug=1 vesafb.invalid=1 RelatedPackageVersions: linux-restricted-modules-4.8.0-26-generic N/A linux-backports-modules-4.8.0-26-generic N/A linux-firmware1.161 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-15 (12 days ago) dmi.bios.date: 02/03/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0KY767 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY767:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 DistroRelease: Ubuntu 16.10 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-12 (15 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: yakkety Uname: Linux 4.6.0-040600rc1-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to yakkety on 2016-10-15 (12 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1637347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** 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/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: Incomplete Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
Related Canonical/Ubuntu hardware certification for this model. Notes suggest Dell-installed image is/may not be the same as used by Ubuntu. https://certification.ubuntu.com/hardware/201707-25590/ -- 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/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: In Progress Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
Here is another related experience which may give some insight: https://ubuntuforums.org/showthread.php?t=2381899 -- 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/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: In Progress Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
Have you used the service tag to see if you can get a link to the Dell Ubuntu 16.04 installation images? "For those who purchased their system from Dell with Ubuntu already installed, there are recovery images on their system and if fitting a new hard drive they can download an installation image by going to the Dell Support site and entering the systems service tag or express service code and selecting Drivers and Downloads." >From https://www.dell.com/support/article/uk/en/ukbsdt1/sln151664/how- to-install-ubuntu-linux-on-your-dell-pc?lang=en Alternatively you may need to contact Dell support directly - that might be the better option here since presumably Dell have configured these images to 'just work' and save you some time needing to debug 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/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: In Progress Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
** Summary changed: - Boot failure on Dell Dell Precision 5820 with Intel Xeon W-2123 CPU + Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (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/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: In Progress Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
Ike, I've subscribed you since I notice you're listed as an upstream maintainer of this module. Are you able to get this committed in mainline and SRU-ed into Ubuntu kernels? -- 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/1811815 Title: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked Status in linux package in Ubuntu: Confirmed Bug description: The issue here is that the drivers/platform/x86/ideapad_laptop.c module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill switch, reads the I/O port for its state, gets a zero, and therefore reports to the kernel that RFkill is hard-blocked. The current workaround is to blacklist the module to stop it being loaded. I've attached a simple patch for the module that teaches it that this model does not have a hardware RF kill switch. Original Report - Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811869] Re: Alienware m15 takes very long to boot Ubuntu
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- 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 Status in linux package in Ubuntu: In Progress Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811869] Re: Alienware m15 takes very long to boot Ubuntu
** Changed in: linux (Ubuntu) Assignee: (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/1811869 Title: Alienware m15 takes very long to boot Ubuntu Status in linux package in Ubuntu: New Bug description: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
