[Kernel-packages] [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead
Dave, The first thing to check is whether new cables fix the problem. The second thing to check is whether the latest development kernel already has a fix that works for you: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/ Third is to report your own bug upstream: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs It's best that everyone reports their own issue upstream because the root causes of these bugs are so hidden that the solutions are likely to be different for different people. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140
[Kernel-packages] [Bug 1942935] Re: kernel io hangs during mdcheck/resync
It won’t let me change the state back to active. Every time I try nothing happens and array_status is always idle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30 [921588.559081] ? kmem_cache_alloc+0x38e/0x440 [921588.559084] ? ext4_init_io_end+0x1f/0x50 [921588.559088] ext4_io_submit+0x4d/0x60 [921588.559091] ext4_writepages+0x2c6/0xcd0 [921588.559094] ? __schedule+0x454/0x8a0 [921588.559097] ?
[Kernel-packages] [Bug 1981075] Re: ubuntu_kernel_selftests.net:fib_nexthops.sh times out on riscv
** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1981075 Title: ubuntu_kernel_selftests.net:fib_nexthops.sh times out on riscv Status in ubuntu-kernel-tests: In Progress Status in linux-riscv package in Ubuntu: Confirmed Status in linux-riscv source package in Jammy: Confirmed Bug description: net:fib_nexthops.sh times out on riscv kernels 12284 12:09:41 DEBUG| [stdout] # 12285 12:09:41 DEBUG| [stdout] # IPv6 runtime resilient nexthop group torture 12286 12:09:41 DEBUG| [stdout] # 12287 12:14:40 INFO | Timer expired (1800 sec.), nuking pid 43387 would be nice to possibly increase timer on riscv, as otherwise the test seems to be running ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1981075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 515937] Re: Filesystems end up remounted read-only
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/515937
Title:
Filesystems end up remounted read-only
Status in linux package in Ubuntu:
Invalid
Bug description:
Sometimes (occasionally after resume, but also after just being left
alone for a while) my /home LV will become read-only.
This is a kern.log snippet from a case where I'd left it alone for a
few minutes:
[...snip irrelevant boot stuff...]
Feb 2 18:37:18 magrathea kernel: [ 107.120041] wlan0: no IPv6 routers
present
Feb 2 20:07:21 magrathea kernel: [ 5510.246995] Monitor-Mwait will be used
to enter C-3 state
Feb 2 20:07:21 magrathea kernel: [ 5510.260250] thinkpad_acpi: EC reports
that Thermal Table has changed
Feb 2 20:07:21 magrathea kernel: [ 5510.271591] CPU0 attaching NULL
sched-domain.
Feb 2 20:07:21 magrathea kernel: [ 5510.271596] CPU1 attaching NULL
sched-domain.
Feb 2 20:07:21 magrathea kernel: [ 5510.300364] ata1.00: exception Emask
0x10 SAct 0x0 SErr 0x5 action 0xe frozen
Feb 2 20:07:21 magrathea kernel: [ 5510.300367] ata1.00: irq_stat
0x0040, PHY RDY changed
Feb 2 20:07:21 magrathea kernel: [ 5510.300370] ata1: SError: { PHYRdyChg
CommWake }
Feb 2 20:07:21 magrathea kernel: [ 5510.300373] ata1.00: failed command:
FLUSH CACHE EXT
Feb 2 20:07:21 magrathea kernel: [ 5510.300377] ata1.00: cmd
ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 2 20:07:21 magrathea kernel: [ 5510.300378] res
50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
Feb 2 20:07:21 magrathea kernel: [ 5510.300380] ata1.00: status: { DRDY }
Feb 2 20:07:21 magrathea kernel: [ 5510.300383] ata1: hard resetting link
Feb 2 20:07:21 magrathea kernel: [ 5510.311958] CPU0 attaching sched-domain:
Feb 2 20:07:21 magrathea kernel: [ 5510.311966] domain 0: span 0-1 level MC
Feb 2 20:07:21 magrathea kernel: [ 5510.311973] groups: 0 1
Feb 2 20:07:21 magrathea kernel: [ 5510.311985] CPU1 attaching sched-domain:
Feb 2 20:07:21 magrathea kernel: [ 5510.311990] domain 0: span 0-1 level MC
Feb 2 20:07:21 magrathea kernel: [ 5510.311996] groups: 1 0
Feb 2 20:07:22 magrathea kernel: [ 5511.050162] ata1: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Feb 2 20:07:22 magrathea kernel: [ 5511.052417] ata1.00: ACPI cmd
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Feb 2 20:07:22 magrathea kernel: [ 5511.052427] ata1.00: ACPI cmd
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Feb 2 20:07:22 magrathea kernel: [ 5511.052436] ata1.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Feb 2 20:07:22 magrathea kernel: [ 5511.056971] ata1.00: ACPI cmd
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Feb 2 20:07:22 magrathea kernel: [ 5511.056980] ata1.00: ACPI cmd
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Feb 2 20:07:22 magrathea kernel: [ 5511.056988] ata1.00: ACPI cmd
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Feb 2 20:07:22 magrathea kernel: [ 5511.058819] ata1.00: configured for
UDMA/133
Feb 2 20:07:22 magrathea kernel: [ 5511.058829] ata1.00: device reported
invalid CHS sector 0
Feb 2 20:07:22 magrathea kernel: [ 5511.064408] ata1.00: configured for
UDMA/133
Feb 2 20:07:22 magrathea kernel: [ 5511.064421] end_request: I/O error, dev
sda, sector 0
Feb 2 20:07:22 magrathea kernel: [ 5511.064448] ata1: EH complete
Feb 2 20:07:22 magrathea kernel: [ 5511.119184] Aborting journal on device
dm-1-8.
Feb 2 20:07:22 magrathea kernel: [ 5511.130652] journal commit I/O error
Feb 2 20:07:22 magrathea kernel: [ 5511.130798] EXT4-fs error (device dm-1):
ext4_journal_start_sb: Detected aborted journal
Feb 2 20:07:22 magrathea kernel: [ 5511.130808] EXT4-fs (dm-1): Remounting
filesystem read-only
Feb 2 20:07:22 magrathea kernel: [ 5511.131189] ecryptfs_encrypt_page: Error
attempting to write lower page; rc = [-30]
Feb 2 20:07:22 magrathea kernel: [ 5511.131198] ecryptfs_write_end: Error
encrypting page (upper index [0x0002])
[...snip lots of eCryptFS error repeats ...]
I think I first noticed this about three weeks ago. I've been
rebooting to fix it.
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wgrant 3837 F pulseaudio
/dev/snd/pcmC0D0p: wgrant 3837 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc02 irq 17'
Mixer name : 'Conexant CX20561 (Hermosa)'
[Kernel-packages] [Bug 1981173] [NEW] Clear PCI errors left from BIOS
Public bug reported: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Low Status: Confirmed ** Tags: oem-priority originate-from-1968671 sutton ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Low ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => Low ** Tags added: oem-priority originate-from-1968671 sutton -- 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/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-gke/5.4.0.1078.86)
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1078.86) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.048.00-1ubuntu0.20.04.2 (amd64) 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/focal/update_excuses.html#linux-meta-gke [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 1981173] 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 1981173 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980060] Re: Fix AMDGPU blank screen when Type-C DP alt is in use
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980060 Title: Fix AMDGPU blank screen when Type-C DP alt is in use Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] When Type-C DP/HDMI is in use, s0ix resume renders both eDP and DP outputs blank. [Fix] Query the firmware to ensure the DP alt status. [Test] Suspend and resume the system, both eDP and Type-C DP/HDMI are working. [Where problems could occur] This fix only applies to certain AMD GFX with certain firmware version, so the scope is very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980087] Re: Fix PSR flickers on Intel TGL laptops + AUO panel
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980087 Title: Fix PSR flickers on Intel TGL laptops + AUO panel Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Screen flickers on certain Intel TGL laptops + AUO panel. [Fix] Enable PSR2 selective fetch only for the specific case to minimize the regression risk. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] The fix becomes very specific, so any other combination won't be affected at all. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980307] Re: Suppress harmless warning from hp-wmi
** Tags removed: verification-needed-focal ** Tags added: verification-don-focal ** Tags removed: verification-don-focal ** Tags added: verification-done-focal -- 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/1980307 Title: Suppress harmless warning from hp-wmi Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] Harmless warning is spewed from hp-wmi driver. [Fix] Ignore the unhandled event. [Test] No more such warning in dmesg. [Where problems could occur] The action for the event is not implemented, so ignoring it won't change any existing behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951927] Re: Array overflow in au_procfs_plm_write
** Changed in: linux (Ubuntu)
Status: Expired => 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/1951927
Title:
Array overflow in au_procfs_plm_write
Status in linux package in Ubuntu:
Confirmed
Bug description:
There is an simple array overflow when count = 20 in
au_procfs_plm_write.
static ssize_t au_procfs_plm_write(struct file *file, const char __user *ubuf,
size_t count, loff_t *ppos)
{
...
char buf[3 + sizeof(unsigned long) * 2 + 1];
err = -EACCES;
if (unlikely(!capable(CAP_SYS_ADMIN)))
goto out;
err = -EINVAL;
if (unlikely(count > sizeof(buf)))
goto out;
err = copy_from_user(buf, ubuf, count);
if (unlikely(err)) {
err = -EFAULT;
goto out;
}
buf[count] = 0; sizeof(buf)))
goto out;
err = copy_from_user(buf, ubuf, count);
if (unlikely(err)) {
err = -EFAULT;
goto out;
}
--- buf[count] = 0;
+++ buf[count - 1] = 0;
...
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951927/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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-gke/5.4.0.1077.85)
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1077.85) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.048.00-1ubuntu0.20.04.2 (amd64) 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/focal/update_excuses.html#linux-meta-gke [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 1980594] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602245/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602246/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602242/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602243/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602244/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602241/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602240/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M Package: linux-starfive-5.17 (not installed) PciMultimedia: ProcCpuinfoMinimal: processor: 7 hart : 7 isa : rv64imafdcsuh mmu : sv48 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 RelatedPackageVersions: linux-restricted-modules-5.17.0-1003-starfive N/A linux-backports-modules-5.17.0-1003-starfive N/A linux-firmware20220621.git7b71b75b-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.17.0-1003-starfive riscv64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
apport information ** Tags added: apport-collected kinetic uec-images ** Description changed: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 10 19:58 seq + crw-rw 1 root audio 116, 33 Jul 10 19:58 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.22.0-0ubuntu4 + Architecture: riscv64 + 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: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.10 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge + +-01.0 Red Hat, Inc. QEMU XHCI Host Controller + +-02.0 Red Hat, Inc. Virtio block device + \-03.0 Red Hat, Inc. Virtio block device + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M + Package: linux-starfive-5.17 (not installed) + PciMultimedia: + + ProcCpuinfoMinimal: + processor: 7 + hart : 7 + isa : rv64imafdcsuh + mmu : sv48 + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M hugepagesz=2M hugepages=2048 earlycon efi=debug + ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9 + RelatedPackageVersions: + linux-restricted-modules-5.17.0-1003-starfive N/A + linux-backports-modules-5.17.0-1003-starfive N/A + linux-firmware20220621.git7b71b75b-0ubuntu1 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: kinetic uec-images + Uname: Linux 5.17.0-1003-starfive riscv64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + acpidump: ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1980594/+attachment/5602239/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Confirmed Status in linux-starfive-5.17 package in Ubuntu: Confirmed Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 19:58 seq crw-rw 1 root audio 116, 33 Jul 10 19:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.22.0-0ubuntu4 Architecture: riscv64 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: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. QEMU XHCI Host Controller +-02.0 Red Hat, Inc. Virtio block device \-03.0 Red Hat, Inc. Virtio block device Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1:
[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up
This bug is not fixed by 5.15.0-40-generic, and still occurs with that kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1958620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] 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 1980594 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-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: Incomplete Status in linux-starfive-5.17 package in Ubuntu: New Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
** Package changed: u-boot (Ubuntu) => linux (Ubuntu) ** Also affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980594 Title: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM Status in linux package in Ubuntu: New Status in linux-starfive-5.17 package in Ubuntu: New Bug description: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980594] [NEW] /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
You have been subscribed to a public bug: QEMU 7.0 supports KVM on RISC-V. Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf. That binary cannot be used to boot via qemu-system-riscv64 -kvm. File u-boot produced by qemu-riscv64_smode_defconfig with CONFIG_MTD_NOR_FLASH=n CONFIG_CMD_NET=n can be used to start U-Boot with qemu-system-riscv64 -kvm. But any virtio access leads to a crash leaving QEMU unresponsive. Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: fr-2521 -- /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM https://bugs.launchpad.net/bugs/1980594 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 1942935] Re: kernel io hangs during mdcheck/resync
Yeah, that's the same issue as this one. The issue is the raid is doing a consistency check (mdcheck) and is transitioned to an "idle" state and hits a deadlock that causes all I/O through the md device to block. The workaround is to change the array state back to active. I made the changes in #5 almost a year ago and no problems, before that it pretty much hung almost every single month when the scheduled consistency check was triggered ever since upgrading to 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071]
[Kernel-packages] [Bug 1981141] 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 1981141 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/1981141 Title: Acer Swift SF114-34 standby/suspend/resume issue Status in linux package in Ubuntu: Incomplete Bug description: When I close the lid the laptop does not go to standby. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981141] Re: Acer Swift SF114-34 standby issue
I updated the package and description. ** Package changed: ubuntu => linux (Ubuntu) ** Summary changed: - Acer Swift SF114-34 standby issue + Acer Swift SF114-34 standby/suspend/resume issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981141 Title: Acer Swift SF114-34 standby/suspend/resume issue Status in linux package in Ubuntu: New Bug description: When I close the lid the laptop does not go to standby. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981141] [NEW] Acer Swift SF114-34 standby issue
You have been subscribed to a public bug: When I close the lid the laptop does not go to standby. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Acer Swift SF114-34 standby issue https://bugs.launchpad.net/bugs/1981141 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 1968631] Re: regression in jammy kernel 5.15 for module ath9k
same as Bug #1978297 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968631 Title: regression in jammy kernel 5.15 for module ath9k Status in linux package in Ubuntu: Confirmed Bug description: wireless connection is unstable with kernel 5.15 in jammy release. the following line is in my log, ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6100 the bug appears to no longer be present in kernel 5.17.2 from the mainline kernel ppa. lsb_release -rd output: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1871 F pulseaudio /dev/snd/controlC1: david 1871 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 18:05:36 2022 InstallationDate: Installed on 2022-02-01 (69 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. X550LA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago) dmi.bios.date: 05/14/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.508 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.508:bd05/14/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X550LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978297] Re: [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211
same as Bug #1968631 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1978297 Title: [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] When bootup Jammy kernel, it shows callrace: kernel: kernel: UBSAN: invalid-load in /home/u/aaron/bionic/net/mac80211/status.c:1164:21 kernel: load of value 216 is not a valid value for type '_Bool' kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.15.36+ #12 kernel: Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET30W (1.11 ) 05/27/2022 kernel: Call Trace: kernel: kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: ieee80211_tx_status_ext.cold+0x1e/0xb0 [mac80211] kernel: ? percpu_ref_kill_and_confirm+0xd0/0xd0 kernel: ? rht_key_get_hash.isra.0+0x19/0x20 [mac80211] kernel: ? sta_info_hash_lookup+0xac/0x100 [mac80211] kernel: ieee80211_tx_status+0x72/0xa0 [mac80211] kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] kernel: tasklet_action_common.constprop.0+0xc0/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: irq_exit_rcu+0x8c/0xb0 kernel: common_interrupt+0x8a/0xa0 kernel: kernel: kernel: asm_common_interrupt+0x1e/0x40 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620 kernel: Code: 3d b4 85 3d 5c e8 57 a7 6b ff 49 89 c7 0f 1f 44 00 00 31 ff e8 a8 b3 6b ff 80 7d d0> kernel: RSP: 0018:9e2dc01f7e38 EFLAGS: 0246 kernel: RAX: 8dfdb6870b00 RBX: 8df6c3ab6c00 RCX: 00023cd33784 kernel: RDX: 00023d103fa8 RSI: 00023cd33784 RDI: kernel: RBP: 9e2dc01f7e88 R08: 00023cd33d63 R09: 000aae60 kernel: R10: 0004 R11: 071c71c71c71c71c R12: a4ce65a0 kernel: R13: 0003 R14: 0003 R15: 00023cd33d63 kernel: ? cpuidle_enter_state+0xc8/0x620 kernel: ? sched_clock_local+0x13/0x90 kernel: cpuidle_enter+0x2e/0x40 kernel: do_idle+0x203/0x2a0 kernel: cpu_startup_entry+0x20/0x30 kernel: start_secondary+0x12a/0x180 kernel: secondary_startup_64_no_verify+0xc2/0xcb kernel: kernel: [Fix] The size of the status_driver_data field was not adjusted when the is_valid_ack_signal field was added. Adjust the struct size accordingly. [Test] Verified on hardware, no error. [Where problems could occur] Low risk, It may break wifi driver. Minor changes in title of "Copyright" when backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
