[Kernel-packages] [Bug 1953587] [NEW] Fix sanity checker and cleanup metadata
Public bug reported: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. [ Where Problems Could Occur ] None. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New -- 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/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Hirsute: New Status in linux-firmware source package in Impish: New Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953575] [NEW] Update gvnic driver code
Public bug reported: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Description changed: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. + + + [Impact] + Missing functionality from the Google gvnic driver + + + [Test Plan] + Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE + + + [Regression potential] + Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. + + + + List of changes: + + 3712db620c613 gve: DQO: Configure interrupts on device up + a9fd7559a367a gve: Check TX QPL was actually assigned + c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check + f48adc2842b17 gve: DQO: Remove incorrect prefetch + 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API + 56c0904d8491d gve: Propagate error codes to caller + 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() + ea364622fb118 gve: Fix warnings reported for DQO patchset + 8890e8783c6e6 gve: DQO: Add RX path + abfc55f80d423 gve: DQO: Add TX path + ef63867982913 gve: DQO: Add ring allocation and initialization + dc3e0aef11bf0 gve: DQO: Add core netdev features + 873fd9825efd7 gve: Update adminq commands to support DQO queues + 543dc0e670472 gve: Add DQO fields for core data structures + b580730931348 gve: Add dqo descriptors + 74e123d3c62b2 gve: Add support for DQO RX PTYPE map + a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic + 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` + a6b09c93c1735 gve: Introduce a new model for device options + 34d6b75678979 gve: Add support for raw addressing in the tx path + 30b6221596699 Revert "gve: Check TX QPL was actually assigned" + 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset + ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument + 5fc5c482008b5 gve: Move some static functions to a common file + ed1e0daeee1ac gve: Rx Buffer Recycling +
[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
This 5.4.0-92 kernel works fine. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952094 Title: CIFS mount error: iocharset utf8 not found Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: After i apt upgrade from linux-image-5.4.0-89-generic to linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS mount error: iocharset utf8 not found", and i rollback it and it restores. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 20:16 seq crw-rw 1 root audio 116, 33 Nov 24 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-07 (109 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 12/17/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933609] Re: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in
Problem seems to be fixed now. Not sure at what point it stopped being broken but the problem is no longer exhibited on Ubuntu 20.04.3 on a 5.11.0-41-generic kernel with Nouveau xserver-xorg-video-nouveau 1:1.0.16-1 with Gnome 1:3.30+2 and GDM3 3.36.3-0ubuntu.20.04.4 using X11 not wayland. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933609 Title: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Trying to run Ubuntu 20.04 on some Dell workstations with Nvidia Quadro P2200 cards. Getting some odd crashes. If a single monitor is plugged and the workstation is power on you can then log in and plug a second monitor in and locking the screen DOES not crash X/Wayland/nouveau. If you boot the system with both monitors plugged in then logging in and locking the computer will cause X/Wayland/Nouveau to crash and only a reboot will fix it. You can still ssh into the box though. The monitors are connected via DisplayPort. There were no kernel backtraces in the journal when running this bug report. But in other cases there has been nouveau backtraces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 25 16:02:35 2021 InstallationDate: Installed on 2021-06-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
[Expired for linux-azure (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-azure (Ubuntu) Status: Incomplete => Expired -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: Very occasionally systemd panics on reboots of an azure instance. A workaround to this issue is described in comment #20 Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
** Package changed: ubuntu => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.13 (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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12: 91218c293a98 [94104.121862] R13: R14: 91214298e510
[Kernel-packages] [Bug 1953554] [NEW] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
You have been subscribed to a public bug: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12: 91218c293a98 [94104.121862] R13: R14: 91214298e510 R15: 91214298e500 [94104.121869] ? do_dentry_open+0x44/0x370 [94104.121873] vfs_open+0x2d/0x30 [94104.121877] do_open.isra.0+0x205/0x3e0 [94104.121881] path_openat+0x18e/0xc80 [94104.121884] ? do_sys_openat2+0x1/0x310 [94104.121887] ? page_counter_cancel+0x2c/0x70 [94104.121891] do_filp_open+0xa2/0x110 [94104.121895] ? __check_object_size+0x13f/0x150 [94104.121898] ? alloc_fd+0x58/0x190 [94104.121903] do_sys_openat2+0x245/0x310 [94104.121906]
[Kernel-packages] [Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight
Boris, This bug is closed so please open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight Status in linux package in Ubuntu: Expired Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Please remember to follow the instructions in comment #1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953400] Re: shutdown not working from GNOME
Reassigning to the kernel because GNOME has no control over shutdown other than the part where GNOME exits. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953400 Title: shutdown not working from GNOME Status in linux package in Ubuntu: Incomplete Bug description: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953400] [NEW] shutdown not working from GNOME
You have been subscribed to a public bug: Upon using ubuntu 22.04 with latest updates. shutdown via gnome does shutdown but the power light stays on on laptop. So I have to hold the button down for ten seconds. oddly enough shutdown works in terminal correctly. sudo shutdown -h now works ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- shutdown not working from GNOME https://bugs.launchpad.net/bugs/1953400 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953557] 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 1953557 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/1953557 Title: sd card reader runs 100% of time and consumes way too much power Status in linux package in Ubuntu: Incomplete Bug description: When inspecting the systems power usage trough powertop I recognized the sd card reader is running 100% of time and consuming between 8 and 16 W on my laptop despite not being even in use. Powertop prints: 11.5 W100,0% Device USB device: USB2.0-CRW (Generic) This problem was not there when inspecting the power usage a few weeks before. Also when inserting actually a sd-card the power usage shrinks drastically so it is not even seen in powertop on the first places. I have tested it with kernel version 5.13.0-21-generic and 5.13.0-22-generic and the problem exists on both, but it seems a bit worse on 5.13.0-22-generic. I have not configured anything manually there. lsusb prints for the sd-card reader the following: Bus 001 Device 003: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller I am using Ubuntu 21.10 Summary: Ubuntu 21.10 Kernel version: 5.13.0-21-generic and 5.13.0-22-generic tested What I expected to happen: SD card reader *not* eating up all that power when not even in use What happened instead: SD card reader eating up all that power when not even in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953557] Re: sd card reader runs 100% of time and consumes way too much power
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953557 Title: sd card reader runs 100% of time and consumes way too much power Status in linux package in Ubuntu: New Bug description: When inspecting the systems power usage trough powertop I recognized the sd card reader is running 100% of time and consuming between 8 and 16 W on my laptop despite not being even in use. Powertop prints: 11.5 W100,0% Device USB device: USB2.0-CRW (Generic) This problem was not there when inspecting the power usage a few weeks before. Also when inserting actually a sd-card the power usage shrinks drastically so it is not even seen in powertop on the first places. I have tested it with kernel version 5.13.0-21-generic and 5.13.0-22-generic and the problem exists on both, but it seems a bit worse on 5.13.0-22-generic. I have not configured anything manually there. lsusb prints for the sd-card reader the following: Bus 001 Device 003: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller I am using Ubuntu 21.10 Summary: Ubuntu 21.10 Kernel version: 5.13.0-21-generic and 5.13.0-22-generic tested What I expected to happen: SD card reader *not* eating up all that power when not even in use What happened instead: SD card reader eating up all that power when not even in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Tags added: amd oem-priority originate-from-1950332 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953557] [NEW] sd card reader runs 100% of time and consumes way too much power
You have been subscribed to a public bug: When inspecting the systems power usage trough powertop I recognized the sd card reader is running 100% of time and consuming between 8 and 16 W on my laptop despite not being even in use. Powertop prints: 11.5 W100,0% Device USB device: USB2.0-CRW (Generic) This problem was not there when inspecting the power usage a few weeks before. Also when inserting actually a sd-card the power usage shrinks drastically so it is not even seen in powertop on the first places. I have tested it with kernel version 5.13.0-21-generic and 5.13.0-22-generic and the problem exists on both, but it seems a bit worse on 5.13.0-22-generic. I have not configured anything manually there. lsusb prints for the sd-card reader the following: Bus 001 Device 003: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138 Card Reader Controller I am using Ubuntu 21.10 Summary: Ubuntu 21.10 Kernel version: 5.13.0-21-generic and 5.13.0-22-generic tested What I expected to happen: SD card reader *not* eating up all that power when not even in use What happened instead: SD card reader eating up all that power when not even in use ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment impish kernel-bug -- sd card reader runs 100% of time and consumes way too much power https://bugs.launchpad.net/bugs/1953557 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight
This is still a problem at least up until kernel 5.10 if not later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight Status in linux package in Ubuntu: Expired Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Hi, I am facing the same problem in Focal, but not with the onboard TL8111/8168/8411 PCI Express Gigabit Ethernet Controller, but with the USB 3.0 one I have (SIX Electronics Corp. AX88179 Gigabit Ethernet): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_rapl_msr snd_soc_sst_ipc intel_rapl_common 8814au(OE) mei_hdcp snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi intel_pmc_bxt snd_soc_core intel_telemetry_pltdrv intel_punit_ipc snd_compress intel_telemetry_core snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek coretemp snd_hda_codec_generic ac97_bus ledtrig_audio snd_pcm_dmaengine kvm_intel snd_hda_intel kvm snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core snd_hwdep snd_pcm snd_timer ax88179_178a cfg80211 efi_pstore mei_me usbnet ee1004 snd mii soundcore mei mac_hid bridge ip6t_REJECT nf_reject_ipv6 stp llc xt_hl [94104.121696] ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_limit xt_addrtype xt_tcpudp xt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables sch_fq_codel iptable_filter bpfilter msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core aesni_intel crypto_simd i2c_i801 xhci_pci i2c_smbus cryptd r8169 realtek xhci_pci_renesas drm sdhci_pci ahci cqhci sdhci libahci video [94104.121771] CPU: 2 PID: 217952 Comm: PLUGIN[cgroups] Tainted: G OE 5.13.0-22-generic #22~20.04.1-Ubuntu [94104.121775] Hardware name: GIGABYTE MZGLKDP-00/MZGLKDP-00, BIOS F1 12/21/2017 [94104.121777] RIP: 0010:dev_watchdog+0x24f/0x260 [94104.121782] Code: c7 36 fd ff eb ab 4c 89 ff c6 05 60 f1 6e 01 01 e8 86 11 fa ff 44 89 e9 4c 89 fe 48 c7 c7 20 9c ca 89 48 89 c2 e8 38 17 17 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 [94104.121785] RSP: 0018:b515c0138e88 EFLAGS: 00010282 [94104.121788] RAX: RBX: 91214fc45e00 RCX: 0027 [94104.121790] RDX: 0027 RSI: dfff RDI: 9124b05189c8 [94104.121792] RBP: b515c0138eb8 R08: 9124b05189c0 R09: b515c0138c60 [94104.121794] R10: 0001 R11: 0001 R12: 0001 [94104.121795] R13: R14: 912154a7d480 R15: 912154a7d000 [94104.121797] FS: 7f74619e5700() GS:9124b050() knlGS: [94104.121800] CS: 0010 DS: ES: CR0: 80050033 [94104.121802] CR2: 5635dd41b584 CR3: 00020592a000 CR4: 00350ee0 [94104.121805] Call Trace: [94104.121807] [94104.121812] ? pfifo_fast_enqueue+0x150/0x150 [94104.121816] call_timer_fn+0x2c/0x100 [94104.121821] run_timer_softirq+0x3d7/0x480 [94104.121824] ? perf_trace_softirq+0x9d/0xd0 [94104.121829] __do_softirq+0xdd/0x29b [94104.121835] irq_exit_rcu+0xa4/0xb0 [94104.121837] sysvec_apic_timer_interrupt+0x7c/0x90 [94104.121841] [94104.121843] asm_sysvec_apic_timer_interrupt+0x12/0x20 [94104.121846] RIP: 0010:errseq_sample+0x2/0x10 [94104.121850] Code: ff 48 d3 e2 48 f7 d2 48 21 d0 0f 01 ca 48 85 c0 0f 94 c0 0f b6 c0 c3 b8 01 00 00 00 c3 b8 f2 ff ff ff c3 cc cc cc cc cc 8b 07 00 00 00 00 f6 c4 10 0f 44 c2 c3 66 90 8b 17 31 c0 39 16 74 1b [94104.121853] RSP: 0018:b515c29cfb68 EFLAGS: 0286 [94104.121855] RAX: RBX: 91214298e500 RCX: 0002 [94104.121857] RDX: 0001 RSI: 0002 RDI: 91218c293c88 [94104.121859] RBP: b515c29cfba0 R08: 91221987a160 R09: 9121e1e8c180 [94104.121860] R10: 00746174 R11: 8196e1bd R12: 91218c293a98 [94104.121862] R13: R14: 91214298e510 R15: 91214298e500 [94104.121869] ? do_dentry_open+0x44/0x370 [94104.121873] vfs_open+0x2d/0x30 [94104.121877] do_open.isra.0+0x205/0x3e0 [94104.121881] path_openat+0x18e/0xc80 [94104.121884] ? do_sys_openat2+0x1/0x310 [94104.121887] ? page_counter_cancel+0x2c/0x70 [94104.121891] do_filp_open+0xa2/0x110 [94104.121895] ? __check_object_size+0x13f/0x150 [94104.121898] ? alloc_fd+0x58/0x190 [94104.121903] do_sys_openat2+0x245/0x310 [94104.121906] do_sys_open+0x46/0x80
[Kernel-packages] [Bug 1943001] Re: hwe 20.04 kernel 5.11 series hang at graphical login leaving laptop unusable
I'm now using a workaround. I added "module_blacklist=amdgpu" to the kernel command line in /etc/default/grub. The kernel 5.11-series now runs fine, albeit without hybrid amd graphics. I have put the relevant bit of kern.log when amdgpu is not blacklisted in the attachment. ** Attachment added: "Relevant bit of kern.log when amdgpu is not blacklisted" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.11/+bug/1943001/+attachment/5546075/+files/excerpt_kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1943001 Title: hwe 20.04 kernel 5.11 series hang at graphical login leaving laptop unusable Status in linux-meta-hwe-5.11 package in Ubuntu: Confirmed Bug description: The 5.11-series 20.04 HWE kernels are not usable on my laptop. They boot up to graphical login. Then the screen goes black for a second every few seconds. When i try to log in the machine seems to hang and the desktop never appears... The kern.log shows a lot of these errors: "[drm:amdgpu_pci_remove [amdgpu]] *ERROR* Hotplug removal is not supported" Many call traces appear as well, involving [amdgpu] and [ttm]. I have reverted to using the 5.8 kernels. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.34.36~20.04.13 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Sep 8 09:58:49 2021 InstallationDate: Installed on 2014-07-16 (2610 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: linux-meta-hwe-5.11 UpgradeStatus: Upgraded to focal on 2021-02-24 (195 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.11/+bug/1943001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
SRU request submitted to the Ubuntu kernel team mailing list for impish, hirsute and focal: https://lists.ubuntu.com/archives/kernel-team/2021-December/thread.html#126349 Changing status to 'In Progress' for impish, hirsute and focal - jammy patch requested on top. ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. * A fix is needed to enhance problem determination of guest kernel under KVM using DIAG 0x318 instruction execution. * The s390x diagnose 318 instruction sets the control program name code (CPNC) and control program version code (CPVC) to provide useful information regarding the OS during debugging. * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment. [Fix] * In general the following 4 commits are needed: * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug statement for diag 318 CPNC data" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove diag318 reset code" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 0x318 sync and reset" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 318: refactor struct" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch * For jammy, hirsute and impish only the first commit is needed, the others are already in. * For focal all 4 commits are needed, but since they do not apply cleanly on focal, the attached backports need to be used instead. [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host. * And setup an Ubuntu KVM virtual on top. * It can then be observed if the CPNC (diag318 data) has been successfully set by looking at the s390dbf messages for the KVM guest. * The CPNC will always be 4 (denotes Linux environment). * Another way to test this is by running the sync_regs_test under tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the kernel self test suite can trigger this. [Where problems could occur] * The approach here is to provide additional debug and diagnose information on top. * Hence even if the diag318 changes are broken, the existing functionality shouldn't be harmed. * The changes themselves are relatively discernible and mostly introduce new structures. * However, with the functional changes broken code could be introduced (e.g. due to erroneous pointer arithmetic for example) that does not compile or causes crashes. But this is what the test builds are for
[Kernel-packages] [Bug 1953520] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953520 Title: NULL pointer dereference in tcp_splice_read Status in linux package in Ubuntu: Confirmed Bug description: A NULL pointer dereference was discovered in “tcp_splice_read”. The problem was originally found by syzbot, https://syzkaller.appspot.com/bug?id=506214c97a1af183589a4caf4a8fa162a9f56cbd. It is reproduced by the root user in the docker container or host on Ubuntu 18.04.6 LTS with Linux 4.15.0-163-generic. It is reproduced on Ubuntu 18.04.6 LTS with Linux Ubuntu-4.15.0-164.172 also. The bug reproducer is built from https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/506214c97a1af183589a4caf4a8fa162a9f56cbd.c. It doesn't reproduce in Ubuntu 20.04.3 LTS with Linux 5.4.0-91-generic and Linux mainline v5.16-rc4. Mainline commit 07603b230895 (ChangeLog-5.1) fixes issue of propagate file from SMC to TCP socket. There are steps to reproduce in the Docker container: --- docker pull ubuntu docker run -ti ubuntu bash apt update apt install gcc wget wget https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/506214c97a1af183589a4caf4a8fa162a9f56cbd.c gcc ./506214c97a1af183589a4caf4a8fa162a9f56cbd.c -static -pthread -o 506214c97a1af183589a4caf4a8fa162a9f56cbd ./506214c97a1af183589a4caf4a8fa162a9f56cbd The kernel crash contains as a result: root@2d6b356e151a:/# ./506214c97a1af183589a4caf4a8fa162a9f56cbd BUG: unable to handle kernel NULL pointer dereference at 0041 IP: tcp_splice_read+0x5f/0x2b0 PGD 800133bd3067 P4D 800133bd3067 PUD 12e34b067 PMD 0 Oops: [#1] SMP PTI Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: smc veth xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack br_netfilter bridge t sysimgblt aesni_intel fb_sys_fops aes_x86_64 crypto_simd glue_helper cryptd psmouse drm floppy e1000 virtio_blk pata_acpi i2c_piix4 CPU: 1 PID: 4601 Comm: 506214c97a1af18 Not tainted 4.15.0-163-generic #171-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:tcp_splice_read+0x5f/0x2b0 RSP: 0018:b50cc381fdb0 EFLAGS: 00010246 RAX: RBX: 9079f86952c0 RCX: 0001 RDX: RSI: fe01 RDI: 95e523a0 RBP: b50cc381fe20 R08: 0002 R09: c096e2c0 R10: R11: R12: 9079f1af7c40 R13: ffe3 R14: 9079edeebbd8 R15: 0001 FS: 01a56880() GS:9079ffd0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0041 CR3: 0001309b2001 CR4: 00360ee0 Call Trace: smc_splice_read+0x96/0xa0 [smc] sock_splice_read+0x25/0x30 do_splice_to+0x79/0x90 SyS_splice+0x6dd/0x730 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-163-generic 4.15.0-163.171 ProcVersionSignature: Ubuntu 4.15.0-163.171-generic 4.15.18 Uname: Linux 4.15.0-163-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 15:27 seq crw-rw 1 root audio 116, 33 Dec 7 15:27 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.27 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: Date: Tue Dec 7 15:28:46 2021 InstallationDate: Installed on 2021-11-29 (7 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochsdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-163-generic root=UUID=8688c2d4-18cc-4c67-b9a9-dc3d4f4ed3f2 ro console=ttyS0 oops=panic panic=86400 ftrace_dump_on_oops=orig_cpu slub_debug=FZ maybe-ubiquity crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-4.15.0-163-generic N/A linux-backports-modules-4.15.0-163-generic N/A
[Kernel-packages] [Bug 1953514] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953514 Title: BUG_ON(!PagePrivate(page)) Status in linux package in Ubuntu: Confirmed Bug description: А “!PagePrivate(page)” assertion fail was discovered in “ext4_writepage”. The problem was originally found by syzbot, https://syzkaller.appspot.com/bug?id=ae0125a57674f57b675fad8f1440eb2be4790fba. It is reproduced by the root user in the docker container or host on Ubuntu 20.04.3 LTS with Linux 5.4.0-91-generic. The bug reproducer is built from https://raw.githubusercontent.com/dvyukov/syzkaller- repros/master/linux/ae0125a57674f57b675fad8f1440eb2be4790fba.c. It reproduces in Ubuntu 18.04.6 LTS with Linux 4.15.0-163-generic and Ubuntu 20.04.3 LTS with Linux mainline v5.16-rc4 also. There are steps to reproduce in the Docker container: --- docker pull ubuntu docker run -ti ubuntu bash apt update apt install gcc wget wget https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/ae0125a57674f57b675fad8f1440eb2be4790fba.c gcc ./ae0125a57674f57b675fad8f1440eb2be4790fba.c -static -pthread -o ae0125a57674f57b675fad8f1440eb2be4790fba ./ae0125a57674f57b675fad8f1440eb2be4790fba The kernel crash contains as a result: kernel BUG at fs/ext4/inode.c:2163! invalid opcode: [#1] SMP PTI CPU: 1 PID: 280 Comm: jbd2/vda2-8 Kdump: loaded Tainted: GW 5.4.0-91-generic #102-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:ext4_writepage+0x2d6/0x310 Code: 8b 45 30 ba 00 10 00 00 31 f6 41 bc fb ff ff ff 48 8b 40 70 48 8b 40 40 e8 47 20 a6 00 4c 89 f7 e8 2f 2c e7 ff e9 86 fe ff ff <0f> 0b 0f 0b e9 78 ff ff ff 4c 89 e7 4c 89 f6 41 bc f4 ff ff ff e8 RSP: 0018:adaf401dfa28 EFLAGS: 00010246 RAX: 000fc037 RBX: 94ec39b9bb48 RCX: 0010 RDX: 0008 RSI: adaf401dfc10 RDI: d75e81decd00 RBP: adaf401dfa78 R08: 94ecfffd3000 R09: 00031155 R10: 00031100 R11: 0015 R12: adaf401dfc10 R13: 94ec39b9b9d0 R14: d75e81decd00 R15: 1000 FS: () GS:94ecfbb0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f8a055c3010 CR3: 000137362002 CR4: 00360ee0 Call Trace: ? __mod_lruvec_state+0x44/0xf0 __writepage+0x1d/0x50 write_cache_pages+0x1ae/0x4b0 ? __wb_calc_thresh+0x130/0x130 ? check_preempt_curr+0x7a/0x90 ? ttwu_do_wakeup+0x1e/0x150 ? ttwu_do_activate+0x5b/0x70 generic_writepages+0x57/0x90 jbd2_journal_submit_inode_data_buffers+0x63/0x80 ext4_journal_submit_inode_data_buffers+0xd5/0x100 jbd2_journal_commit_transaction+0x48f/0x18c0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 14:39 seq crw-rw 1 root audio 116, 33 Dec 7 14:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Dec 7 14:40:03 2021 InstallationDate: Installed on 2021-11-29 (8 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=2ad85404-d6b7-4c7d-a860-b873557a175c ro console=ttyS0 slub_debug=FZ crashkernel=256M RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias:
[Kernel-packages] [Bug 1953518] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953518 Title: CPU stuck Status in linux package in Ubuntu: Confirmed Bug description: CPU stuck were discovered at task hung in do_truncate. The problem was originally found by syzbot, https://syzkaller.appspot.com/bug?id=18b2ab4c697021ee8369. It is reproduced by the root user in the docker container or host on Ubuntu 20.04.3 LTS with Linux 5.4.0-91-generic. The bug reproducer is built from https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/18b2ab4c697021ee8369.c. It reproduces in Ubuntu 18.04.6 LTSwith Linux 4.15.0-163-generic and Ubuntu 20.04.3 LTS with Linux mainline v5.16-rc4 also. I used MSI GT72 6QD Dominator with i7-6820HK. There are steps to reproduce in the Docker container: --- docker pull ubuntu docker run -ti ubuntu bash apt update apt install gcc wget wget https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/18b2ab4c697021ee8369.c gcc ./18b2ab4c697021ee8369.c -static -pthread -o 18b2ab4c697021ee8369 ./18b2ab4c697021ee8369 The kernel crash contains as a result: root@de45b02a83c0:/# ./18b2ab4c697021ee8369 �� @cgroup.controllers�./file0[ 7977.039018] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [18b2ab4c697021e:4427] [ 8005.212380] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [18b2ab4c697021e:4427] [ 8012.900740] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 8012.904199] rcu: 1-: (148 ticks this GP) idle=db2/1/0x4004 softirq=30262/30262 fqs=7456 �� @cgroup.controllers�./file0�� @cgroup.controllers�./file0[ 8097.026740] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [apport:33113] [ 8181.189733] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:0:1478] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 14:39 seq crw-rw 1 root audio 116, 33 Dec 7 14:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Dec 7 15:11:42 2021 InstallationDate: Installed on 2021-11-29 (8 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=2ad85404-d6b7-4c7d-a860-b873557a175c ro console=ttyS0 slub_debug=FZ crashkernel=256M RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953518] Re: CPU stuck
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953518 Title: CPU stuck Status in linux package in Ubuntu: Confirmed Bug description: CPU stuck were discovered at task hung in do_truncate. The problem was originally found by syzbot, https://syzkaller.appspot.com/bug?id=18b2ab4c697021ee8369. It is reproduced by the root user in the docker container or host on Ubuntu 20.04.3 LTS with Linux 5.4.0-91-generic. The bug reproducer is built from https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/18b2ab4c697021ee8369.c. It reproduces in Ubuntu 18.04.6 LTSwith Linux 4.15.0-163-generic and Ubuntu 20.04.3 LTS with Linux mainline v5.16-rc4 also. I used MSI GT72 6QD Dominator with i7-6820HK. There are steps to reproduce in the Docker container: --- docker pull ubuntu docker run -ti ubuntu bash apt update apt install gcc wget wget https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/18b2ab4c697021ee8369.c gcc ./18b2ab4c697021ee8369.c -static -pthread -o 18b2ab4c697021ee8369 ./18b2ab4c697021ee8369 The kernel crash contains as a result: root@de45b02a83c0:/# ./18b2ab4c697021ee8369 �� @cgroup.controllers�./file0[ 7977.039018] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [18b2ab4c697021e:4427] [ 8005.212380] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [18b2ab4c697021e:4427] [ 8012.900740] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 8012.904199] rcu: 1-: (148 ticks this GP) idle=db2/1/0x4004 softirq=30262/30262 fqs=7456 �� @cgroup.controllers�./file0�� @cgroup.controllers�./file0[ 8097.026740] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [apport:33113] [ 8181.189733] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:0:1478] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 14:39 seq crw-rw 1 root audio 116, 33 Dec 7 14:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Dec 7 15:11:42 2021 InstallationDate: Installed on 2021-11-29 (8 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=2ad85404-d6b7-4c7d-a860-b873557a175c ro console=ttyS0 slub_debug=FZ crashkernel=256M RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953514] Re: BUG_ON(!PagePrivate(page))
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953514 Title: BUG_ON(!PagePrivate(page)) Status in linux package in Ubuntu: Confirmed Bug description: А “!PagePrivate(page)” assertion fail was discovered in “ext4_writepage”. The problem was originally found by syzbot, https://syzkaller.appspot.com/bug?id=ae0125a57674f57b675fad8f1440eb2be4790fba. It is reproduced by the root user in the docker container or host on Ubuntu 20.04.3 LTS with Linux 5.4.0-91-generic. The bug reproducer is built from https://raw.githubusercontent.com/dvyukov/syzkaller- repros/master/linux/ae0125a57674f57b675fad8f1440eb2be4790fba.c. It reproduces in Ubuntu 18.04.6 LTS with Linux 4.15.0-163-generic and Ubuntu 20.04.3 LTS with Linux mainline v5.16-rc4 also. There are steps to reproduce in the Docker container: --- docker pull ubuntu docker run -ti ubuntu bash apt update apt install gcc wget wget https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/ae0125a57674f57b675fad8f1440eb2be4790fba.c gcc ./ae0125a57674f57b675fad8f1440eb2be4790fba.c -static -pthread -o ae0125a57674f57b675fad8f1440eb2be4790fba ./ae0125a57674f57b675fad8f1440eb2be4790fba The kernel crash contains as a result: kernel BUG at fs/ext4/inode.c:2163! invalid opcode: [#1] SMP PTI CPU: 1 PID: 280 Comm: jbd2/vda2-8 Kdump: loaded Tainted: GW 5.4.0-91-generic #102-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:ext4_writepage+0x2d6/0x310 Code: 8b 45 30 ba 00 10 00 00 31 f6 41 bc fb ff ff ff 48 8b 40 70 48 8b 40 40 e8 47 20 a6 00 4c 89 f7 e8 2f 2c e7 ff e9 86 fe ff ff <0f> 0b 0f 0b e9 78 ff ff ff 4c 89 e7 4c 89 f6 41 bc f4 ff ff ff e8 RSP: 0018:adaf401dfa28 EFLAGS: 00010246 RAX: 000fc037 RBX: 94ec39b9bb48 RCX: 0010 RDX: 0008 RSI: adaf401dfc10 RDI: d75e81decd00 RBP: adaf401dfa78 R08: 94ecfffd3000 R09: 00031155 R10: 00031100 R11: 0015 R12: adaf401dfc10 R13: 94ec39b9b9d0 R14: d75e81decd00 R15: 1000 FS: () GS:94ecfbb0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f8a055c3010 CR3: 000137362002 CR4: 00360ee0 Call Trace: ? __mod_lruvec_state+0x44/0xf0 __writepage+0x1d/0x50 write_cache_pages+0x1ae/0x4b0 ? __wb_calc_thresh+0x130/0x130 ? check_preempt_curr+0x7a/0x90 ? ttwu_do_wakeup+0x1e/0x150 ? ttwu_do_activate+0x5b/0x70 generic_writepages+0x57/0x90 jbd2_journal_submit_inode_data_buffers+0x63/0x80 ext4_journal_submit_inode_data_buffers+0xd5/0x100 jbd2_journal_commit_transaction+0x48f/0x18c0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 14:39 seq crw-rw 1 root audio 116, 33 Dec 7 14:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Dec 7 14:40:03 2021 InstallationDate: Installed on 2021-11-29 (8 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=2ad85404-d6b7-4c7d-a860-b873557a175c ro console=ttyS0 slub_debug=FZ crashkernel=256M RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias:
[Kernel-packages] [Bug 1953520] Re: NULL pointer dereference in tcp_splice_read
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953520 Title: NULL pointer dereference in tcp_splice_read Status in linux package in Ubuntu: Confirmed Bug description: A NULL pointer dereference was discovered in “tcp_splice_read”. The problem was originally found by syzbot, https://syzkaller.appspot.com/bug?id=506214c97a1af183589a4caf4a8fa162a9f56cbd. It is reproduced by the root user in the docker container or host on Ubuntu 18.04.6 LTS with Linux 4.15.0-163-generic. It is reproduced on Ubuntu 18.04.6 LTS with Linux Ubuntu-4.15.0-164.172 also. The bug reproducer is built from https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/506214c97a1af183589a4caf4a8fa162a9f56cbd.c. It doesn't reproduce in Ubuntu 20.04.3 LTS with Linux 5.4.0-91-generic and Linux mainline v5.16-rc4. Mainline commit 07603b230895 (ChangeLog-5.1) fixes issue of propagate file from SMC to TCP socket. There are steps to reproduce in the Docker container: --- docker pull ubuntu docker run -ti ubuntu bash apt update apt install gcc wget wget https://raw.githubusercontent.com/dvyukov/syzkaller-repros/master/linux/506214c97a1af183589a4caf4a8fa162a9f56cbd.c gcc ./506214c97a1af183589a4caf4a8fa162a9f56cbd.c -static -pthread -o 506214c97a1af183589a4caf4a8fa162a9f56cbd ./506214c97a1af183589a4caf4a8fa162a9f56cbd The kernel crash contains as a result: root@2d6b356e151a:/# ./506214c97a1af183589a4caf4a8fa162a9f56cbd BUG: unable to handle kernel NULL pointer dereference at 0041 IP: tcp_splice_read+0x5f/0x2b0 PGD 800133bd3067 P4D 800133bd3067 PUD 12e34b067 PMD 0 Oops: [#1] SMP PTI Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: smc veth xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack br_netfilter bridge t sysimgblt aesni_intel fb_sys_fops aes_x86_64 crypto_simd glue_helper cryptd psmouse drm floppy e1000 virtio_blk pata_acpi i2c_piix4 CPU: 1 PID: 4601 Comm: 506214c97a1af18 Not tainted 4.15.0-163-generic #171-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:tcp_splice_read+0x5f/0x2b0 RSP: 0018:b50cc381fdb0 EFLAGS: 00010246 RAX: RBX: 9079f86952c0 RCX: 0001 RDX: RSI: fe01 RDI: 95e523a0 RBP: b50cc381fe20 R08: 0002 R09: c096e2c0 R10: R11: R12: 9079f1af7c40 R13: ffe3 R14: 9079edeebbd8 R15: 0001 FS: 01a56880() GS:9079ffd0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0041 CR3: 0001309b2001 CR4: 00360ee0 Call Trace: smc_splice_read+0x96/0xa0 [smc] sock_splice_read+0x25/0x30 do_splice_to+0x79/0x90 SyS_splice+0x6dd/0x730 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-163-generic 4.15.0-163.171 ProcVersionSignature: Ubuntu 4.15.0-163.171-generic 4.15.18 Uname: Linux 4.15.0-163-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 7 15:27 seq crw-rw 1 root audio 116, 33 Dec 7 15:27 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.27 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: Date: Tue Dec 7 15:28:46 2021 InstallationDate: Installed on 2021-11-29 (7 days ago) InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochsdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-163-generic root=UUID=8688c2d4-18cc-4c67-b9a9-dc3d4f4ed3f2 ro console=ttyS0 oops=panic panic=86400 ftrace_dump_on_oops=orig_cpu slub_debug=FZ maybe-ubiquity crashkernel=512M-:192M RelatedPackageVersions: linux-restricted-modules-4.15.0-163-generic N/A linux-backports-modules-4.15.0-163-generic N/A linux-firmware
[Kernel-packages] [Bug 1443924] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush
I love to play https://relaxmodapk.com/ludo-king/ DO you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Description changed: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to - the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO + the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. - [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. ** Description changed: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] - This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button + This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953540] [NEW] Fix power button wakeup with shared IRQs on AMD platforms
Public bug reported: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Alex Hung (alexhung) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => 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/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.13.0.1012.18)
All autopkgtests for the newly accepted linux-meta-raspi (5.13.0.1012.18) for impish have finished running. The following regressions have been reported in tests triggered by the package: libvpoll-eventfd/unknown (arm64) glibc/unknown (arm64) bbswitch/unknown (arm64) jool/unknown (arm64) rtl8812au/unknown (arm64) gost-crypto/unknown (arm64) adv-17v35x/unknown (arm64) backport-iwlwifi-dkms/unknown (arm64) systemd/unknown (arm64) ddcci-driver-linux/unknown (arm64) acpi-call/unknown (arm64) dm-writeboost/unknown (arm64) iptables-netflow/unknown (arm64) openafs/unknown (arm64) langford/unknown (arm64) lime-forensics/unknown (arm64) lxc/unknown (arm64) xtrx-dkms/unknown (arm64) v4l2loopback/unknown (arm64) west-chamber/unknown (arm64) digimend-dkms/unknown (arm64) xtables-addons/unknown (arm64) r8168/unknown (arm64) dpdk-kmods/unknown (arm64) snapd/unknown (arm64) wireguard-linux-compat/unknown (arm64) rtl8821ce/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
No more crashes with firmware https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/snapshot/linux-firmware-20211027.tar.gz and kernel 5.15.6. -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on appleton node (arm64)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu) 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on appleton node (arm64) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288702] secondary_start_kernel+0x198/0x288 Dec 2 12:17:46 appleton-kernel kernel: [ 98.829315] rcu: INFO: rcu_sched detected
[Kernel-packages] [Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
@ayanamist - Given your last result I have to say that this does not look like a kernel problem. This should be the kernel that will be released on Jan 4. Please give it a try. wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-image-unsigned-5.4.0-92-generic_5.4.0-92.103_amd64.deb wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-modules-5.4.0-92-generic_5.4.0-92.103_amd64.deb wget https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-modules-extra-5.4.0-92-generic_5.4.0-92.103_amd64.deb sudo dpkg -i *.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952094 Title: CIFS mount error: iocharset utf8 not found Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: After i apt upgrade from linux-image-5.4.0-89-generic to linux-image-5.4.0-90-generic, mount.cifs failed with dmesg "CIFS VFS: CIFS mount error: iocharset utf8 not found", and i rollback it and it restores. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 24 20:16 seq crw-rw 1 root audio 116, 33 Nov 24 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-07 (109 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=fd942b77-19c9-4959-a01c-c8e3f7b583b6 ro ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 12/17/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 1425-2986-4285-1154-1589-7450-41 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd12/17/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
https://lore.kernel.org/linuxppc- dev/20211207130557.40566-1-casca...@canonical.com/T/#u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
+ handled.
+
+ * A fix is needed to enhance problem determination of guest kernel under
+ KVM using DIAG 0x318 instruction execution.
+
+ * The s390x diagnose 318 instruction sets the control program name code
+ (CPNC) and control program version code (CPVC) to provide useful
+ information regarding the OS during debugging.
+
+ * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.
+
+ [Fix]
+
+ * In general the following 4 commits are needed:
+
+ * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
+
+ * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
+
+ * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
+
+ * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
+
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
+
+ * For jammy, hirsute and impish only the first commit is needed, the
+ others are already in.
+
+ * For focal all 4 commits are needed, but since they do not apply
+ cleanly on focal, the attached backports need to be used instead.
+
+ [Test Case]
+
+ * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.
+
+ * And setup an Ubuntu KVM virtual on top.
+
+ * It can then be observed if the CPNC (diag318 data) has been
+ successfully set by looking at the s390dbf messages for the KVM guest.
+
+ * The CPNC will always be 4 (denotes Linux environment).
+
+ * Another way to test this is by running the sync_regs_test under
+ tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
+ kernel self test suite can trigger this.
+
+ [Where problems could occur]
+
+ * The approach here is to provide additional debug and diagnose
+ information on top.
+
+ * Hence even if the diag318 changes are broken, the existing
+ functionality shouldn't be harmed.
+
+ * The changes themselves are relatively discernible and mostly introduce
+ new structures.
+
+ * However, with the functional changes broken code could be introduced
+ (e.g. due to erroneous pointer arithmetic for example) that does not
+ compile or causes crashes. But this is what the test builds are for
+ (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).
+
+ * On top the diag318 diagnose data might not properly provided - maybe
+ empty or wrong. Again that is what the test builds and the verification
+ later is targeted at.
+
+ * Since diag318 is s390x specific, all the modifications touch s390x
+ code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
+ arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
+ diag.h). At least no other other architecture will be affected.
+
+ * Well, there is one tiny bit of a common code change, but it's just a
+ new define statement in include/uapi/linux/kvm.h ('#define
+ KVM_CAP_S390_DIAG318 186').
+
+ [Other]
+
+ * Request was to add the patches to focal / 20.04, but to avoid
+ potential regressions on upgrades, the patches need to be added to
+ jammy, impish and hirsute, too.
+
+ * As mentioned above, Jammy, Hirsute and Impish includes almost
+ everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
+ for diag 318 CPNC data".
+
+ * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
+ invasive for Jammy, Hirsute and Impish, also because commit 3fd8417f2c72
+ can be cleanly cherry-picked form there.
+
+ * LP#1953338 is related to this bug and covers the qemu/KVM bits.
+ __
+
Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled.
Fix needed to enhance problem determination of guest kernel under KVM
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel
under KVM using DIAG 0x318 instruction execution.
*
[Kernel-packages] [Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
This looks like very similar to the vulnerable case that I changed to return as skipped. It's possible that the host is doing one mitigation while the guest is informed of a different mitigation, leading to this mis-match. I will take this upstream and see how it goes. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
focal/linux-ibm has not been updated to the latest focal/master-next version (5.4.0-92.103), which has the fix. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-ibm source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-ibm source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-ibm source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-ibm source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2
[Kernel-packages] [Bug 1948811] Re: Touchpad not detected when pci=nocrs not specified
Thank you very much Hui, I'll keep waiting then. Florent -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo 884 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: PC Specialist LTD NL4x_NL5xLU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 pci=nocrs ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2020 dmi.bios.release: 7.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.02TPCS dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4XLU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.02TPCS:bd08/19/2020:br7.2:efr7.2:svnPCSpecialistLTD:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnCLEVO:rnNL4XLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
As this is failing on ADT, it is failing on VMs on an environment we don't have much control of. This could be caused by host kernel, qemu or libvirt combinations that will make the guest kernel observe a given mitigation while it's not really in place. This test was added after 5.4, so the failure won't be observed on kernels before 5.11. I have fixed it once so it detects the Vulnerable case and have the test return the SKIP code. We need to fix this sooner rather than later, otherwise ADT test results will continue to fail. The other option is to skip this on our tests. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-23.23 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This test was previously being skipped. After recent test changes, it's now showing up as a failure. Not a regression. ubuntu_kernel_selftests.powerpc/security:spectre_v2 consistently failing on 5.13 and 5.11 Found failing on: Impish/linux 5.13.0-23.23 Hirsute/linux 5.11.0-42.46 (passed on first run, though failing after retrigger) Foal/hwe-5.13 5.13.0-23.23~20.04.1 Focal/hwe-5.11 5.11.0-42.46~20.04.1 23:45:31 DEBUG| [stdout] # selftests: powerpc/security: spectre_v2 23:45:31 DEBUG| [stdout] # test: spectre_v2 23:45:31 DEBUG| [stdout] # tags: git_version:d9c024c2-dirty 23:45:50 DEBUG| [stdout] # sysfs reports: 'Mitigation: Software count cache flush, Software link stack flush' 23:45:50 DEBUG| [stdout] # PM_BR_PRED_CCACHE: result 2147483649 running/enabled 19680067308 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_CCACHE: result 2147475077 running/enabled 19680064034 23:45:50 DEBUG| [stdout] # PM_BR_PRED_PCACHE: result 0 running/enabled 19680062840 23:45:50 DEBUG| [stdout] # PM_BR_MPRED_PCACHE: result 0 running/enabled 19680061722 23:45:50 DEBUG| [stdout] # Miss percent 99 % 23:45:50 DEBUG| [stdout] # Branch misses > 15% unexpected in this configuration! 23:45:50 DEBUG| [stdout] # Possible mis-match between reported & actual mitigation 23:45:50 DEBUG| [stdout] # failure: spectre_v2 23:45:50 DEBUG| [stdout] not ok 1 selftests: powerpc/security: spectre_v2 # exit=1 23:45:50 DEBUG| [stdout] make: Leaving directory '/tmp/autopkgtest.XkeXuO/build.i7C/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/security' Testing failed on: ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211204_000820_141a2@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948811] Re: Touchpad not detected when pci=nocrs not specified
the maintainer wants the patch to be verified in some distribution first, if there is no regression, maybe he will merge the patch: So I've discussed this with the Fedora kernel maintainers and they have agreed to add the patch to the Fedora 5.15 kernels, which we will ask our users to start testing soon (we first run some voluntary testing before eventually moving all users over). This will provide us with valuable feedback wrt this patch causing regressions as you are worried about, or not. Assuming no regressions show up I hope that this will give you some assurance that there the patch causes no regressions and that you will then be willing to pick this up later during the 5.16 cycle so that Fedora only deviates from upstream for 1 cycle. Regards, Hans -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo 884 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: PC Specialist LTD NL4x_NL5xLU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 pci=nocrs ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2020 dmi.bios.release: 7.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.02TPCS dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4XLU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.02TPCS:bd08/19/2020:br7.2:efr7.2:svnPCSpecialistLTD:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnCLEVO:rnNL4XLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
Kernel team, is it safe to revert the order today for jammy?
I.e., can we apply this to the wireguard-tools package:
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,7 @@ Rules-Requires-Root: no
Package: wireguard
Architecture: all
Depends:
- wireguard-dkms (>= 0.0.20200121-2) | wireguard-modules (>= 0.0.20191219),
+ wireguard-modules (>= 0.0.20191219) | wireguard-dkms (>= 0.0.20200121-2),
wireguard-tools (>= ${source:Version}),
${misc:Depends},
Description: fast, modern, secure kernel VPN tunnel (metapackage)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1873288
Title:
wireguard-tools should NOT recommend wireguard-dkms
Status in linux-meta package in Ubuntu:
Fix Released
Status in wireguard package in Ubuntu:
Confirmed
Bug description:
With 20.04, the wireguard-dkms is not strictly needed as the
wireguard.ko is now shipped with kernel packages.
# apt-cache show wireguard-tools | grep Recommends
Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) |
wireguard-modules (>= 0.0.20171001)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948811] Re: Touchpad not detected when pci=nocrs not specified
Hi Hui, The actual patch has been accepted by Bjorn Helgaas in pend/resource branch for almost 2 months but doesn't get merge within its "next" branch. Do you know why it's still pending? How to get its current status? Regards Florent -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948811 Title: Touchpad not detected when pci=nocrs not specified Status in linux package in Ubuntu: Confirmed Bug description: Touchpad on Clevo NL41LU2 is not detected with 5.13.0-20-generic kernel unless pci=nocrs is specified. Please find iomem, dmesg and lspci dump attached. Ubuntu details: $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Florent --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo 884 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-26 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: PC Specialist LTD NL4x_NL5xLU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p6 pci=nocrs ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201 Tags: wayland-session impish Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2020 dmi.bios.release: 7.2 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.02TPCS dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4XLU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.02TPCS:bd08/19/2020:br7.2:efr7.2:svnPCSpecialistLTD:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnCLEVO:rnNL4XLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => 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/1788578 Title: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: [Impact] Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. [Test case] Run the bpf test_verifier. [Potential regression] Loading sample_period of bpf_perf_event_data may fail. Unaligned access may lead to processor exceptions on some architectures. == This issue was only spotted on i386 Bionic kernel. #146/p unpriv: spill/fill of different pointers ldx FAIL Unexpected error message! 0: (bf) r6 = r10 1: (07) r6 += -8 2: (15) if r1 == 0x0 goto pc+3 R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 3: (bf) r2 = r10 4: (07) r2 += -76 5: (7b) *(u64 *)(r6 +0) = r2 6: (55) if r1 != 0x0 goto pc+1 R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp 7: (7b) *(u64 *)(r6 +0) = r1 8: (79) r1 = *(u64 *)(r6 +0) 9: (79) r1 = *(u64 *)(r1 +68) #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (71) r0 = *(u8 *)(r1 +68) invalid bpf_context access off=68 size=1 #353/p check bpf_perf_event_data->sample_period half load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (69) r0 = *(u16 *)(r1 +68) invalid bpf_context access off=68 size=2 #354/p check bpf_perf_event_data->sample_period word load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (61) r0 = *(u32 *)(r1 +68) invalid bpf_context access off=68 size=4 #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (79) r0 = *(u64 *)(r1 +68) invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 08:23 seq crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 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: CurrentDmesg: Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)
** Changed in: ubuntu-kernel-tests 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/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: [Impact] selftests net will fail on i386, requiring engineers time to investigate, or leading to new BPF failures to be ignored. [Fix] The fix is only to tests. [Test case] Run test_bpf.sh from tools/testing/selftests/net/. [Potential regression] Tests could fail on other architectures. This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
For focal SRUs we must ensure that all requested patches are also included in all versions newer than focal - this is to avoid any regressions that may occur after upgrades. Hence I had to look-up the situation of the patches not only in focal (where the four backports apply cleanly), but also on hirsute (5.11), impish (5.13) and jammy (5.15) - and when the commits got upstream accepted. 1) a23816f3cdcb "s390/setup: diag 318: refactor struct" is upstream with v5.10-rc1 and newer 2) 23a60f834406 "s390/kvm: diagnose 0x318 sync and reset" is upstream with v5.10-rc1 and newer 3) 6cbf1e960fa5 "KVM: s390: remove diag318 reset code" is upstream with v5.10-rc6 and newer 4) but 3fd8417f2c72 "KVM: s390: add debug statement for diag 318 CPNC data" was just recently upstream accepted with v5.16-rc1 and newer. Hence first three commits are already in hirsute, impish and jammy, BUT the last one is not, and needs to be applied on hirsute, impish and jammy on top of the work on focal. I'm glad to see that 3fd8417f2c72 can be cleanly cherry-picked from hirsute, impish and jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926439] Re: Dependencies conflicts breaks upgrade process
Problem is still here: ~$ apt show linux-modules-nvidia-470-5.4.0-91-generic Package: linux-modules-nvidia-470-5.4.0-91-generic Version: 5.4.0-91.102+2 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32,8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-91-generic | linux-image-unsigned-5.4.0-91-generic, linux-signatures-nvidia-5.4.0-91-generic (= 5.4.0-91.102+2), linux-objects-nvidia-470-5.4.0-91-generic (= 5.4.0-91.102+2), nvidia-kernel-common-470 (<= 470.86-1), nvidia-kernel-common-470 (>= 470.86) -- 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/1926439 Title: Dependencies conflicts breaks upgrade process Status in NVIDIA Drivers Ubuntu: New Status in unattended-upgrades: New Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: Latest updates of linux-restricted-modules breaks upgrade process, updates cannot be installed without removing nvidia modules for previous kernel version, unattended-upgrade cannot do that, as result we have broken system without nvidia driver ~# apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: linux-modules-nvidia-460-5.4.0-71-generic The following NEW packages will be installed: linux-modules-nvidia-460-5.4.0-72-generic linux-objects-nvidia-460-5.4.0-72-generic linux-signatures-nvidia-5.4.0-72-generic The following packages will be upgraded: libnvidia-cfg1-460 libnvidia-compute-460 libnvidia-compute-460:i386 libnvidia-decode-460 libnvidia-decode-460:i386 libnvidia-encode-460 libnvidia-encode-460:i386 libnvidia-extra-460 libnvidia-fbc1-460 libnvidia-fbc1-460:i386 libnvidia-gl-460 libnvidia-gl-460:i386 libnvidia-ifr1-460 libnvidia-ifr1-460:i386 linux-modules-nvidia-460-generic nvidia-compute-utils-460 nvidia-driver-460 nvidia-kernel-common-460 nvidia-kernel-source-460 nvidia-utils-460 xserver-xorg-video-nvidia-460 21 upgraded, 3 newly installed, 1 to remove and 0 not upgraded. Need to get 199 MB of archives. After this operation, 45.6 MB of additional disk space will be used. Do you want to continue? [Y/n] ~# apt show linux-modules-nvidia-460-5.4.0-71-generic Package: linux-modules-nvidia-460-5.4.0-71-generic Version: 5.4.0-71.79+1 Priority: optional Section: restricted/kernel Source: linux-restricted-modules Origin: Ubuntu Maintainer: Canonical Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 32.8 kB Depends: debconf (>= 0.5) | debconf-2.0, linux-image-5.4.0-71-generic | linux-image-unsigned-5.4.0-71-generic, linux-signatures-nvidia-5.4.0-71-generic (= 5.4.0-71.79+1), linux-objects-nvidia-460-5.4.0-71-generic (= 5.4.0-71.79+1), nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) Download-Size: 7136 B APT-Manual-Installed: no APT-Sources: http://archive.pls.pbank.com.ua/ubuntu-current focal-updates/restricted amd64 Packages Description: Linux kernel nvidia modules for version 5.4.0-71 This dependencies should be removed to fix this problem: nvidia-kernel-common-460 (<= 460.56-1), nvidia-kernel-common-460 (>= 460.56) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1926439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
We are using the kernel level from tjcw:linux-xlnx$ git checkout xilinx-v2020.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
You can only log in to the affected system after you have accessed the IBM network, i.e. when you are inside the firewall. VPN access can be granted (I believe) to whoever is assignde to fix this bug. ** Attachment added: "How to log in to the affected system" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+attachment/5545944/+files/howto-embedded-arm-3.tar.z -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
** Attachment added: "Consiole log from boot to occurrence of crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+attachment/5545942/+files/kcrashlog.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/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952185] Re: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk
** Attachment added: "Consiole log from boot to occurrence of crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+attachment/5545943/+files/kcrashlog.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/1952185 Title: Embedded ARM64 crash trying to zero-fill an 8GB ramdisk Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- Kernel crash when setting up ramdisk on embedded ARM Contact Information = Chris Ward t...@uk.ibm.com Mohit Kapur moh...@us.ibm.com ---Additional Hardware Info--- Embedded ARM with FPGA ---uname output--- Linux cuttlefisharm1 5.4.0-xilinx-v2020.2 #1 SMP Thu Nov 18 18:44:45 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Machine Type = IBM Research internal processor based on xilinx ---System Hang--- Unresponsive. Power cycle reclaims ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Boot the system. Try dd if=/dev/zero of=/dev/ram0 bs=... count=... A small ramdisk works and gives the expected error when trying to write 8G of data into an 8M ramdisk. tjcw@cuttlefisharm1:~$ sudo dd if=/dev/zero of=/dev/ram0 bs=4096 count=1048576 [sudo] password for tjcw: dd: error writing '/dev/ram0': No space left on device 2049+0 records in 2048+0 records out 8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.0531788 s, 158 MB/s tjcw@cuttlefisharm1:~$ A 2GB ramdisk works, a 4GB ramdisk causes a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
