Bug#986863: correcting metadata
Control: notfound -1 5.8.14-1 Control: found -1 5.10.28-1 signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#986863: correcting metadata
Processing control commands: > notfound -1 5.8.14-1 Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted during bootup Ignoring request to alter found versions of bug #986863 to the same values previously set > found -1 5.10.28-1 Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted during bootup Marked as found in versions linux/5.10.28-1. -- 986863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux-signed-i386_5.10.28+1_source.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Apr 2021 20:17:58 +0200 Source: linux-signed-i386 Architecture: source Version: 5.10.28+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-i386 (5.10.28+1) unstable; urgency=medium . * Sign kernel from linux 5.10.28-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.27 - mm/memcg: rename mem_cgroup_split_huge_fixup to split_page_memcg and add nr_pages argument - mm/memcg: set memcg when splitting page - mt76: fix tx skb error handling in mt76_dma_tx_queue_skb - net: stmmac: fix dma physical address of descriptor when display ring - [arm64,armhf] net: fec: ptp: avoid register access when ipg clock is disabled - [powerpc*] 4xx: Fix build errors from mfdcr() - atm: eni: dont release is never initialized - atm: lanai: dont run lanai_dev_close if not open - Revert "r8152: adjust the settings about MAC clock speed down for RTL8153" - [x86] ALSA: hda: ignore invalid NHLT table - ixgbe: Fix memleak in ixgbe_configure_clsu32 - blk-cgroup: Fix the recursive blkg rwstat - net: tehuti: fix error return code in bdx_probe() - net: intel: iavf: fix error return code of iavf_init_get_resources() - sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count - gianfar: fix jumbo packets+napi+rx overrun crash (CVE-2021-29264) - cifs: ask for more credit on async read/write code paths - gfs2: fix use-after-free in trans_drain - [arm64,armhf] cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev - gpiolib: acpi: Add missing IRQF_ONESHOT - nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default - NFS: Correct size calculation for create reply length - [arm64] net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch() - [arm64] net: enetc: set MAC RX FIFO to recommended value - atm: uPD98402: fix incorrect allocation - atm: idt77252: fix null-ptr-dereference - cifs: change noisy error message to FYI - kbuild: add image_name to no-sync-config-targets - umem: fix error return code in mm_pci_probe() - [sparc64] Fix opcode filtering in handling of no fault loads - u64_stats,lockdep: Fix u64_stats_init() vs lockdep - block: Fix REQ_OP_ZONE_RESET_ALL handling - drm/amdgpu: fb BO should be ttm_bo_type_device - drm/radeon: fix AGP dependency - nvme: simplify error logic in nvme_validate_ns() - nvme: add NVME_REQ_CANCELLED flag in nvme_cancel_request() - nvme-fc: set NVME_REQ_CANCELLED in nvme_fc_terminate_exchange() - nvme-fc: return NVME_SC_HOST_ABORTED_CMD when a command has been aborted - nvme-core: check ctrl css before setting up zns - nvme-rdma: Fix a use after free in nvmet_rdma_write_data_done - nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a - nfs: we don't support removing system.nfs4_acl - block: Suppress uevent for hidden device when removed - mm/fork: clear PASID for new mm - [ia64] fix ia64_syscall_get_set_arguments() for break-based syscalls - [ia64] fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign - static_call: Pull some static_call declarations to the type headers - [x86] static_call: Allow module use without exposing static_call_key - [x86] static_call: Fix the module key fixup - [x86] static_call: Fix static_call_set_init() - [x86] KVM: Protect userspace MSR filter with SRCU, and set atomically-ish - btrfs: fix sleep while in non-sleep context during qgroup removal - selinux: don't log MAC_POLICY_LOAD record on failed policy load - selinux: fix variable scope issue in live sidtab conversion - [arm64] netsec: restore phy power state after controller reset - [x86] platform/x86: intel-vbtn: Stop reporting SW_DOCK events - psample: Fix user API breakage - z3fold: prevent reclaim/free race for headless pages - squashfs: fix inode lookup sanity checks - squashfs: fix xattr id and id lookup sanity checks - hugetlb_cgroup: fix imbalanced css_get and css_put pair for shared mappings - [x86] ACPI: video: Add missing callback back for Sony VPCEH3U1E - ACPICA: Always create namespace nodes using acpi_ns_create_node() - [arm64] stacktrace: don't trace arch_stack_walk() - integrity: double check iint_cache was initialized - [armhf] drm/etnaviv: Use FOLL_FORCE for userptr - drm/amdgpu: Add additional Sienna Cichlid PCI ID - [x86] drm/i915: Fix the GT fence revocation runtime PM logic - dm verity: fix DM_VERITY_OPTS_MAX value - dm ioctl: fix out of bounds array access when no devices - [armhf] bus: omap_l3_noc: mark l3 irqs as IRQF_NO_THREAD - [armhf] OMAP2+: Fix smartreflex init regression after dropping legacy
Bug#986848: linux: Please enable CONFIG_RMI4_F3A kernel config option
Hi Justin, Le 2021-04-12 15:53, Justin King-Lacroix a écrit : > Source: linux > Severity: normal > X-Debbugs-Cc: justi...@google.com > > Kernel config option CONFIG_RMI4_F3A is not enabled by default on Debian > kernels. > > It is required for touchpad "click" functionality to work on the Lenovo P1 > Gen 2 > (among possibly other laptop models). It is also required by the Lenovo Thinkpad X1 Extreme Gen 2. > Can it please be enabled for future kernels? > (Related: is there a reason why it isn't?) I'll propose a merge request to the kernel team. Cheers, Vincent signature.asc Description: PGP signature
Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image
On Tue, Apr 13, 2021 at 11:36:11AM +0200, Bastian Blank wrote: > > > Where was that discussed? > > It was discussed in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759 > > , with responses from both Ben and Noah. > > As this is incomplete at best, I intend to revert that change. > > Otherwise it at least needs in addition: > - hyperv pci support (for nvme), > - hyperv block and > - virtio-scsi. This should probably be discussed in depth outside of this bug, but I do not think this is the right approach. The kernel config changes have been in place for over a year, and were merged only after discussion both on salsa and the BTS. They accomplish the desired effect, which is to allow the cloud kernel to boot without an initrd on common cloud instance types (specifically AWS Nitro instance types). While this is not the default behavior for any of our cloud images, it is simple for users to enable it on derivative images if they can benefit from the reduced boot time. If we want to support initrd-less booting on instances aside from Nitro instance types, that's great, and we should consider doing that. That would be much more beneficial to our users than reverting the change. > However this bug is about dhcp support. If there is no network device > support available, how does it do dhcp? I'd also argue that NIC drivers (in particular ena.ko, used on Nitro instances) should be left configured as modules, even if we do want to support initrd-less booting. AWS publishes an out-of-tree variant of the ENA driver that may be ahead of what's in the stable kernel tree, and some users may have a need to run that. noah signature.asc Description: PGP signature
Processed: Re: linux: Serial terminal for RPi 4 and p400 corrupted during bootup
Processing commands for cont...@bugs.debian.org: > found 986863 5.10.0-6-arm64 Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted during bootup The source 'linux' and version '5.10.0-6-arm64' do not appear to match any binary packages Marked as found in versions linux/5.10.0-6-arm64. > notfound 986863 5.8.0-3-arm64 Bug #986863 [src:linux] linux: Serial terminal for RPi 4 and p400 corrupted during bootup The source 'linux' and version '5.8.0-3-arm64' do not appear to match any binary packages Ignoring request to alter found versions of bug #986863 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 986863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986863: linux: Serial terminal for RPi 4 and p400 corrupted during bootup
found 986863 5.10.0-6-arm64 notfound 986863 5.8.0-3-arm64 thanks I blacklisted the vc4 module, and the console works reliably again, so that's a way to get a working system. I will blacklist in the images I produce, but this should not be needed for users to know! I am also trying with a kernel from the 5.8 series, as noted in the pseudo-headers to the BTS. The bug does not happen under kernel 5.8.0-3. I will try to more precisely pinpoint the place where it stopped working. Just to have as much information together -- If I boot without loading the vc4 module, then load it via modprobe, I get the following messages: root@rpi4-20210226:~# modprobe vc4 [ 71.824867] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi-0' already present! [ 71.835045] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4]) [ 71.869840] debugfs: Directory 'fef05700.hdmi' with parent 'vc4-hdmi-1' already present! [ 71.879230] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4]) [ 71.899628] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops [vc4]) [ 71.906197] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4]) [ 71.912815] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.920100] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.927301] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.934495] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 71.941850] fb0: switching to vc4drmfb from simple [ 71.947094] Console: switching to colour dummy device 80x25 [ 71.974285] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 [ 72.035497] Console: switching to colour frame buffer device 160x45 [ 72.041942] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device root@rpi4-20210226:~# After which, the console becomes unoperative. I tested this in the p400 as well, the behavior us the same. signature.asc Description: PGP signature
Processed: severity of 984873 is important
Processing commands for cont...@bugs.debian.org: > # probably fixed by #977694 in initramfs-tools > severity 984873 important Bug #984873 [src:linux] linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device) Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 984873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic
Hi $ ./scripts/get_maintainer.pl ./drivers/block/aoe/ Justin Sanders (supporter:ATA OVER ETHERNET (AOE) DRIVER) Jens Axboe (maintainer:BLOCK LAYER) linux-bl...@vger.kernel.org (open list:BLOCK LAYER) linux-ker...@vger.kernel.org (open list) Thanks for your help. The bug has been reported upstream: linux-kernel: https://lkml.org/lkml/2021/4/13/672 linux-block: https://lore.kernel.org/linux-block/b6aea08d-7190-e341-8780-13ba8e015...@vrvis.at/T/#u kernel.org bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212665 Regards, Valentin
linux-signed-i386_5.10.28+1_source.changes is NEW
Mapping sid to unstable. binary:acpi-modules-5.10.0-6-686-di is NEW. binary:acpi-modules-5.10.0-6-686-pae-di is NEW. binary:ata-modules-5.10.0-6-686-di is NEW. binary:ata-modules-5.10.0-6-686-pae-di is NEW. binary:btrfs-modules-5.10.0-6-686-di is NEW. binary:btrfs-modules-5.10.0-6-686-pae-di is NEW. binary:cdrom-core-modules-5.10.0-6-686-di is NEW. binary:cdrom-core-modules-5.10.0-6-686-pae-di is NEW. binary:crc-modules-5.10.0-6-686-di is NEW. binary:crc-modules-5.10.0-6-686-pae-di is NEW. binary:crypto-dm-modules-5.10.0-6-686-di is NEW. binary:crypto-dm-modules-5.10.0-6-686-pae-di is NEW. binary:crypto-modules-5.10.0-6-686-di is NEW. binary:crypto-modules-5.10.0-6-686-pae-di is NEW. binary:efi-modules-5.10.0-6-686-di is NEW. binary:efi-modules-5.10.0-6-686-pae-di is NEW. binary:event-modules-5.10.0-6-686-di is NEW. binary:event-modules-5.10.0-6-686-pae-di is NEW. binary:ext4-modules-5.10.0-6-686-di is NEW. binary:ext4-modules-5.10.0-6-686-pae-di is NEW. binary:f2fs-modules-5.10.0-6-686-di is NEW. binary:f2fs-modules-5.10.0-6-686-pae-di is NEW. binary:fat-modules-5.10.0-6-686-di is NEW. binary:fat-modules-5.10.0-6-686-pae-di is NEW. binary:fb-modules-5.10.0-6-686-di is NEW. binary:fb-modules-5.10.0-6-686-pae-di is NEW. binary:firewire-core-modules-5.10.0-6-686-di is NEW. binary:firewire-core-modules-5.10.0-6-686-pae-di is NEW. binary:fuse-modules-5.10.0-6-686-di is NEW. binary:fuse-modules-5.10.0-6-686-pae-di is NEW. binary:i2c-modules-5.10.0-6-686-di is NEW. binary:i2c-modules-5.10.0-6-686-pae-di is NEW. binary:input-modules-5.10.0-6-686-di is NEW. binary:input-modules-5.10.0-6-686-pae-di is NEW. binary:isofs-modules-5.10.0-6-686-di is NEW. binary:isofs-modules-5.10.0-6-686-pae-di is NEW. binary:jfs-modules-5.10.0-6-686-di is NEW. binary:jfs-modules-5.10.0-6-686-pae-di is NEW. binary:kernel-image-5.10.0-6-686-di is NEW. binary:kernel-image-5.10.0-6-686-pae-di is NEW. binary:linux-image-5.10.0-6-686 is NEW. binary:linux-image-5.10.0-6-686-pae is NEW. binary:linux-image-5.10.0-6-rt-686-pae is NEW. binary:loop-modules-5.10.0-6-686-di is NEW. binary:loop-modules-5.10.0-6-686-pae-di is NEW. binary:md-modules-5.10.0-6-686-di is NEW. binary:md-modules-5.10.0-6-686-pae-di is NEW. binary:mmc-core-modules-5.10.0-6-686-di is NEW. binary:mmc-core-modules-5.10.0-6-686-pae-di is NEW. binary:mmc-modules-5.10.0-6-686-di is NEW. binary:mmc-modules-5.10.0-6-686-pae-di is NEW. binary:mouse-modules-5.10.0-6-686-di is NEW. binary:mouse-modules-5.10.0-6-686-pae-di is NEW. binary:mtd-core-modules-5.10.0-6-686-di is NEW. binary:mtd-core-modules-5.10.0-6-686-pae-di is NEW. binary:multipath-modules-5.10.0-6-686-di is NEW. binary:multipath-modules-5.10.0-6-686-pae-di is NEW. binary:nbd-modules-5.10.0-6-686-di is NEW. binary:nbd-modules-5.10.0-6-686-pae-di is NEW. binary:nic-modules-5.10.0-6-686-di is NEW. binary:nic-modules-5.10.0-6-686-pae-di is NEW. binary:nic-pcmcia-modules-5.10.0-6-686-di is NEW. binary:nic-pcmcia-modules-5.10.0-6-686-pae-di is NEW. binary:nic-shared-modules-5.10.0-6-686-di is NEW. binary:nic-shared-modules-5.10.0-6-686-pae-di is NEW. binary:nic-usb-modules-5.10.0-6-686-di is NEW. binary:nic-usb-modules-5.10.0-6-686-pae-di is NEW. binary:nic-wireless-modules-5.10.0-6-686-di is NEW. binary:nic-wireless-modules-5.10.0-6-686-pae-di is NEW. binary:pata-modules-5.10.0-6-686-di is NEW. binary:pata-modules-5.10.0-6-686-pae-di is NEW. binary:pcmcia-modules-5.10.0-6-686-di is NEW. binary:pcmcia-modules-5.10.0-6-686-pae-di is NEW. binary:pcmcia-storage-modules-5.10.0-6-686-di is NEW. binary:pcmcia-storage-modules-5.10.0-6-686-pae-di is NEW. binary:ppp-modules-5.10.0-6-686-di is NEW. binary:ppp-modules-5.10.0-6-686-pae-di is NEW. binary:rfkill-modules-5.10.0-6-686-di is NEW. binary:rfkill-modules-5.10.0-6-686-pae-di is NEW. binary:sata-modules-5.10.0-6-686-di is NEW. binary:sata-modules-5.10.0-6-686-pae-di is NEW. binary:scsi-core-modules-5.10.0-6-686-di is NEW. binary:scsi-core-modules-5.10.0-6-686-pae-di is NEW. binary:scsi-modules-5.10.0-6-686-di is NEW. binary:scsi-modules-5.10.0-6-686-pae-di is NEW. binary:scsi-nic-modules-5.10.0-6-686-di is NEW. binary:scsi-nic-modules-5.10.0-6-686-pae-di is NEW. binary:serial-modules-5.10.0-6-686-di is NEW. binary:serial-modules-5.10.0-6-686-pae-di is NEW. binary:sound-modules-5.10.0-6-686-di is NEW. binary:sound-modules-5.10.0-6-686-pae-di is NEW. binary:speakup-modules-5.10.0-6-686-di is NEW. binary:speakup-modules-5.10.0-6-686-pae-di is NEW. binary:squashfs-modules-5.10.0-6-686-di is NEW. binary:squashfs-modules-5.10.0-6-686-pae-di is NEW. binary:udf-modules-5.10.0-6-686-di is NEW. binary:udf-modules-5.10.0-6-686-pae-di is NEW. binary:uinput-modules-5.10.0-6-686-di is NEW. binary:uinput-modules-5.10.0-6-686-pae-di is NEW. binary:usb-modules-5.10.0-6-686-di is NEW. binary:usb-modules-5.10.0-6-686-pae-di is NEW. binary:usb-serial-modules-5.10.0-6-686-di is NEW. binary:usb-serial-modules-5.10.0-6-686-pae-di is NEW. binary:usb-storage-modules-5.10.0-6-686-di is NEW. binary:usb-stora
Processing of linux-signed-i386_5.10.28+1_source.changes
linux-signed-i386_5.10.28+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_5.10.28+1.dsc linux-signed-i386_5.10.28+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#986887: linux-image-5.10.0-5-amd64: mpt3sas driver fails to initialize drives on LSI SAS2116 chipset without a queue depth workaround
Package: src:linux
Version: 5.10.26-1
Severity: important
Tags: upstream
X-Debbugs-Cc: luke.ree...@gmail.com
Dear Maintainer,
I've upgraded from Buster to Bullseye and my external drive array using an LSI
SAS2116 chipset (and the mpt3sas driver) stopped detecting all drives. There
were no error messages discernable but in the output of lspci -vv there was now
a missing line about "driver in use". After a bunch of digging I found other
people had mitigated this issue by clamping down the maximum queue depth
configured for the card. Adding the kernel parameter
"mpt3sas.max_queue_depth=1" made all the drives appear again after a reboot.
Note that this report is tained with ZFS but I also tested with a clean boot
and no dkms-built modules loaded to verify the issue.
-- Package-specific info:
** Version:
Linux version 5.10.0-5-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP
Debian 5.10.26-1 (2021-03-27)
** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-5-amd64
root=UUID=4a6cca79-4f72-4c12-b6e4-3e3aa93f8562 ro mpt3sas.max_queue_depth=1
i915.force_probe=4c8b
** Tainted: PUOE (12353)
* proprietary module was loaded
* taint requested by userspace application
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: To Be Filled By O.E.M.
product_name: To Be Filled By O.E.M.
product_version: To Be Filled By O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends International, LLC.
bios_version: P1.70
board_vendor: ASRock
board_name: B560M Pro4
board_version:
** Loaded modules:
xt_nat
xt_tcpudp
veth
btrfs
blake2b_generic
ufs
qnx4
hfsplus
hfs
cdrom
minix
msdos
jfs
xfs
dm_mod
xt_conntrack
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack_netlink
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
xfrm_user
xfrm_algo
nft_counter
xt_addrtype
nft_compat
nf_tables
br_netfilter
nfnetlink
overlay
rfkill
bridge
stp
llc
binfmt_misc
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
kvm_intel
iTCO_wdt
kvm
intel_pmc_bxt
iTCO_vendor_support
intel_wmi_thunderbolt
wmi_bmof
efi_pstore
pcspkr
watchdog
ee1004
nls_ascii
nls_cp437
vfat
fat
zfs(POE)
zunicode(POE)
zzstd(OE)
zlua(OE)
zavl(POE)
icp(POE)
zcommon(POE)
znvpair(POE)
spl(OE)
joydev
mei_me
mei
sg
evdev
intel_pmc_core
acpi_pad
acpi_tad
hwmon_vid
coretemp
msr
fuse
configfs
sunrpc
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
vfio_pci
vfio_virqfd
vfio_iommu_type1
vfio
irqbypass
sd_mod
ses
t10_pi
enclosure
crc_t10dif
crct10dif_generic
hid_logitech_hidpp
hid_logitech_dj
hid_generic
usbhid
hid
i915
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
i2c_algo_bit
ahci
drm_kms_helper
libahci
xhci_pci
aesni_intel
xhci_hcd
cec
libaes
mpt3sas
libata
drm
e1000e
crypto_simd
raid_class
scsi_transport_sas
usbcore
scsi_mod
ptp
cryptd
glue_helper
i2c_i801
pps_core
i2c_smbus
usb_common
wmi
video
button
** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4c53] (rev 01)
Subsystem: ASRock Incorporation Device [1849:4c53]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- (32-bit, non-prefetchable)
Expansion ROM at
00:01.0 PCI bridge [0604]: Intel Corporation Device [8086:4c01] (rev 01)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4c8b]
(rev 04) (prog-if 00 [VGA controller])
Subsystem: ASRock Incorporation Device [1849:4c8b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: i915
Kernel modules: i915
00:08.0 System peripheral [0880]: Intel Corporation Device [8086:4c11] (rev 01)
Subsystem: ASRock Incorporation Device [1849:4c11]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:43ed] (rev 11)
(prog-if 30 [XHCI])
Subsystem: ASRock Inc
Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic
Hi Valentin, On Tue, Apr 13, 2021 at 01:42:49PM +0200, Valentin Kleibel wrote: > Hi Salvatore, > > > Thanks for the report. I assume you can reproduce the issue as well > > with 5.10.28-1 in unstable? > > I did not test this before as the aoe driver code was not changed at all in > the last 7 months. I can now report that the behavior is exactly the same > running the kernel 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 from unstable. Ack thanks for confirming that as well. > > > Can you report the issue to upstream and loop in the bug? > > Yes but i did not do this before. From what i can find i'd report to > the IO/STorage - Other section in bugzilla [1] and mail to the listed > maintainer "Justin Sanders" . Is that the way to go or > did i forget something? You can run the get_maintainer.pl script to get information where to report the issue, it gives me: $ ./scripts/get_maintainer.pl ./drivers/block/aoe/ Justin Sanders (supporter:ATA OVER ETHERNET (AOE) DRIVER) Jens Axboe (maintainer:BLOCK LAYER) linux-bl...@vger.kernel.org (open list:BLOCK LAYER) linux-ker...@vger.kernel.org (open list) So yes, this is the right approach, mail to Justin and Jens, keeping the mailinglist in the loop. Let me know if you need help here further! Regards, Salvatore
Bug#986881: iw: Incorporate useful bits of crda?
Package: iw Version: 5.9-3 Severity: wishlist X-Debbugs-Cc: debian-kernel@lists.debian.org Earlier I filed bug #972994 to remove the Recommends on crda, which was then fixed, thanks. Today I got an update of network-manager which fixed bug #973241 for which the request and fix was similar to #972994. In that bug Ben Hutchings got looped in, hence debian-kernel ML in CC, in which Ben said the following: "I think you can safely drop it for bullseye. In addition to crda itself, the package also contains a udev rule for setting the regulatory domain that may still be useful, but it is not generally needed." I also found bug #920740 titled "Should crda be shipped in buster?" I think it was still needed for Buster, but questionable wrt Bullseye. I also noticed that crda's homepage gives a 404. I don't really know/understand how/what/when crda did that could still be useful/needed, but Ben's comment indicates that at least the udev rule may still be useful. Looking into crda's package I found /etc/default/crda with which you can set a default regulatory domain. And in /lib/crda/setregdomain it uses that file/value to call 'iw reg set ""'. The udev rule calls the crda binary btw, so I don't know if 'setregdomain' is actually called. This bug is basically to ensure that the useful part of crda doesn't get lost. I'm assuming that the maintainers who'll read this bug can determine if/what/how/where the useful part should be preserved. Maybe the 'wireless-regdb' package is more appropriate, if so feel free to reassign. And if nothing needs to be preserved, you can close it. I filed it against the 'iw' package as I saw the 'iw reg set' call and 'wireless-regdb' doesn't (yet?) have a dependency on 'iw'. Cheers, Diederik -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iw depends on: ii libc6 2.31-11 ii libnl-3-200 3.4.0-1+b1 ii libnl-genl-3-200 3.4.0-1+b1 Versions of packages iw recommends: ii wireless-regdb 2020.04.29-2 iw suggests no packages. -- no debconf information
Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic
Hi Salvatore, Thanks for the report. I assume you can reproduce the issue as well with 5.10.28-1 in unstable? I did not test this before as the aoe driver code was not changed at all in the last 7 months. I can now report that the behavior is exactly the same running the kernel 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 from unstable. Can you report the issue to upstream and loop in the bug? Yes but i did not do this before. From what i can find i'd report to the IO/STorage - Other section in bugzilla [1] and mail to the listed maintainer "Justin Sanders" . Is that the way to go or did i forget something? Regards, Valentin [1] https://bugzilla.kernel.org/buglist.cgi?component=Other&product=IO%2FStorage&resolution=---
Processed: Re: Bug#986822: installation-reports: Debian 11 Breaks Analague sound on Thinkpad Helix 2nd Gen
Processing control commands: > reassign -1 src:linux Bug #986822 [installation-reports] installation-reports: Debian 11 Breaks Analague sound on Thinkpad Helix 2nd Gen Bug reassigned from package 'installation-reports' to 'src:linux'. Ignoring request to alter found versions of bug #986822 to the same values previously set Ignoring request to alter fixed versions of bug #986822 to the same values previously set > retitle -1 Missing support for Haswell/Broadwell platforms with I2S codec > present Bug #986822 [src:linux] installation-reports: Debian 11 Breaks Analague sound on Thinkpad Helix 2nd Gen Changed Bug title to 'Missing support for Haswell/Broadwell platforms with I2S codec present' from 'installation-reports: Debian 11 Breaks Analague sound on Thinkpad Helix 2nd Gen'. -- 986822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#986822: installation-reports: Debian 11 Breaks Analague sound on Thinkpad Helix 2nd Gen
Processing control commands: > reassign -1 src:linux Bug #986822 [src:linux] Missing support for Haswell/Broadwell platforms with I2S codec present Ignoring request to reassign bug #986822 to the same package > retitle -1 Missing support for Haswell/Broadwell platforms with I2S codec > present Bug #986822 [src:linux] Missing support for Haswell/Broadwell platforms with I2S codec present Ignoring request to change the title of bug#986822 to the same title -- 986822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986822: installation-reports: Debian 11 Breaks Analague sound on Thinkpad Helix 2nd Gen
Control: reassign -1 src:linux Control: retitle -1 Missing support for Haswell/Broadwell platforms with I2S codec present Hi, Le 2021-04-12 13:40, dekks herton a écrit : > Comments/Problems: > > No analogue sound on Tablet from Broadwell-U from intel smart sound chipset - > hw works on Buster but breaks on Bullseye > Card0 on Buster no longer detected on Bullseye Due to various bugs, Intel has rewritten the audio driver for Haswell/Broadwell in Linux 5.10. The bad news is that our kernel configuration does not seem to provide the necessary bits to enable support for the Intel Audio DSP on Haswell U/Y and Broadwell U. I'm willing to provide a patch to fix this but the release of Bullseye is approaching really fast so we might have to wait for the first point release. > Tried installing Intel SOF drivers/firmware to no effect, forcing > snd_hda_intel > via modprobe conf doesn't work either > Broadwell-U works eith with HDA or SOF drivers theoretically. > There is record of a kernel compilation flag to enable SOF functionality > SND_SOC_SOF_BROADWELL_SUPPORT=Y breaking legacy and snd_hda_intel too. We do not support SOF on Broadwell. This is even not recommended by upstream due to some limitations related to DMA and suspend-resume so installing firmware-sof-signed is of no use in your case. Cheers, Vincent signature.asc Description: PGP signature
Bug#981586: Bullseye armhf kernel for Raspberry Pi 4b does not boot
Control: tags -1 + wontfix patch
From: Der_Martin
Date: Fri, 9 Apr 2021 10:45:13 +0200
> On 16 Mar 2021 someone published a solution to that bug. Obviously nobody
> cares?
Bug #981586 is a duplicate of #971059.
#981586 is unlikely to get fixed because
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971059#12
So I add "wontfix".
Only
CONFIG_PCIE_BRCMSTB=m
is sufficient for linux-image-armmp-lpae to boot on RPi4B 8GB.
The following script on Debian Bullseye armhf (in a container or a VM)
builds a kernel bootable from USB MSD on RPi4B 8GB.
#!/bin/sh
set -ex
KVAR=5.10.29
wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-${KVAR}.tar.xz
tar Jxf linux-${KVAR}.tar.xz
apt-get -q -y install linux-config-5.10 build-essential libncurses-dev fakeroot
dpkg-dev
apt-get -q -y build-dep linux
cd linux-${KVAR}
xzcat /usr/src/linux-config-5.10/config.armhf_none_armmp-lpae.xz >.config
ARCH=arm
export ARCH
echo 'CONFIG_PCIE_BRCMSTB=m' >>.config
make oldconfig
nice -19 make -j 12 bindeb-pkg
Best regards, Ryutaroh Matsumoto
Processed: Re: Bullseye armhf kernel for Raspberry Pi 4b does not boot
Processing control commands: > tags -1 + wontfix patch Bug #981586 [src:linux] Bullseye armhf kernel for Raspberry Pi 4b does not boot Ignoring request to alter tags of bug #981586 to the same tags previously set -- 981586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bullseye armhf kernel for Raspberry Pi 4b does not boot
Processing control commands: > tags -1 + wontfix patch Bug #981586 [src:linux] Bullseye armhf kernel for Raspberry Pi 4b does not boot Added tag(s) patch and wontfix. -- 981586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986741: Please enable CONFIG_IP_PNP_DHCP=y in cloud image
On Mon, Apr 12, 2021 at 10:30:49PM -0700, Josh Triplett wrote: > On Tue, Apr 13, 2021 at 06:39:26AM +0200, Bastian Blank wrote: > > Where was that discussed? > It was discussed in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759 > , with responses from both Ben and Noah. As this is incomplete at best, I intend to revert that change. Otherwise it at least needs in addition: - hyperv pci support (for nvme), - hyperv block and - virtio-scsi. However this bug is about dhcp support. If there is no network device support available, how does it do dhcp? Bastian -- You can't evaluate a man by logic alone. -- McCoy, "I, Mudd", stardate 4513.3
Bug#986156: marked as done (linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel)
Your message dated Tue, 13 Apr 2021 11:03:55 +0200 with message-id and subject line Re: Bug#986156: linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel has caused the Debian Bug report #986156, regarding linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.10.24-1 Severity: important Dear Maintainer, * What led up to the situation? I used the tool debos https://github.com/go-debos/debos to create a debian image on my machine. debos uses qemu to setup an install environment for debian. After a while the process got stucked. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? I got a kernel warning Mar 30 15:45:10 hpjp kernel: [ cut here ] Mar 30 15:45:10 hpjp kernel: WARNING: CPU: 3 PID: 339240 at fs/eventfd.c:74 eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: Modules linked in: hid_plantronics nls_utf8 cifs libdes rpcsec_gss_krb5 nfsv4 dns_resolver nfs nfs_ssc fscache nfsd au> Mar 30 15:45:10 hpjp kernel: cpufreq_ondemand snd_soc_dmic cmac snd_sof_pci algif_hash snd_sof_intel_byt algif_skcipher snd_sof_intel_ipc af_alg s> Mar 30 15:45:10 hpjp kernel: videobuf2_v4l2 hid_sensor_als snd r8152 hid_sensor_trigger mii soundcore drbg videobuf2_common cfg80211 hid_sensor_ii> Mar 30 15:45:10 hpjp kernel: intel_ish_ipc i2c_i801 crct10dif_common glue_helper intel_lpss i2c_hid i2c_smbus idma64 usb_common intel_ishtp hid wm> Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 Mar 30 15:45:10 hpjp kernel: check_preemption_disabled: 44 callbacks suppressed Mar 30 15:45:10 hpjp kernel: BUG: using smp_processor_id() in preemptible [] code: qemu-system-x86/339240 Mar 30 15:45:10 hpjp kernel: caller is print_stop_info+0x1b/0x40 Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 Mar 30 15:45:10 hpjp kernel: Call Trace: Mar 30 15:45:10 hpjp kernel: dump_stack+0x6b/0x83 Mar 30 15:45:10 hpjp kernel: check_preemption_disabled+0xcd/0xd0 Mar 30 15:45:10 hpjp kernel: print_stop_info+0x1b/0x40 Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: show_regs+0x15/0x50 Mar 30 15:45:10 hpjp kernel: __warn+0x7d/0xb0 Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: report_bug+0x9a/0xc0 Mar 30 15:45:10 hpjp kernel: handle_bug+0x35/0x80 Mar 30 15:45:10 hpjp kernel: exc_invalid_op+0x14/0x70 Mar 30 15:45:10 hpjp kernel: asm_exc_invalid_op+0x12/0x20 Mar 30 15:45:10 hpjp kernel: RIP: 0010:eventfd_signal+0x7e/0x90 Mar 30 15:45:10 hpjp kernel: Code: 01 00 00 00 be 03 00 00 00 4c 89 ef e8 db b0 db ff 65 ff 0d 74 e4 0f 7d 4c 89 ef e8 cc bd 5b 00 4c 89 e0 5b 5d 4> Mar 30 15:45:10 hpjp kernel: RSP: 0018:b81b91d47d50 EFLAGS: 00010202 Mar 30 15:45:10 hpjp kernel: RAX: 0001 RBX: 9da5c68d4000 RCX: Mar 30 15:45:10 hpjp kernel: RDX: fe007000 RSI: 0001 RDI: 9da5c4c6fb40 Mar 30 15:45:10 hpjp kernel: RBP: b81b91d47db0 R08: R09: fe007000 Mar 30 15:45:10 hpjp kernel: R10: R11: R12: 0040 Mar 30 15:45:10 hpjp kernel: R13: 9da7be878000 R14: R15: 9da7be878038 Mar 30 15:45:10 hpjp kernel: ioeventfd_write+0x51/0x80 [kvm] Mar 30 15:45:10 hpjp kernel: __kvm_io_bus_write+0x88/0xb0 [kvm] Mar 30 15:45:10 hpjp kernel: kvm_io_bus_write+0x54/0x80 [kvm] Mar 30 15:45:10 hpjp kernel: handle_ept_misconfig+0x45/0x130 [kvm_intel] Mar 30 15:45:10 hpjp kernel: kvm_arch_vcpu_ioctl_run+0xc9d/0x1780 [kvm] Mar 30 15:45:10 hpjp kernel: kvm_vcpu_ioctl+0x239/0x5f0 [kvm] Mar 30 15:45:10 hpjp kernel: __x64_sys_ioctl+0x83/0xb0 Mar 30 15:45:10 hpjp kernel: do_syscall_64+0x33/0x80 Mar 30 15:45:10 hpjp kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Mar 30 15:45:10 hpjp kernel: RIP: 0033:0x7f10d88fecc7 Mar 30 15:45:10 hpjp kernel: Code:
Bug#986156: linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel
Source: linux Source-Version: 5.10.26-1 Control: tags -1 - moreinfo Hi, On Tue, Apr 13, 2021 at 10:25:07AM +0200, Dr. Johann Pfefferl wrote: > Hi, > > Salvatore Bonaccorso wrote: > > Control: tags -1 + moreinfo > > > > Hi, > > > > On Tue, Mar 30, 2021 at 04:40:18PM +0200, Dr. Johann Pfefferl wrote: > > > Package: src:linux > > > Version: 5.10.24-1 > > > Severity: important > > > > > > Dear Maintainer, > > > > > >* What led up to the situation? > > >I used the tool debos https://github.com/go-debos/debos to create a > > >debian image on my machine. debos uses qemu to setup an install > > >environment for debian. After a while the process got stucked. > > >* What exactly did you do (or not do) that was effective (or > > > ineffective)? > > >* What was the outcome of this action? > > >I got a kernel warning > > > Mar 30 15:45:10 hpjp kernel: [ cut here ] > > > Mar 30 15:45:10 hpjp kernel: WARNING: CPU: 3 PID: 339240 at > > > fs/eventfd.c:74 eventfd_signal+0x7e/0x90 > > > Mar 30 15:45:10 hpjp kernel: Modules linked in: hid_plantronics nls_utf8 > > > cifs libdes rpcsec_gss_krb5 nfsv4 dns_resolver nfs nfs_ssc fscache nfsd > > > au> > > > Mar 30 15:45:10 hpjp kernel: cpufreq_ondemand snd_soc_dmic cmac > > > snd_sof_pci algif_hash snd_sof_intel_byt algif_skcipher snd_sof_intel_ipc > > > af_alg s> > > > Mar 30 15:45:10 hpjp kernel: videobuf2_v4l2 hid_sensor_als snd r8152 > > > hid_sensor_trigger mii soundcore drbg videobuf2_common cfg80211 > > > hid_sensor_ii> > > > Mar 30 15:45:10 hpjp kernel: intel_ish_ipc i2c_i801 crct10dif_common > > > glue_helper intel_lpss i2c_hid i2c_smbus idma64 usb_common intel_ishtp > > > hid wm> > > > Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 > > > Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 > > > Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 > > > Notebook PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 > > > Mar 30 15:45:10 hpjp kernel: check_preemption_disabled: 44 callbacks > > > suppressed > > > Mar 30 15:45:10 hpjp kernel: BUG: using smp_processor_id() in preemptible > > > [] code: qemu-system-x86/339240 > > > Mar 30 15:45:10 hpjp kernel: caller is print_stop_info+0x1b/0x40 > > > Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 > > > Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 > > > Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 > > > Notebook PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 > > > Mar 30 15:45:10 hpjp kernel: Call Trace: > > > Mar 30 15:45:10 hpjp kernel: dump_stack+0x6b/0x83 > > > Mar 30 15:45:10 hpjp kernel: check_preemption_disabled+0xcd/0xd0 > > > Mar 30 15:45:10 hpjp kernel: print_stop_info+0x1b/0x40 > > > Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 > > > Mar 30 15:45:10 hpjp kernel: show_regs+0x15/0x50 > > > Mar 30 15:45:10 hpjp kernel: __warn+0x7d/0xb0 > > > Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 > > > Mar 30 15:45:10 hpjp kernel: report_bug+0x9a/0xc0 > > > Mar 30 15:45:10 hpjp kernel: handle_bug+0x35/0x80 > > > Mar 30 15:45:10 hpjp kernel: exc_invalid_op+0x14/0x70 > > > Mar 30 15:45:10 hpjp kernel: asm_exc_invalid_op+0x12/0x20 > > > Mar 30 15:45:10 hpjp kernel: RIP: 0010:eventfd_signal+0x7e/0x90 > > > Mar 30 15:45:10 hpjp kernel: Code: 01 00 00 00 be 03 00 00 00 4c 89 ef e8 > > > db b0 db ff 65 ff 0d 74 e4 0f 7d 4c 89 ef e8 cc bd 5b 00 4c 89 e0 5b 5d 4> > > > Mar 30 15:45:10 hpjp kernel: RSP: 0018:b81b91d47d50 EFLAGS: 00010202 > > > Mar 30 15:45:10 hpjp kernel: RAX: 0001 RBX: 9da5c68d4000 > > > RCX: > > > Mar 30 15:45:10 hpjp kernel: RDX: fe007000 RSI: 0001 > > > RDI: 9da5c4c6fb40 > > > Mar 30 15:45:10 hpjp kernel: RBP: b81b91d47db0 R08: > > > R09: fe007000 > > > Mar 30 15:45:10 hpjp kernel: R10: R11: > > > R12: 0040 > > > Mar 30 15:45:10 hpjp kernel: R13: 9da7be878000 R14: > > > R15: 9da7be878038 > > > Mar 30 15:45:10 hpjp kernel: ioeventfd_write+0x51/0x80 [kvm] > > > Mar 30 15:45:10 hpjp kernel: __kvm_io_bus_write+0x88/0xb0 [kvm] > > > Mar 30 15:45:10 hpjp kernel: kvm_io_bus_write+0x54/0x80 [kvm] > > > Mar 30 15:45:10 hpjp kernel: handle_ept_misconfig+0x45/0x130 [kvm_intel] > > > Mar 30 15:45:10 hpjp kernel: kvm_arch_vcpu_ioctl_run+0xc9d/0x1780 [kvm] > > > Mar 30 15:45:10 hpjp kernel: kvm_vcpu_ioctl+0x239/0x5f0 [kvm] > > > Mar 30 15:45:10 hpjp kernel: __x64_sys_ioctl+0x83/0xb0 > > > Mar 30 15:45:10 hpjp kernel: do_syscall_64+0x33/0x80 > > > Mar 30 15:45:10 hpjp kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 > > > Mar 30 15:45:10 hpjp kernel: RIP: 0033:0x7f10d88fecc7 > > > Mar 30 15:45:10 hpjp kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 > > > 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 0> > > >
Bug#986156: linux-image-5.10.0-5-rt-amd64: qemu/kvm caused trouble on the 5.10 PREMPT_RT kernel
Hi, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > Hi, > > On Tue, Mar 30, 2021 at 04:40:18PM +0200, Dr. Johann Pfefferl wrote: > > Package: src:linux > > Version: 5.10.24-1 > > Severity: important > > > > Dear Maintainer, > > > >* What led up to the situation? > >I used the tool debos https://github.com/go-debos/debos to create a > >debian image on my machine. debos uses qemu to setup an install > >environment for debian. After a while the process got stucked. > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > >* What was the outcome of this action? > >I got a kernel warning > > Mar 30 15:45:10 hpjp kernel: [ cut here ] > > Mar 30 15:45:10 hpjp kernel: WARNING: CPU: 3 PID: 339240 at fs/eventfd.c:74 > > eventfd_signal+0x7e/0x90 > > Mar 30 15:45:10 hpjp kernel: Modules linked in: hid_plantronics nls_utf8 > > cifs libdes rpcsec_gss_krb5 nfsv4 dns_resolver nfs nfs_ssc fscache nfsd au> > > Mar 30 15:45:10 hpjp kernel: cpufreq_ondemand snd_soc_dmic cmac > > snd_sof_pci algif_hash snd_sof_intel_byt algif_skcipher snd_sof_intel_ipc > > af_alg s> > > Mar 30 15:45:10 hpjp kernel: videobuf2_v4l2 hid_sensor_als snd r8152 > > hid_sensor_trigger mii soundcore drbg videobuf2_common cfg80211 > > hid_sensor_ii> > > Mar 30 15:45:10 hpjp kernel: intel_ish_ipc i2c_i801 crct10dif_common > > glue_helper intel_lpss i2c_hid i2c_smbus idma64 usb_common intel_ishtp hid > > wm> > > Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 > > Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 > > Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook > > PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 > > Mar 30 15:45:10 hpjp kernel: check_preemption_disabled: 44 callbacks > > suppressed > > Mar 30 15:45:10 hpjp kernel: BUG: using smp_processor_id() in preemptible > > [] code: qemu-system-x86/339240 > > Mar 30 15:45:10 hpjp kernel: caller is print_stop_info+0x1b/0x40 > > Mar 30 15:45:10 hpjp kernel: CPU: 3 PID: 339240 Comm: qemu-system-x86 > > Tainted: GW 5.10.0-5-rt-amd64 #1 Debian 5.10.24-1 > > Mar 30 15:45:10 hpjp kernel: Hardware name: HP HP EliteBook 840 G7 Notebook > > PC/8723, BIOS S70 Ver. 01.04.02 01/18/2021 > > Mar 30 15:45:10 hpjp kernel: Call Trace: > > Mar 30 15:45:10 hpjp kernel: dump_stack+0x6b/0x83 > > Mar 30 15:45:10 hpjp kernel: check_preemption_disabled+0xcd/0xd0 > > Mar 30 15:45:10 hpjp kernel: print_stop_info+0x1b/0x40 > > Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 > > Mar 30 15:45:10 hpjp kernel: show_regs+0x15/0x50 > > Mar 30 15:45:10 hpjp kernel: __warn+0x7d/0xb0 > > Mar 30 15:45:10 hpjp kernel: ? eventfd_signal+0x7e/0x90 > > Mar 30 15:45:10 hpjp kernel: report_bug+0x9a/0xc0 > > Mar 30 15:45:10 hpjp kernel: handle_bug+0x35/0x80 > > Mar 30 15:45:10 hpjp kernel: exc_invalid_op+0x14/0x70 > > Mar 30 15:45:10 hpjp kernel: asm_exc_invalid_op+0x12/0x20 > > Mar 30 15:45:10 hpjp kernel: RIP: 0010:eventfd_signal+0x7e/0x90 > > Mar 30 15:45:10 hpjp kernel: Code: 01 00 00 00 be 03 00 00 00 4c 89 ef e8 > > db b0 db ff 65 ff 0d 74 e4 0f 7d 4c 89 ef e8 cc bd 5b 00 4c 89 e0 5b 5d 4> > > Mar 30 15:45:10 hpjp kernel: RSP: 0018:b81b91d47d50 EFLAGS: 00010202 > > Mar 30 15:45:10 hpjp kernel: RAX: 0001 RBX: 9da5c68d4000 > > RCX: > > Mar 30 15:45:10 hpjp kernel: RDX: fe007000 RSI: 0001 > > RDI: 9da5c4c6fb40 > > Mar 30 15:45:10 hpjp kernel: RBP: b81b91d47db0 R08: > > R09: fe007000 > > Mar 30 15:45:10 hpjp kernel: R10: R11: > > R12: 0040 > > Mar 30 15:45:10 hpjp kernel: R13: 9da7be878000 R14: > > R15: 9da7be878038 > > Mar 30 15:45:10 hpjp kernel: ioeventfd_write+0x51/0x80 [kvm] > > Mar 30 15:45:10 hpjp kernel: __kvm_io_bus_write+0x88/0xb0 [kvm] > > Mar 30 15:45:10 hpjp kernel: kvm_io_bus_write+0x54/0x80 [kvm] > > Mar 30 15:45:10 hpjp kernel: handle_ept_misconfig+0x45/0x130 [kvm_intel] > > Mar 30 15:45:10 hpjp kernel: kvm_arch_vcpu_ioctl_run+0xc9d/0x1780 [kvm] > > Mar 30 15:45:10 hpjp kernel: kvm_vcpu_ioctl+0x239/0x5f0 [kvm] > > Mar 30 15:45:10 hpjp kernel: __x64_sys_ioctl+0x83/0xb0 > > Mar 30 15:45:10 hpjp kernel: do_syscall_64+0x33/0x80 > > Mar 30 15:45:10 hpjp kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 > > Mar 30 15:45:10 hpjp kernel: RIP: 0033:0x7f10d88fecc7 > > Mar 30 15:45:10 hpjp kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 > > 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 0> > > Mar 30 15:45:10 hpjp kernel: RSP: 002b:7f10d5d37508 EFLAGS: 0246 > > ORIG_RAX: 0010 > > Mar 30 15:45:10 hpjp kernel: RAX: ffda RBX: ae80 > > RCX: 7f10d88fecc7 > > Mar 30 15:45:10 hpjp kernel: RDX: RSI: ae80 > > RDI: 000b > > Mar 30 15
