[Kernel-packages] [Bug 1831587] Re: brightness control not work with OLED panel
When using multiple monitors, and disconnecting and reconnecting them, I
noticed that Ubuntu 20.04 likes to set the external monitor's brightness
to 0.06, and the laptop's brightness to maximum. This is done without
changing the file at
(/sys/class/backlight/intel_backlight/actual_brightness).
I have modified the above script to work with multiple monitors, and to
change the brightness whenever a discrepancy between the desired and
actual brightnesses of all monitors is detected. The script assumes that
the internal laptop monitor's brightness is the only one to be changed
by brightness keys, and that the laptop's monitor is the first monitor
listed in the command `xrandr --listmonitors`.
Please reply if you have any issues with this script, as I do want to
improve this.
#!/bin/bash
#-
# /usr/local/bin/brightness
# be sure this file is executable
#-----
# Define a function which finds luminance values in default Ubuntu
# location, converts into a factor of maximum brightness
# Get the max brightness for reference.
# Get it to 2 decimal places
backlight_path=/sys/class/backlight/intel_backlight
read -r max < "$backlight_path"/max_brightness
luminance() {
read -r level < "$backlight_path"/actual_brightness
printf "%.2f" $(bc <<< "scale=10;$level/$max")
}
# Set up infinite loop
while true
do
# Get the current brightness levels from xrandr. Store in array
mapfile \
-t xrandrbrightness \
< <(xrandr --verbose --current \
| grep Brightness \
| sed 's/.* //' \
| xargs printf "%.2f\n")
# Get list of monitors and store in array
mapfile \
-t monitors \
< <(xrandr --listmonitors --current \
| grep -v 'Monitors' \
| awk '{print $4}')
# If the current brightness for monitor 0 != the desired value +/-0.01
if (( $(echo "${xrandrbrightness[0]} != $(luminance)" | bc -l) ))
then
# Set the brightness of the laptop monitor to the desired value
echo "${monitors[0]} Current:${xrandrbrightness[0]}
Desired:$(luminance)"
xrandr --output "${monitors[0]}" --brightness "$(luminance)"
fi
# Go through the rest of the monitors in the list
for (( i=1; i<${#monitors[@]}; i++ ))
do
# Change the brightness of external monitors to 1 if they aren't
if (( $(echo "${xrandrbrightness[$i]} != 1.00" | bc -l) ))
then
echo "${monitors[$i]} Current:${xrandrbrightness[$i]}"
xrandr --output "${monitors[$i]}" --brightness 1
fi
done
# Check every 100ms
sleep 0.1
done
--
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/1831587
Title:
brightness control not work with OLED panel
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
image: disco 19.04
kernel: 5.0.0-15-generic
also verified failed on linux-image-unsigned-5.2.0-050200rc2-generic
also refer to :
-
https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness
- https://bugs.freedesktop.org/show_bug.cgi?id=97883
Linux can not control the brightness on the OLED panel in the traditional way
[1].
Although there's a workaround from the community [2] that to execute script
while brightness hotkey event is triggered. But if we want to upstream it, it's
still a problem to recognize the OLED panel so that the system knows when to go
workaround.
- EDID of my laptop which has OLED: https://paste.ubuntu.com/p/w7rVqJTYDy/
- EDID of the same model without OLED: https://paste.ubuntu.com/p/P3ChhX9yBJ/
there's a kernel patch related OLED for reference:
- https://patchwork.kernel.org/patch/6133471/
[1] https://wiki.ubuntu.com/Kernel/Debugging/Backlight
[2]
https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831587/+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 1864897] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333121/+files/ProcModules.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/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333113/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333122/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333115/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] Re: booting 5.3.0-40 with encrypted disk fails
apport information ** Tags added: apport-collected ** Description changed: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: al 1309 F pulseaudio + /dev/snd/controlC0: al 1309 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-10-17 (137 days ago) + InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-29-generic N/A + linux-backports-modules-5.3.0-29-generic N/A + linux-firmware1.183.4 + Tags: eoan + Uname: Linux 5.3.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/16/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X512DA.305 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X512DA + 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: VivoBook + dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333111/+files/AlsaInfo.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/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pul
[Kernel-packages] [Bug 1864897] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333114/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333112/+files/CRDA.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/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333118/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333123/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333120/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333124/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333117/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333116/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333119/+files/ProcEnviron.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/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1864897/+attachment/5333125/+files/WifiSyslog.txt ** 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/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1864897] Re: booting 5.3.0-40 with encrypted disk fails
Kernel installed as described in https://wiki.ubuntu.com/Kernel/MainlineBuilds . First dpkg -i linux- image- unsigned-5.6.0-050600rc4-generic_5.6.0-050600rc4.202003012332_amd64.deb was terminated unsuccessfully with error messages; trying it again as last instead of third file yielded several messages but worked. The test kernel boots OK, i. e., the password for disk decryption is asked for and afterwards the user password. -- 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/1864897 Title: booting 5.3.0-40 with encrypted disk fails Status in linux package in Ubuntu: Confirmed Bug description: Booting the laptop with 5.3.0-40 (Asus Vivo Book, AMD Ryzen 3) ends up in a blank screen. Selecting 5.3.0-29 in the grub menu instead works, i. e., "please unlock disk" is displayed and after doing so xubuntu 19.10 is started. The installation is encrypted as provided by the installer. Is some different but might be related to bug #1863759. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Feb 26 18:11:45 2020 InstallationDate: Installed on 2019-10-17 (131 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-02-24 17:34:11.828555 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1309 F pulseaudio /dev/snd/controlC0: al 1309 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-17 (137 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_F512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA 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.:bvrX512DA.305:bd07/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_F512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_F512DA 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/1864897/+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 1788997] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180634/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180642/+files/ProcModules.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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180644/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
apport information ** Tags added: apport-collected bionic ** Description changed: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. - The expectation is that wifi through rtl8723be will still work under - 4.15.0-33.36 as it did previously. + The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: al 1234 F pulseaudio + /dev/snd/controlC0: al 1234 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2018-05-27 (89 days ago) + InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: Hewlett-Packard HP Notebook + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-33-generic N/A + linux-backports-modules-4.15.0-33-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/01/2015 + dmi.bios.vendor: Insyde + dmi.bios.version: F.02 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 8137 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 99.02 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV G=N L=CON B=HP + dmi.product.name: HP Notebook + dmi.product.version: Type1ProductConfigId + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180632/+files/AlsaInfo.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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chas
[Kernel-packages] [Bug 1788997] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180635/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180638/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180641/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180633/+files/CRDA.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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180636/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180637/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180646/+files/WifiSyslog.txt ** 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180643/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180645/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
The above diagnosis was performed having started the computer with 4.15.0-33.36 amd64; as a result there was no network connection. To obtain network connection for submitting the data, a Gigaset USB Adapter 108 has been plugged in prior to running apport-collect 1788997. -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180639/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1788997/+attachment/5180640/+files/ProcEnviron.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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Thx! With the test kernel from http://kernel.ubuntu.com/~jsalisbury/lp1788997 according to #21 wifi of the laptop HP 1S-af023ngof works again. So reverting commit af8a41cccf8f469165c6debc8fe07c5fd2ca501a seems to fix 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1781016] Re: Slow flood of do_IRQ: No irq for vector
Running an Intel S2600ST motherboard with dual Gold 6148 I get this error regularly after the last kernel update I did. The number before the dot seems to be a CPU number since I see many varied numbers and there's 40 cores/80 threads on my motherboard e.g. [Wed Dec 26 14:20:25 2018] do_IRQ: 14.216 No irq handler for vector [Wed Dec 26 18:35:32 2018] do_IRQ: 46.40 No irq handler for vector [Thu Dec 27 00:56:21 2018] do_IRQ: 15.55 No irq handler for vector (there are 37 of these over the last 2 weeks) There's no /sys/kernel/debug/irq/ folder The current kernel on "Ubuntu 16.04.5 LTS" I am using is "vmlinuz-4.4.0-140-generic" I updated from "vmlinuz-4.4.0-119-generic" (which was also 16.04 LTS) I've had this server for over a year and with the 4.4.0-140 update is the first time I've seen this. -- 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/1781016 Title: Slow flood of do_IRQ: No irq for vector Status in linux package in Ubuntu: Incomplete Bug description: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 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.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cv
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
Hi! Finally I also upgraded to Kubuntu 14.04, and have also still the crackles. Since it is a very old Laptop, there are only USB 2.0 connectors, so for sure no USB-3.0 problem... And: running on the same laptop daphile (which is a headless player based on Gentoo) works fine, without any problems. Wondering why it's fine with that one, but not Kubuntu... So, let's see if I can help anything... Here's my lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 003: ID 0451:8200 Texas Instruments, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub So, the 5th is the DAC, a Audiolab 8200CD. (no other USB devices connected) dmesg gives a lot of outputs, so only ones that differ while playback are: [19545.228188] 3:2:1: cannot get freq at ep 0x1 [19545.231204] 3:2:1: cannot get freq at ep 0x1 [19549.621200] delay: estimated 265, actual 44 (all other lines are similar to: [19550.940214] status interrupt: 80 02) Since I am also more a user then a linux pro: what prompts might be useful to narrow the problem down? -- 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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split trans
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
Ok, finally got the time. Attached is the output stream with some audible cracks, like explained above. Hope I did it right... Not sure if the output of cat /sys/kernel/debug/usb/devices is of any interest, but here it is: T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0451 ProdID=8200 Rev= 1.60 S: Manufacturer=Lakewest Audio S: Product=Audiolab 8200 Series C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr= 0mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=32ms I:* If#= 1 Alt= 0 #EPs= 1 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=32ms I:* If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio I: If#= 2 Alt= 1 #EPs= 2 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio E: Ad=01(O) Atr=05(Isoc) MxPS= 582 Ivl=1ms E: Ad=81(I) Atr=11(Isoc) MxPS= 3 Ivl=1ms ** Attachment added: "output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1136110/+attachment/4124889/+files/1.mon.out -- 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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDe
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
Not sure if uploading my attachment worked right, got a confirmation, but can't find it in my comment. Used the "add attachment" below the comment field. If it is lost somewhere, I could upload it again. -- 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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 0053A11 MarkForUpload: True Package: linux 3.5.0.26.32 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Proc
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
Thanks for looking into it! But I wonder, if this should be an issue of my hardware, why I can use the same laptop with the same DAC without problems with daphile (http://www.daphile.com/ , a headless Gentoo-based player)? Shouldn't daphile have the same problems? Or is there a way to configure the PCI bus to get it working? -- 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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 0053A11 MarkForUpload: True Package: linux 3.5.0.26.32 PackageArchitecture: amd64 Pr
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
@mark: since i have the same problem (see #158) and am also unexperienced with kernel installations, I just wait now until the kernel 3.13 is in the package updates, I hope at latest with 14.04, so in 2 months... or is there anywhere a simple manual how to do this update? which kernel will be in 14.04? or will be an kernel-update before? -- 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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 0053A11 MarkForUpload: True Package: linux 3.5.0.26.32 PackageArchitecture: amd6
[Kernel-packages] [Bug 1325884] Re: [Asus X550LD] Microphone not working Ubuntu 14.04
This same bug with the same hardware exists. I have a fresh install of kubuntu 14.0.1 fully updated and I have this issue on my X550L laptop. -- 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/1325884 Title: [Asus X550LD] Microphone not working Ubuntu 14.04 Status in “linux” package in Ubuntu: Expired Bug description: Want to record with audacity but there is no voice input. With the rc2 upstream-kernel the microphone was working as it should; in the rc8 again no voice. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-27-generic 3.13.0-27.50 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jibba 1820 F pulseaudio /dev/snd/controlC1: jibba 1820 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 3 11:21:21 2014 HibernationDevice: RESUME=UUID=8565074e-439a-43bc-942f-c601146e3278 InstallationDate: Installed on 2014-05-15 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. X550LD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic.efi.signed root=UUID=8485f9a5-8383-4eb2-8965-b2b55dc40c51 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-27-generic N/A linux-backports-modules-3.13.0-27-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LD.300:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnX550LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LD 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/1325884/+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 1440618] Re: BUG: unable to handle kernel paging request at 00007f4c3ab447c0
I have the same problem with Ubuntu 15.04. Only kernel 3.18.0-13 or previous versions work. All 3.19.* kernels also 4.* RC will freeze the system after a few seconds... -- 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/1440618 Title: BUG: unable to handle kernel paging request at 7f4c3ab447c0 Status in linux package in Ubuntu: Incomplete Bug description: Freeze when i use virtual machine on virtualbox after few minutes ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-12-generic 3.19.0-12.12 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 Annotation: Your system might become unstablenow and might need to be restarted. ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lightdm1336 F pulseaudio futex 1750 F pulseaudio /dev/snd/controlC0: lightdm1336 F pulseaudio futex 1750 F pulseaudio Date: Mon Apr 6 01:02:40 2015 DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: 0010:location location 0xc001d415 Failure: oops HibernationDevice: RESUME=UUID=e929b771-de16-42ca-aca5-f1af14d69c6e InstallationDate: Installed on 2015-04-04 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224) MachineType: LENOVO 20BX000TML ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic root=/dev/mapper/rootvg-rootlv ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 SourcePackage: linux Title: BUG: unable to handle kernel paging request at 7f4c3ab447c0 UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000TML dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BX000TML:pvrThinkPadT450s:rvnLENOVO:rn20BX000TML:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX000TML dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440618/+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 1136110] Re: USB Audio Codec choppy playback
Just a short update: Since my old computer brock down (more then 8 years old laptop), I have now a Thinkpad T450p. Running Kubuntu 14.10, as before my DAC is an Audiolab 8200CD. And this issue does not occur anymore, neither on the USB 2 nor USB 3 plug. So might have been really an hardware issue somehow for me before. Cheers! -- 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/1136110 Title: USB Audio Codec choppy playback Status in linux package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 0053A11 MarkForUpload: True Package: linux 3.5.0.26.32 PackageArchitecture: amd64 ProcEnv
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
Think I have similar problems using my Audiolab 8200 CD with the latest Kubuntu (Kernel 3.11.0-14). Described my problem here: http://ubuntuforums.org/showthread.php?t=2190729 , but got no useful help, and found now this bug report. Please let me know if I can do something what would help the debugging, beside the informations in the link... ** Changed in: linux (Ubuntu) Assignee: (unassigned) => a! (a-guenther) -- 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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineTyp
[Kernel-packages] [Bug 1136110] Re: USB Audio Codec choppy playback
** Changed in: linux (Ubuntu) Assignee: a! (a-guenther) => (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/1136110 Title: USB Audio Codec choppy playback Status in “linux” package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu using Ubuntu 12.10 AMD64. Ubuntu 13.04 AMD64, daily build as new as 20130314. 2) The version of the package used linux-image-3.5.0-26-generic linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.6-quantal/ linux-image-3.7.7-030707-generic_3.7.7-030707.201302111436_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7.7-raring/ linux-image-3.8.0-030800rc7-generic_3.8.0-030800rc7.201302081635_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ This bug had been confirmed appearing after the following kernel upgrade step: v3.5.0-25 > v3.5.0-26 ~ v3.5.0-27 v3.5.7.5 > v3.5.7.6 ~ v3.5.7.8 v3.7.6 > v3.7.7 ~ v3.7.10 v3.8.0-rc6 > v3.8.0-rc7 ~ v3.8.5 The v3.9 branch has been affected since its very first release. v3.9-rc1, v3.9-rc2, v3.9-rc3 v3.9-rc4 are all affected. 3) What you expected to happen When using a USB DAC to play audio, the audio should be played normally without any interruption. 4) What happened instead This bug seems to affect only a certain kind of hardware, which is called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so called "Synchronous USB DAC", uses the clock hosted by the mother board, which is not affected by this bug. When this bug affects an asynchronous USB DAC, the audio played by the DAC is constantly interrupted. The playback itself does not stop, but the output becomes discontinous, filling with constant crackling noises, destroying everything the DAC plays. Using CLI command grep device.buffering to get the buffer from the devices, those affected kernels are reporting back a different number to the unaffected devices. The choppy noise is very similar to the situation when buffer size is not correctly set. I have tested four USB DACs, two Asynchronous and two Synchronous. Only the Asynchronous ones are affected by this bug. Affected Devices: Arce MDAC5 Arce MDAC mini Ayre Acoustics QB-9 Dragonfly USB DAC Musical Fidelity v2 DAC USB Audio Streaming Controller on affected devices: Texas Instrument TAS1020 http://www.ti.com/product/tas1020 Audio DAC on affected devices: Texas Instruments PCM1742 http://www.ti.com/product/pcm1742 This bug had been confirmed appearing after the following kernel upgrade step: 3.5.0-25 > 3.5.0-26 3.5.7.5 > 3.5.7.6 (and all 3.5.7.x above) 3.7.6 > 3.7.7 (and all 3.7.x above) 3.8.0-rc6 > 3.8.0-rc7 (and all 3.8.x above) I used Kdiff to find the similar patches, and find the following patches suspicous: USB: XHCI: fix memory leak of URB-private data (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix for leaking isochronous data (appeared in 3.7.7/3.8.0-rc7) usb: Prevent dead ports when xhci is not enabled (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) usb: Using correct way to clear usb3.0 device's remote wakeup feature (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: remove ASS/PSS polling timeout (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: unlink one async QH at a time (appeared in 3.7.7/3.8.0-rc7) USB: EHCI: fix timer bug affecting port resume (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) USB: EHCI: fix bug in scheduling periodic split transfers (appeared in 3.5.7.6/3.7.7/3.8.0-rc7) Hope someone can look into this bug soon! --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tysontan 2117 F pulseaudio /dev/snd/controlC1: tysontan 2117 F pulseaudio /dev/snd/pcmC1D0p: tysontan 2117 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=8545c3e2-caba-4eaa-8fa4-2fbebcc2d9bb InstallationDate: Installed on 2013-02-15 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: LENOVO 0053A11 MarkForUpload: True Package: linux 3.5.0.26.32 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic root=UUID=8c60a142-505f-4d74-afa0-376
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
Are you kidding download 500 Mb if someone changed one line in some config ? I reverted to debian because of this. You are mad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+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 1926107] [NEW] After LTS upgrade to 20.04 mdadm init.d are all broken links
Public bug reported: Upgraded a number of servers (more than 30) from various LTS versions to LTS 20.04 In each case that uses mdadm, all links for mdadm in /etc/rcX.d/*mdadm* are broken links. Every upgraded server using mdadm matches the issue exactly, but choosing one server: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" mdadm: Installed: 4.1-5ubuntu1.2 Easiest way to see the issue is to type: # ls -lasd `find /etc | grep mdadm` 4 -rw-r--r-- 1 root root 831 Dec 15 22:36 /etc/default/mdadm 4 -rw-r--r-- 1 root root 3426 Feb 28 2014 /etc/logcheck/ignore.d.server/mdadm 4 -rw-r--r-- 1 root root 411 Feb 28 2014 /etc/logcheck/violations.d/mdadm 4 drwxr-xr-x 2 root root 4096 Dec 15 22:36 /etc/mdadm 4 -rw-r--r-- 1 root root 982 Dec 15 22:36 /etc/mdadm/mdadm.conf 4 -rw-r--r-- 1 root root 379 Jan 15 2020 /etc/modprobe.d/mdadm.conf 0 lrwxrwxrwx 1 root root 15 Jul 3 2016 /etc/rc0.d/K01mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 24 Dec 15 22:11 /etc/rc0.d/K05mdadm-waitidle -> ../init.d/mdadm-waitidle 0 lrwxrwxrwx 1 root root 15 Jul 3 2016 /etc/rc1.d/K01mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc2.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc3.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc4.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc5.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Jul 3 2016 /etc/rc6.d/K01mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 24 Dec 15 22:11 /etc/rc6.d/K05mdadm-waitidle -> ../init.d/mdadm-waitidle Since init.d/mdadm and init.d/mdadm-waitidle don't exist, all the /etc/rcX.d/*mdadm* links are broken links - and in a colour terminal are all highlighted distinctly All systems boot successfully, so I'm not sure if it is simply a cleanup issue during upgrade from 18.04 to 20.04, or if the files should exist? However, a previous version desktop, which is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS" has init.d/mdadm and init.d/mdadm-waitidle thus they aren't broken links ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => mdadm (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/1926107 Title: After LTS upgrade to 20.04 mdadm init.d are all broken links Status in mdadm package in Ubuntu: New Bug description: Upgraded a number of servers (more than 30) from various LTS versions to LTS 20.04 In each case that uses mdadm, all links for mdadm in /etc/rcX.d/*mdadm* are broken links. Every upgraded server using mdadm matches the issue exactly, but choosing one server: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" mdadm: Installed: 4.1-5ubuntu1.2 Easiest way to see the issue is to type: # ls -lasd `find /etc | grep mdadm` 4 -rw-r--r-- 1 root root 831 Dec 15 22:36 /etc/default/mdadm 4 -rw-r--r-- 1 root root 3426 Feb 28 2014 /etc/logcheck/ignore.d.server/mdadm 4 -rw-r--r-- 1 root root 411 Feb 28 2014 /etc/logcheck/violations.d/mdadm 4 drwxr-xr-x 2 root root 4096 Dec 15 22:36 /etc/mdadm 4 -rw-r--r-- 1 root root 982 Dec 15 22:36 /etc/mdadm/mdadm.conf 4 -rw-r--r-- 1 root root 379 Jan 15 2020 /etc/modprobe.d/mdadm.conf 0 lrwxrwxrwx 1 root root 15 Jul 3 2016 /etc/rc0.d/K01mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 24 Dec 15 22:11 /etc/rc0.d/K05mdadm-waitidle -> ../init.d/mdadm-waitidle 0 lrwxrwxrwx 1 root root 15 Jul 3 2016 /etc/rc1.d/K01mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc2.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc3.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc4.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Dec 15 22:09 /etc/rc5.d/S03mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 15 Jul 3 2016 /etc/rc6.d/K01mdadm -> ../init.d/mdadm 0 lrwxrwxrwx 1 root root 24 Dec 15 22:11 /etc/rc6.d/K05mdadm-waitidle -> ../init.d/mdadm-waitidle Since init.d/mdadm and init.d/mdadm-waitidle don't exist, all the /etc/rcX.d/*mdadm* links are broken links - and in a colour terminal are all highlighted distinctly All systems boot successfully, so I'm not sure if it is simply a cleanup issue during upgrade from 18.04 to 20.04, or if the files should exist? However, a previous version desktop, which is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
[Kernel-packages] [Bug 2081537] [NEW] KDE wayland stop working on kernel 6.11 with nvidia drivers
Public bug reported: After kernel updated to 6.11 login to KDE wayland session stop working - just black screen. Also tried 560 version - same there. On previous kernel 6.8 all works fine. I just set it as default for a while. Plasma 6.1 OpenGL renderer string: NVIDIA GeForce RTX 2060/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 550.107.02 ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Description changed: After kernel updated to 6.11 login to KDE wayland session stop working - just black screen. Also tried 560 version - same there. On previous kernel 6.8 all works fine. I just set it as default for a while. + + Plasma 6.1 ** Description changed: After kernel updated to 6.11 login to KDE wayland session stop working - just black screen. Also tried 560 version - same there. On previous kernel 6.8 all works fine. I just set it as default for a while. Plasma 6.1 + OpenGL renderer string: NVIDIA GeForce RTX 2060/PCIe/SSE2 + OpenGL core profile version string: 4.6.0 NVIDIA 550.107.02 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2081537 Title: KDE wayland stop working on kernel 6.11 with nvidia drivers Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: After kernel updated to 6.11 login to KDE wayland session stop working - just black screen. Also tried 560 version - same there. On previous kernel 6.8 all works fine. I just set it as default for a while. Plasma 6.1 OpenGL renderer string: NVIDIA GeForce RTX 2060/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 550.107.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2081537/+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 1973139] [NEW] package linux-modules-extra-5.4.0-110-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-110-generic/kernel/drivers/misc/ti-st/
Public bug reported: Only a message that there was a problem discovered with the question to report this via a bug. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-110-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3987 F pulseaudio /dev/snd/pcmC0D0p: tom3987 F...m pulseaudio CasperMD5CheckResult: skip Date: Thu May 12 08:59:18 2022 DuplicateSignature: package:linux-modules-extra-5.4.0-110-generic:(not installed) Unpacking linux-modules-5.4.0-110-generic (5.4.0-110.124) ... dpkg: error processing archive /tmp/apt-dpkg-install-W7My0y/0-linux-modules-5.4.0-110-generic_5.4.0-110.124_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-110-generic.list-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-110-generic/kernel/drivers/misc/ti-st/st_drv.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=99128a7f-d4b1-4fd8-8173-4e4755980a65 InstallationDate: Installed on 2015-06-27 (2511 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-109-generic root=UUID=9919a918-697d-4446-b698-2adfda1b25c2 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux Title: package linux-modules-extra-5.4.0-110-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-110-generic/kernel/drivers/misc/ti-st/st_drv.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to focal on 2022-05-06 (5 days ago) dmi.bios.date: 07/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H81M-HDS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/02/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1973139 Title: package linux-modules-extra-5.4.0-110-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-110-generic/kernel/drivers/misc/ti- st/st_drv.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: New Bug description: Only a message that there was a problem discovered with the question to report this via a bug. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-110-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3987 F pulseaudio /dev/snd/pcmC0D0p: tom3987 F...m pulseaudio CasperMD5CheckResult: skip Date: Thu May 12 08:59:18 2022 DuplicateSignature: package:linux-modules-extra-5.4.0-110-generic:(not installed) Unpacking linux-modules-5.4.0-110-generic (5.4.0-110.124) ... dpkg: error processing archive /tmp/apt-dpkg-install-W7My0y/0-linux-modules-5.4.0-110-generic_5.4.0-110.124_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-110-generic.list-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-110-generic/kernel/drivers/misc/ti-st/st_drv.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=99128a7f-d4b1-4fd8-8173-4e4755980a65 InstallationDate: Installed on 2015-06-27 (2511 days ago) InstallationMedia: Ubuntu 14.04.2 LTS &
[Kernel-packages] [Bug 1774711] Re: excessive seccomp audit logs
For the record: My/our signature line is: Ubuntu 4.15.0-50.54-generic 4.15.18 Messages look like this: Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5 Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5 Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5 Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5 Jun 07 01:40:42 TDOG-ADM-AD-VM7 audit[25263]: SECCOMP auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=25263 comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 arch=c03e syscall=257 compat=0 ip=0x7f658fa04db1 code=0x5 ... Precondition is that auditd.service is started. -- 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/1774711 Title: excessive seccomp audit logs Status in linux package in Ubuntu: Triaged Bug description: Hello, my audit logs are currently filled with messages from Firefox's seccomp filters which looks like this: type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 $ aa-decode 57656220436F6E74656E74 Decoded: Web Content $ aa-decode 2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 Decoded: /usr/lib/firefox/firefox (deleted) Over a recent 48 hour stretch it averaged out to nearly one message per second. My current audit rules are: ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 --loginuid-immutable -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change -a alway
[Kernel-packages] [Bug 1871766] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350425/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noise vision I described earlier
[Kernel-packages] [Bug 1871766] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350426/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noise vision I described earlier
[Kernel-packages] [Bug 1871766] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350423/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] Re: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive
apport information ** Tags added: apport-collected ** Description changed: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re-appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noise vision I described earlier and that I show in the other video file. - video20200409_011018907.mp4 : The other video file, recorded this time with my phone, showing the screen once it has switched to it's "noisy" state described earlier. There was no sound playing from the speakers, so I recorded with no sound (thanks Ubuntu Touch for that option). Also, my mouse froze after some time.
[Kernel-packages] [Bug 1871766] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350430/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350429/+files/ProcEnviron.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/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350422/+files/CRDA.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/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noise vision I described earlier
[Kernel-packages] [Bug 1871766] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350424/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350428/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350427/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350434/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350431/+files/ProcModules.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/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350432/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1871766/+attachment/5350433/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871766 Title: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive Status in linux package in Ubuntu: Incomplete Bug description: # DESCRIPTION : Playing a "partially corrupt" video starts normally, then starts showing visual artifacts (apparition of a red gradient on the bottom of the viewframe and a green gradient on top), which increase in intensity over time (can result in brigth blinking, black bars appearing in the middle of the video, etc.) and can, at some point, result in a complete system freeze. Once the system is frozen, the mouse can still move, but nothing else on the screen reacts - neither on click nor on hover. After a few seconds, the screens (I have two screens) go black briefly, then re- appear to show complete noise, with a 64x64-pixel-box of lighter noise around where the mouse is. The mouse can still move normally (the lighter 64x64 box moves at the same speed my mouse moved before the crash - no lag, no FPS drop). # IMPORTANT BEHAVIORAL OBSERVATIONS : - Alt + SysReq + R, E, I, S, U, B DOES NOT RESPOND (that's why I believe the kernel is affected). I tried several times, waiting a full second between each input; no response. I believe I was doing it correctly because I have used that technique successfully several times in the past on different systems. - The bug first occurred a few months ago, and since then I have updated my system several times (using Ubuntu's built-in graphical update notifier - I've installed everything update I saw), and none of the updates have fixed the problem. I did notice, though, that lately the bug was harder to reproduce, but I have no idea if that correlation means causation or not. - The same physical machine runs another instance of the exact same operating system (Ubuntu 18.04.4 LTS) on a different hard drive. I just switch hard drives manually to change systems. The other system has always used VLC to play videos as Totem lacks codecs to play the videos I want. It (the other system) suffers no major glitch, AFAIK. # STEPS TO REPRODUCE (might not work on different system - read further for why I believe it is necessary to report nevertheless): - Play a partially corrupt video file (I provided two in the attachment) with Totem and wait. I believe - but I am not sure - that stressing the application (for example, dragging the video scroller while the video plays) increases the likeliness of visual artifacts appearing. Usually, the green-at-the-top and red-at-the-bottom appear quite easily, the rest comes by letting the whole thing run in the background for a few minutes, maybe a few hours at most (never took up to an hour on my side). # WHY I THINK IT'S AN IMPORTANT ISSUE (but not a "security issue" per se) : The entire operating system was rendered unresponsive. While some visual cues appearing on the video may hint that everything isn't right, if you were working on something while the video plays and it crashes, you lost everything you were doing back to the last point you saved. I also believe - though I could be wrong - the the Kernel was dead as well, since REISUB doesn't work, as mentioned earlier. The bug shows it is possible for an ordinary application to cause a complete denial of service on the whole system. No matter what the problem inside Totem is, it has the power to creep down to the whole system (and maybe the kernel); an application running in user space shouldn't have such power. However, I struggled to find clear, easily reproducible steps that could result in a crash 100% of the time on any Ubuntu 18.04.4 LTS system. I therefore cannot guarantee it isn't just a problem on my end (but even if it is, I would like to understand how a bug in Totem can have such a huge impact). If my reasoning is wrong, then I apologize for the inconvenience. Feel free to classify my report the way it should be if need there is. # FILES ATTACHED : - 2020-04-09 01-04-59.mp4 : (I apologize for the unprofessional video... I tested it on a meme) A recording made with OBS of the apparition of the visual artifacts. The artifacts are essentially concentrated in the first minute of the video - the rest shows only the red/green gradients, which are still disturbing but much less aggressive on the eye. At the very end of the video, I close the target file and re-open it; fatal decision, it was at that moment that my computer roze and stopped responding. A few moments later, the screen went black, and showed the strange noi
[Kernel-packages] [Bug 1871766] Re: Totem : Playing a corrupt video can result in full system crash - Linux Kernel unresponsive
The command seems to have run successfully, but printed a surprising amount of console messages. If useful, here's the output that appeared when running the command : The authorization page: (https://launchpad.net/+authorize-token?oauth_token=[IProbablyShouldntPostTheTokenHereEvenThoughIAlreadyRevokedIt]&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... [3176:3275:0409/123220.869990:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.166" (uid=1001 pid=3176 comm="/snap/opera/70/usr/lib/x86_64-linux-gnu/opera/oper" label="snap.opera.opera (enforce)") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply="0" destination="org.freedesktop.UPower" (uid=0 pid=1340 comm="/usr/lib/upower/upowerd " label="unconfined") [3176:3275:0409/123220.870323:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.166" (uid=1001 pid=3176 comm="/snap/opera/70/usr/lib/x86_64-linux-gnu/opera/oper" label="snap.opera.opera (enforce)") interface="org.freedesktop.UPower" member="GetDisplayDevice" error name="(unset)" requested_reply="0" destination="org.freedesktop.UPower" (uid=0 pid=1340 comm="/usr/lib/upower/upowerd " label="unconfined") [3176:3275:0409/123220.870483:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.166" (uid=1001 pid=3176 comm="/snap/opera/70/usr/lib/x86_64-linux-gnu/opera/oper" label="snap.opera.opera (enforce)") interface="org.freedesktop.UPower" member="EnumerateDevices" error name="(unset)" requested_reply="0" destination="org.freedesktop.UPower" (uid=0 pid=1340 comm="/usr/lib/upower/upowerd " label="unconfined") [3287:3287:0409/123224.526232:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [3646:1:0409/123225.090978:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer [3287:3287:0409/123225.510860:ERROR:gles2_cmd_decoder.cc(8617)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glFramebufferTexture2D: <- error from previous GL command [3439:1:0409/123225.714003:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123225.714378:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123225.750076:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123225.750568:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123225.868173:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123225.868475:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123226.300341:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123226.301008:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123226.303887:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3439:1:0409/123226.304522:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. [3673:1:0409/123230.409901:ERROR:child_thread_impl.cc(784)] Receiver for unknown Channel-associated interface: chrome.mojom.SearchBouncer [3176:3272:0409/123232.968243:
[Kernel-packages] [Bug 1774711] Re: excessive seccomp audit logs
Will the required pat set be backported to older kernel, such as Ubuntu 4.15.0-70.79-generic 4.15.18? Will the patches be in 20.04 LTS (kernel >= 4.18), which is around the corner? NOTE: Unfortunately with issue #1774711 the use of "auditd" has become problematic on systems with SSDs, since systemd allows in-memory configuration (Storage=volatile; SplitMode=none), but auditd does not support such a complex configuration (write_logs = no; log_file = /var/log/audit/audit.log). That means with the excessive SECCOMP lines (i.e. tens/hundreds of thousands a day) we cannot re-enable auditd (sudo systemctl start|enable auditd.service) until this issue is resolved, UNLESS there is a way to make auditd not to write logs to disk but continue to function properly. We need auditd for enforcing audit.rules (complex ISO 27001, PCI-DSS, etc. compliant rulesets) and statistics (sudo aureport (-n)), which require log data stored (dmesg kernel bugger is insufficient for ISO compliant store and analysis of events and stats). Our tests show, that up to several hundred MiB of logs are written to the SSDs per pay, which accumulates to approx 0.5 TiB over the course of 4 years. With in avg. 50% of the SSD cells occupied and given the models, this translates to a slightly increased wear-out of our SSDs, even when a good wear-leveling algorithm and background garbage collector is in use (our desktop models: Samsung Enterprise SSD with super capacitor mod. SM/PM863(a)). -- 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/1774711 Title: excessive seccomp audit logs Status in linux package in Ubuntu: Triaged Bug description: Hello, my audit logs are currently filled with messages from Firefox's seccomp filters which looks like this: type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 $ aa-decode 57656220436F6E74656E74 Decoded: Web Content $ aa-decode 2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 Decoded: /usr/lib/firefox/firefox (deleted) Over a recent 48 hour stretch it averaged out to nearly one message per second. My current audit rules are: ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 --loginuid-immutable -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=tim
[Kernel-packages] [Bug 1740289] Re: print_req_error: critical target error, dev sr0, sector 2097136
It's not exactly the same, but I see the following during reboot, when testing Xubuntu 18.04 daily ISO (2018-04-21), on VirtualBox 4.3 installed on a trusty system. [ 118.XX] print_req_error: I/O error, dev sr0, sector 1178984 [ 118.XX] print_req_error: I/O error, dev loop0, sector 1177462 References: http://cdimage.ubuntu.com/xubuntu/daily-live/current/ https://www.google.com/search?q=launchpad+print_req_error%3A+I%2FO+error%2C+dev+sr0 -- 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/1740289 Title: print_req_error: critical target error, dev sr0, sector 2097136 Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 1816.482664] print_req_error: critical target error, dev sr0, sector 2097136 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 1655 F...m pulseaudio /dev/snd/controlC0: caravena 1655 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 27 15:28:36 2017 InstallationDate: Installed on 2017-10-13 (75 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740289/+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 1773392] Re: zfs hangs on mount/unmount
vmlinuz-4.15.0-23-generic - it seems ok! I have upgraded normally and everything is fine, the machine boots up. It's all done for me. Thanks! -- 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/1773392 Title: zfs hangs on mount/unmount Status in linux package in Ubuntu: Confirmed Bug description: I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and 4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16; also tried 0.7.9). Sometimes lxd hangs when I try to stop / restart or "stop && move" some containers. Furhter investigation showed that problem is in zfs mount or unmount: it just hangs and lxd just wait it. Also commands like "zfs list" hangs to. It seems that it is not lxd or zfs issue, but kernel bug? https://github.com/lxc/lxd/issues/4104#issuecomment-392072939 I have one test ct that always hangs on restart, so here is info: dmesg: [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds. [ 1330.390994] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.391101] txg_syncD0 9944 2 0x8000 [ 1330.391105] Call Trace: [ 1330.391117] __schedule+0x297/0x8b0 [ 1330.391122] schedule+0x2c/0x80 [ 1330.391136] cv_wait_common+0x11e/0x140 [spl] [ 1330.391141] ? wait_woken+0x80/0x80 [ 1330.391152] __cv_wait+0x15/0x20 [spl] [ 1330.391234] rrw_enter_write+0x3c/0xa0 [zfs] [ 1330.391306] rrw_enter+0x13/0x20 [zfs] [ 1330.391380] spa_sync+0x7c9/0xd80 [zfs] [ 1330.391457] txg_sync_thread+0x2cd/0x4a0 [zfs] [ 1330.391534] ? txg_quiesce_thread+0x3d0/0x3d0 [zfs] [ 1330.391543] thread_generic_wrapper+0x74/0x90 [spl] [ 1330.391549] kthread+0x121/0x140 [ 1330.391558] ? __thread_exit+0x20/0x20 [spl] [ 1330.391562] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1330.391566] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1330.391569] ret_from_fork+0x35/0x40 [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds. [ 1330.391630] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.391735] lxd D0 12419 1 0x [ 1330.391739] Call Trace: [ 1330.391745] __schedule+0x297/0x8b0 [ 1330.391749] schedule+0x2c/0x80 [ 1330.391752] rwsem_down_write_failed+0x162/0x360 [ 1330.391808] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 1330.391814] call_rwsem_down_write_failed+0x17/0x30 [ 1330.391817] ? call_rwsem_down_write_failed+0x17/0x30 [ 1330.391821] down_write+0x2d/0x40 [ 1330.391825] grab_super+0x30/0x90 [ 1330.391901] ? zpl_create+0x160/0x160 [zfs] [ 1330.391905] sget_userns+0x91/0x490 [ 1330.391908] ? get_anon_bdev+0x100/0x100 [ 1330.391983] ? zpl_create+0x160/0x160 [zfs] [ 1330.391987] sget+0x7d/0xa0 [ 1330.391990] ? get_anon_bdev+0x100/0x100 [ 1330.392066] zpl_mount+0xa8/0x160 [zfs] [ 1330.392071] mount_fs+0x37/0x150 [ 1330.392077] vfs_kern_mount.part.23+0x5d/0x110 [ 1330.392080] do_mount+0x5ed/0xce0 [ 1330.392083] ? copy_mount_options+0x2c/0x220 [ 1330.392086] SyS_mount+0x98/0xe0 [ 1330.392092] do_syscall_64+0x73/0x130 [ 1330.392096] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 1330.392099] RIP: 0033:0x4db36a [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 00a5 [ 1330.392104] RAX: ffda RBX: RCX: 004db36a [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 00c420a23b60 [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: [ 1330.392110] R10: R11: 0216 R12: [ 1330.392112] R13: 0039 R14: 0038 R15: 0080 [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds. [ 1330.392171] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.392276] lxd D0 16725 1 0x0002 [ 1330.392279] Call Trace: [ 1330.392284] __schedule+0x297/0x8b0 [ 1330.392289] ? irq_work_queue+0x8d/0xa0 [ 1330.392293] schedule+0x2c/0x80 [ 1330.392297] io_schedule+0x16/0x40 [ 1330.392302] wait_on_page_bit_common+0xd8/0x160 [ 1330.392305] ? page_cache_tree_insert+0xe0/0xe0 [ 1330.392309] __filemap_fdatawait_range+0xfa/0x160 [ 1330.392313] ? _cond_resched+0x19/0x40 [ 1330.392317] ? bdi_split_work_to_wbs+0x45/0x2c0 [ 1330.392321] ? _cond_resched+0x19/0x40 [ 1330.392324] filemap_fdatawait_keep_errors+0x1e/0x40 [ 1330.392327] sync_inodes_sb+0
[Kernel-packages] [Bug 279999]
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. -- 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/27 Title: NaturalPoint SmartNav4 support Status in HAL: Invalid Status in hal-info package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Bug description: Binary package hint: hal-info Here's a start at an FDI file for the SmartNav4 hands-free mouse: SmartNav 4 evdev true To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/27/+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 532137]
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. -- 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/532137 Title: Wacom Intuos2 tablet hotplug only works once after booting Status in X.Org X server: Invalid Status in linux package in Ubuntu: Incomplete Status in xf86-input-wacom package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-wacom The following two tablets do not work out plug-and-play of the box in Lucid: 056a:0041 Wacom Co., Ltd Intuos2 4x5 056a:0044 Wacom Co., Ltd Intuos2 12x12 messages/syslog: Mar 4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB device using uhci_hcd and address 6 Mar 4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen from 1 choice Mar 4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18 ProblemType: Bug Architecture: i386 Date: Thu Mar 4 14:36:17 2010 DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: nvidia-graphics-drivers Uname: Linux 2.6.32-15-generic i686 dmi.bios.date: 06/05/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG965MQ dmi.board.vendor: Intel Corporation dmi.board.version: AAD37419-102 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr: glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucidarchitecture: i686kernel: 2.6.32-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532137/+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 385370]
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server. -- 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/385370 Title: [i965gm] lost use of mouse on resume Status in X.Org X server: Invalid Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: xorg 64bit karmic, I just resumed from suspend and I can use the keyboard fine, and move the mouse, but motion events and button events are not getting to X applications (confirmed with xev and a lack of window focus following the apparently moving pointer). ProblemType: Bug Architecture: amd64 Date: Tue Jun 9 22:30:23 2009 DistroRelease: Ubuntu 9.10 MachineType: LENOVO 647814G Package: xorg 1:7.4~5ubuntu21 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.30-8-generic root=UUID=c59ca6c6-d7b8-4f2a-90e9-8328b69fd8ca ro quiet splash ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-8.9-generic RelatedPackageVersions: xserver-xorg 1:7.4~5ubuntu21 libgl1-mesa-glx 7.4.1-1ubuntu2 libdrm2 2.4.11-0ubuntu1 xserver-xorg-video-intel 2:2.7.99.1+git20090602.ec2fde7c-0ubuntu2 xserver-xorg-video-ati 1:6.12.2-2ubuntu1 SourcePackage: xorg Uname: Linux 2.6.30-8-generic x86_64 XorgConf: dmi.bios.date: 05/11/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7TET36WW (1.10 ) dmi.board.name: 647814G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7TET36WW(1.10):bd05/11/2009:svnLENOVO:pn647814G:pvrThinkPadX300:rvnLENOVO:rn647814G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 647814G dmi.product.version: ThinkPad X300 dmi.sys.vendor: LENOVO fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.30-8-generic [lspci] 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) Subsystem: Lenovo Device [17aa:20b3] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) Subsystem: Lenovo Device [17aa:20b5] To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/385370/+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 374090] Re: [VX800] Samsung NC20 installation problem(viafb problem)
** Changed in: module-init-tools (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/374090
Title:
[VX800] Samsung NC20 installation problem(viafb problem)
Status in linux package in Ubuntu:
Fix Released
Status in module-init-tools package in Ubuntu:
Fix Released
Status in xserver-xorg-video-openchrome package in Ubuntu:
Fix Released
Bug description:
Bug also affects the installed (non Live System) Version of Ubuntu
10.04 i386 and amd64. Lucid Live System (10.04 Beta1 and Beta2)
running properly.
Binary package hint: ubiquity
First, thanks and greetings to all who contribute to this wonderful
community :-)
I guess the package in problem is is Ubiquity. But I am not sure.
I bought this new netbook - Samsung NC 20. More info at
http://www.sammynetbook.com/samsung-nc20
# CPU: VIA Nano™ ULV Processor U2250 (1.3+GHz, 800MHz)
# Chipset: VIA VX800 Unified Digital Media IGP Chipset
# Graphics: Integrated VIA Chrome9™ with DirectX 9.0 3D graphics support and
hardware video acceleration
# OS: Microsoft○R Windows○R XP Home Edition
# Memory: 1GB DDR2 (1SODMM)
I tried to install Ubuntu 9.04 from after downloading it from
http://www.ubuntu.com/getubuntu/download a couple of days ago (week of
8th May 2009). Since I do not have a CD rom drive, i used UNetBooting
to create a bootable USB from the ISO image. While booting I got the
options menu. I chose default. I could see the Ubuntu logo with a
horizontal bar for some time. Then the screen blurred. I could see
some blurred image of Ubuntu on the screen. I had to stop installation
there. Then I tried to give boot switches in the first(and only) menu.
I tried vga=771 and fb=off. But they did not work. The screen
resolution is 1280x800 for which I do not see a number. From web I
could get a number of 640x400, that also did not work. The same thing
happened with Xubuntu 9.04. Then I changed to Ubuntu 8.04LTS. This
time I could get the windows (is it Xwindows?) I clicked on install.
It worked and I could take it through complete installation. But now
the WLAN is not detected (it could be another bug).
This bug is about getting the correct display during installation
boot. Could you do anything? Please let me know how I could help.
Some references:
People are following this up but AFAK there is not bug report filed on this
problem.
http://ubuntuforums.org/showthread.php?s=78563ca7e43d092bdba026fbdf8e03d0&t=1079314&page=6
https://help.ubuntu.com/community/NC20
[lspci]
00:00.0 Host bridge [0600]: VIA Technologies, Inc. Unknown device [1106:0353]
(rev 12)
Subsystem: Samsung Electronics Co Ltd Unknown device [144d:c04e]
00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. Unknown
device [1106:1122] (rev 11) (prog-if 00 [VGA controller])
Subsystem: Samsung Electronics Co Ltd Unknown device [144d:c04e]
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: VT82xx [HDA VIA VT82xx], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: VT82xx [HDA VIA VT82xx], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gv 1369 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xfd40 irq 67'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,144dc04e,0011'
Controls : 16
Simple ctrls : 9
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
HibernationDevice: RESUME=UUID=3fbb5c52-ac7e-48e5-9a85-9e4d3e34d76b
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InstallationMedia__: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC20/NB20
Package: xserver-xorg-video-openchrome 1:0.2.904+svn916-1build1 [modified:
usr/lib/libchromeXvMC.so.1.0.0 usr/lib/libchromeXvMCPro.so.1.0.0
usr/lib/xorg/modules/drivers/openchrome_drv.so]
PackageArchitecture: i386
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=9fbad170-1de3-4f50-8d95-19b8d29e41b2 ro vga=792 quiet splash
vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
ProcVersionSignatu
[Kernel-packages] [Bug 1815857] [NEW] linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132
Public bug reported: I'm not 100% sure what this firmware blob is actually used for, as the card is mostly functional without it and I'm not confident the broken bits aren't due to an incomplete driver, but it requests it for CA0132-based PCIe addin cards (Sound Blaster Recon3D, Z series, X AE-5). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 22:49:48 2019 Dependencies: InstallationDate: Installed on 2018-09-12 (155 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1815857 Title: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132 Status in linux-firmware package in Ubuntu: New Bug description: I'm not 100% sure what this firmware blob is actually used for, as the card is mostly functional without it and I'm not confident the broken bits aren't due to an incomplete driver, but it requests it for CA0132-based PCIe addin cards (Sound Blaster Recon3D, Z series, X AE-5). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 22:49:48 2019 Dependencies: InstallationDate: Installed on 2018-09-12 (155 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1815857/+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 1815857] Re: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132
I just noticed that the source code also calls for a "ctefx-r3di.bin" that's needed for a "Recon3Di" (apparently a Dell proprietary variant?) and the -sbz file was renamed "ctefx-desktop.bin" in 4.20. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1815857 Title: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132 Status in linux-firmware package in Ubuntu: New Bug description: I'm not 100% sure what this firmware blob is actually used for, as the card is mostly functional without it and I'm not confident the broken bits aren't due to an incomplete driver, but it requests it for CA0132-based PCIe addin cards (Sound Blaster Recon3D, Z series, X AE-5). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 22:49:48 2019 Dependencies: InstallationDate: Installed on 2018-09-12 (155 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1815857/+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 1815857] Re: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132
A recent driver contributor has made the blobs available here: https://www.reddit.com/r/SoundBlasterOfficial/comments/9mm5ad/sound_blaster_r3dr3dizzxrae5_linux_driver/ No idea on the licensing situation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1815857 Title: linux-firmware is missing ctefx-sbz.bin for snd_hda_codec_ca0132 Status in linux-firmware package in Ubuntu: Incomplete Bug description: I'm not 100% sure what this firmware blob is actually used for, as the card is mostly functional without it and I'm not confident the broken bits aren't due to an incomplete driver, but it requests it for CA0132-based PCIe addin cards (Sound Blaster Recon3D, Z series, X AE-5). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 22:49:48 2019 Dependencies: InstallationDate: Installed on 2018-09-12 (155 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1815857/+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 50692]
https://gitlab.freedesktop.org/xorg/xserver/issues/260 -- 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/50692 Title: New Sony Vaios hotkeys don't work (fn_key polling) Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: On new Sony Vaios (FS and FJ series) hotkeys don't work. A piece of code that enables them as been released on gentoo forums. The programs runs as a service and as a config file in /etc/fsfn.conf. Here is the dmidecode output on my laptop: System Information Manufacturer: Sony Corporation Product Name: VGN-FJ3S_W Basically, the same config (default) enables hotkeys on all VGN-FN* computers and adding BRT_HACK_FJS=1 parameter in /etc/fsfn.conf files, enables them for VGN-FJ* series. As an attachement to this bug, here is the fsfn tarball (latest version from the gentoo boards). To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/50692/+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 1774711] Re: excessive seccomp audit logs
Oh in short my /etc/audit/rules.d/audit.rules looks like this: -D -b 8192 -f 1 -i --backlog_wait_time 0 -w /etc/anacrontab -p w -k AU-FS01-0001 [some more -w `foo` -p w -k `bar` here ...] Has someone here tried https://bugzilla.redhat.com/show_bug.cgi?id=1117953 / adding a "-a task,never" to /etc/audit/rules.d/audit.rules? Is that a bit extendive? However, https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/kernel/seccomp.c?id=326bee0286d7f6b0d780f5b75a35ea9fe489a802 looks very promising! - /* -* Let the audit subsystem decide if the action should be audited based -* on whether the current task itself is being audited. -*/ - return audit_seccomp(syscall, signr, action); + audit_seccomp(syscall, signr, action); Thanks Tyler! :× -- 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/1774711 Title: excessive seccomp audit logs Status in linux package in Ubuntu: Triaged Bug description: Hello, my audit logs are currently filled with messages from Firefox's seccomp filters which looks like this: type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 $ aa-decode 57656220436F6E74656E74 Decoded: Web Content $ aa-decode 2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 Decoded: /usr/lib/firefox/firefox (deleted) Over a recent 48 hour stretch it averaged out to nearly one message per second. My current audit rules are: ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 --loginuid-immutable -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change -a always,exit -F arch=b32 -S clock_settime -F a0=0x0 -F key=time-change -a always,exit -F arch=b64 -S clock_settime -F a0=0x0 -F key=time-change -w /etc/localtime -p wa -k time-change -w /usr/share/zoneinfo/ -p wa -k time-change -w /etc/group -p wa -k identity -w /etc/passwd -p wa -k identity -w /etc/gshadow -p wa -k identity -w /etc/shadow -p wa -k identity -w /etc/security/opasswd -p wa -k identity -a always,exit -F arch=b32 -S sethostname,setdomainname -F key=system-locale -a always,exit -F arch=b64 -S sethostname,setdomainname -F key=system-locale -w /etc/issue -p wa -k system-locale -w /etc/issue.net -p wa -k system-locale -w /etc/hosts -p wa -k system-locale -w /etc/network -p wa -k system-locale -a always,exit -F dir=/etc/NetworkManager/ -F perm=wa -F key=system-l
[Kernel-packages] [Bug 1774711] Re: excessive seccomp audit logs
After some research I can now safely confirm this bug. However, the log lines do not seem to be related to any rules in "/etc/audit/rules.d" or AppArmor profiles loaded. %‑) The only difference between the log lines in *this* bug report, my lines and the ones mentioned on https://bugzilla.redhat.com/show_bug.cgi?id=1507282 seems to be system- specific configuration, e.g. SELinux. Over the past 24 hours, I also had sometimes 100 lines at once in my log when opening or reloading a web page, in a new tab in Firefox. Therefore Firefox seems to be the only "offending" application at present. I also cleared the /etc/audit/rules.d and uninstalled the AppArmor extras packages (apparmor-profiles, apparmor-profiles-extra) with the Firefox profiles in it. Unfortunately the logs lines still poured in. Therefore I also changed the abstractions for Firefox (/etc/apparmor.d/abstractions/ubuntu-browsers) and commented out everything Firefox related, with no avail. The problem is somewhere deeper and not Firefox-specific. I hope Tyler Hicks (tyhicks) is correct and the fixes mentioned will soon be available. Due to the problem I generated several GiB of logs a day which is not so good for my SSD (even with wear-leveling). My temporary workaround is to stop auditd, since unlike /etc/systemd/journald.conf there is no Storage=volatile option for auditd. :-0 ',:-l >:/ ** Bug watch added: Red Hat Bugzilla #1507282 https://bugzilla.redhat.com/show_bug.cgi?id=1507282 ** Bug watch added: Red Hat Bugzilla #1117953 https://bugzilla.redhat.com/show_bug.cgi?id=1117953 -- 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/1774711 Title: excessive seccomp audit logs Status in linux package in Ubuntu: Triaged Bug description: Hello, my audit logs are currently filled with messages from Firefox's seccomp filters which looks like this: type=SECCOMP msg=audit(1527882167.659:223316): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.659:223317): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.659:223318): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.687:223319): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.687:223320): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.687:223321): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 type=SECCOMP msg=audit(1527882167.691:223322): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=257 compat=0 ip=0x7f4329623d19 code=0x3 type=SECCOMP msg=audit(1527882167.691:223323): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=4 compat=0 ip=0x7f4329623775 code=0x3 type=SECCOMP msg=audit(1527882167.691:223324): auid=1000 uid=1000 gid=1000 ses=1 pid=28901 comm=57656220436F6E74656E74 exe=2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 sig=0 arch=c03e syscall=87 compat=0 ip=0x7f4329625d47 code=0x3 $ aa-decode 57656220436F6E74656E74 Decoded: Web Content $ aa-decode 2F7573722F6C69622F66697265666F782F66697265666F78202864656C6574656429 Decoded: /usr/lib/firefox/firefox (deleted) Over a recent 48 hour stretch it averaged out to nearly one message per second. My current audit rules are: ## This file is automatically generated from /etc/audit/rules.d -D -b 8192 --loginuid-immutable -a always,exit -F arch=b32 -S adjtimex,settimeofday,stime -F key=time-change -a always,exit -F arch=b64 -S adjtimex,settimeofday -F key=time-change -a always,exit -F arch=
[Kernel-packages] [Bug 792085]
SUSE-SU-2017:1102-1: An update that solves 27 vulnerabilities and has 114 fixes is now available. Category: security (important) Bug References: 1003077,1003344,1003568,1003677,1003813,1003866,1003925,1004517,1004520,1005857,1005877,1005896,1005903,1006917,1006919,1007615,1007944,1008557,1008645,1008831,1008833,1008893,1009875,1010150,1010175,1010201,1010467,1010501,1010507,1010711,1010716,1011685,1011820,1012411,1012422,1012832,1012851,1012917,1013018,1013038,1013042,1013070,1013531,1013533,1013542,1013604,1014410,1014454,1014746,1015561,1015752,1015760,1015796,1015803,1015817,1015828,1015844,1015848,1015878,1015932,1016320,1016505,1016520,1016668,1016688,1016824,1016831,1017686,1017710,1019148,1019165,1019348,1019783,1020214,1021258,748806,763198,771065,786036,790588,795297,799133,800999,803320,821612,824171,851603,853052,860441,863873,865783,871728,901809,907611,908458,908684,909077,909350,909484,909491,909618,913387,914939,919382,922634,924708,925065,928138,929141,953233,956514,960689,961589,962846,963655,967716,968010,969340,973203,973691,979681,984194,986337,987333,987576,989152,989680,989764,989896,990245,992566,992991,993739,993832,995968,996541,996557,997401,998689,999101,07 CVE References: CVE-2004-0230,CVE-2012-6704,CVE-2013-6368,CVE-2015-1350,CVE-2015-8956,CVE-2015-8962,CVE-2015-8964,CVE-2016-10088,CVE-2016-3841,CVE-2016-5696,CVE-2016-7042,CVE-2016-7097,CVE-2016-7117,CVE-2016-7910,CVE-2016-7911,CVE-2016-7916,CVE-2016-8399,CVE-2016-8632,CVE-2016-8633,CVE-2016-8646,CVE-2016-9555,CVE-2016-9576,CVE-2016-9685,CVE-2016-9756,CVE-2016-9793,CVE-2016-9794,CVE-2017-5551 Sources used: SUSE Linux Enterprise Real Time Extension 11-SP4 (src): kernel-rt-3.0.101.rt130-68.1, kernel-rt_trace-3.0.101.rt130-68.1, kernel-source-rt-3.0.101.rt130-68.1, kernel-syms-rt-3.0.101.rt130-68.1 SUSE Linux Enterprise Debuginfo 11-SP4 (src):kernel-rt-3.0.101.rt130-68.1, kernel-rt_debug-3.0.101.rt130-68.1, kernel-rt_trace-3.0.101.rt130-68.1 -- 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/792085 Title: Automatic remount of safely removed USB 3.0 drive Status in Nautilus: New Status in thunar: Invalid Status in linux package in Ubuntu: In Progress Status in nautilus package in Ubuntu: Confirmed Status in thunar package in Ubuntu: Confirmed Status in udev package in Ubuntu: Confirmed Status in nautilus source package in Precise: New Status in thunar source package in Precise: New Status in udev source package in Precise: New Status in linux source package in Trusty: In Progress Status in nautilus source package in Trusty: New Status in thunar source package in Trusty: New Status in udev source package in Trusty: New Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in Fedora: Unknown Status in openSUSE: Fix Released Bug description: Binary package hint: nautilus When I choose "Safely remove drive" context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens. I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Thu Jun 2 23:40:08 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/792085/+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 1899042] Re: System slow when using updated kernel
apport information ** Tags added: apport-collected ** Description changed: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz - Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for - just using the system. + Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu49 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: eladmin F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-08-16 (52 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera + Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: HP HP Laptop 15-bs0xx + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-20-generic N/A + linux-backports-modules-5.8.0-20-generic N/A + linux-firmware1.190 + Tags: groovy + Uname: Linux 5.8.0-20-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) + UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/07/2017 + dmi.bios.release: 15.2 + dmi.bios.vendor: Insyde + dmi.bios.version: F.02 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: 8328 + dmi.board.vendor: HP + dmi.board.version: 23.21 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 23.21 + dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Notebook + dmi.product.name: HP Laptop 15-bs0xx + dmi.product.sku: 1VH28EA#ABE + dmi.product.version: Type1ProductConfigId + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419569/+files/AlsaInfo.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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) P
[Kernel-packages] [Bug 1899042] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419577/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419576/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419584/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419582/+files/ProcModules.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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419575/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419580/+files/ProcEnviron.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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419570/+files/CRDA.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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419583/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419571/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419573/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419578/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419581/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419579/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419574/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419572/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419586/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419585/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1899042/+attachment/5419587/+files/acpidump.txt ** 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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] Re: System slow when using updated kernel
x fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips: 3999.93 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: -- 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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1899042] Re: System slow when using updated kernel
How can I update the newer kernel form my old and working kernel, without touching my working kernel, so if the update does not fix the problem, I can just still using the old kernel. Also, thanks for your time, as a open source developer I know this is not easy. -- 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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Confirmed Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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
