[Kernel-packages] [Bug 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
Private is the default state for crashes because those bugs could potentially contain personal information in crash data. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
That's the only crash I'm experiencing. I didn't intend to set the other bug as private, so I'm not sure what's up there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
Bug 1924221 is private so I can't see it. But I'm confident we have the right links now (unless you're experiencing multiple different crashes). ** Summary changed: - bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] + bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
** Changed in: bluez Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd 5.56 segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd segfaults when Trackpoint II keyboard connects
Judging by the newness of the problem, the crash address and the logs, this looks like it's probably bug 1924220. But we will need you to follow the instructions in comment #2 to confirm that. ** Bug watch added: github.com/bluez/bluez/issues #112 https://github.com/bluez/bluez/issues/112 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()]
I ran ubuntu-bug on the .crash file. The bug that created is here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1924221 I also did a quick build of bluez 5.58 and can confirm it does not seem to segfault when connecting my keyboard. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 --- bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1924217/+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 1924217] Re: bluetoothd segfaults when Trackpoint II keyboard connects
Actually upstream bug report https://github.com/bluez/bluez/issues/112 confirms the symptoms. ** Summary changed: - bluetoothd segfaults when Trackpoint II keyboard connects + bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 + + --- + bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 - [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] + [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/zsh + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 - UP RUNNING - RX bytes:267050 acl:16636 sco:0 events:966 errors:0 - TX bytes:28087 acl:371 sco:0 commands:388 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 + UP RUNNING + RX bytes:267050 acl:16636 sco:0 events:966 errors:0 + TX bytes:28087 acl:371 sco:0 commands:388 errors:0 ** Also affects: bluez via https://github.com/bluez/bluez/issues/112 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-5.57 fixed-upstream ** Summary changed: - bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] + bluetoothd segfaults when keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- You rece
[Kernel-packages] [Bug 1924220] Re: bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()
*** This bug is a duplicate of bug 1924217 *** https://bugs.launchpad.net/bugs/1924217 ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:get_report_cb:notify_handler:notify_handler:queue_foreach:queue_foreach + bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach() ** This bug has been marked a duplicate of bug 1924217 bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924220 Title: bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach() Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.56-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1924220/+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 1924220] [NEW] bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()
*** This bug is a duplicate of bug 1924217 *** https://bugs.launchpad.net/bugs/1924217 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.56-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924220 Title: bluetoothd crashed with SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach() Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.56-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/e93420b383ce737e9a5dd894617135836bd75eb8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1924220/+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 1924217] Re: bluetoothd segfaults when Trackpoint II keyboard connects
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: regression-release ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd segfaults when Trackpoint II keyboard connects [SIGSEGV in get_report_cb() from notify_handler() from notify_handler() from queue_foreach() from queue_foreach()] Status in bluez package in Ubuntu: Incomplete Bug description: bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1924217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://he
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
Kernel 5.4.0-71 works for us with xen. Thank you very much! ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107&id=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1924217] [NEW] bluetoothd segfaults when Trackpoint II keyboard connects
Public bug reported: bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem went away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 Uname: Linux 5.11.0-051100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Apr 14 21:03:29 2021 InstallationDate: Installed on 2021-02-26 (47 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20AW0006US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-051100-generic root=UUID=d3f49081-f2cd-43ca-b9ed-bd8157d94ee3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-14 (0 days ago) dmi.bios.date: 01/27/2015 dmi.bios.release: 2.31 dmi.bios.vendor: LENOVO dmi.bios.version: GLET77WW (2.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AW0006US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrGLET77WW(2.31):bd01/27/2015:br2.31:efr1.8:svnLENOVO:pn20AW0006US:pvrThinkPadT440p:rvnLENOVO:rn20AW0006US:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AW0006US dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 10:4A:7D:01:8D:7F ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:267050 acl:16636 sco:0 events:966 errors:0 TX bytes:28087 acl:371 sco:0 commands:388 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924217 Title: bluetoothd segfaults when Trackpoint II keyboard connects Status in bluez package in Ubuntu: New Bug description: bluetoothd crashes when my Lenovo Trackpoint II keyboard connects. I see this in dmesg: [ 58.257605] input: TrackPoint Keyboard II Keyboard as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input26 [ 58.258542] input: TrackPoint Keyboard II Mouse as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input27 [ 58.259561] input: TrackPoint Keyboard II Consumer Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input /input28 [ 58.259661] input: TrackPoint Keyboard II System Control as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/i nput29 [ 58.260151] input: TrackPoint Keyboard II as /devices/virtual/misc/uhid/0005:17EF:60E1.0005/input/input31 [ 58.260267] hid-generic 0005:17EF:60E1.0005: input,hidraw4: BLUETOOTH HID v0.47 Keyboard [TrackPoint Keyboard II] on 10:4a:7d:01:8d:7f [ 58.263556] bluetoothd[685]: segfault at 59 ip 5574d1d10683 sp 7ffd03bd7570 error 6 in bluetoothd[5574d1ce5000+a9000] [ 58.263568] Code: 00 00 4c 8b 21 64 48 8b 04 25 28 00 00 00 48 89 84 24 38 11 00 00 31 c0 48 8d 6c 24 10 89 fb 49 89 c9 48 89 ef b9 23 02 00 00 <41> c7 44 24 58 00 00 00 00 f3 48 ab c7 44 24 10 0a 00 00 00 c7 07 This segfault is with bluez 5.56-0ubuntu3 in Ubuntu 21.04 (up-to-date as of today). It did not happen in 20.10. When I downgraded bluez to 5.55-0ubuntu1.1 the problem w
[Kernel-packages] [Bug 1924207] Re: [SRU][F/G/H] add realtek 8852 bluetooth support
** Description changed:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
- Backport for commit 05672a2c14 ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
+ Backport for commit 0d484db60f ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924207
Title:
[SRU][F/G/H] add realtek 8852 bluetooth support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
New
Status in linux-oem-5.10 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:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
Backport for commit 0d484db60f ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1924207/+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 1924207] Re: [SRU][F/G/H] add realtek 8852 bluetooth support
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: hwe-next
Assignee: (unassigned) => AaronMa (mapengyu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924207
Title:
[SRU][F/G/H] add realtek 8852 bluetooth support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
New
Status in linux-oem-5.10 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:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
Backport for commit 05672a2c14 ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1924207/+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 1924207] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1924207
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** 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/1924207
Title:
[SRU][F/G/H] add realtek 8852 bluetooth support
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.10 package in Ubuntu:
New
Status in linux-oem-5.10 source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
Incomplete
Bug description:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
Backport for commit 05672a2c14 ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1924207/+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 1924207] [NEW] [SRU][F/G/H] add realtek 8852 bluetooth support
Public bug reported:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
Backport for commit 05672a2c14 ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Incomplete
** Tags: oem-priority originate-from-1923394 sutton
** Also affects: linux (Ubuntu)
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
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Groovy)
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
** No longer affects: linux-oem-5.10 (Ubuntu Groovy)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux-oem-5.10 (Ubuntu Hirsute)
** Tags added: oem-priority originate-from-1923394 sutton
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1924207
Title:
[SRU][F/G/H] add realtek 8852 bluetooth support
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.10 package in Ubuntu:
New
Status in linux-oem-5.10 source package in Focal:
New
Status in linux source package in Groovy:
New
Status in linux source package in Hirsute:
Incomplete
Bug description:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
Backport for commit 05672a2c14 ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1924207/+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 1880631] Re: l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable
https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- 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/1880631 Title: l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable Status in ubuntu-kernel-tests: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Bug description: Issue found on 5.6.0-1011.11-oem # selftests: net: l2tp.sh # Warning: file l2tp.sh is not executable, correct this. not ok 32 selftests: net: l2tp.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880631/+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 1923925] Re: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260
Comment #1 is a different issue which either needs a new bug opened or you might wish to use bug 1576559. ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923925 Title: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260 Status in bluez package in Ubuntu: New Bug description: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923925/+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 1880631] Re: l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable
** Summary changed: - l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable on F-OEM-5.6 + l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable -- 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/1880631 Title: l2tp.sh from net in ubuntu_kernel_selftests failed with test not executable Status in ubuntu-kernel-tests: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Bug description: Issue found on 5.6.0-1011.11-oem # selftests: net: l2tp.sh # Warning: file l2tp.sh is not executable, correct this. not ok 32 selftests: net: l2tp.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880631/+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 1924203] Re: [SRU][F/G][linux-firmware] add realtek 8852 bluetooth fimware
** Summary changed: - [SRU][F/G] add realtek 8852 bluetooth fimware + [SRU][F/G][linux-firmware] add realtek 8852 bluetooth fimware -- 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/1924203 Title: [SRU][F/G][linux-firmware] add realtek 8852 bluetooth fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with bluetooth headset and file transfer, all good. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924203/+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 1924203] Re: [SRU][F/G] add realtek 8852 bluetooth fimware
** Tags added: oem-priority originate-from-1923394 sutton ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Description changed: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. Kernel driver will be in another SRU. [Test] - Verified on hardware with bluetooth headset and file file transfer. + Verified on hardware with bluetooth headset and file transfer. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. ** Description changed: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. Kernel driver will be in another SRU. [Test] - Verified on hardware with bluetooth headset and file transfer. + Verified on hardware with bluetooth headset and file transfer, all good. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. -- 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/1924203 Title: [SRU][F/G] add realtek 8852 bluetooth fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with bluetooth headset and file transfer, all good. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924203/+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 1924203] [NEW] [SRU][F/G] add realtek 8852 bluetooth fimware
Public bug reported: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with bluetooth headset and file file transfer. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1923394 sutton ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New ** Description changed: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. - Kernel driver will be in another SRU. + Kernel driver will be in another SRU. [Test] Verified on hardware with bluetooth headset and file file transfer. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. + Hirsute already got it, only SRU fw for F/G. -- 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/1924203 Title: [SRU][F/G] add realtek 8852 bluetooth fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: New Bug description: SRU justification: [Impact] Realtek 8852A bluetooth can not work without proper firmware. [Fix] Add realtek 8852 bluetooth fimware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with bluetooth headset and file file transfer. [Where problems could occur] The bluetooth chip 8852A may fail to work. It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924203/+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 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
** Changed in: linux Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+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 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
Thanks Tim for building the test kernel, and Hmpf, thanks for testing it and confirming it fixes the problem. Okay, so the problem is: commit a738c93fb1c17e386a09304b517b1c6b2a6a5a8b Author: Shyam Prasad N Date: Thu Feb 11 03:26:54 2021 -0800 Subject: cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath. Link: https://github.com/torvalds/linux/commit/a738c93fb1c17e386a09304b517b1c6b2a6a5a8b Looking at Focal, it seems Tim has submitted the revert and it has been applied for the next kernel update: https://lists.ubuntu.com/archives/kernel-team/2021-April/119241.html https://lists.ubuntu.com/archives/kernel-team/2021-April/119242.html https://lists.ubuntu.com/archives/kernel-team/2021-April/119243.html https://lists.ubuntu.com/archives/kernel-team/2021-April/119244.html https://lists.ubuntu.com/archives/kernel-team/2021-April/119246.html Thanks Tim! As for Bionic, it seems to still be applied to master-next, and hasn't been tagged into a release yet: https://paste.ubuntu.com/p/k9SffBrBMb/ Groovy seems to be in the same situation: https://paste.ubuntu.com/p/wRX79WKpy3/ Tim, are there any plans to get the revert landed in Bionic and Groovy for this cycle? I really don't want cause any regressions if we can avoid it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-
[Kernel-packages] [Bug 1923844] Re: i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: regression-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/1923844 Title: i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic Status in linux package in Ubuntu: Confirmed Bug description: This is a regression introduced with the latest kernel (linux- image-5.8.0-49-generic). Kubuntu 20.04, since upgrading kernel from version 5.8.0-48.54 to version 5.8.0-49.55 the system boots properly but the GUI often hangs, either immediately after user login to GUI or any time after that (screen stops updating with various artifacts and UI no longer responds) and computer has to be restarted. Messages like these appear in dmesg: Apr 13 08:43:24 kubuntu kernel: [47776.927523] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 08:43:24 kubuntu kernel: [4.029098] i915 :00:02.0: [drm] VMSVGA FIFO[40] context reset due to GPU hang Apr 13 11:25:37 kubuntu kernel: [ 45.168120] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:37 kubuntu kernel: [ 45.168166] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:37 kubuntu kernel: [ 45.270406] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 13 11:25:41 kubuntu kernel: [ 47.984475] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:41 kubuntu kernel: [ 47.984520] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:41 kubuntu kernel: [ 48.088097] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 13 11:25:47 kubuntu kernel: [ 54.128068] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:47 kubuntu kernel: [ 54.128111] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:47 kubuntu kernel: [ 54.230401] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 14 14:35:53 kubuntu kernel: [ 32.106297] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:c07f, in ksplashqml [3096] Apr 14 14:35:53 kubuntu kernel: [ 32.106341] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 14 14:35:53 kubuntu kernel: [ 32.207704] i915 :00:02.0: [drm] ksplashqml[3096] context reset due to GPU hang With previous kernel 5.8.0-48.54 (and all other previous kernels) there was never any problem like this. System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 61 Memory at f740 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 Boot info with i915 and drm: [0.00] microcode: microcode updated early to revision 0x21, date = 2019-02-13 [0.00] Linux version 5.8.0-49-generic (buildd@lgw01-amd64-055) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #55~20.04.1-Ubuntu SMP Fri Mar 26 01:01:07 UTC 2021 (Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.8.0-49-generic root=UUID=123 ro quiet splash vt.handoff=7 [0.00] DMI: System manufacturer System Product Name/P8Z68-V PRO GEN3, BIOS 3802 01/15/2015 [1.083804] fb0: switching to inteldrmfb from EFI VGA [1.083864] i915 :00:02.0: vgaarb: deactivate vga console [1.093201] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.097872] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.119734] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [1.260356] fbcon: i915drmfb (fb0) is primary device [1.260360] i915 :00:02.0: fb0: i915drmfb frame buffer device [5.070962] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. [5.526454] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Not blocking as I can stay on previous kernel but until this is fixed I can no longer use vulnerability fixes which
[Kernel-packages] [Bug 1923925] Re: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260
Just recognized that only output is working, there is no mic device even if I select HSP/HFP manually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923925 Title: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260 Status in bluez package in Ubuntu: New Bug description: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923925/+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 1923844] [NEW] i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic
You have been subscribed to a public bug: This is a regression introduced with the latest kernel (linux- image-5.8.0-49-generic). Kubuntu 20.04, since upgrading kernel from version 5.8.0-48.54 to version 5.8.0-49.55 the system boots properly but the GUI often hangs, either immediately after user login to GUI or any time after that (screen stops updating with various artifacts and UI no longer responds) and computer has to be restarted. Messages like these appear in dmesg: Apr 13 08:43:24 kubuntu kernel: [47776.927523] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 08:43:24 kubuntu kernel: [4.029098] i915 :00:02.0: [drm] VMSVGA FIFO[40] context reset due to GPU hang Apr 13 11:25:37 kubuntu kernel: [ 45.168120] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:37 kubuntu kernel: [ 45.168166] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:37 kubuntu kernel: [ 45.270406] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 13 11:25:41 kubuntu kernel: [ 47.984475] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:41 kubuntu kernel: [ 47.984520] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:41 kubuntu kernel: [ 48.088097] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 13 11:25:47 kubuntu kernel: [ 54.128068] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:85fc, in plasmashell [2918] Apr 13 11:25:47 kubuntu kernel: [ 54.128111] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 13 11:25:47 kubuntu kernel: [ 54.230401] i915 :00:02.0: [drm] plasmashell[2918] context reset due to GPU hang Apr 14 14:35:53 kubuntu kernel: [ 32.106297] i915 :00:02.0: [drm] GPU HANG: ecode 7:1:c07f, in ksplashqml [3096] Apr 14 14:35:53 kubuntu kernel: [ 32.106341] i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 Apr 14 14:35:53 kubuntu kernel: [ 32.207704] i915 :00:02.0: [drm] ksplashqml[3096] context reset due to GPU hang With previous kernel 5.8.0-48.54 (and all other previous kernels) there was never any problem like this. System is Asus P8Z68V-Pro Gen3, i7-3770, iGPU: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 61 Memory at f740 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 Boot info with i915 and drm: [0.00] microcode: microcode updated early to revision 0x21, date = 2019-02-13 [0.00] Linux version 5.8.0-49-generic (buildd@lgw01-amd64-055) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #55~20.04.1-Ubuntu SMP Fri Mar 26 01:01:07 UTC 2021 (Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.8.0-49-generic root=UUID=123 ro quiet splash vt.handoff=7 [0.00] DMI: System manufacturer System Product Name/P8Z68-V PRO GEN3, BIOS 3802 01/15/2015 [1.083804] fb0: switching to inteldrmfb from EFI VGA [1.083864] i915 :00:02.0: vgaarb: deactivate vga console [1.093201] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.097872] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.119734] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0 [1.260356] fbcon: i915drmfb (fb0) is primary device [1.260360] i915 :00:02.0: fb0: i915drmfb frame buffer device [5.070962] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. [5.526454] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Not blocking as I can stay on previous kernel but until this is fixed I can no longer use vulnerability fixes which makes the issue critical. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- i915 drm GPU hang - introduced with linux-image-5.8.0-49-generic https://bugs.launchpad.net/bugs/1923844 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@l
[Kernel-packages] [Bug 1923925] [NEW] Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260
Public bug reported: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923925 Title: Bluetooth headset (Teufel Airy True Wireless) does not pair with intel ac 9260 Status in bluez package in Ubuntu: New Bug description: A new bluetooth headset (Teufel Airy True Wireless) cannot be paired on my dell precision 5530 having an intel ac 9260 bluetooth chipset using ubuntu 20.04. Using an ubuntu 18.04 (boot from usb) I was able to connect the headset without any problem. As a workaround I transfering the device info file (/var/lib/bluetooth///info) to 20.04, having it paired this way it works without problems. It was important to reset device list on the hedphones before, it was not connecting in 18.04 after unsuccessfuly trying with 20.04 so maybe there was already a device key stored in the headset. Please let me know if I could give you further debug information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923925/+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 1921355] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1921355 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1921355 Title: cgroups related kernel panics Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: Hi! Recently (throughout the last 6 months) we've upgraded our hypervisor compute hosts from ubuntu bionic kernel 4.15.* to ubuntu bionic hwe kernel 5.4. This month we noticed that several nodes failed due to bugs in cgroups. Trace was different almost every time, but it all revolves around cgroups - either null pointer failures, or panic caught by BUG_ON() macro. Looked like some cgroup didn't exist anymore but somebody tried to access it, thus causing kernel panic. Please find the logs attached. 3 of 4 cases happened after a VM shutdown. We tried to spawn lots of VMs, load them, shut them down, but didn't manage to reproduce the behavior. Actually, every case is sort of different - patch kernel versions (5.4.0-42 to 5.4.0-66), uptime vary (from 1 day to ~half a year). There are also lots of hosts with several months of uptime, no issue with them. Also, on 4.15 we've never seen this behavior, at all. That's quite disturbing, as I don't want dozens of VMs crash (due to host outage) at random times for some vague reason... I didn't manage to find any related bugs on the bug tracker, thus creating this one. I wonder if anybody in the community came across something like that. Could somebody give an advice how to debug further, or where else to report / look for a similar the case? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921355/+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 1921355] Re: cgroups related kernel panics
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921355 Title: cgroups related kernel panics Status in linux package in Ubuntu: New Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: Hi! Recently (throughout the last 6 months) we've upgraded our hypervisor compute hosts from ubuntu bionic kernel 4.15.* to ubuntu bionic hwe kernel 5.4. This month we noticed that several nodes failed due to bugs in cgroups. Trace was different almost every time, but it all revolves around cgroups - either null pointer failures, or panic caught by BUG_ON() macro. Looked like some cgroup didn't exist anymore but somebody tried to access it, thus causing kernel panic. Please find the logs attached. 3 of 4 cases happened after a VM shutdown. We tried to spawn lots of VMs, load them, shut them down, but didn't manage to reproduce the behavior. Actually, every case is sort of different - patch kernel versions (5.4.0-42 to 5.4.0-66), uptime vary (from 1 day to ~half a year). There are also lots of hosts with several months of uptime, no issue with them. Also, on 4.15 we've never seen this behavior, at all. That's quite disturbing, as I don't want dozens of VMs crash (due to host outage) at random times for some vague reason... I didn't manage to find any related bugs on the bug tracker, thus creating this one. I wonder if anybody in the community came across something like that. Could somebody give an advice how to debug further, or where else to report / look for a similar the case? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921355/+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 1923897] Re: Bionic update: upstream stable patchset 2021-04-14
** Description changed:
+ SRU Justification
- 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:
- 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:
+ upstream stable patchset 2021-04-14
-upstream stable patchset 2021-04-14
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.226, v4.19.181
+v4.19.182
+ v4.14.227, v4.19.183
+
+ from git://git.kernel.org/
+
+ uapi: nfnetlink_cthelper.h: fix userspace compilation error
+ ath9k: fix transmitting to stations in dynamic SMPS mode
+ net: Fix gro aggregation for udp encaps with zero csum
+ net: Introduce parse_protocol header_ops callback
+ net: check if protocol extracted by virtio_net_hdr_set_proto is correct
+ net: avoid infinite loop in mpls_gso_segment when mpls_hlen == 0
+ can: skb: can_skb_set_owner(): fix ref counting if socket was closed before
setting skb ownership
+ can: flexcan: assert FRZ bit in flexcan_chip_freeze()
+ can: flexcan: enable RX FIFO after FRZ/HALT valid
+ netfilter: x_tables: gpf inside xt_find_revision()
+ cifs: return proper error code in statfs(2)
+ scripts/recordmcount.{c,pl}: support -ffunction-sections .text.* section names
+ Revert "mm, slub: consider rest of partial list if acquire_slab() fails"
+ sh_eth: fix TRSCER mask for SH771x
+ net/mlx4_en: update moderation when config reset
+ net: stmmac: fix incorrect DMA channel intr enable setting of EQoS v4.10
+ net: sched: avoid duplicates in classes dump
+ net: usb: qmi_wwan: allow qmimux add/del with master up
+ cipso,calipso: resolve a number of problems with the DOI refcounts
+ net: lapbether: Remove netif_start_queue / netif_stop_queue
+ net: davicom: Fix regulator not turned off on failed probe
+ net: davicom: Fix regulator not turned off on driver removal
+ net: stmmac: stop each tx channel independently
+ perf traceevent: Ensure read cmdlines are null terminated.
+ s390/cio: return -EFAULT if copy_to_user() fails again
+ drm/compat: Clear bounce structures
+ drm: meson_drv add shutdown function
+ s390/cio: return -EFAULT if copy_to_user() fails
+ media: usbtv: Fix deadlock on suspend
+ net: phy: fix save wrong speed and duplex problem if autoneg is on
+ udf: fix silent AED tagLocation corruption
+ mmc: mxs-mmc: Fix a resource leak in an error handling path in
'mxs_mmc_probe()'
+ mmc: mediatek: fix race condition between msdc_request_timeout and irq
+ powerpc: improve handling of unrecoverable system reset
+ powerpc/perf: Record counter overflow always if SAMPLE_IP is unset
+ PCI: xgene-msi: Fix race in installing chained irq handler
+ PCI: mediatek: Add missing of_node_put() to fix reference leak
+ s390/smp: __smp_rescan_cpus() - move cpumask away from stack
+ scsi: libiscsi: Fix iscsi_prep_scsi_cmd_pdu() error handling
+ ALSA: hda/hdmi: Cancel pending works before suspend
+ ALSA: hda: Drop the BATCH workaround for AMD controllers
+ ALSA: hda: Avoid spurious unsol event handling during S3/S4
+ ALSA: usb-audio: Fix "cannot get freq eq" errors on Dell AE515 sound bar
+ Revert 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file
capabilities")
+ s390/dasd: fix hanging DASD driver unbind
+ s390/dasd: fix hanging IO request during DASD driver unbind
+ mmc: core: Fix partition switch time for eMMC
+ Goodix Fingerprint device is not a modem
+ USB: gadget: u_ether: Fix a configfs return code
+ usb: gadget: f_uac2: always increase endpoint max_packet_size by one audio
slot
+ usb: gadget: f_uac1: stop playback on function disable
+ usb: renesas_usbhs: Clear PIPECFG for re-enabling pipe with other EPNUM
+ xhci: Improve detection of device initiated wake signal.
+ usb: xhci: Fix ASMedia ASM1042A and ASM3242 DMA addressing
+ USB: serial: io_edgeport: fix memory leak in edge_startup
+ USB: serial: ch341: add new Product ID
+ USB: serial: cp210x: add ID for Acuity Brands nLight Air Adapter
+ USB: serial: cp210x: add some more GE USB IDs
+ usbip: fix stub_dev to check for stream socket
+ usbip: fix vhci_hcd to check for stream socket
+ usbip: fix vudc to check for stream socket
+ usbip: fix vhci_hcd attach_stor
[Kernel-packages] [Bug 1923897] [NEW] Bionic update: upstream stable patchset 2021-04-14
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:
upstream stable patchset 2021-04-14
Ported from the following upstream stable releases:
v4.14.226, v4.19.181
v4.19.182
v4.14.227, v4.19.183
from git://git.kernel.org/
uapi: nfnetlink_cthelper.h: fix userspace compilation error
ath9k: fix transmitting to stations in dynamic SMPS mode
net: Fix gro aggregation for udp encaps with zero csum
net: Introduce parse_protocol header_ops callback
net: check if protocol extracted by virtio_net_hdr_set_proto is correct
net: avoid infinite loop in mpls_gso_segment when mpls_hlen == 0
can: skb: can_skb_set_owner(): fix ref counting if socket was closed before
setting skb ownership
can: flexcan: assert FRZ bit in flexcan_chip_freeze()
can: flexcan: enable RX FIFO after FRZ/HALT valid
netfilter: x_tables: gpf inside xt_find_revision()
cifs: return proper error code in statfs(2)
scripts/recordmcount.{c,pl}: support -ffunction-sections .text.* section names
Revert "mm, slub: consider rest of partial list if acquire_slab() fails"
sh_eth: fix TRSCER mask for SH771x
net/mlx4_en: update moderation when config reset
net: stmmac: fix incorrect DMA channel intr enable setting of EQoS v4.10
net: sched: avoid duplicates in classes dump
net: usb: qmi_wwan: allow qmimux add/del with master up
cipso,calipso: resolve a number of problems with the DOI refcounts
net: lapbether: Remove netif_start_queue / netif_stop_queue
net: davicom: Fix regulator not turned off on failed probe
net: davicom: Fix regulator not turned off on driver removal
net: stmmac: stop each tx channel independently
perf traceevent: Ensure read cmdlines are null terminated.
s390/cio: return -EFAULT if copy_to_user() fails again
drm/compat: Clear bounce structures
drm: meson_drv add shutdown function
s390/cio: return -EFAULT if copy_to_user() fails
media: usbtv: Fix deadlock on suspend
net: phy: fix save wrong speed and duplex problem if autoneg is on
udf: fix silent AED tagLocation corruption
mmc: mxs-mmc: Fix a resource leak in an error handling path in 'mxs_mmc_probe()'
mmc: mediatek: fix race condition between msdc_request_timeout and irq
powerpc: improve handling of unrecoverable system reset
powerpc/perf: Record counter overflow always if SAMPLE_IP is unset
PCI: xgene-msi: Fix race in installing chained irq handler
PCI: mediatek: Add missing of_node_put() to fix reference leak
s390/smp: __smp_rescan_cpus() - move cpumask away from stack
scsi: libiscsi: Fix iscsi_prep_scsi_cmd_pdu() error handling
ALSA: hda/hdmi: Cancel pending works before suspend
ALSA: hda: Drop the BATCH workaround for AMD controllers
ALSA: hda: Avoid spurious unsol event handling during S3/S4
ALSA: usb-audio: Fix "cannot get freq eq" errors on Dell AE515 sound bar
Revert 95ebabde382c ("capabilities: Don't allow writing ambiguous v3 file
capabilities")
s390/dasd: fix hanging DASD driver unbind
s390/dasd: fix hanging IO request during DASD driver unbind
mmc: core: Fix partition switch time for eMMC
Goodix Fingerprint device is not a modem
USB: gadget: u_ether: Fix a configfs return code
usb: gadget: f_uac2: always increase endpoint max_packet_size by one audio slot
usb: gadget: f_uac1: stop playback on function disable
usb: renesas_usbhs: Clear PIPECFG for re-enabling pipe with other EPNUM
xhci: Improve detection of device initiated wake signal.
usb: xhci: Fix ASMedia ASM1042A and ASM3242 DMA addressing
USB: serial: io_edgeport: fix memory leak in edge_startup
USB: serial: ch341: add new Product ID
USB: serial: cp210x: add ID for Acuity Brands nLight Air Adapter
USB: serial: cp210x: add some more GE USB IDs
usbip: fix stub_dev to check for stream socket
usbip: fix vhci_hcd to check for stream socket
usbip: fix vudc to check for stream socket
usbip: fix vhci_hcd attach_store() races leading to gpf
staging: rtl8192u: fix ->ssid overflow in r8192_wx_set_scan()
staging: rtl8188eu: prevent ->ssid overflow in rtw_wx_set_scan()
staging: rtl8712: unterminated string leads to read overflow
staging: rtl8188eu: fix potential memory corruption in rtw_check_beacon_data()
staging: ks7010: prevent buffer overflow in ks_wlan_set_scan()
staging: rtl8712: Fix possible buffer overflow in r8712_sitesurvey_cmd
staging: rtl8192e: Fix possible buffer overflow in _rtl92e_wx_set_scan
staging: comedi: addi_apci_1032: Fix endian problem for COS sample
staging: comedi: addi_apci_1500: Fix endian problem for command sample
staging: comedi: adv_pci1710: Fix endian problem for AI command data
staging:
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gkeop (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oracle (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-oracle (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oracle (Ubuntu Groovy) Status: New => Fix Committed -- 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/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Committed Status in linux-gkeop source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+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 1923230] Re: Can not boot Cavium ThunderX
I found a system running old firmware and I was able to reproduce this. I updated the firmware, and the issue went away. Of course, it seems like a regression that the kernel now *crashes* with the bad firmware (see bug 1755304 for my reasoning for it being bad), when it used to just emit errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923230 Title: Can not boot Cavium ThunderX Status in linux package in Ubuntu: Incomplete Bug description: Hi I am tryring to deploy a Hirsute server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits Im getting a kernel panic occurs during the boot: [8.417589] Code: a90153f3 aa0003f3 2a0103f4 3774 (79437000) [8.425298] ---[ end trace 2f743d3081d8a73b ]--- [8.431538] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [8.440888] SMP: stopping secondary CPUs [8.446480] Kernel Offset: disabled [8.451581] CPU features: 0x00040002,69101108 [8.457552] Memory Limit: none [8.462197] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230/+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 1905591] Re: no brightness control in {455, 460} after update from 450
To add more info on what I tried, I have put it here:
https://askubuntu.com/questions/1329928/legion-5-pro-brightness-control-
doesnt-work-on-ubuntu-20-04-with-nvidia-driver . Surprisingly the
brightness also works on Manjaro (as mentioned in my post) after adding
'Option "RegistryDwords" "EnableBrightnessControl=1"' to x.conf.d. Also,
it also works on Regolith Linux 1.5.3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
nvidia-driver-460: 460.39-0ubuntu0.18.04.1
*WORKAROUND: See comment #11 (add nvidia drivers to initramfs).
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+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 1923888] [NEW] Apply Patch to 4.15 kernels which will resolve a netvsc bug
Public bug reported: A soft lockup is happening to 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 Author: Stephen Hemminger Date: Sat Sep 29 14:52:56 2018 +0200 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. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Apply Patch to 4.15 kernels to resolve netvsc bug + Apply Patch to 4.15 kernels which will resolve a netvsc bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1923888 Title: Apply Patch to 4.15 kernels which will resolve a netvsc bug Status in linux-azure package in Ubuntu: New Bug description: A soft lockup is happening to 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 Author: Stephen Hemminger Date: Sat Sep 29 14:52:56 2018 +0200 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1923888/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:29:27 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.32.03-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). -- Alberto Milone Thu, 25 Feb 2021 16:34:45 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.102.04-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:51:33 +0100 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:26:13 +0100 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.181.07-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:18:23 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.32.03-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). -- Alberto Milone Thu, 25 Feb 2021 16:36:50 +0100 ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.102.04-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:52:53 +0100 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:28:05 +0100 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.181.07-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:19:47 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.32.03-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). -- Alberto Milone Thu, 25 Feb 2021 16:38:36 +0100 ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.102.04-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:54:49 +0100 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.181.07-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:21:01 +0100 ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:29:27 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server == * debian/templates/control.in: - Add missing conflict/replace/provide for libn
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.32.03-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). -- Alberto Milone Thu, 25 Feb 2021 16:34:45 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server == * debian/temp
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.102.04-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:51:33 +0100 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:26:13 +0100 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.181.07-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:18:23 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cu
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.141-0ubuntu0.20.10.2 --- nvidia-graphics-drivers-390 (390.141-0ubuntu0.20.10.2) groovy; urgency=medium * debian/templates/control.in: - Add conflicts/replace/provides for all the metapackages (LP: #1915935). - Add XB-Support field and set it to "Legacy". * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:01:55 +0100 ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server ==
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.32.03-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). -- Alberto Milone Thu, 25 Feb 2021 16:36:50 +0100 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server == * debian/templ
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.102.04-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:52:53 +0100 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support f
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-450 - 450.102.04-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-450 (450.102.04-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:28:05 +0100 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1.
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.181.07-0ubuntu0.20.04.2 --- nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.20.04.2) focal; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:19:47 +0100 ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-460-server - 460.32.03-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). -- Alberto Milone Thu, 25 Feb 2021 16:38:36 +0100 ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server == * debia
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.102.04-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-450-server (450.102.04-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 16:54:49 +0100 ** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-418-server - 418.181.07-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-418-server (418.181.07-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:21:01 +0100 ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.141-0ubuntu0.18.04.2 --- nvidia-graphics-drivers-390 (390.141-0ubuntu0.18.04.2) bionic; urgency=medium * debian/templates/control.in: - Add conflicts/replace/provides for all the metapackages (LP: #1915935). - Add XB-Support field and set it to "Legacy". * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). Note: UVM is disabled for Linux >= 5.10. -- Alberto Milone Thu, 25 Feb 2021 17:07:58 +0100 ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and
[Kernel-packages] [Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
Yes, I can access the DFS entries with the provided test kernel. Please let me know if you need more info from my side. I do not think that it matters here, but I did not install the header files as linux-headers-5.4.0-72-generic depends on linux- headers-5.4.0-72 which is not in the linked web directory. Cheers and thanks for the fast work. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat sambashare scanner sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET61W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS00T00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET61W(1.39):bd04/20/2020:svnLENOVO:pn20HMS00T00:pvrThinkPadX270:rvnLENOVO:rn20HMS00T00:rvrNotDefined
[Kernel-packages] [Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050
Also worth mentioning. We are only seeing this on the A100. Neither our automated testing or manual testing of ftrace saw any issues on DGX2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922387 Title: BUG: kernel NULL pointer dereference, address: 0050 Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: I observed the following kernel panic with the 5.4.0-71.79-generic kernel while running kernel selftests: blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28 [ 1672.118199] mmiotrace: Error taking CPU254 down: -28 [ 1672.230306] mmiotrace: Error taking CPU255 down: -28 [ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050 [ 2503.367527] #PF: supervisor read access in kernel mode [ 2503.373257] #PF: error_code(0x) - not-present page [ 2503.378989] PGD 0 P4D 0 [ 2503.381812] Oops: [#1] SMP NOPTI [ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.4.0-71-generic #79-Ubuntu [ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.33 01/19/2021 [ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100 [ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00 00 48 8d 7d a0 e8 d0 a4 ca ff 49 89 c4 48 85 c0 74 37 49 8b 87 b8 03 00 00 <48> 8b 70 50 48 85 f6 74 45 49 8d 7c 24 08 ba 20 00 00 00 e8 59 91 [ 2503.432683] RSP: 0018:a8d6c0003d90 EFLAGS: 00010286 [ 2503.438513] RAX: RBX: RCX: 8100 [ 2503.446474] RDX: 9968a228f418 RSI: 0100 RDI: 9968a228f414 [ 2503.454436] RBP: a8d6c0003df8 R08: 9968a228f414 R09: 0100 [ 2503.462394] R10: 0007 R11: 0007 R12: 9968a228f418 [ 2503.470353] R13: fffa R14: 0003 R15: 9a686f9b3000 [ 2503.478316] FS: () GS:99690cc0() knlGS: [ 2503.487342] CS: 0010 DS: ES: CR0: 80050033 [ 2503.493752] CR2: 0050 CR3: 007e08ad6000 CR4: 00340ef0 [ 2503.501712] Call Trace: [ 2503.504438] [ 2503.506682] wb_timer_fn+0x1d6/0x3c0 [ 2503.510672] ? blk_stat_free_callback_rcu+0x30/0x30 [ 2503.516112] blk_stat_timer_fn+0x134/0x140 [ 2503.520683] call_timer_fn+0x32/0x130 [ 2503.524768] __run_timers.part.0+0x180/0x280 [ 2503.529535] ? trace_event_raw_event_softirq+0x5d/0xa0 [ 2503.535267] run_timer_softirq+0x2a/0x50 [ 2503.539644] __do_softirq+0xe1/0x2d6 [ 2503.543629] irq_exit+0xae/0xb0 [ 2503.547132] smp_apic_timer_interrupt+0x7b/0x140 [ 2503.552280] apic_timer_interrupt+0xf/0x20 [ 2503.556848] [ 2503.559187] RIP: 0010:native_safe_halt+0xe/0x10 [ 2503.564239] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d 66 dd 52 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d 56 dd 52 00 fb f4 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 cd cd 63 ff 65 [ 2503.585191] RSP: 0018:94803e18 EFLAGS: 0202 ORIG_RAX: ff13 [ 2503.593635] RAX: 0001e7c0 RBX: 996849080de8 RCX: 00149022 [ 2503.601595] RDX: 00149022 RSI: RDI: 948c5ba0 [ 2503.609556] RBP: 94803e38 R08: 02a8 R09: 9968a228f000 [ 2503.617516] R10: R11: 0002 R12: [ 2503.625475] R13: R14: R15: [ 2503.633440] ? default_idle+0x20/0x140 [ 2503.637623] arch_cpu_idle+0x15/0x20 [ 2503.641608] default_idle_call+0x23/0x30 [ 2503.645984] do_idle+0x1fb/0x270 [ 2503.649583] cpu_startup_entry+0x20/0x30 [ 2503.653960] rest_init+0xae/0xb0 [ 2503.657563] arch_call_rest_init+0xe/0x1b [ 2503.662025] start_kernel+0x549/0x56a [ 2503.666108] x86_64_start_reservations+0x24/0x26 [ 2503.671258] x86_64_start_kernel+0x75/0x79 [ 2503.675828] secondary_startup_64+0xa4/0xb0 [ 2503.680493] Modules linked in: sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat iptable_nat xt_nat nf_nat algif_hash af_alg ip6table_filter xt_conntrack nf_conntrack nf_defrag_ipv4 ip6_tables nf_defrag_ipv6 ip_vti ip6_vti fou6 sit ipip tunnel4 geneve act_mirred cls_basic esp6 authenc echainiv iptable_filter xt_policy bpfilter veth esp4_offload esp4 xfrm_user xfrm_algo macsec fou vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua amd64_edac_mod edac_mce_amd kvm_amd kvm ipmi_ssif input_leds cdc_ether usbnet mii ccp k10temp ipmi_si ipmi_devintf i
[Kernel-packages] [Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050
Here are the steps I used to reproduce: #if using proposed pocket kernel https://wiki.ubuntu.com/Testing/EnableProposed #Need to enable deb-src for proposed/updates for this work sudo apt update $ sudo apt-get source linux #After source is pulled, build and run ftrace selftests $ sudo make -C linux-5.4.0/tools/testing/selftests TARGETS=ftrace run_tests I also tested on Ubuntu-5.4.0-70.78 and saw similar behavior with soft lockups, but have yet to replicate the crash. Though I don't feel I have evidence to indicate this is a kernel regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922387 Title: BUG: kernel NULL pointer dereference, address: 0050 Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: I observed the following kernel panic with the 5.4.0-71.79-generic kernel while running kernel selftests: blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28 [ 1672.118199] mmiotrace: Error taking CPU254 down: -28 [ 1672.230306] mmiotrace: Error taking CPU255 down: -28 [ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050 [ 2503.367527] #PF: supervisor read access in kernel mode [ 2503.373257] #PF: error_code(0x) - not-present page [ 2503.378989] PGD 0 P4D 0 [ 2503.381812] Oops: [#1] SMP NOPTI [ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.4.0-71-generic #79-Ubuntu [ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.33 01/19/2021 [ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100 [ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00 00 48 8d 7d a0 e8 d0 a4 ca ff 49 89 c4 48 85 c0 74 37 49 8b 87 b8 03 00 00 <48> 8b 70 50 48 85 f6 74 45 49 8d 7c 24 08 ba 20 00 00 00 e8 59 91 [ 2503.432683] RSP: 0018:a8d6c0003d90 EFLAGS: 00010286 [ 2503.438513] RAX: RBX: RCX: 8100 [ 2503.446474] RDX: 9968a228f418 RSI: 0100 RDI: 9968a228f414 [ 2503.454436] RBP: a8d6c0003df8 R08: 9968a228f414 R09: 0100 [ 2503.462394] R10: 0007 R11: 0007 R12: 9968a228f418 [ 2503.470353] R13: fffa R14: 0003 R15: 9a686f9b3000 [ 2503.478316] FS: () GS:99690cc0() knlGS: [ 2503.487342] CS: 0010 DS: ES: CR0: 80050033 [ 2503.493752] CR2: 0050 CR3: 007e08ad6000 CR4: 00340ef0 [ 2503.501712] Call Trace: [ 2503.504438] [ 2503.506682] wb_timer_fn+0x1d6/0x3c0 [ 2503.510672] ? blk_stat_free_callback_rcu+0x30/0x30 [ 2503.516112] blk_stat_timer_fn+0x134/0x140 [ 2503.520683] call_timer_fn+0x32/0x130 [ 2503.524768] __run_timers.part.0+0x180/0x280 [ 2503.529535] ? trace_event_raw_event_softirq+0x5d/0xa0 [ 2503.535267] run_timer_softirq+0x2a/0x50 [ 2503.539644] __do_softirq+0xe1/0x2d6 [ 2503.543629] irq_exit+0xae/0xb0 [ 2503.547132] smp_apic_timer_interrupt+0x7b/0x140 [ 2503.552280] apic_timer_interrupt+0xf/0x20 [ 2503.556848] [ 2503.559187] RIP: 0010:native_safe_halt+0xe/0x10 [ 2503.564239] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d 66 dd 52 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d 56 dd 52 00 fb f4 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 cd cd 63 ff 65 [ 2503.585191] RSP: 0018:94803e18 EFLAGS: 0202 ORIG_RAX: ff13 [ 2503.593635] RAX: 0001e7c0 RBX: 996849080de8 RCX: 00149022 [ 2503.601595] RDX: 00149022 RSI: RDI: 948c5ba0 [ 2503.609556] RBP: 94803e38 R08: 02a8 R09: 9968a228f000 [ 2503.617516] R10: R11: 0002 R12: [ 2503.625475] R13: R14: R15: [ 2503.633440] ? default_idle+0x20/0x140 [ 2503.637623] arch_cpu_idle+0x15/0x20 [ 2503.641608] default_idle_call+0x23/0x30 [ 2503.645984] do_idle+0x1fb/0x270 [ 2503.649583] cpu_startup_entry+0x20/0x30 [ 2503.653960] rest_init+0xae/0xb0 [ 2503.657563] arch_call_rest_init+0xe/0x1b [ 2503.662025] start_kernel+0x549/0x56a [ 2503.666108] x86_64_start_reservations+0x24/0x26 [ 2503.671258] x86_64_start_kernel+0x75/0x79 [ 2503.675828] secondary_startup_64+0xa4/0xb0 [ 2503.680493] Modules linked in: sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat iptable_nat xt_nat nf_nat algif_hash af_alg ip6table_filter xt_conntrack nf_conntrack nf_defrag_ipv4 ip6_tables nf_defrag_ipv6 ip_vti ip6_vti fou6 sit ipip tunnel4 geneve act_mirred cls_basic esp6 authenc echainiv iptable_filt
[Kernel-packages] [Bug 1923872] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1923872 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1923872 Title: Issues with using webcam, system freezes or gets unstable after some time Status in linux package in Ubuntu: Incomplete Bug description: I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does connect properly. I can use it in some applications, like skype, zoom and discord. But after some time (around 3 minutes, sometimes way longer) the cam won't turn on anymore and the system completely freezes or gets very unstable, until I unplug the webcam. dmesg | grep uvcvideo: [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893) [4.700237] usbcore: registered new interface driver uvcvideo [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: -110 (exp. 5). [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: -110 (exp. 5). [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 18:31:37 2021 InstallationDate: Installed on 2020-10-06 (190 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.50 dmi.board.name: X470 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923872/+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 1922293] Re: Snaps appear broken on 21.04 Beta with ZFS
This is fixed in todays build, so closing this bug ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1922293 Title: Snaps appear broken on 21.04 Beta with ZFS Status in snapd package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Bug description: I've attempted to use two different userland snaps (qownnotes and keepassxc) neither function. When attempting to launch I get the following error: ``` chalbersma@abdos:~$ qownnotes cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_t3kehe//dev: No such file or directory ``` Additionally the snaps installed "by default" have a note of "broken" next to them : ``` chalbersma@abdos:~$ sudo snap list Name Version RevTracking Publisher Notes core18 1997 latest/stablecanonical✓ broken gnome-3-34-1804 66 latest/stable/… canonical✓ broken gtk-common-themes 1514 latest/stable/… canonical✓ broken qownnotes 21.3.9 8183 latest/stablepbek- snap-store 518latest/stable/… canonical✓ broken snapd 11402 latest/stablecanonical✓ broken ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
Testing on google cloud, this is still broken for: bionic hwe (5.4.0-1041-gcp #44~18.04.1-Ubuntu) focal ga (5.4.0-1041-gcp #44-Ubuntu) focal hwe (5.8.0-49-generic #55~20.04.1-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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+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 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
Hmpf - Here is a test kernel with just commit ea42fd91d3041b81d704624b87f35b56f3a00841 from v5.4.112 applied. https://kernel.ubuntu.com/~rtg/LP1923670/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat sambashare scanner sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET61W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS00T00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET61W(1.39):bd04/20/2020:svnLENOVO:pn20HMS00T00:pvrThinkPadX270:rvnLENOVO:rn20HMS00T00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS00T00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.s
[Kernel-packages] [Bug 1923874] [NEW] Focal update: v5.4.111 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.4.111 upstream stable release from git://git.kernel.org/ ARM: dts: am33xx: add aliases for mmc interfaces bus: ti-sysc: Fix warning on unbind if reset is not deasserted platform/x86: intel-hid: Support Lenovo ThinkPad X1 Tablet Gen 2 bpf, x86: Use kvmalloc_array instead kmalloc_array in bpf_jit_comp net/mlx5e: Enforce minimum value check for ICOSQ size net: pxa168_eth: Fix a potential data race in pxa168_eth_remove mISDN: fix crash in fritzpci mac80211: choose first enabled channel for monitor drm/msm/adreno: a5xx_power: Don't apply A540 lm_setup to other GPUs drm/msm: Ratelimit invalid-fence message netfilter: conntrack: Fix gre tunneling over ipv6 platform/x86: thinkpad_acpi: Allow the FnLock LED to change state x86/build: Turn off -fcf-protection for realmode targets scsi: target: pscsi: Clean up after failure in pscsi_map_sg() ia64: mca: allocate early mca with GFP_ATOMIC ia64: fix format strings for err_inject cifs: revalidate mapping when we open files for SMB1 POSIX cifs: Silently ignore unknown oplock break handle nvme-mpath: replace direct_make_request with generic_make_request init/Kconfig: make COMPILE_TEST depend on !S390 init/Kconfig: make COMPILE_TEST depend on HAS_IOMEM Linux 5.4.111 UBUNTU: upstream stable to v5.4.111 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - 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.4.111 upstream stable release + from git://git.kernel.org/ -v5.4.111 upstream stable release -from git://git.kernel.org/ + ARM: dts: am33xx: add aliases for mmc interfaces + bus: ti-sysc: Fix warning on unbind if reset is not deasserted + platform/x86: intel-hid: Support Lenovo ThinkPad X1 Tablet Gen 2 + bpf, x86: Use kvmalloc_array instead kmalloc_array in bpf_jit_comp + net/mlx5e: Enforce minimum value check for ICOSQ size + net: pxa168_eth: Fix a potential data race in pxa168_eth_remove + mISDN: fix crash in fritzpci + mac80211: choose first enabled channel for monitor + drm/msm/adreno: a5xx_power: Don't apply A540 lm_setup to other GPUs + drm/msm: Ratelimit invalid-fence message + netfilter: conntrack: Fix gre tunneling over ipv6 + platform/x86: thinkpad_acpi: Allow the FnLock LED to change state + x86/build: Turn off -fcf-protection for realmode targets + scsi: target: pscsi: Clean up after failure in pscsi_map_sg() + ia64: mca: allocate early mca with GFP_ATOMIC + ia64: fix format strings for err_inject + cifs: revalidate mapping when we open files for SMB1 POSIX + cifs: Silently ignore unknown oplock break handle + nvme-mpath: replace direct_make_request with generic_make_request + init/Kconfig: make COMPILE_TEST depend on !S390 + init/Kconfig: make COMPILE_TEST depend on HAS_IOMEM + Linux 5.4.111 + UBUNTU: upstream stable to v5.4.111 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/b
[Kernel-packages] [Bug 1923872] [NEW] Issues with using webcam, system freezes or gets unstable after some time
Public bug reported: I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does connect properly. I can use it in some applications, like skype, zoom and discord. But after some time (around 3 minutes, sometimes way longer) the cam won't turn on anymore and the system completely freezes or gets very unstable, until I unplug the webcam. dmesg | grep uvcvideo: [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893) [4.700237] usbcore: registered new interface driver uvcvideo [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: -110 (exp. 5). [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: -110 (exp. 5). [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 18:31:37 2021 InstallationDate: Installed on 2020-10-06 (190 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.50 dmi.board.name: X470 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal gstreamer-error webcam -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923872 Title: Issues with using webcam, system freezes or gets unstable after some time Status in linux package in Ubuntu: New Bug description: I use my Logitech Streamcam with Ubuntu 20.04.2 LTS and it does connect properly. I can use it in some applications, like skype, zoom and discord. But after some time (around 3 minutes, sometimes way longer) the cam won't turn on anymore and the system completely freezes or gets very unstable, until I unplug the webcam. dmesg | grep uvcvideo: [4.684206] uvcvideo: Found UVC 1.00 device Logitech StreamCam (046d:0893) [4.700237] usbcore: registered new interface driver uvcvideo [14322.880477] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: -110 (exp. 5). [15471.160277] uvcvideo: Failed to query (GET_DEF) UVC control 9 on unit 11: -110 (exp. 5). [15524.183921] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). [15529.303890] uvcvideo: Failed to set UVC probe control : -110 (exp. 26). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 14 18:31:37 2021 InstallationDate: Installed on 2020-10-06 (190 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. RelatedPackageVersions: cheese3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.50 dmi.board.name: X470 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd08/05/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dm
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
Second problem (freeze after suspend/resume) seems to be fixed with 5.4.0-71-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Confirmed Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+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 1923869] [NEW] Focal update: v5.4.110 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.4.110 upstream stable release from git://git.kernel.org/ selinux: vsock: Set SID for socket returned by accept() ipv6: weaken the v4mapped source check modsign: print module name along with error message module: merge repetitive strings in module_sig_check() module: avoid *goto*s in module_sig_check() module: harden ELF info handling ext4: shrink race window in ext4_should_retry_alloc() ext4: fix bh ref count on error paths fs: nfsd: fix kconfig dependency warning for NFSD_V4 rpc: fix NULL dereference on kmalloc failure iomap: Fix negative assignment to unsigned sis->pages in iomap_swapfile_activate ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10 ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10 ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on probe ASoC: es8316: Simplify adc_pga_gain_tlv table ASoC: cs42l42: Fix Bitclock polarity inversion ASoC: cs42l42: Fix channel width support ASoC: cs42l42: Fix mixer volume control ASoC: cs42l42: Always wait at least 3ms after reset NFSD: fix error handling in NFSv4.0 callbacks powerpc: Force inlining of cpu_has_feature() to avoid build failure vhost: Fix vhost_vq_reset() scsi: st: Fix a use after free in st_open() scsi: qla2xxx: Fix broken #endif placement staging: comedi: cb_pcidas: fix request_irq() warn staging: comedi: cb_pcidas64: fix request_irq() warn ASoC: rt5659: Update MCLK rate in set_sysclk() thermal/core: Add NULL pointer check before using cooling device stats locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling ext4: do not iput inode under running transaction in ext4_rename() net: mvpp2: fix interrupt mask/unmask skip condition flow_dissector: fix TTL and TOS dissection on IPv4 fragments can: dev: move driver related infrastructure into separate subdir net: introduce CAN specific pointer in the struct net_device can: tcan4x5x: fix max register value brcmfmac: clear EAP/association status bits on linkdown events ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr() net: ethernet: aquantia: Handle error cleanup of start on open appletalk: Fix skb allocation size in loopback case net: wan/lmc: unregister device when no matching device is found bpf: Remove MTU check in __bpf_skb_max_len ALSA: usb-audio: Apply sample rate quirk to Logitech Connect ALSA: hda: Re-add dropped snd_poewr_change_state() calls ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks ALSA: hda/realtek: fix a determine_headset_type issue for a Dell AIO ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook xtensa: move coprocessor_flush to the .text section PM: runtime: Fix race getting/putting suppliers at probe PM: runtime: Fix ordering in pm_runtime_get_suppliers() tracing: Fix stack trace event size mm: fix race by making init_zero_pfn() early_initcall drm/amdgpu: fix offset calculation in amdgpu_vm_bo_clear_mappings() drm/amdgpu: check alignment on CPU page for bo map reiserfs: update reiserfs_xattrs_initialized() condition vfio/nvlink: Add missing SPAPR_TCE_IOMMU depends pinctrl: rockchip: fix restore error in resume extcon: Add stubs for extcon_register_notifier_all() functions extcon: Fix error handling in extcon_dev_register firewire: nosy: Fix a use-after-free bug in nosy_ioctl() usbip: vhci_hcd fix shift out-of-bounds in vhci_hub_control() USB: quirks: ignore remote wake-up on Fibocom L850-GL LTE modem usb: musb: Fix suspend with devices connected for a64 usb: xhci-mtk: fix broken streams issue on 0.96 xHCI cdc-acm: fix BREAK rx code path adding necessary calls USB: cdc-acm: untangle a circular dependency between callback and softint USB: cdc-acm: downgrade message to debug USB: cdc-acm: fix double free on probe failure USB: cdc-acm: fix use-after-free after probe failure usb: gadget: udc: amd5536udc_pci fix null-ptr-dereference usb: dwc2: Fix HPRT0.PrtSusp bit setting for HiKey 960 board. usb: dwc2: Prevent core suspend when port connection flag is 0 staging: rtl8192e: Fix incorrect source in memcpy() staging: rtl8192e: Change state information from u16 to u8 drivers: video: fbcon: fix NULL dereference in fbcon_cursor() Linux 5.4.110 UBUNTU: upstream stable to v5.4.110 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed **
[Kernel-packages] [Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
** Changed in: linux (Ubuntu Focal) 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/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat sambashare scanner sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET61W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS00T00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET61W(1.39):bd04/20/2020:svnLENOVO:pn20HMS00T00:pvrThinkPadX270:rvnLENOVO:rn20HMS00T00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS00T00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://
[Kernel-packages] [Bug 1922387] Re: BUG: kernel NULL pointer dereference, address: 0000000000000050
I did some manual ubuntu_kernel_selftests ftrace testing on the 5.4.0-71.79-generic kernel. I was able to replicate the panic, but not on every run, but even on runs with no panic dmesg would report several soft lockups. After removing the MOFED dkms, I was unable to replicate a panic or any of the soft lockups previously seen. Currently I don't have evidence as to which MOFED module is potentially triggering the 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/1922387 Title: BUG: kernel NULL pointer dereference, address: 0050 Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: I observed the following kernel panic with the 5.4.0-71.79-generic kernel while running kernel selftests: blanka login: [ 1671.958400] mmiotrace: Error taking CPU253 down: -28 [ 1672.118199] mmiotrace: Error taking CPU254 down: -28 [ 1672.230306] mmiotrace: Error taking CPU255 down: -28 [ 2503.359753] BUG: kernel NULL pointer dereference, address: 0050 [ 2503.367527] #PF: supervisor read access in kernel mode [ 2503.373257] #PF: error_code(0x) - not-present page [ 2503.378989] PGD 0 P4D 0 [ 2503.381812] Oops: [#1] SMP NOPTI [ 2503.385896] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE 5.4.0-71-generic #79-Ubuntu [ 2503.395795] Hardware name: NVIDIA DGXA100 920-23687-2530-000/DGXA100, BIOS 0.33 01/19/2021 [ 2503.405027] RIP: 0010:trace_event_raw_event_wbt_timer+0x6f/0x100 [ 2503.411728] Code: 59 80 e5 02 0f 85 8f 00 00 00 4c 89 e6 ba 34 00 00 00 48 8d 7d a0 e8 d0 a4 ca ff 49 89 c4 48 85 c0 74 37 49 8b 87 b8 03 00 00 <48> 8b 70 50 48 85 f6 74 45 49 8d 7c 24 08 ba 20 00 00 00 e8 59 91 [ 2503.432683] RSP: 0018:a8d6c0003d90 EFLAGS: 00010286 [ 2503.438513] RAX: RBX: RCX: 8100 [ 2503.446474] RDX: 9968a228f418 RSI: 0100 RDI: 9968a228f414 [ 2503.454436] RBP: a8d6c0003df8 R08: 9968a228f414 R09: 0100 [ 2503.462394] R10: 0007 R11: 0007 R12: 9968a228f418 [ 2503.470353] R13: fffa R14: 0003 R15: 9a686f9b3000 [ 2503.478316] FS: () GS:99690cc0() knlGS: [ 2503.487342] CS: 0010 DS: ES: CR0: 80050033 [ 2503.493752] CR2: 0050 CR3: 007e08ad6000 CR4: 00340ef0 [ 2503.501712] Call Trace: [ 2503.504438] [ 2503.506682] wb_timer_fn+0x1d6/0x3c0 [ 2503.510672] ? blk_stat_free_callback_rcu+0x30/0x30 [ 2503.516112] blk_stat_timer_fn+0x134/0x140 [ 2503.520683] call_timer_fn+0x32/0x130 [ 2503.524768] __run_timers.part.0+0x180/0x280 [ 2503.529535] ? trace_event_raw_event_softirq+0x5d/0xa0 [ 2503.535267] run_timer_softirq+0x2a/0x50 [ 2503.539644] __do_softirq+0xe1/0x2d6 [ 2503.543629] irq_exit+0xae/0xb0 [ 2503.547132] smp_apic_timer_interrupt+0x7b/0x140 [ 2503.552280] apic_timer_interrupt+0xf/0x20 [ 2503.556848] [ 2503.559187] RIP: 0010:native_safe_halt+0xe/0x10 [ 2503.564239] Code: 7b ff ff ff eb bd 90 90 90 90 90 90 e9 07 00 00 00 0f 00 2d 66 dd 52 00 f4 c3 66 90 e9 07 00 00 00 0f 00 2d 56 dd 52 00 fb f4 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 e8 cd cd 63 ff 65 [ 2503.585191] RSP: 0018:94803e18 EFLAGS: 0202 ORIG_RAX: ff13 [ 2503.593635] RAX: 0001e7c0 RBX: 996849080de8 RCX: 00149022 [ 2503.601595] RDX: 00149022 RSI: RDI: 948c5ba0 [ 2503.609556] RBP: 94803e38 R08: 02a8 R09: 9968a228f000 [ 2503.617516] R10: R11: 0002 R12: [ 2503.625475] R13: R14: R15: [ 2503.633440] ? default_idle+0x20/0x140 [ 2503.637623] arch_cpu_idle+0x15/0x20 [ 2503.641608] default_idle_call+0x23/0x30 [ 2503.645984] do_idle+0x1fb/0x270 [ 2503.649583] cpu_startup_entry+0x20/0x30 [ 2503.653960] rest_init+0xae/0xb0 [ 2503.657563] arch_call_rest_init+0xe/0x1b [ 2503.662025] start_kernel+0x549/0x56a [ 2503.666108] x86_64_start_reservations+0x24/0x26 [ 2503.671258] x86_64_start_kernel+0x75/0x79 [ 2503.675828] secondary_startup_64+0xa4/0xb0 [ 2503.680493] Modules linked in: sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat iptable_nat xt_nat nf_nat algif_hash af_alg ip6table_filter xt_conntrack nf_conntrack nf_defrag_ipv4 ip6_tables nf_defrag_ipv6 ip_vti ip6_vti fou6 sit ipip tunnel4 geneve act_mirred cls_basic esp6 authenc echainiv iptable_filter xt_policy bpfilter veth esp4_offload esp4 xfrm_user xfrm_algo macsec fou vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mr
[Kernel-packages] [Bug 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat sambashare scanner sudo vboxusers _MarkForUpload: False dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET61W (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS00T00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET61W(1.39):bd04/20/2020:svnLENOVO:pn20HMS00T00:pvrThinkPadX270:rvnLENOVO:rn20HMS00T00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS00T00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys
[Kernel-packages] [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** No longer affects: qemu (Ubuntu Hirsute) ** No longer affects: qemu (Ubuntu) ** No longer affects: glibc (Ubuntu Hirsute) ** No longer affects: glibc (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/1920784 Title: qemu-system-ppc64le fails with kvm acceleration Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: (Suspected glibc issue!) qemu-system-ppc64(le) fails when invoked with kvm acceleration with error "illegal instruction" > qemu-system-ppc64(le) -M pseries,accel=kvm Illegal instruction (core dumped) In dmesg: Facility 'SCV' unavailable (12), exception at 0x7624f8134c0c, MSR=9280f033 Version-Release number of selected component (if applicable): qemu 5.2.0 Linux kernel 5.11 glibc 2.33 all latest updates as of submitting the bug report How reproducible: Always Steps to Reproduce: 1. Run qemu with kvm acceleration Actual results: Illegal instruction Expected results: Normal VM execution Additional info: The machine is a Raptor Talos II Lite with a Sforza V1 8-core, but was also observed on a Raptor Blackbird with the same processor. This was also observed on Fedora 34 beta, which uses glibc 2.33 Also tested on ArchPOWER (unofficial port of Arch Linux for ppc64le) with glibc 2.33 Fedora 33 and Ubuntu 20.10, both using glibc 2.32 do not have this issue, and downgrading the Linux kernel from 5.11 to 5.4 LTS on ArchPOWER solved the problem. Kernel 5.9 and 5.10 have the same issue when combined with glibc2.33 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qemu-system 1:5.2+dfsg-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' ApportVersion: 2.20.11-0ubuntu60 Architecture: ppc64el CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Mar 22 14:48:39 2021 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha ppc64el (20210321) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND ProcKernelCmdLine: root=UUID=f3d03315-0944-4a02-9c87-09c00eba9fa1 ro ProcLoadAvg: 1.20 0.73 0.46 1/1054 6071 ProcSwaps: Filename TypeSizeUsed Priority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.11.0-11-generic (buildd@bos02-ppc64el-002) (gcc (Ubuntu 10.2.1-20ubuntu1) 10.2.1 20210220, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #12-Ubuntu SMP Mon Mar 1 19:26:20 UTC 2021 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 acpidump: cpu_cores: Number of cores present = 8 cpu_coreson: Number of cores online = 8 cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1920784/+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 1921498] Re: [UBUNUT 21.04] s390/vtime: fix increased steal time accounting
The commit "s390/vtime: fix increased steal time accounting" landed in hirsute
as c64e48d4ace3 in kernel Ubuntu-5.11.0-14 and this kernel is in hirsute's
release pocket:
linux-generic | 5.11.0.14.15 | hirsute | s390x
Hence closing the hirsute entry as Fix Released.
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921498
Title:
[UBUNUT 21.04] s390/vtime: fix increased steal time accounting
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* The reported steal time on s390x is erroneously increasing and
therefore broken.
* This problem got introduced with commit 152e9b8676c6e
("s390/vtime: steal time exponential moving average") - upstream with v5.1
[Fix]
* d54cb7d54877d529bc1e0e1f47a3dd082f73add3 d54cb7d54877 "s390/vtime:
fix increased steal time accounting"
[Test Case]
* An IBM Z or LinuxONE systems, installed with Ubuntu Server 20.04,
20.10 and 21.04 on LPAR, are needed.
* The system needs to be configured as KVM host with one or more KVM
guests.
* Now put significant workload on the guest(s), so that the hypervisor starts
to 'steal time'.
This can be best forced by having only very limited CPU resources for the
hypervisor itself.
* Start monitoring the steal time, that is reported at /proc/stat,
but can be more easily verified with tools like vmstat or even top.
* If the steal time starts ever growing (exponentially), the situation
is broken.
* In case the steal time stays relatively constant,
or grows only very limited after a ramp up phase of some minutes,
or just oscillates around a certain value, a fixed/patched kernel is in use.
[Regression Potential]
* The patch only changes the single line that calculates:
account_steal_time
* In case the account_steal_time calculation is still broken after the
modification,
the steal time is just again not reported correctly on s390x,
but maybe in a different way (rather than exponentially growing).
* But it will not further harm virtualization on s390x systems.
* The modification is very limited with that one line change.
* The commit got upstream accepted with 5.12-rc4.
[Other]
* Since the patch is needed for kernel higher than 5.1 and got upstream
accepted with 5.12-rc4,
hirsute, groovy and focal are affected.
* The upstream commit can be cleanly cherry-picked from all three affected
Ubuntu releases.
__
Description: s390/vtime: fix increased steal time accounting
Symptom: Increased steal time values.
Problem: Commit 152e9b8676c6e ("s390/vtime: steal time exponential
moving average") inadvertently changed the input value for
account_steal_time() from "cputime_to_nsecs(steal)" to just
"steal", resulting in broken increased steal time accounting.
Solution: Fix this by changing it back to "cputime_to_nsecs(steal)".
Reproduction: -
Upstream-ID: d54cb7d54877d529bc1e0e1f47a3dd082f73add3
Stable tagged : kernel 5.1.
Therefore only to be applyable for focal, groovy, hirsuite.
Due to stable tag integration , only for integration checking..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921498/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
** No longer affects: debianutils (Ubuntu) ** No longer affects: debianutils (Ubuntu Hirsute) ** No longer affects: debianutils (Ubuntu Focal) ** No longer affects: debianutils (Ubuntu Bionic) -- 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/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: New Status in linux-base source package in Focal: New Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+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 1920571] Re: Groovy update: upstream stable patchset 2021-03-19
@Kamal, I am dropping "cifs: Set CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath." from the set due to bug #1923670 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920571 Title: Groovy update: upstream stable patchset 2021-03-19 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: 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: upstream stable patchset 2021-03-19 Ported from the following upstream stable releases: v5.4.98, v5.10.16, v5.4.99, v5.10.17, v5.4.100, v5.10.18, v5.4.101, v5.10.19 from git://git.kernel.org/ af_key: relax availability checks for skb size calculation regulator: core: avoid regulator_resolve_supply() race condition ASoC: wm_adsp: Fix control name parsing for multi-fw mac80211: 160MHz with extended NSS BW in CSA ASoC: Intel: Skylake: Zero snd_ctl_elem_value chtls: Fix potential resource leak pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process() pNFS/NFSv4: Improve rejection of out-of-order layouts ALSA: hda: intel-dsp-config: add PCI id for TGL-H ASoC: ak4458: correct reset polarity ASoC: Intel: sof_sdw: set proper flags for Dell TGL-H SKU 0A5E iwlwifi: mvm: skip power command when unbinding vif during CSA iwlwifi: mvm: take mutex for calling iwl_mvm_get_sync_time() iwlwifi: pcie: add a NULL check in iwl_pcie_txq_unmap iwlwifi: pcie: fix context info memory leak iwlwifi: mvm: invalidate IDs of internal stations at mvm start iwlwifi: pcie: add rules to match Qu with Hr2 iwlwifi: mvm: guard against device removal in reprobe SUNRPC: Move simple_get_bytes and simple_get_netobj into private header SUNRPC: Handle 0 length opaque XDR object data properly i2c: mediatek: Move suspend and resume handling to NOIRQ phase blk-cgroup: Use cond_resched() when destroy blkgs regulator: Fix lockdep warning resolving supplies bpf: Fix verifier jmp32 pruning decision logic bpf: Fix 32 bit src register truncation on div/mod bpf: Fix verifier jsgt branch analysis on max bound drm/i915: Fix ICL MG PHY vswing handling drm/i915: Skip vswing programming for TBT nilfs2: make splice write available again squashfs: avoid out of bounds writes in decompressors squashfs: add more sanity checks in id lookup squashfs: add more sanity checks in inode lookup squashfs: add more sanity checks in xattr id lookup UBUNTU: upstream stable to v5.4.98, v5.10.16 gpio: mxs: GPIO_MXS should not default to y unconditionally gpio: ep93xx: fix BUG_ON port F usage gpio: ep93xx: Fix single irqchip with multi gpiochips tracing: Do not count ftrace events in top level enable output tracing: Check length before giving out the filter buffer drm/i915: Fix overlay frontbuffer tracking arm/xen: Don't probe xenbus as part of an early initcall cgroup: fix psi monitor for root cgroup drm/i915/tgl+: Make sure TypeC FIA is powered up when initializing it drm/dp_mst: Don't report ports connected if nothing is attached to them dmaengine: move channel device_node deletion to driver soc: ti: omap-prm: Fix boot time errors for rst_map_012 bits 0 and 1 arm64: dts: rockchip: Fix PCIe DT properties on rk3399 arm64: dts: qcom: sdm845: Reserve LPASS clocks in gcc ARM: OMAP2+: Fix suspcious RCU usage splats for omap_enter_idle_coupled arm64: dts: rockchip: remove interrupt-names property from rk3399 vdec node platform/x86: hp-wmi: Disable tablet-mode reporting by default ovl: perform vfs_getxattr() with mounter creds cap: fix conversions on getxattr ovl: skip getxattr of security labels scsi: lpfc: Fix EEH encountering oops with NVMe traffic x86/split_lock: Enable the split lock feature on Sapphire Rapids and Alder Lake CPUs x86/split_lock: Enable the split lock feature on another Alder Lake CPU nvme-pci: ignore the subsysem NQN on Phison E16 drm/amd/display: Fix DPCD translation for LTTPR AUX_RD_INTERVAL drm/amd/display: Add more Clock Sources to DCN2.1 drm/amd/display: Release DSC before acquiring drm/amd/display: Fix dc_sink kref count in emulated_link_detect drm/amd/display: Free atomic state after drm_atomic_commit drm/amd/display: Decrement refcount of dc_sink before reassignment riscv: virt_addr_valid must check the address belongs to linear mapping ARM: dts: lpc32xx: Rev
[Kernel-packages] [Bug 1922800] Re: Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and subsequent versions
Daniel, just a heads-up: it fails for all Nvidia drivers, hence I marked "nvidia-graphics-drivers" instead of the -460. Cheers, Guilherme -- 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/1922800 Title: Nvidia proprietary DKMS drivers cannot build in linux-kvm 5.8 and subsequent versions Status in linux-kvm package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in linux-kvm source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: New Bug description: After an ADT/DKMS modification (see https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051) binary DKMS packages without -dkms in the name started to get tested on ADT run. This exposed a problem in the Nvidia proprietary DKMS modules for linux-kvm build: if we don't have CONFIG_X86_PAT set, the Nvidia drivers (all versions) set NV_ENABLE_BUILTIN_PAT_SUPPORT to 1 and attempt to build the file nvidia/nv-pat.c - two functions there make use of __flush_tlb() exported symbol. But, after kernel v5.8, this symbol is not exported anymore [0][1], not even flush_tlb_local() is available. For the time being, we ADT-hinted linux-kvm package, but the driver requires modifications, in order to fix that. [0] http://git.kernel.org/linus/2faf153bb734 [1] http://git.kernel.org/linus/bfe3d8f6313d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1922800/+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 1922403] Re: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Hirsute) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** 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 Focal) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+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 1923859] Re: Remove an unused file
** Description changed: + [Impact] + debian.aws-20.10/scripts/helpers/copy-files is unused and can be - confusing. + confusing, especially for derivatives. + + The eye of Sauron (in the form of apw) has cast its baleful glare on + this bit of cruft. + + [Test Plan] + + Perform a successful build + + [Where problems could occur] + + Any regressions will be noted at build time. + + [Other Info] + + None -- 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/1923859 Title: Remove an unused file Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: In Progress Bug description: [Impact] debian.aws-20.10/scripts/helpers/copy-files is unused and can be confusing, especially for derivatives. The eye of Sauron (in the form of apw) has cast its baleful glare on this bit of cruft. [Test Plan] Perform a successful build [Where problems could occur] Any regressions will be noted at build time. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923859/+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 1923859] [NEW] Remove an unused file
Public bug reported: [Impact] debian.aws-20.10/scripts/helpers/copy-files is unused and can be confusing, especially for derivatives. The eye of Sauron (in the form of apw) has cast its baleful glare on this bit of cruft. [Test Plan] Perform a successful build [Where problems could occur] Any regressions will be noted at build time. [Other Info] None ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Focal) Importance: Low Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Tags: bot-stop-nagging ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Tags added: bot-stop-nagging ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923859 Title: Remove an unused file Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-aws source package in Focal: In Progress Bug description: [Impact] debian.aws-20.10/scripts/helpers/copy-files is unused and can be confusing, especially for derivatives. The eye of Sauron (in the form of apw) has cast its baleful glare on this bit of cruft. [Test Plan] Perform a successful build [Where problems could occur] Any regressions will be noted at build time. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923859/+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 1923670] Re: CIFS DFS entries not accessible with 5.4.0-71.74-generic
After figuring out the correct upstream repo for the ubuntu kernel repo (not https://git.launchpad.net/ubuntu/+source/linux but https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal) I replicated your command $ git log --grep 'cifs' Ubuntu-5.4.0-70.78..Ubuntu-5.4.0-71.79 and the most recent commit (f28b34becc655b6139216a72d12378001faa5784) caught my attention. Indeed it was reverted upstream 2 days ago [1]. I think those are the related discussions on linux-kernel [2] and debian-user [3]. The last one describes the same scenario. 1: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.112 2: https://www.mail-archive.com/search?l=linux- ker...@vger.kernel.org&q=subject:%22Re%5C%3A+%5C%5BEXTERNAL%5C%5D+Re%5C%3A+%5C%5BPATCH+4.19+013%5C%2F247%5C%5D+cifs%5C%3A+Set+CIFS_MOUNT_USE_PREFIX_PATH+flag+on+setting+cifs_sb%5C-%3Eprepath.%22&o=newest 3: https://lists.debian.org/debian-user/2021/04/msg00062.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923670 Title: CIFS DFS entries not accessible with 5.4.0-71.74-generic Status in linux package in Ubuntu: Confirmed Bug description: When booting 5.4.0-71-generic I can not access DFS entries anymore, with 5.4.0-70-generic this still works. Some details: fstab entry: //example.com/public /home/user/remotecifs noauto,vers=default,noserverino,users,_netdev,user=remote_user,domain=example.com 00 shell session ~$ mount /home/user/remote Password for remote_user@//example.com/public: ~$ ls /home/user/remote/dfs-folder dfs-subfolder dfs-entry ~$ ls /home/user/remote/dfs-folder/dfs-entry ls: cannot access '/home/user/remote/dfs-folder/dfs-entry': No such file or directory dmesg excerpt [ 1219.568778] CIFS: Attempting to mount //DC01.example.com/Public/dfs-folder/dfs-entry [ 1219.584975] FS-Cache: Duplicate cookie detected [ 1219.584986] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.584990] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.584993] FS-Cache: O-key=[6] '5075626c6963' [ 1219.585001] FS-Cache: N-cookie c=a0608786 [p=f4725c61 fl=2 nc=0 na=1] [ 1219.585004] FS-Cache: N-cookie d=a11c1428 n=901f6a53 [ 1219.585007] FS-Cache: N-key=[6] '5075626c6963' [ 1219.725834] FS-Cache: Duplicate cookie detected [ 1219.725847] FS-Cache: O-cookie c=6e995395 [p=f4725c61 fl=222 nc=0 na=1] [ 1219.725851] FS-Cache: O-cookie d=a11c1428 n=71ab21ba [ 1219.725854] FS-Cache: O-key=[6] '5075626c6963' [ 1219.725864] FS-Cache: N-cookie c=0509709f [p=f4725c61 fl=2 nc=0 na=1] [ 1219.725868] FS-Cache: N-cookie d=a11c1428 n=556f158b [ 1219.725870] FS-Cache: N-key=[6] '5075626c6963' [ 1220.216524] CIFS VFS: cifs_read_super: get root inode failed The dmesg from 5.4.0-70-generic does not have the line CIFS VFS: cifs_read_super: get root inode failed ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release: ~$ lsb_release -rd Description:KDE neon User Edition 5.21 Release:20.04 20.04 ~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.71.74 Candidate: 5.4.0.71.74 Version table: *** 5.4.0.71.74 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dirk 2946 F pulseaudio /dev/snd/controlC1: dirk 2946 F pulseaudio /dev/snd/controlC0: dirk 2946 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: KDE neon 20.04 InstallationDate: Installed on 2017-07-27 (1356 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20170614-00:52 MachineType: LENOVO 20HMS00T00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic root=/dev/mapper/vg00-lv_root ro intel_iommu=off ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-71-generic N/A linux-backports-modules-5.4.0-71-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.4.0-71-generic x86_64 UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist. UpgradeStatus: Upgraded to focal on 2020-11-22 (142 days ago) UserGroups: adm cdrom davfs2 dialout dip kvm libvirt lpadmin plugdev roccat
[Kernel-packages] [Bug 1923846] [NEW] Kernel panic
Public bug reported: I use Hyper-V and created VM with "Generation 2", I cannot boot Ubuntu Hirsute Hippo Live CD, it gives me kernel panic, I tried it when there were included 5.11.0-13 and 5.11.0-14 kernels - same result, when there was 5.11.0-11 and older it was fine. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel panic screenshot" https://bugs.launchpad.net/bugs/1923846/+attachment/5487827/+files/Screenshot%20%28550%29.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1923846 Title: Kernel panic Status in linux-signed package in Ubuntu: New Bug description: I use Hyper-V and created VM with "Generation 2", I cannot boot Ubuntu Hirsute Hippo Live CD, it gives me kernel panic, I tried it when there were included 5.11.0-13 and 5.11.0-14 kernels - same result, when there was 5.11.0-11 and older it was fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1923846/+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 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Attachment added: "install.log" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487811/+files/install.log ** Description changed: - evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream - updates for 5.11 proved problematic, and a working set of updates became - available in the upstream project only recently. Unfortunately these - updates are difficult to backport due to upstream changes, and if they - are backported the kernel team has no access to hardware to confirm that - the backports function as intended. Therefore the safest course of - action seems to be to move forward to the latest upstream evdi release - plus they fixes for 5.11 from git, which has been tested by a number of - evdi users already. + evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as + it will fail to build. Upstream updates for 5.11 proved problematic, and + a working set of updates became available in the upstream project only + recently. Unfortunately these updates are difficult to backport due to + upstream changes, and if they are backported the kernel team has no + access to hardware to confirm that the backports function as intended. + Therefore the safest course of action seems to be to move forward to the + latest upstream evdi release plus they fixes for 5.11 from git, which + has been tested by a number of evdi users already. ** Changed in: evdi (Ubuntu) Importance: Undecided => High ** Changed in: evdi (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as it will fail to build. Upstream updates for 5.11 proved problematic, and a working set of updates became available in the upstream project only recently. Unfortunately these updates are difficult to backport due to upstream changes, and if they are backported the kernel team has no access to hardware to confirm that the backports function as intended. Therefore the safest course of action seems to be to move forward to the latest upstream evdi release plus they fixes for 5.11 from git, which has been tested by a number of evdi users already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+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 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Attachment added: "build.log" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487810/+files/build.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as it will fail to build. Upstream updates for 5.11 proved problematic, and a working set of updates became available in the upstream project only recently. Unfortunately these updates are difficult to backport due to upstream changes, and if they are backported the kernel team has no access to hardware to confirm that the backports function as intended. Therefore the safest course of action seems to be to move forward to the latest upstream evdi release plus they fixes for 5.11 from git, which has been tested by a number of evdi users already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+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 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
The project does not maintain a changelog, so instead attaching the git commit history between the v1.7.0 and v1.9.1 tags. ** Attachment added: "changelog.txt" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487808/+files/changelog.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/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as it will fail to build. Upstream updates for 5.11 proved problematic, and a working set of updates became available in the upstream project only recently. Unfortunately these updates are difficult to backport due to upstream changes, and if they are backported the kernel team has no access to hardware to confirm that the backports function as intended. Therefore the safest course of action seems to be to move forward to the latest upstream evdi release plus they fixes for 5.11 from git, which has been tested by a number of evdi users already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
This bug was fixed in the package linux-base - 4.5ubuntu5 --- linux-base (4.5ubuntu5) hirsute; urgency=medium * Add kernel postinst hook to update initrd softlinks to match the kernel version targets (LP: #1877088). -- Stefan Bader Wed, 03 Feb 2021 16:05:08 +0100 ** Changed in: linux-base (Ubuntu Hirsute) Status: In Progress => Fix Released -- 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/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: In Progress Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: Fix Released Status in debianutils source package in Bionic: New Status in linux-base source package in Bionic: New Status in debianutils source package in Focal: New Status in linux-base source package in Focal: New Status in debianutils source package in Hirsute: New Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/18770
[Kernel-packages] [Bug 1918134] Re: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key Status in linux package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: To allow decoupling of nvidia-graphics-drivers- streams and versions from the underlying kernel versions we wish to be able to sign new kernel modules into an existing kernel after the fact. Under bug #1898716 we added support for an Ubuntu Modules signing key certificate. Rebuild the LRM package to make use of this new signature. This involves splitting the LRM package into three. linux-restricted- modules first builds the nvidia-graphics-drivers-* we require signed. linux-restricted-generate then consumes the .o's produced in that build and forms a signing custom binary upload for this. linux- restricted-signatures then consumes the signing result from the LRG upload and expresses clean redistributible signatures which are consumed by LRM at installation time. LRG must be embargoed as it (necessarily) generates fully formed .ko files for signing. Additional process is added to the kernel build life-cycle to handle the privacy requirements of the LRG/LRS interaction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918134/+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 1918134] Re: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1918134 Title: LRMv4: switch to signing nvidia modules via the Ubuntu Modules signing key Status in linux package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: To allow decoupling of nvidia-graphics-drivers- streams and versions from the underlying kernel versions we wish to be able to sign new kernel modules into an existing kernel after the fact. Under bug #1898716 we added support for an Ubuntu Modules signing key certificate. Rebuild the LRM package to make use of this new signature. This involves splitting the LRM package into three. linux-restricted- modules first builds the nvidia-graphics-drivers-* we require signed. linux-restricted-generate then consumes the .o's produced in that build and forms a signing custom binary upload for this. linux- restricted-signatures then consumes the signing result from the LRG upload and expresses clean redistributible signatures which are consumed by LRM at installation time. LRG must be embargoed as it (necessarily) generates fully formed .ko files for signing. Additional process is added to the kernel build life-cycle to handle the privacy requirements of the LRG/LRS interaction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918134/+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 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Summary changed: - [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 + [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 ** Description changed: - This is a scripted bug report about ADT failures while running evdi - tests for linux/5.11.0-14.15 on hirsute. Whether this is caused by the - dep8 tests of the tested source or the kernel has yet to be determined. - - Testing failed on: + evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream + updates for 5.11 proved problematic, and a working set of updates became + available in the upstream project only recently. Unfortunately these + updates are difficult to backport due to upstream changes, and if they + are backported the kernel team has no access to hardware to confirm that + the backports function as intended. Therefore the safest course of + action seems to be to move forward to the latest upstream evdi release + plus they fixes for 5.11 from git, which has been tested by a number of + evdi users 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/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream updates for 5.11 proved problematic, and a working set of updates became available in the upstream project only recently. Unfortunately these updates are difficult to backport due to upstream changes, and if they are backported the kernel team has no access to hardware to confirm that the backports function as intended. Therefore the safest course of action seems to be to move forward to the latest upstream evdi release plus they fixes for 5.11 from git, which has been tested by a number of evdi users already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.56-0ubuntu0.20.10.1 --- nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. -- Alberto Milone Thu, 25 Feb 2021 16:15:13 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.56-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. -- Alberto Milone Thu, 25 Feb 2021 16:17:06 +0100 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1915935] Re: Switching between NVIDIA drivers fails
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.56-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-460 (460.56-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. -- Alberto Milone Thu, 25 Feb 2021 16:18:42 +0100 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915935 Title: Switching between NVIDIA drivers fails Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Trying to install nvidia-driver-450-server over nvidia-driver-450 triggers the following error: Unpacking libnvidia-common-450-server (450.102.04-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-e75h80/01-libnvidia-common- 450-server_450.102.04-0ubuntu0.20.04.1_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.102.04-k ey-documentation', which is also in package libnvidia-common-450 450.102.04-0ubu ntu0.20.04.1 ... Unpacking nvidia-driver-450-server (450.102.04-0ubuntu0.20.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1915935/+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 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.56-0ubuntu0.20.10.1 --- nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. -- Alberto Milone Thu, 25 Feb 2021 16:15:13 +0100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.56-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-460 (460.56-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. -- Alberto Milone Thu, 25 Feb 2021 16:17:06 +0100 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
This bug was fixed in the package nvidia-graphics-drivers-460 - 460.56-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-460 (460.56-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. -- Alberto Milone Thu, 25 Feb 2021 16:18:42 +0100 ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Committed Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the
[Kernel-packages] [Bug 1923638] Re: [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Summary changed: - evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15 + [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running evdi tests for linux/5.11.0-14.15 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+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
