[Kernel-packages] [Bug 1852976] Re: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle
** Tags added: 5.11 hirsute sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852976 Title: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle Status in ubuntu-kernel-tests: Fix Released Status in linux-aws package in Ubuntu: New Status in linux-signed-oracle package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Status in linux-signed-oracle source package in Bionic: New Status in linux-aws source package in Disco: Won't Fix Status in linux-signed-oracle source package in Disco: Invalid Bug description: It looks like the failures in zram01 are causing zram02 and zram03 to fail as well. Seems that this is broken since commit 7cfac804 (zram: Rewrite shell tests into new API) tag=zram01 stime=1573887406 dur=300 exit=signaled stat=9 core=no cu=23757 cs=7590 startup='Sat Nov 16 06:56:46 2019' zram01 1 TINFO: timeout per run is 0h 5m 0s zram01 1 TINFO: create '4' zram device(s) zram01 1 TPASS: test succeeded zram01 1 TCONF: The device attribute max_comp_streams was introduced in kernel 3.15 and deprecated in 4.7 zram01 2 TINFO: test that we can set compression algorithm zram01 2 TINFO: supported algs: [lzo] lz4 lz4hc 842 zstd zram01 2 TINFO: /sys/block/zram0/comp_algorithm = 'lzo' (1/4) zram01 2 TINFO: /sys/block/zram1/comp_algorithm = 'lzo' (2/4) zram01 2 TINFO: /sys/block/zram2/comp_algorithm = 'lzo' (3/4) zram01 2 TINFO: /sys/block/zram3/comp_algorithm = 'lzo' (4/4) zram01 2 TPASS: test succeeded zram01 3 TINFO: set disk size to zram device(s) zram01 3 TINFO: /sys/block/zram0/disksize = '26214400' (1/4) zram01 3 TINFO: /sys/block/zram1/disksize = '26214400' (2/4) zram01 3 TINFO: /sys/block/zram2/disksize = '26214400' (3/4) zram01 3 TINFO: /sys/block/zram3/disksize = '402653184' (4/4) zram01 3 TPASS: test succeeded zram01 4 TINFO: set memory limit to zram device(s) zram01 4 TINFO: /sys/block/zram0/mem_limit = '25M' (1/4) zram01 4 TINFO: /sys/block/zram1/mem_limit = '25M' (2/4) zram01 4 TINFO: /sys/block/zram2/mem_limit = '25M' (3/4) zram01 4 TINFO: /sys/block/zram3/mem_limit = '384M' (4/4) zram01 4 TPASS: test succeeded zram01 5 TINFO: make ext3 filesystem on /dev/zram0 zram01 5 TINFO: make ext4 filesystem on /dev/zram1 zram01 5 TINFO: make xfs filesystem on /dev/zram2 zram01 5 TINFO: make btrfs filesystem on /dev/zram3 zram01 5 TPASS: zram_makefs succeeded zram01 6 TINFO: mount /dev/zram0 zram01 6 TINFO: mount /dev/zram1 zram01 6 TINFO: mount /dev/zram2 zram01 6 TINFO: mount /dev/zram3 zram01 6 TPASS: mount of zram device(s) succeeded zram01 7 TINFO: filling zram0 (it can take long time) zram01 7 TPASS: zram0 was filled with '20628' KB zram01 7 TPASS: compression ratio: 732.90:1 zram01 7 TINFO: filling zram1 (it can take long time) zram01 7 TPASS: zram1 was filled with '20140' KB zram01 7 TPASS: compression ratio: 5151.97:1 zram01 7 TINFO: filling zram2 (it can take long time) zram01 7 TPASS: zram2 was filled with '17756' KB zram01 7 TPASS: compression ratio: 285.26:1 zram01 7 TINFO: filling zram3 (it can take long time) zram01 1 TBROK: test killed, timeout! If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tag=zram02 stime=1573887712 dur=0 exit=exited stat=1 core=no cu=2 cs=0 startup='Sat Nov 16 07:01:52 2019' zram02 1 TINFO: timeout per run is 0h 5m 0s zram02 1 TINFO: create '1' zram device(s) zram02 1 TFAIL: unexpected num of devices: 4 /opt/ltp/testcases/bin/zram02.sh: 27: echo: echo: I/O error zram02 1 TINFO: AppArmor enabled, this may affect test results zram02 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) zram02 1 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 1 skipped 0 warnings 0 tag=zram03 stime=1573887718 dur=0 exit=exited stat=2 core=no cu=0 cs=0 startup='Sat Nov 16 07:01:58 2019' zram03 0 TINFO : create a zram device with 536870912 bytes in size. zram03 1 TBROK : safe_file_ops.c:301: Failed to close FILE '/sys/block/zram0/disksize' at zram03.c:87: errno=EBUSY(16): Device or resource busy zram03 2 TBROK : safe_file_ops.c:301: Remaining cases broken ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9 ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21 Uname: Linux 5.0.0-1005-oracle x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Nov 18 07:50:37 2019 SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1852976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1929504] Re: Add support for IO functions of AAEON devices
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/1929504 Title: Add support for IO functions of AAEON devices Status in linux package in Ubuntu: New Status in linux source package in Groovy: New Bug description: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+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 1735945] Re: Brightness control not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1735945 Title: Brightness control not working Status in linux package in Ubuntu: Expired Bug description: Brightness control not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 2 17:53:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2017-11-30 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=101a39ce-07bc-4b02-87e9-77428c23bae1 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN45WW(V1.18) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN45WW(V1.18):bd05/10/2013:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.name: 20211 dmi.product.version: Lenovo IdeaPad P400 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Dec 2 16:42:49 2017 xserver.configfile: default xserver.errors: intel(0): Unrecognised backlight control interface 'ideapad' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8254 vendor AUO xserver.version: 2:1.19.3-1ubuntu1~16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735945/+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 1921437] Re: Kernel 5.4.0-70 webcam's logitech c930e microphone not found
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1921437 Title: Kernel 5.4.0-70 webcam's logitech c930e microphone not found Status in linux package in Ubuntu: Expired Bug description: Kernel 5.0.4-67 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921437/+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 1929504] [NEW] Add support for IO functions of AAEON devices
Public bug reported: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929504 Title: Add support for IO functions of AAEON devices Status in linux package in Ubuntu: New Bug description: [Impact] Require drivers to enable AAEON devices. [Fix] AAEON provides a series of patches to support its GPIO/LED/Watchdog/HWMON devices. [Test] Verified on AAEON platform. [Where problems could occur] No, they are new drivers, should not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929504/+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 1926564] Re: An recursive locking in igb and igc drivers
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1926564 Title: An recursive locking in igb and igc drivers Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] This commit currently is still under discussion fixes the issue. https://lkml.org/lkml/2021/4/20/123 [Test] Verified on Dell Precision workstations. [Where problems could occur] The patch is pretty straightforward, no problems could occur by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926564/+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 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+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 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead
Also note that 3K/4K-wide at 60Hz requires an HDMI 2.0 port and cable, or for you to limit your refresh rate to 30Hz (not recommended for desktop usage) for HDMI v1.4: https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video -- 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2"
[Kernel-packages] [Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead
Ideally use DisplayPort if you can, because it has supported higher resolutions and higher bandwidth than HDMI for a long time already. -- 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390
[Kernel-packages] [Bug 1928222] Re: System stuck on boot with error message "vmaster hook already present before cdev"
** Summary changed: - System stuck on boot with error message + System stuck on boot with error message "vmaster hook already present before cdev" -- 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/1928222 Title: System stuck on boot with error message "vmaster hook already present before cdev" Status in linux package in Ubuntu: Incomplete Bug description: Hello, my system stuck after I installed updates for Ubuntu 20.04 LTS with error message "vmaster hook already present before cdev". I expected that system will load to the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928222/+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 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead
Comment #29 shows this problem is originating in the i915 kernel driver. So there's no need to include 'xorg-server' here, Xorg is only following the (incomplete) list of modes exposed by the kernel. ** No longer affects: xorg-server (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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2"
[Kernel-packages] [Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead
It looks like this issue keeps happening with HDMI for i915 users. Maybe Intel is being conservative (or just accurate) with bandwidth limitations... Anyone affected, please follow the instructions in comment #34. -- 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080
[Kernel-packages] [Bug 1893601] Re: [i915] 4K modes are missing when connected by HDMI (but are shown in the EDID)
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 ** This bug has been marked a duplicate of bug 1901470 [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead -- 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/1893601 Title: [i915] 4K modes are missing when connected by HDMI (but are shown in the EDID) Status in linux package in Ubuntu: Confirmed Bug description: Windows 10 is working with 4k monitor, but not Ubuntu 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 30 20:35:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:81b4] InstallationDate: Installed on 2020-08-28 (2 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 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP 510-p114 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=906d29e9-4c50-43be-a8f5-2f6d9df94188 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: CNV6370S3L dmi.board.name: 81B4 dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV6370S3L dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.13:bd08/02/2016:svnHP:pn510-p114:pvr:rvnHP:rn81B4:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p114 dmi.product.sku: X6F90AA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893601/+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 1806177] Re: Display resolution with later kernels
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 ** This bug has been marked a duplicate of bug 1901470 [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead -- 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/1806177 Title: Display resolution with later kernels Status in linux package in Ubuntu: Confirmed Bug description: Hardware - thinkpad T430, 3rd gen integrated graphics, external LG ultrawide monitor (2560x1080). OS linux mint. Any kernel later than 4.5.7. will not correctly identify the monitor resolution only giving 1920x1080 as the max. No problems with the earlier kernels. Further information: https://forums.linuxmint.com/viewtopic.php?f=46=280143 While not hard fact, it would appear that other older thinkpads, e.g. X220 and 4k screens have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806177/+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 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in Linux: Unknown Status in linux package in Ubuntu: Won't Fix Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jik3196 F pulseaudio /dev/snd/pcmC1D0p: jik3196 F...m pulseaudio /dev/snd/controlC0: jik3196 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2019-09-20 10:09:14,777 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2019-09-12 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan ubuntu Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-20 (38 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified]
[Kernel-packages] [Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead
** Summary changed: - [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead + [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead ** Tags added: regression-release ** Summary changed: - [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead + [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead -- 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS"
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I'm just facing this same issue since today after upgrading 20.04 kernel from 5.8.x to 5.12.6-051206-generic. Second screen is detected by Nvidia, but black. When I change down the resolution from 1920x1080 to 1280x1024 the 2nd screen reappear. Then if I put back 1920x1080, the screen keeps alive but the refresh rate appears to 59hz in display settings, so screen is blinking. If I manually put the refresh rate to 60hz, the screen works fine until the next reboot. Then I have to start over. GPU is Nvidia GTX1060 and driver is Nouveau. Proprietary drivers didn't detects the 2nd screen at all. -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the
[Kernel-packages] [Bug 1929455] Re: Hirsute update: v5.11.21 upstream stable release
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1929455 Title: Hirsute update: v5.11.21 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.21 upstream stable release from git://git.kernel.org/ Bluetooth: verify AMP hci_chan before amp_destroy bluetooth: eliminate the potential race condition when removing the HCI controller net/nfc: fix use-after-free llcp_sock_bind/connect Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" usb: roles: Call try_module_get() from usb_role_switch_find_by_fwnode() tty: moxa: fix TIOCSSERIAL jiffies conversions tty: amiserial: fix TIOCSSERIAL permission check USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions staging: greybus: uart: fix TIOCSSERIAL jiffies conversions USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL permission check drm: bridge: fix LONTIUM use of mipi_dsi_() functions usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply usb: typec: tcpm: update power supply once partner accepts usb: xhci-mtk: remove or operator for setting schedule parameters usb: xhci-mtk: improve bandwidth scheduling with TT ASoC: samsung: tm2_wm5110: check of of_parse return value ASoC: Intel: kbl_da7219_max98927: Fix kabylake_ssp_fixup function ASoC: tlv320aic32x4: Register clocks before registering component ASoC: tlv320aic32x4: Increase maximum register in regmap MIPS: pci-mt7620: fix PLL lock check MIPS: pci-rt2880: fix slot 0 configuration FDDI: defxx: Bail out gracefully with unassigned PCI resource for CSR PCI: Allow VPD access for QLogic ISP2722 KVM: x86: Defer the MMU unload to the normal path on an global INVPCID PCI: keystone: Let AM65 use the pci_ops defined in pcie-designware-host.c PM / devfreq: Unlock mutex and free devfreq struct in error path soc/tegra: regulators: Fix locking up when voltage-spread is out of range iio: inv_mpu6050: Fully validate gyro and accel scale writes iio: sx9310: Fix write_.._debounce() iio:accel:adis16201: Fix wrong axis assignment that prevents loading iio:adc:ad7476: Fix remove handling iio: sx9310: Fix access to variable DT array sc16is7xx: Defer probe if device read fails phy: cadence: Sierra: Fix PHY power_on sequence misc: lis3lv02d: Fix false-positive WARN on various HP models phy: ti: j721e-wiz: Invoke wiz_init() before of_platform_device_create() misc: vmw_vmci: explicitly initialize vmci_notify_bm_set_msg struct misc: vmw_vmci: explicitly initialize vmci_datagram payload selinux: add proper NULL termination to the secclass_map permissions x86, sched: Treat Intel SNC topology as default, COD as exception async_xor: increase src_offs when dropping destination page md/bitmap: wait for external bitmap writes to complete during tear down md-cluster: fix use-after-free issue when removing rdev md: split mddev_find md: factor out a mddev_find_locked helper from mddev_find md: md_open returns -EBUSY when entering racing area md: Fix missing unused status line of /proc/mdstat MIPS: generic: Update node names to avoid unit addresses mt76: mt7615: use ieee80211_free_txskb() in mt7615_tx_token_put() ipw2x00: potential buffer overflow in libipw_wx_set_encodeext() cfg80211: scan: drop entry from hidden_list on overflow rtw88: Fix array overrun in rtw_get_tx_power_params() mt76: fix potential DMA mapping leak FDDI: defxx: Make MMIO the configuration default except for EISA drm/qxl: use ttm bo priorities drm/ingenic: Fix non-OSD mode drm/panfrost: Clear MMU irqs before handling the fault drm/panfrost: Don't try to map pages that are already mapped drm/radeon: fix copy of uninitialized variable back to userspace drm/dp_mst: Revise broadcast msg lct & lcr drm/dp_mst: Set CLEAR_PAYLOAD_ID_TABLE as broadcast drm: bridge: fix ANX7625 use of mipi_dsi_() functions drm: bridge/panel: Cleanup connector on bridge detach drm/amd/display: Reject non-zero src_y and src_x for video planes drm/amdgpu: fix concurrent VM
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
It has crashed multiple times after that today. I also saw the filestystem read only error as well where the whole screen goes into the terminal view and the list of io errors like I had reported originally. What else need to be looked at? If it crashes too frequently I will probably change the default_ps_max_latency_us back to 0 -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units Written: 526,042 [269
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
if anyone have a problem with oserror, as advice by Håkon Vågsether (haakov) check 1 sec wait solution, another way that worked for me, i have edit .service before start the install and changed the line 7 from Type=simple to Type=idle, in fact man define: Behavior of idle is very similar to simple; however, actual execution of the service program is delayed until all active jobs are dispatched. This may be used to avoid interleaving of output of shell services with the status output on the console. Note that this type is useful only to improve console output, it is not useful as a general unit ordering tool, and the effect of this service type is subject to a 5s timeout, after which the service program is invoked anyway. Thank you Badaoui Mohamed (mohamed-badaoui),Logix (logix2) and Håkon Vågsether (haakov) -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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 1929424] Re: package linux-modules-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x8
** Tags removed: 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/1929424 Title: package linux-modules-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko" in "/lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko .dpkg-new": fine del file o dello stream inattesa Status in linux package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: idealab1343 F pulseaudio /dev/snd/controlC1: idealab1343 F pulseaudio CasperMD5CheckResult: skip Date: Mon May 24 13:26:42 2021 Dependencies: ErrorMessage: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko" in "/lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko.dpkg-new": fine del file o dello stream inattesa InstallationDate: Installed on 2021-01-21 (123 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire 5738 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=d5823afd-e2c8-4f1d-8947-3ad24be81f10 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.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.6 SourcePackage: linux Title: package linux-modules-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko" in "/lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko.dpkg-new": fine del file o dello stream inattesa UpgradeStatus: Upgraded to groovy on 2021-05-24 (0 days ago) dmi.bios.date: 12/22/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.28 dmi.board.name: JV50 dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd12/22/2009:svnAcer:pnAspire5738:pvr0100:rvnAcer:rnJV50:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5738 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929424/+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 1929424] Re: package linux-modules-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x8
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1929424 Title: package linux-modules-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko" in "/lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko .dpkg-new": fine del file o dello stream inattesa Status in linux package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-modules-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: idealab1343 F pulseaudio /dev/snd/controlC1: idealab1343 F pulseaudio CasperMD5CheckResult: skip Date: Mon May 24 13:26:42 2021 Dependencies: ErrorMessage: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko" in "/lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko.dpkg-new": fine del file o dello stream inattesa InstallationDate: Installed on 2021-01-21 (123 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire 5738 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=d5823afd-e2c8-4f1d-8947-3ad24be81f10 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.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.6 SourcePackage: linux Title: package linux-modules-5.8.0-50-generic 5.8.0-50.56 failed to install/upgrade: impossibile copiare i dati estratti per "./lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko" in "/lib/modules/5.8.0-50-generic/kernel/arch/x86/crypto/curve25519-x86_64.ko.dpkg-new": fine del file o dello stream inattesa UpgradeStatus: Upgraded to groovy on 2021-05-24 (0 days ago) dmi.bios.date: 12/22/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.28 dmi.board.name: JV50 dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd12/22/2009:svnAcer:pnAspire5738:pvr0100:rvnAcer:rnJV50:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5738 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929424/+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 1174827] Re: CVE-2013-1979
I will create a patch accordance to the work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-backport-maverick in Ubuntu. https://bugs.launchpad.net/bugs/1174827 Title: CVE-2013-1979 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1174827] Re: CVE-2013-1979
I will create a patch accordance to the work. ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Aaron Farias (timido) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-backport-maverick in Ubuntu. https://bugs.launchpad.net/bugs/1174827 Title: CVE-2013-1979 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux-lts-backport-oneiric source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Fix Released Status in linux-lts-raring source package in Precise: Fix Released Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux-lts-backport-maverick source package in Raring: Invalid Status in linux-lts-backport-natty source package in Raring: Invalid Status in linux-lts-backport-oneiric source package in Raring: Invalid Status in linux-lts-backport-maverick source package in Saucy: Invalid Status in linux-lts-backport-natty source package in Saucy: Invalid Status in linux-lts-backport-oneiric source package in Saucy: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-lts-wily source package in Trusty: Invalid Status in linux-lts-xenial source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in
[Kernel-packages] [Bug 1925056] Re: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem
Problem seems to be gone with the newer 5.10.0-1028-oem kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1925056 Title: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.6/+bug/1925056/+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 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64
groovy/linux-aws: 5.8.0-1034.36 ** Tags added: sru-20210510 -- 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/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Bug description: This issue can be found on 2 different ARM64 node, TunderX Cavium node "starmie" and Moonshot "ms10-34-mcdivittB0-kernel" Running test_maps bpf test.. Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Failed sockmap unexpected timeout ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio
[Kernel-packages] [Bug 1828187] Re: ibm, dynamic-memory property not found while loading kexec kernel (4.18.0-18-generic)
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18042
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1828187
Title:
ibm,dynamic-memory property not found while loading kexec kernel
(4.18.0-18-generic)
Status in The Ubuntu-power-systems project:
Fix Released
Status in kexec-tools package in Ubuntu:
Fix Released
Status in kexec-tools source package in Bionic:
Fix Released
Status in kexec-tools source package in Cosmic:
Fix Released
Bug description:
For SRU:
[Impact]
* The ibm,dynamic-memory-v2 device tree property replaced the
original ibm,dynamic-memory property. Since kexec-tools doesn't know
to look for the "-v2" property yet, it fails to successfully parse the
node using the new "-v2" property.
* These changes enable the new "-v2" property to be successfully
parsed from the node.
[Test Case]
* Load panic kernel or regular kernel with kexec command:
kdump-config unload; kdump-config load
OR
kexec -l --append="`cat /proc/cmdline`"
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
* Expected result: kexec loads without any warning/error messages
[Testing]
These changes were tested by Hari with a positive result on a 4.18
kernel for ppc64el.
[Regression Potential]
* Low.
* These changes exist in 'kexec-tools' for disco and onwards (these kernels
are all >= 4.16 where the -v2 property was enabled).
* The Bionic edge and Cosmic kernels have support for the -v2 property since
they are also >= 4.16.
* The regular 4.15 Bionic kernel is the more interesting of the bunch in
terms of regression potential since 4.15 is too early to have the -v2 property
enabled. The changes introduced by this patch appear to only attempt "-v2"
parsing if it was unable to parse the "-v1" node. The absence of the v1 node
implies that the device tree is using the "v2" property. Since the "-v2" option
is not enabled for the 4.15 kernel, if the "-v1" parsing fails, then the "-v2"
parsing will certainly fail, and the code throws the same error condition is it
did before the patch was applied anyway.
Original bug description below.
---
== Comment: #0 - Hari Krishna Bathini - 2019-05-07
13:37:51 ==
---Problem Description---
On 4.18.0-18-generic kernel, kexec load command throws below traces:
---
Regular kexec load:
root@ubuntu:~# kexec -l --append="`cat /proc/cmdline`"
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
/proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No
such file or directory
Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
root@ubuntu:~#
---
KDump kernel load:
root@ubuntu:~# kdump-config unload
* unloaded kdump kernel
root@ubuntu:~# kdump-config load
* Creating symlink /var/lib/kdump/vmlinuz
* Creating symlink /var/lib/kdump/initrd.img
/proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No
such file or directory
/proc/device-tree/ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory: No
such file or directory
Modified cmdline:BOOT_IMAGE=/boot/vmlinux-4.18.0-18-generic
root=UUID=1aa9458c-3974-4cb4-9ab3-9ee03c0f4e5e ro maxcpus=1
systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb
elfcorehdr=158912K
* loaded kdump kernel
root@ubuntu:~#
---
Contact Information = hbath...@in.ibm.com
---uname output---
Linux ubuntu 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC
2019 ppc64le ppc64le ppc64le GNU/Linux
---Additional Hardware Info---
na
Machine Type = na
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Load panic kernel or regular kernel with kexec command:
kdump-config unload; kdump-config load
OR
kexec -l --append="`cat /proc/cmdline`"
--initrd=/boot/initrd.img-`uname -r` /boot/vmlinux-`uname -r`
Actual Result:
DT files are not found while loading the kernel
Expected result:
kexec loads without any warning/error messages
Userspace tool common name: kexec-tools
The userspace tool has the following bit modes: 64-bit
Userspace rpm: kexec-tools
Userspace tool obtained from project website: na
*Additional Instructions for hbath...@in.ibm.com:
-Attach ltrace and strace of userspace application.
== Comment: #1 - Hari Krishna Bathini -
2019-05-07 13:44:25 ==
Since v4.16 kernel, ibm,dynamic-memory-v2 Device Tree Property is supported
in the kernel. This leaves kexec-tools on ppc64le broken without the below
fix patches:
https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=c740fdb2048265551f77d3f0fe53b2fddc0c8489
("kexec: add a helper function to add ranges")
[Kernel-packages] [Bug 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
I've been unable to reproduce the issue with the fixed kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux-aws source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux-aws source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Committed
Status in linux-aws source package in Groovy:
Confirmed
Status in linux source package in Hirsute:
Fix Committed
Status in linux-aws source package in Hirsute:
Confirmed
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+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 1926184] Re: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Marking verification done, though I've not had explicit testing results
from Amazon. Their comment in SF:#00308561 was, "thanks for putting in
the extra effort to get this released so quickly." By that I assume they
have been successfully using the test kernel as this bug was an arm64
show stopper for them.
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal
verification-done-groovy verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926184
Title:
locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
Status in linux package in Ubuntu:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux-aws source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux-aws source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Committed
Status in linux-aws source package in Groovy:
Confirmed
Status in linux source package in Hirsute:
Fix Committed
Status in linux-aws source package in Hirsute:
Confirmed
Bug description:
[Impact]
* Out of order reads can fetch a NULL pointer causing a kernel crash. Affects
kernels from v4.15 to v5.11.
[Fix]
* commit 84a24bf8c52e ("locking/qrwlock: Fix ordering in
queued_write_lock_slowpath()")
* For Bionic, we also require an additional patch: commit fcfdfe30e324
("locking/barriers: Introduce smp_cond_load_relaxed() and
atomic_cond_read_relaxed()")
[Where problems could occur]
* This is quite a subtle bug. It is more prevalent on arm64. Regression
possibility seems quite low. The worst impact could be a minor performance
degradation.
* Kernels 4.15 / 5.4 / 5.8 / 5.11 were successfully built and booted
with this patch. Also, by using ftrace we could see that the changed
function was executed with success multiple times.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926184/+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 1910965] Re: riscv: backport support for SiFive Unmatched
** Changed in: linux (Ubuntu Focal) Assignee: William Wilson (jawn-smith) => (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/1910965 Title: riscv: backport support for SiFive Unmatched Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Released Bug description: == SRU Justifcation Groovy/RISCV == The SiFive HiFive Unmatched board should be supported as well as the current Unleashed. There are various upstream commits for this support and some misc fixes for the Unleashed and Unmatched that are required for this board support. == The fix(es) == The following changes since commit 7295e646e91b648b7f45b4f36eba14bfe59dd3f6: UBUNTU: Ubuntu-riscv-5.8.0-13.15 (2020-12-15 10:33:23 +0100) are available in the Git repository at: https://git.launchpad.net/~colin-king/+git/ubuntu-riscv-groovy for you to fetch changes up to 86de0730500269fee8b71fcb1be29193455c3be7: UBUNTU: [Config] Align configs with Unleashed defconfigs (2021-01-11 09:37:13 +) Colin Ian King (1): UBUNTU: [Config] Align configs with Unleashed defconfigs David Abdurachmanov (5): PCI: microsemi: Add host driver for Microsemi PCIe controller Microsemi PCIe expansion board DT entry. HACK: Revert "of/device: Really only set bus DMA mask when appropriate" SiFive Unleashed CPUFreq SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4) Greentime Hu (2): irqchip/sifive-plic: Fix broken irq_set_affinity() callback irqchip/sifive-plic: Fix getting wrong chip_data when interrupt is hierarchy Pragnesh Patel (1): clk: sifive: Add clock enable and disable ops Rob Herring (2): dt-bindings: More whitespace clean-ups in schema files dt-bindings: Explicitly allow additional properties in board/SoC schemas Sagar Kadam (2): dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema dt-bindings: riscv: convert pwm bindings to json-schema Sagar Shrikant Kadam (1): i2c: ocores: fix polling mode workaround on FU540-C000 SoC Yash Shah (6): RISC-V: Update l2 cache DT documentation to add support for SiFive FU740 RISC-V: sifive_l2_cache: Update L2 cache driver to support SiFive FU740 dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC riscv: dts: add initial support for the SiFive FU740-C000 SoC dt-bindings: riscv: Update YAML doc to support SiFive HiFive Unmatched board riscv: dts: add initial board data for the SiFive HiFive Unmatched Zong Li (5): clk: sifive: Extract prci core to common base clk: sifive: Use common name for prci configuration clk: sifive: Add a driver for the SiFive FU740 PRCI IP block clk: sifive: Fix the wrong bit field shift dt-bindings: fu740: prci: add YAML documentation for the FU740 PRCI Documentation/devicetree/bindings/clock/sifive/fu740-prci.yaml | 60 Documentation/devicetree/bindings/gpio/sifive,gpio.yaml| 4 +- Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 6 +- Documentation/devicetree/bindings/pwm/pwm-sifive.txt | 33 --- Documentation/devicetree/bindings/pwm/pwm-sifive.yaml | 72 + Documentation/devicetree/bindings/riscv/cpus.yaml | 6 + Documentation/devicetree/bindings/riscv/sifive-l2-cache.txt| 51 Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 127 + Documentation/devicetree/bindings/riscv/sifive.yaml| 20 +- Documentation/devicetree/bindings/serial/sifive-serial.yaml| 4 +- Documentation/devicetree/bindings/spi/spi-sifive.yaml | 10 +- arch/riscv/Kconfig | 8 + arch/riscv/Kconfig.socs| 2 +- arch/riscv/boot/dts/sifive/Makefile| 3 +- arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 5 + arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 293 +++ arch/riscv/boot/dts/sifive/hifive-unleashed-a00-microsemi.dts | 28 ++ arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts| 66 + arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dts| 253 + arch/riscv/configs/defconfig | 5 + debian.riscv/config/annotations| 17 +- debian.riscv/config/config.common.ubuntu | 47 +-- drivers/clk/sifive/Kconfig
[Kernel-packages] [Bug 1924314] Re: netvsc may cause CPU lockup
Microsoft says, "We have not seen this issue in our regular testing. The
issue only showed up in a customer’s environment. For this patch,
regression tests should be good enough. Regression tests are performed
before a new SRU kernel is sign-off on."
Given that no regressions have been reported I am marking this
verification done.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924314
Title:
netvsc may cause CPU lockup
Status in linux package in Ubuntu:
Incomplete
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Bug description:
[SRU Justification]
SF#00308239
[Impact]
A soft lockup is happening to Azure cloud customers due to a bug in
netvsc_poll.
Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config
file, there is a bug in netvsc that may cause CPU lockup with
POLL_CONTROLLER. This bug has been fixed by the following patch:
commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5 ("hv_netvsc: remove
ndo_poll_controller")
This commit is in mainline as of 4.20-rc1.
Microsoft would like to request this patch in 4.15 based Azure
kernels.
[Test Plan]
Run high stress network traffic on an Azure instance.
[Where problems could occur]
There could be a decrease in performance or dropped packets due to NAPI not
being able to keep up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924314/+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 1929455] [NEW] Hirsute update: v5.11.21 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.21 upstream stable release from git://git.kernel.org/ Bluetooth: verify AMP hci_chan before amp_destroy bluetooth: eliminate the potential race condition when removing the HCI controller net/nfc: fix use-after-free llcp_sock_bind/connect Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" usb: roles: Call try_module_get() from usb_role_switch_find_by_fwnode() tty: moxa: fix TIOCSSERIAL jiffies conversions tty: amiserial: fix TIOCSSERIAL permission check USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions staging: greybus: uart: fix TIOCSSERIAL jiffies conversions USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL jiffies conversions tty: moxa: fix TIOCSSERIAL permission check staging: fwserial: fix TIOCSSERIAL permission check drm: bridge: fix LONTIUM use of mipi_dsi_() functions usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply usb: typec: tcpm: update power supply once partner accepts usb: xhci-mtk: remove or operator for setting schedule parameters usb: xhci-mtk: improve bandwidth scheduling with TT ASoC: samsung: tm2_wm5110: check of of_parse return value ASoC: Intel: kbl_da7219_max98927: Fix kabylake_ssp_fixup function ASoC: tlv320aic32x4: Register clocks before registering component ASoC: tlv320aic32x4: Increase maximum register in regmap MIPS: pci-mt7620: fix PLL lock check MIPS: pci-rt2880: fix slot 0 configuration FDDI: defxx: Bail out gracefully with unassigned PCI resource for CSR PCI: Allow VPD access for QLogic ISP2722 KVM: x86: Defer the MMU unload to the normal path on an global INVPCID PCI: keystone: Let AM65 use the pci_ops defined in pcie-designware-host.c PM / devfreq: Unlock mutex and free devfreq struct in error path soc/tegra: regulators: Fix locking up when voltage-spread is out of range iio: inv_mpu6050: Fully validate gyro and accel scale writes iio: sx9310: Fix write_.._debounce() iio:accel:adis16201: Fix wrong axis assignment that prevents loading iio:adc:ad7476: Fix remove handling iio: sx9310: Fix access to variable DT array sc16is7xx: Defer probe if device read fails phy: cadence: Sierra: Fix PHY power_on sequence misc: lis3lv02d: Fix false-positive WARN on various HP models phy: ti: j721e-wiz: Invoke wiz_init() before of_platform_device_create() misc: vmw_vmci: explicitly initialize vmci_notify_bm_set_msg struct misc: vmw_vmci: explicitly initialize vmci_datagram payload selinux: add proper NULL termination to the secclass_map permissions x86, sched: Treat Intel SNC topology as default, COD as exception async_xor: increase src_offs when dropping destination page md/bitmap: wait for external bitmap writes to complete during tear down md-cluster: fix use-after-free issue when removing rdev md: split mddev_find md: factor out a mddev_find_locked helper from mddev_find md: md_open returns -EBUSY when entering racing area md: Fix missing unused status line of /proc/mdstat MIPS: generic: Update node names to avoid unit addresses mt76: mt7615: use ieee80211_free_txskb() in mt7615_tx_token_put() ipw2x00: potential buffer overflow in libipw_wx_set_encodeext() cfg80211: scan: drop entry from hidden_list on overflow rtw88: Fix array overrun in rtw_get_tx_power_params() mt76: fix potential DMA mapping leak FDDI: defxx: Make MMIO the configuration default except for EISA drm/qxl: use ttm bo priorities drm/ingenic: Fix non-OSD mode drm/panfrost: Clear MMU irqs before handling the fault drm/panfrost: Don't try to map pages that are already mapped drm/radeon: fix copy of uninitialized variable back to userspace drm/dp_mst: Revise broadcast msg lct & lcr drm/dp_mst: Set CLEAR_PAYLOAD_ID_TABLE as broadcast drm: bridge: fix ANX7625 use of mipi_dsi_() functions drm: bridge/panel: Cleanup connector on bridge detach drm/amd/display: Reject non-zero src_y and src_x for video planes drm/amdgpu: fix concurrent VM flushes on Vega/Navi v2 drm/amdgpu: add new MC firmware for Polaris12 32bit ASIC drm/amdgpu: Init GFX10_ADDR_CONFIG for VCN v3 in DPG mode. ALSA: hda/realtek: Re-order ALC882 Acer quirk table entries ALSA: hda/realtek: Re-order ALC882 Sony quirk table entries ALSA: hda/realtek: Re-order ALC882 Clevo quirk table entries ALSA: hda/realtek: Re-order ALC269 HP quirk table entries ALSA: hda/realtek: Re-order ALC269 Acer quirk table entries ALSA: hda/realtek: Re-order ALC269 Dell quirk table entries ALSA: hda/realtek: Re-order ALC269 ASUS quirk table entries ALSA:
[Kernel-packages] [Bug 1929452] [NEW] upstream stable would break ubuntu/xr-usb-serial (deprecated ASYNC flags)
Public bug reported: The Ubuntu kernel has carried an out-of-tree driver "ubuntu/xr-usb- serial/" since forever. That driver uses the #define'd constant ASYNCB_INITIALIZED in multiple places, e.g.: if (test_bit(ASYNCB_INITIALIZED, _usb_serial->port.flags)) But this recent mainline commit (and all linux-stable's >= 4.14) removes the definition of ASYNCB_INITIALIZED ... [mainline] d09845e98a05 tty: actually undefine superseded ASYNC flags Some kernel-internal ASYNC flags have been superseded by tty-port flags and should no longer be used by kernel drivers. Fix the misspelled "__KERNEL__" compile guards which failed their sole purpose to break out-of-tree drivers that have not yet been updated. ... Which would make ubuntu/xr-usb-serial/ fail to build (as the upstream commit intends). To avoid that breakage, the stable backports of [mainline] d09845e98a05 will be omitted from all Ubuntu kernels, pending some other resolution of the problem with ubuntu/xr-usb-serial. ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Medium Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Medium Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929452 Title: upstream stable would break ubuntu/xr-usb-serial (deprecated ASYNC flags) Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Bug description: The Ubuntu kernel has carried an out-of-tree driver "ubuntu/xr-usb- serial/" since forever. That driver uses the #define'd constant ASYNCB_INITIALIZED in multiple places, e.g.: if (test_bit(ASYNCB_INITIALIZED, _usb_serial->port.flags)) But this recent mainline commit (and all linux-stable's >= 4.14) removes the definition of ASYNCB_INITIALIZED ... [mainline] d09845e98a05 tty: actually undefine superseded ASYNC flags Some kernel-internal ASYNC flags have been superseded by tty-port flags and should no longer be used by kernel drivers. Fix the misspelled "__KERNEL__" compile guards which failed their sole purpose to break out-of-tree drivers that have not yet been updated. ... Which would make ubuntu/xr-usb-serial/ fail to build (as the upstream commit intends). To avoid that breakage, the stable backports of [mainline] d09845e98a05 will be omitted from all Ubuntu kernels, pending some other resolution of the problem with ubuntu/xr-usb-serial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929452/+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 1928878] Re: Touchpad suddenly not responding
It did appear randomly one day. I guess some update caused, but I have no way of knowing which one. -- 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/1928878 Title: Touchpad suddenly not responding Status in linux package in Ubuntu: Incomplete Bug description: After leaving my laptop on sleep mode for a while, then bringing it up again causes the touchpad to stop responding completely. Checked for it in the bus/input/devices folder and didn't see it. Laptop model: ASUS X450L Touchpad manufacturer: I presume to also be ASUS Symptom first appeared less than a week ago. EDIT: Forgot to mention, the touchpad comes back after a restart. Touchpad info is as follows: Bus=0011 Vendor=0002 Product=000e Version= Name="ETPS/2 Elantech Touchpad" Phys=isa0060/serio1/input0 Sysfs=/devices/platform/i8042/serio1/input/input5 Uniq= Handlers=mouse0 event4 PROP=5 EV=b KEY=e420 1 0 0 0 0 ABS=66180001103 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-73-generic 5.4.0-73.82 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luiz 1541 F pulseaudio /dev/snd/controlC0: luiz 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 21:15:53 2021 InstallationDate: Installed on 2018-10-11 (950 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=3aa08318-3527-4824-a97a-cc0084649c15 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-18 (181 days ago) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP 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.:bvrX450LCP.206:bd02/20/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LCP dmi.product.sku: ASUS-NotebookSKU 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/1928878/+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 1929425] Re: Suspend/resume problem
How do i do that? -- 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/1929425 Title: Suspend/resume problem Status in linux package in Ubuntu: Incomplete Bug description: My PC won't resume from suspend. When i try resumig it by pressing a button on keyboard or PC i get a not working screen, though i can hear the pc work. The function works fine on Debian Buster (10.9.0). The function's a 'must have' for me. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu44048 F pulseaudio /dev/snd/controlC0: ubuntu44048 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon May 24 15:48:40 2021 IwConfig: lono wireless extensions. enp2s0no wireless extensions. LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 3020 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2018 dmi.bios.release: 65.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 040DDP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd10/30/2018:br65.19:svnDellInc.:pnOptiPlex3020:pvr00:rvnDellInc.:rn040DDP:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3020 dmi.product.sku: 0612 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929425/+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 1927866] Re: Root filesystem becomes readonly frequenty freezing system
I just got the crash again. System had locked and I was in the lockscreen when this happened. The icons on the login screen turned blank and I was not able to login. -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units Written: 526,042 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles:
[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails
Further information: Booting the same laptop into MSWindows lets me insert SD cards whilst the system is running and it all works as expected. (So not a hardware problem). -- 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/1929444 Title: SD card initialization on insertion fails Status in linux package in Ubuntu: New Bug description: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+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 1927866] Re: Root filesystem becomes readonly frequenty freezing system
@kaihengfeng - I have set the parameter. cat /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=11000" GRUB_CMDLINE_LINUX="" cat /sys/module/nvme_core/parameters/default_ps_max_latency_us 11000 -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units
[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Thanks for looking into this @kaihengfeng. I will try that and post results. I have been running the system for a few days without running into the error. The usual symptom I see when I run into the issue is that all the icons on the desktop becomes a blank icon / broken icon. So all the icons in the favorites bar and the notification area becomes same icon. In addition to the above change with the filessytem remount rw, I had also turned off fast boot in Windows. I hoped that would stop windows from setting unnecessary hardware settings when it shuts down. However I ran into the same blank icon state today. The system was in standby mode. I had closed the laptop (not shutdown) yesterday and opened it today. I worked on the system for a few minutes and then this crash happened. I tried to cat /var/syslog but that did not work. What commands should I try next time I run into this state? I have uploaded /var/log/syslog here. I am going to also make the change suggested by kaihengfeng and will keep the thread posted. ** Attachment added: "Syslog from the recent crash." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927866/+attachment/5499978/+files/syslog -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1
[Kernel-packages] [Bug 1929444] [NEW] SD card initialization on insertion fails
Public bug reported: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1929444 Title: SD card initialization on insertion fails Status in linux package in Ubuntu: New Bug description: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go
[Kernel-packages] [Bug 1928222] Re: System stuck on boot with error message
Sure. I can only take a photo of the screen. Is it ok? -- 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/1928222 Title: System stuck on boot with error message Status in linux package in Ubuntu: Incomplete Bug description: Hello, my system stuck after I installed updates for Ubuntu 20.04 LTS with error message "vmaster hook already present before cdev". I expected that system will load to the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928222/+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 1928530] Re: linux mint not booting or freeze on logo
Can you please see if kernel parameter "modprobe.blacklist=tg3" helps? -- 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/1928530 Title: linux mint not booting or freeze on logo Status in linux package in Ubuntu: Incomplete Bug description: bug report on the screen : watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [NetworkManager:630] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wili 1010 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-05-06 (9 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Acer Aspire 4738 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=c115b4b7-e7fb-4f44-ae67-7b016b824bea ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 Tags: ulyssa Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZQ8 dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.02:bd08/09/2010:svnAcer:pnAspire4738:pvrV1.02:rvnAcer:rnZQ8:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 4738 dmi.product.sku: Calpella_CRB dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928530/+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 1929439] [NEW] Not able to connect bluetooth microsoft designer mouse
Public bug reported: The bluetooth on Ubuntu budgie is not showing Microsoft wireless designer mouse, but it works completely fine when I boot this laptop on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: avtech 1000 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon May 24 10:52:08 2021 Dependencies: InstallationDate: Installed on 2021-05-22 (1 days ago) InstallationMedia: Ubuntu-Budgie 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210210.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 m6 Convertible PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=UUID=4ee18edf-4d5d-42bc-be4d-52e744eeafff ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2020 dmi.bios.release: 15.61 dmi.bios.vendor: Insyde dmi.bios.version: F.61 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81AD dmi.board.vendor: HP dmi.board.version: 58.54 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 58.54 dmi.modalias: dmi:bvnInsyde:bvrF.61:bd11/09/2020:br15.61:efr58.54:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AD:rvr58.54:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY x360 m6 Convertible dmi.product.sku: W2K45UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1929439 Title: Not able to connect bluetooth microsoft designer mouse Status in linux-firmware package in Ubuntu: New Bug description: The bluetooth on Ubuntu budgie is not showing Microsoft wireless designer mouse, but it works completely fine when I boot this laptop on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: avtech 1000 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon May 24 10:52:08 2021 Dependencies: InstallationDate: Installed on 2021-05-22 (1 days ago) InstallationMedia: Ubuntu-Budgie 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210210.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 m6 Convertible PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=UUID=4ee18edf-4d5d-42bc-be4d-52e744eeafff ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2020 dmi.bios.release: 15.61 dmi.bios.vendor: Insyde dmi.bios.version: F.61 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81AD dmi.board.vendor: HP dmi.board.version: 58.54 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 58.54 dmi.modalias: dmi:bvnInsyde:bvrF.61:bd11/09/2020:br15.61:efr58.54:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AD:rvr58.54:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP ENVY x360 m6 Convertible dmi.product.sku: W2K45UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to:
[Kernel-packages] [Bug 1928315] Re: Touchpad problem
Please run `sudo modprobe i2c_hid` and see if it helps. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1928315 Title: Touchpad problem Status in linux package in Ubuntu: Incomplete Bug description: Fujitsu Lifebook U931x The touchpad is not detected at all (as far as I understand it - newbie) and does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-72-generic. ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kari884 F pulseaudio Card0.Amixer.info: Card hw:0 'sofhdadsp'/'FUJITSUCLIENTCOMPUTINGLIMITED-LIFEBOOKU9310X-10601736746-FJNB2DB' Mixer name : 'Realtek ALC255' Components : 'HDA:8086280b,80860101,0010 HDA:10ec0255,1e267505,0012 cfg-dmics:2' Controls : 47 Simple ctrls : 18 CasperMD5CheckResult: skip CurrentDesktop: Enlightenment Date: Thu May 13 11:06:23 2021 InstallationDate: Installed on 2021-05-13 (0 days ago) InstallationMedia: Bodhi 20.04 - Release amd64 (20210510.0) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U9310X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=3ea6e40f-26b4-454d-b009-4d6eb6cc2b4d ro i8042.notimeout i8042.nomux quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.13 dmi.board.name: FJNB2DB dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U9310X dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.13:bd06/19/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU9310X:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2DB:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct31:cvrLIFEBOOKU9310X: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U9310X dmi.product.sku: SK00 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928315/+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 1928222] Re: System stuck on boot with error message
The error is from audio subsystem, and I don't think that error blocks the boot process. Can you please attach a screenshot? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1928222 Title: System stuck on boot with error message Status in linux package in Ubuntu: Incomplete Bug description: Hello, my system stuck after I installed updates for Ubuntu 20.04 LTS with error message "vmaster hook already present before cdev". I expected that system will load to the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928222/+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 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
With Secure Boot disabled, I can boot kernel 5.13.0-rc2 fine (if a few acpi errors). Resuming from suspend works as expected on this kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 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 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+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 1928507] Re: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11
how do you play the video? any acceleration being used, like VA? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
Detail can be found here: https://wiki.ubuntu.com/Kernel/KernelBootParameters -- 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/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. Status in linux package in Ubuntu: Confirmed Bug description: For some reason, my distro (Ubuntu 21.04) doesn't suspend properly. I want to solve this problem it is fixable because it will save a lot of battery. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 16:00:17 2021 InstallationDate: Installed on 2020-02-16 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-04-24 (17 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+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 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Can you please try kernel parameter "nvme- core.default_ps_max_latency_us=11000"? -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units Written: 526,042 [269 GB] Host Read Commands: 4,462,163 Host Write Commands:4,686,788 Controller Busy Time: 25 Power Cycles: 20 Power On Hours: 76 Unsafe Shutdowns:
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Possible bug in i915: [ 35.655312] i915 :00:02.0: [drm] Resetting rcs0 for CS error [ 35.655359] i915 :00:02.0: [drm] Xwayland[944] context reset due to GPU hang [ 35.663410] i915 :00:02.0: [drm] GPU HANG: ecode 9:1:8cbf8db6, in Xwayland [944] Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc3/amd64/ If the issue persists, use kernel parameter "nomodeset" so it can proceed to test the WiFi driver. -- 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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1929425] Re: Suspend/resume problem
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc3/amd64/ ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1929425 Title: Suspend/resume problem Status in linux package in Ubuntu: Incomplete Bug description: My PC won't resume from suspend. When i try resumig it by pressing a button on keyboard or PC i get a not working screen, though i can hear the pc work. The function works fine on Debian Buster (10.9.0). The function's a 'must have' for me. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu44048 F pulseaudio /dev/snd/controlC0: ubuntu44048 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon May 24 15:48:40 2021 IwConfig: lono wireless extensions. enp2s0no wireless extensions. LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 3020 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2018 dmi.bios.release: 65.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 040DDP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd10/30/2018:br65.19:svnDellInc.:pnOptiPlex3020:pvr00:rvnDellInc.:rn040DDP:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3020 dmi.product.sku: 0612 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929425/+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 1898808] Re: unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
Is this still an issue? ** Changed in: maas Status: New => Incomplete -- 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/1898808 Title: unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias:
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
I have it running on two machines now that needed big RAID 10s: # uname -rv 5.4.0-72-generic #80+TEST1896578v20210504b1-Ubuntu SMP Tue May 4 00:30:36 UTC 202 # df -h /opt/raid Filesystem Size Used Avail Use% Mounted on /dev/md0 30T 208G 29T 1% /opt/raid # cat /proc/mdstat Personalities : [raid10] md0 : active raid10 nvme7n1[7] nvme6n1[6] nvme5n1[5] nvme4n1[4] nvme3n1[3] nvme2n1[2] nvme1n1[1] nvme0n1[0] 31255576576 blocks super 1.2 512K chunks 2 near-copies [8/8] [] [>] resync = 0.1% (48777600/31255576576) finish=2514.8min speed=206813K/sec bitmap: 233/233 pages [932KB], 65536KB chunk FWIW the mkfs.xfs took ~1 minute across 8x8TB NVMe disks with this patched kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commit enables
[Kernel-packages] [Bug 1928535] Re: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build
It appears that the build fails because of the `/debian/debian.env` file. The contents of it changed recently in the 5.10. line (starting with 5.10.37) - but are OK before that and also in 5.12.x . It is also noticeable that that "faulty" (?) commits/configs come from "kathleen" instead of "sita". 5.10.36 commit f0cc96561db7d294a8d39833e1ba90677191d18c Author: Kernel Builder (sita) Date: Tue May 11 13:31:18 2021 + diff --git a/debian/debian.env b/debian/debian.env +DEBIAN=debian.master 5.10.37 commit f3cf7622efde3cd18d3f4e70ee2bd69f8c764492 Author: Kernel Builder (kathleen) Date: Fri May 14 09:34:35 2021 + diff --git a/debian/debian.env b/debian/debian.env +DEBIAN=debian.master-21.10 5.10.39 commit a5637af073ffe933b864b9566b942c9e8c09d262 Author: Kernel Builder (kathleen) Date: Sat May 22 10:33:45 2021 + diff --git a/debian/debian.env b/debian/debian.env +DEBIAN=debian.master-21.10 5.12.6 commit 8e019e1f614023866e34a9b6b0b54ac6ab7cbf20 Author: Kernel Builder (sita) Date: Sat May 22 10:33:33 2021 + diff --git a/debian/debian.env b/debian/debian.env +DEBIAN=debian.master -- 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/1928535 Title: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build Status in linux package in Ubuntu: Confirmed Bug description: It looks like the build machine ran out of disk space while building 5.11.20 amd64 and 5.10.36 armhf. From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.20/amd64/log ld: final link failed: No space left on device make[2]: *** [/home/kernel/COD/linux/Makefile:1183: vmlinux] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic' make[1]: *** [Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux' make: *** [debian/rules.d/2-binary-arch.mk:50: /home/kernel/COD/linux/debian/stamps/stamp-build-generic] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 No packages have been built for 5.10.37, 5.11.20, or 5.11.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928535/+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 1929425] [NEW] Suspend/resume problem
Public bug reported: My PC won't resume from suspend. When i try resumig it by pressing a button on keyboard or PC i get a not working screen, though i can hear the pc work. The function works fine on Debian Buster (10.9.0). The function's a 'must have' for me. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu44048 F pulseaudio /dev/snd/controlC0: ubuntu44048 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon May 24 15:48:40 2021 IwConfig: lono wireless extensions. enp2s0no wireless extensions. LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 3020 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2018 dmi.bios.release: 65.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 040DDP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd10/30/2018:br65.19:svnDellInc.:pnOptiPlex3020:pvr00:rvnDellInc.:rn040DDP:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3020 dmi.product.sku: 0612 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1929425 Title: Suspend/resume problem Status in linux package in Ubuntu: New Bug description: My PC won't resume from suspend. When i try resumig it by pressing a button on keyboard or PC i get a not working screen, though i can hear the pc work. The function works fine on Debian Buster (10.9.0). The function's a 'must have' for me. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu44048 F pulseaudio /dev/snd/controlC0: ubuntu44048 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon May 24 15:48:40 2021 IwConfig: lono wireless extensions. enp2s0no wireless extensions. LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 3020 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2018 dmi.bios.release: 65.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 040DDP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd10/30/2018:br65.19:svnDellInc.:pnOptiPlex3020:pvr00:rvnDellInc.:rn040DDP:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 3020 dmi.product.sku: 0612 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929425/+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 1929255] Re: update-initrd-links creates incorrect symlinks
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Confirmed Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby
** Changed in: linux (Debian) Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612916 Title: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby Status in linux package in Ubuntu: Confirmed Status in Arch Linux: New Status in linux package in Debian: New Bug description: On initial boot, sound on internal speakers is working. After standby it doesn work anymore, but a analog headset does. Switching around in pavucontrol doesn't work... Internal microphone works. I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel. Toshiba/Dynabook Portege Z20T-C: https://support.dynabook.com/support/modelHome?freeText=1200015981=785 WORKAROUND: Use suspend to disk. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michi 6510 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/1tb-swap MachineType: TOSHIBA PORTEGE Z20t-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.60 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z20t-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z20t-C dmi.product.version: PT16BE-00W006GR dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 1909814] Re: Keyboard not working
thkx for the support ! Doesn't work, same as it was. -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1918142] Re: Headphone microphone doesn't work - ALC255
Here it is, this is alsa-info output as of using temp fix. I am also using module-echo-cancel at the moment if it makes any difference. Hope it helps. ** Attachment added: "alsa info output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+attachment/5499820/+files/alsa-info.txt.SWrPqCgPfw -- 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1927019] Re: System freeze, continuous NVME PCIe errors
Can you please check if the issue persist if "RAID mode" is disabled in BIOS? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1927019 Title: System freeze, continuous NVME PCIe errors Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927019/+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 1918142] Re: Headphone microphone doesn't work - ALC255
Julien, please test this kernel: https://people.canonical.com/~khfeng/lp1918142/ -- 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1918142] Re: Headphone microphone doesn't work - ALC255
Bijay, can you please attach output of `alsa-info` here? -- 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1918142] Re: Headphone microphone doesn't work - ALC255
Please check comment #24. I have explained there. Not really a real fix as it disables internal microphone completely but if anyone is desperate like me to get external microphone working at any cost then it may help. -- 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1909814] Re: Keyboard not working
Ok, can you please run `sudo systemctl isolate multi-user` and see if keyboard works? Run `sudo systemctl isolate graphical` to go back to graphical session. -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1918142] Re: Headphone microphone doesn't work - ALC255
What's your temp fix? -- 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1909814] Re: Keyboard not working
Pls note that I add to use an external USB keyboard to generate dmesg output. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1927050] Re: Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1927050 Title: Enable BLK_DEV_NVME =y to support "shielded VM minimal images" Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp-4.15 package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Invalid Status in linux-gcp-4.15 source package in Bionic: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp-4.15 source package in Focal: Invalid Status in linux-gcp source package in Groovy: Fix Committed Status in linux-gcp-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Hirsute: Fix Committed Status in linux-gcp-4.15 source package in Hirsute: Invalid Bug description: This is requested by CPC -- see the title. [Impact] nvme.ko exists outside the kernel currently [Fix] Enable BLK_DEV_NVME=y [Test] Tested by CPC crew / Google: > The test images have passed testing and we would like this enabled so we > can have minimal images boot with NVME boot disk and so we can enable > GCE confidential VMs with minimal images. [Regression Potential] Not aware of any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+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 1909814] Re: Keyboard not working
Here is th output of dmesg in fie dmesg.txt Thkx for your interest ** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+attachment/5499781/+files/dmesg.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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type)
This is caused by the absence of CONFIG_VETH -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type) Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=2 Note, the following error has been fix in bug 1908342 Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+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 1929144] Re: linux ADT test failure with linux/4.15.0-144.148 i386 (stress-misaligned.0 failed)
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1929144
Title:
linux ADT test failure with linux/4.15.0-144.148 i386 (stress-
misaligned.0 failed)
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is a scripted bug report about ADT failures while running linux
tests for linux/4.15.0-144.148 on bionic. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.
Testing failed on:
i386:
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz
Only found on i386. Failing tests with the same output:
ubuntu_stress_smoke_test.setup
ubuntu_stress_smoke_test.stress-smoke-test
ubuntu_ramfs_stress.setup
ubuntu_ramfs_stress.ramfs-stress
ubuntu_vfat_stress.setup
ubuntu_vfat_stress.vfat-stress
Makefile:385: recipe for target 'stress-misaligned.o' failed
make[1]: Leaving directory
'/tmp/autopkgtest.Y8PkHb/build.Fp9/src/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng'
Makefile:370: recipe for target 'all' failed
stderr:
stress-aio-linux.c: In function ‘stress_aiol’:
stress-aio-linux.c:513:23: warning: large integer implicitly truncated to
unsigned type [-Woverflow]
cb[i].u.c.nbytes = ~0ULL; /* invalid */
^
stress-misaligned.c:419:18: error: ‘stress_misaligned_int128atomic’
undeclared here (not in a function); did you mean
‘stress_misaligned_int32atomic’?
{ "int128tomic",stress_misaligned_int128atomic, false, false },
^~
stress_misaligned_int32atomic
make[1]: *** [stress-misaligned.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929144/+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 1928535] Re: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build
Can you please check again, the builder fails to build 5.10.x and 5.11.x. Other builds 5.12, daily, etc are not affected. ** Changed in: linux (Ubuntu) Status: Fix Released => 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/1928535 Title: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build Status in linux package in Ubuntu: Confirmed Bug description: It looks like the build machine ran out of disk space while building 5.11.20 amd64 and 5.10.36 armhf. From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.20/amd64/log ld: final link failed: No space left on device make[2]: *** [/home/kernel/COD/linux/Makefile:1183: vmlinux] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic' make[1]: *** [Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux' make: *** [debian/rules.d/2-binary-arch.mk:50: /home/kernel/COD/linux/debian/stamps/stamp-build-generic] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 No packages have been built for 5.10.37, 5.11.20, or 5.11.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928535/+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 1928535] Re: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build
Hi Kai-Heng, I'm sure the disk issue on the builder was resolved quickly, however the 5.10.x and 5.11.x builds have been failing ever since the disk filled. The builder is still failing to build the most recent kernels. See: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.39/ and https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.22/ The 5.12 and the 5.13 series are no affected. -- 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/1928535 Title: No disk space, mainline 5.10.37 and 5.11.20, 5.11.21 failed to build Status in linux package in Ubuntu: Confirmed Bug description: It looks like the build machine ran out of disk space while building 5.11.20 amd64 and 5.10.36 armhf. From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.20/amd64/log ld: final link failed: No space left on device make[2]: *** [/home/kernel/COD/linux/Makefile:1183: vmlinux] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/debian/build/build-generic' make[1]: *** [Makefile:185: __sub-make] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux' make: *** [debian/rules.d/2-binary-arch.mk:50: /home/kernel/COD/linux/debian/stamps/stamp-build-generic] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 No packages have been built for 5.10.37, 5.11.20, or 5.11.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928535/+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 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type)
** Summary changed: - test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels + test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type) ** Description changed: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. + not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=2 + + + Note, the following error has been fix in bug 1908342 Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory - not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels (Error: Unknown device type) Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=2 Note, the following error has been fix in bug 1908342 Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+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 1918142] Re: Headphone microphone doesn't work - ALC255
Since it's the same codec alc255 I assume the issue is shared? I already have a temp fix which is working fine at the moment and there are already too many similar threads with 0 progress for many years. So, doubt a new bug report will do any good. I just shared my results here, will wait patiently for OP to respond or this thread gets closed due to inactivity. -- 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1926100] Re: Hotspot (access point) is not working properly on two different wifi adapters.
Yes, both Wifi NICs support AP mode. So it's not a kernel bug. ** Package changed: linux (Ubuntu) => gnome-control-center (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/1926100 Title: Hotspot (access point) is not working properly on two different wifi adapters. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Wifi adapters: RALINK RT 5370 (RT5370) and RALINK RT 2070 (RT2070). Ubuntu 20.04.2 LTS. Kernel 5.8.0-50-generic. Motherboard GA78LMT. Expected behavior: that it would be possible to share the internet through the access point (hotspot) without any problems, through any of the adapters. Real behavior: The adapters work fine with good wifi signal, and sometimes the hotpost is possible. But most of the time the hotspot option is neither clickable nor selectable (gray). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: poe1877 F pulseaudio /dev/snd/controlC1: poe1877 F pulseaudio /dev/snd/pcmC1D0p: poe1877 F...m pulseaudio /dev/snd/controlC2: poe1877 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-04 (52 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1926100/+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 1925768] Re: Losing Wifi connection when USB-C Hub was plugged-in
Looks like something interferes the WiFi? Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc2/amd64/ And we'll need to report this issue to upstream if that kernel doesn't solve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925768 Title: Losing Wifi connection when USB-C Hub was plugged-in Status in linux package in Ubuntu: Incomplete Bug description: Hello Ubuntu community, I have a problem with my system: when i connect my new USB-C hub to my Intel Nuc, my wifi-connection get disconnected and try to reconnect to my Wifi. The System cannot connect until i disconnect my USB-C hub. I also tries do disable the cable-connection-Ports without success. I always receive the message: could not connect to wifi... My OS: Ubuntu 20.04.2 LTS always up to date. Here is my Nuc: https://www.notebooksbilliger.de/intel+nuc+kit+nuc8i3bek2+388252?gclid=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB_id=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB:G:s_kwcid=AL!8069!3!504856654760!!!g!626707857982!=6004 Link to my Adapter: https://www.amazon.de/1-Adapter-USB-C-Stromversorgung-RJ45-Gigabit- Ethernet-TF-Kartenleser-5-mm- Audiobuchse/dp/B08N424Y25/ref=sr_1_4?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91=1=usb+c+hub=1619169213=8-4 Best Regards Miro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925768/+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 1918142] Re: Headphone microphone doesn't work - ALC255
Since your laptop is different to the this bug, can you please file a new bug? 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/1918142 Title: Headphone microphone doesn't work - ALC255 Status in linux package in Ubuntu: Incomplete Bug description: Hello, The headphone microphone is not working : I cannot register any sound from it. Driver is alc255 and the laptop is an Acer SF314-42. I am not sure what else I should post :S Best --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Acer Swift SF314-42 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-44-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: 08/26/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918142/+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 1904480] Re: RTL8822CE Realtek Wi-Fi dropping connection
Maybe give OEM kernel a try? $ sudo apt install linux-oem-20.04b ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1904480 Title: RTL8822CE Realtek Wi-Fi dropping connection Status in linux package in Ubuntu: Incomplete Bug description: Wifi is still connected but it just stops working, this can be resolved by disconnecting or putting wifi on airplane mode and turning it back again. A few cases this does not work and the Wifi stops working and a system restart is needed. This is happening on Ubuntu 20.10 x64 Below the info for the wifi card: description: Wireless interface product: RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: 8c:c8:4b:95:0f:8b width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.0-29-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:79 ioport:2000(size=256) memory:fc70-fc70 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kain 2109 F pulseaudio /dev/snd/controlC0: kain 2109 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-06-25 (145 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=70cc7384-d3bc-4d41-8c3c-d4c54a560bef ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-17 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/22/2020 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: EECN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Flex 5 14ARE05 dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrEECN21WW:bd04/22/2020:br1.21:efr1.16:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05: dmi.product.family: IdeaPad Flex 5 14ARE05 dmi.product.name: 81X2 dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05 dmi.product.version: IdeaPad Flex 5 14ARE05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kain 2109 F pulseaudio /dev/snd/pcmC2D0p: kain 2109 F...m pulseaudio /dev/snd/controlC0: kain 2109 F pulseaudio /dev/snd/timer: kain 2109 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-06-25 (146 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81X2 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=70cc7384-d3bc-4d41-8c3c-d4c54a560bef ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RebootRequiredPkgs: gnome-shell RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-17 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
https://lists.ubuntu.com/archives/kernel-team/2021-May/120569.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions[SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions[SKIP] TEST:
[Kernel-packages] [Bug 1928878] Re: Touchpad suddenly not responding
Was the issue present before the update? -- 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/1928878 Title: Touchpad suddenly not responding Status in linux package in Ubuntu: Incomplete Bug description: After leaving my laptop on sleep mode for a while, then bringing it up again causes the touchpad to stop responding completely. Checked for it in the bus/input/devices folder and didn't see it. Laptop model: ASUS X450L Touchpad manufacturer: I presume to also be ASUS Symptom first appeared less than a week ago. EDIT: Forgot to mention, the touchpad comes back after a restart. Touchpad info is as follows: Bus=0011 Vendor=0002 Product=000e Version= Name="ETPS/2 Elantech Touchpad" Phys=isa0060/serio1/input0 Sysfs=/devices/platform/i8042/serio1/input/input5 Uniq= Handlers=mouse0 event4 PROP=5 EV=b KEY=e420 1 0 0 0 0 ABS=66180001103 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-73-generic 5.4.0-73.82 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luiz 1541 F pulseaudio /dev/snd/controlC0: luiz 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 21:15:53 2021 InstallationDate: Installed on 2018-10-11 (950 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=3aa08318-3527-4824-a97a-cc0084649c15 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-18 (181 days ago) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP 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.:bvrX450LCP.206:bd02/20/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LCP dmi.product.sku: ASUS-NotebookSKU 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/1928878/+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 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
** Description changed: + [Impact] + The pmtu.sh test in net from ubuntu_kernel_selftests will be marked + as failed even there is no obvious failure message from the test: + $ sudo ./pmtu.sh + TEST: ipv4: PMTU exceptions [ OK ] + TEST: ipv6: PMTU exceptions [ OK ] + vxlan4 not supported + TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] + vxlan4 not supported + TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] + TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] + TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] + geneve4 not supported + TEST: IPv4 over geneve4: PMTU exceptions [SKIP] + geneve4 not supported + TEST: IPv6 over geneve4: PMTU exceptions [SKIP] + TEST: IPv4 over geneve6: PMTU exceptions [ OK ] + TEST: IPv6 over geneve6: PMTU exceptions [ OK ] + TEST: IPv4 over fou4: PMTU exceptions [ OK ] + TEST: IPv6 over fou4: PMTU exceptions [ OK ] + TEST: IPv4 over fou6: PMTU exceptions [ OK ] + TEST: IPv6 over fou6: PMTU exceptions [ OK ] + TEST: IPv4 over gue4: PMTU exceptions [ OK ] + TEST: IPv6 over gue4: PMTU exceptions [ OK ] + TEST: IPv4 over gue6: PMTU exceptions [ OK ] + TEST: IPv6 over gue6: PMTU exceptions [ OK ] + TEST: vti6: PMTU exceptions [ OK ] + TEST: vti4: PMTU exceptions [ OK ] + TEST: vti4: default MTU assignment [ OK ] + TEST: vti6: default MTU assignment [ OK ] + TEST: vti4: MTU setting on link creation [ OK ] + TEST: vti6: MTU setting on link creation [ OK ] + TEST: vti6: MTU changes on link changes [ OK ] + vxlan4 not supported + TEST: ipv4: cleanup of cached exceptions [SKIP] + TEST: ipv6: cleanup of cached exceptions [ OK ] + TEST: ipv4: list and flush cached exceptions [ OK ] + TEST: ipv6: list and flush cached exceptions [ OK ] + $ echo $? + 1 + + This is because the test script treats all non-zero return code as a + failure, thus it will be marked as FAILED when some sub-test got + skipped. + + [Fix] + * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return + code + * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing + + This patchset will: + 1. Use the kselftest framework skip code $ksft_skip to replace the + hardcoded SKIP return code. + 2. Improve the result processing, the test will be marked as PASSED + if nothing goes wrong and not all the tests were skipped. + + These have already landed in newer releases and this test does not + exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. + + The first patch needs to be backported (except on F-OEM-5.10) as some + test cases were not added yet. + The second one can be cherry-picked. + + [Test] + Run this test directly on a patched kernel. The skipped test will cause + failure to this test. + + [Where problems could occur] + Changes limited to testing tools, it's unlikely to cause any problem + to kernel functions. + + + [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: - $ sudo ./pmtu.sh + $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] - vxlan4 not supported + vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] - vxlan4 not supported + vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] - geneve4 not supported + geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions[SKIP] - geneve4 not supported + geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions[SKIP] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on
[Kernel-packages] [Bug 1928820] Re: Add support for AMD wireless button
** Information type changed from Private to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Medium => Low -- 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/1928820 Title: Add support for AMD wireless button Status in amd: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Some OEM platforms will be using a new ACPI interface for controlling wireless button. It behaves identically to existing hp-wireless driver, just has new ACPI interface. Here is the patch for it submitted into maintainer's tree for 5.13. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=fixes=89ec1e5e0ca9dfe745cb48f4d33979e3b6cc847d Can Canonical team please pull into oem-5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928820/+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 1928878] Re: Touchpad suddenly not responding
I'm not sure what you mean. I've updated the operating system to the latest version available, if that's what you're asking. -- 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/1928878 Title: Touchpad suddenly not responding Status in linux package in Ubuntu: Incomplete Bug description: After leaving my laptop on sleep mode for a while, then bringing it up again causes the touchpad to stop responding completely. Checked for it in the bus/input/devices folder and didn't see it. Laptop model: ASUS X450L Touchpad manufacturer: I presume to also be ASUS Symptom first appeared less than a week ago. EDIT: Forgot to mention, the touchpad comes back after a restart. Touchpad info is as follows: Bus=0011 Vendor=0002 Product=000e Version= Name="ETPS/2 Elantech Touchpad" Phys=isa0060/serio1/input0 Sysfs=/devices/platform/i8042/serio1/input/input5 Uniq= Handlers=mouse0 event4 PROP=5 EV=b KEY=e420 1 0 0 0 0 ABS=66180001103 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-73-generic 5.4.0-73.82 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luiz 1541 F pulseaudio /dev/snd/controlC0: luiz 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 21:15:53 2021 InstallationDate: Installed on 2018-10-11 (950 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=3aa08318-3527-4824-a97a-cc0084649c15 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-18 (181 days ago) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP 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.:bvrX450LCP.206:bd02/20/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LCP dmi.product.sku: ASUS-NotebookSKU 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/1928878/+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 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
Would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1928600 Title: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Incomplete Bug description: With this hardware configuration this issue has been a problem only when suspending or resuming from suspend under 20.04. Having decided to upgrade through 20.10 to 21.04 to see if things improve enough to help me identify which package to report a bug against things have become significantly worse. With 20.04 it was an occasional occurrence found when returning to the computer. Either it was stuck in the suspend process with a blank screen or one with artefacts on, or it would start the resume and then lock. On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough time to tidy up and upgrade again), the system seemed improved initially - including notably improved boot times (no idea if that is related). After a bit of checking things out I went to enable the PPAs that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome - all of which have been installed after the problems were initially noted). When the window to authenticate popped up the screen filled with artefacts and I had to reset. After several attempts to reboot into a working desktop variously booting to artefacts, or getting artefacts immediately after logging in (usually when opening and maximising a terminal to capture the logs for later) I managed to change from Wayland to X.Org and logged in successfully with no problems for the rest of the day (including a Jitsi meeting lasting about 4 hours or more). The next day (today) suspend and resume is causing problems as before, boot has slowed down again (again, no idea if this is related). Compared to 20.04 there are more frequent locks (it had reached one every other day, but now it is more frequent - 4 today so far). Key things I have noted: - it is significantly worse under Wayland (to the point of being unusable) - it usually happens during the suspend / resume, but not always - when using the desktop it will always related to moving or resizing a window - leaving the PC powered off for a few minutes helps to get a reliable reboot (as in, if you reboot too quickly you get artefacts immediately after logging in) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 16 19:23:00 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-16 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-10-16 (214 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B79 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 RfKill: Tags: hirsute Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-05-15 (3 days ago) UserGroups: adm cdrom dip lpadmin
[Kernel-packages] [Bug 1928878] Re: Touchpad suddenly not responding
Is it a regression? Does it work before kernel upgrade? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1928878 Title: Touchpad suddenly not responding Status in linux package in Ubuntu: Incomplete Bug description: After leaving my laptop on sleep mode for a while, then bringing it up again causes the touchpad to stop responding completely. Checked for it in the bus/input/devices folder and didn't see it. Laptop model: ASUS X450L Touchpad manufacturer: I presume to also be ASUS Symptom first appeared less than a week ago. EDIT: Forgot to mention, the touchpad comes back after a restart. Touchpad info is as follows: Bus=0011 Vendor=0002 Product=000e Version= Name="ETPS/2 Elantech Touchpad" Phys=isa0060/serio1/input0 Sysfs=/devices/platform/i8042/serio1/input/input5 Uniq= Handlers=mouse0 event4 PROP=5 EV=b KEY=e420 1 0 0 0 0 ABS=66180001103 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-73-generic 5.4.0-73.82 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luiz 1541 F pulseaudio /dev/snd/controlC0: luiz 1541 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 18 21:15:53 2021 InstallationDate: Installed on 2018-10-11 (950 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. X450LCP ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=3aa08318-3527-4824-a97a-cc0084649c15 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-73-generic N/A linux-backports-modules-5.4.0-73-generic N/A linux-firmware1.187.12 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-18 (181 days ago) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X450LCP.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X450LCP 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.:bvrX450LCP.206:bd02/20/2014:svnASUSTeKCOMPUTERINC.:pnX450LCP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LCP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X450LCP dmi.product.sku: ASUS-NotebookSKU 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/1928878/+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
