Bug#1028368: dahdi-dkms fails to install after arrival of 6.1.0-1 kernel
hi, you're thinking about swapping to this repo? sounds good here... :) thanks, cs On 1/14/23 10:11, Jonas Smedegaard wrote: Quoting m...@freemail.hu (2023-01-14 09:46:18) would be nice, this is the package that provides support for my factory new osmocom e1 usb dongle... but if you cannot, then proceed removing the package, as you see appropriate... Seems there is some recent work for kernel 6.1 likely useful here: https://gitea.osmocom.org/retronetworking/dahdi-linux Jonas
Bug#1028368: dahdi-dkms fails to install after arrival of 6.1.0-1 kernel
hi, would be nice, this is the package that provides support for my factory new osmocom e1 usb dongle... but if you cannot, then proceed removing the package, as you see appropriate... thanks, cs On 1/14/23 09:39, Salvatore Bonaccorso wrote: Hi, According to https://github.com/asterisk/dahdi-linux/issues/16#issuecomment-1354772551 dahdi-linux upstream is basically absent. The base for src:dahdi-dkms is as well quite old. Does it still make sense to ship dahdi-linux in bookworm? Regards, Salvatore
Bug#1028368: dahdi-dkms fails to install after arrival of 6.1.0-1 kernel
Package: dahdi-dkms Version: 1:2.11.1.0.20170917~dfsg-8 Severity: normal Dear Maintainer, as title says thanks, cs mc36@noti:~$ sudo apt install dahdi-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libecj-java libtonezone2.0 linux-headers-6.0.0-5-common Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: dahdi-linux The following NEW packages will be installed: dahdi-dkms dahdi-linux 0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/859 kB of archives. After this operation, 6,213 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package dahdi-dkms. (Reading database ... 801204 files and directories currently installed.) Preparing to unpack .../dahdi-dkms_1%3a2.11.1.0.20170917~dfsg-8_all.deb ... Unpacking dahdi-dkms (1:2.11.1.0.20170917~dfsg-8) ... Selecting previously unselected package dahdi-linux. Preparing to unpack .../dahdi-linux_1%3a2.11.1.0.20170917~dfsg-8_all.deb ... Unpacking dahdi-linux (1:2.11.1.0.20170917~dfsg-8) ... Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-8) ... Loading new dahdi-2.11.1.0.20170917~dfsg-8 DKMS files... Building for 6.1.0-1-amd64 Building initial module for 6.1.0-1-amd64 Error! Bad return status for module build on kernel: 6.1.0-1-amd64 (x86_64) Consult /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/make.log for more information. dpkg: error processing package dahdi-dkms (--configure): installed dahdi-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of dahdi-linux: dahdi-linux depends on dahdi-dkms | dahdi-source; however: Package dahdi-dkms is not configured yet. Package dahdi-source is not installed. dpkg: error processing package dahdi-linux (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: dahdi-dkms dahdi-linux E: Sub-process /usr/bin/dpkg returned an error code (1) mc36@noti:~$ cat /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/make.log DKMS make.log for dahdi-2.11.1.0.20170917~dfsg-8 for kernel 6.1.0-1-amd64 (x86_64) Tue Jan 10 04:47:05 AM CET 2023 make -C /lib/modules/6.1.0-1-amd64/build KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/include DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-6.1.0-1-amd64' CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-8/build/dri
Bug#1027955: samba cannot be installed/upgraded
Package: samba Version: 2:4.17.4+dfsg-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? my regular dist-upgrade wants to remove samba for a while now... * What exactly did you do (or not do) that was effective (or ineffective)? sudo apt dist-upgrade * What was the outcome of this action? mc36@noti:~$ sudo apt install samba Reading package lists... Done Building dependency tree... Done Reading state information... Done samba is already the newest version (2:4.17.4+dfsg-2). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-samba : Depends: python3-tdb but it is not going to be installed E: Unable to correct problems, you have held broken packages. mc36@noti:~$ * What outcome did you expect instead? nothing special as usual... :) *** End of the template - remove these template lines *** -- Package-specific info: * /etc/samba/smb.conf present, and attached * /var/lib/samba/dhcp.conf present, and attached -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii init-system-helpers1.65.2 ii libbsd00.11.7-1 ii libc6 2.36-7 ii libcups2 2.4.2-1+b2 ii libgnutls303.7.8-4 ii libldap-2.5-0 2.5.13+dfsg-2+b1 ii libldb22:2.6.1+samba4.17.4+dfsg-2 ii libpam-modules 1.5.2-6 ii libpam-runtime 1.5.2-6 ii libpopt0 1.19+dfsg-1 ii libtalloc2 2.3.4-2 ii libtasn1-6 4.19.0-2 ii libtdb11.4.7-2 ii libtevent0 0.13.0-2 ii lsb-base 11.5 ii passwd 1:4.13+dfsg1-1 ii procps 2:4.0.2-3 ii python33.10.6-3+b1 ii python3-dnspython 2.2.1-2 ii python3-samba 2:4.17.4+dfsg-2 ii samba-common 2:4.17.4+dfsg-2 ii samba-common-bin 2:4.17.4+dfsg-2 ii samba-libs 2:4.17.4+dfsg-2 ii sysvinit-utils [lsb-base] 3.06-2 ii tdb-tools 1.4.7-2+b1 Versions of packages samba recommends: ii attr1:2.5.1-3 ii logrotate 3.21.0-1 ii python3-markdown3.4.1-2 ii samba-ad-provision 2:4.17.4+dfsg-2 ii samba-dsdb-modules 2:4.17.4+dfsg-2 ii samba-vfs-modules 2:4.17.4+dfsg-2 Versions of packages samba suggests: pn bind9 pn bind9utils pn ctdb pn ldb-tools ii ntp 1:4.2.8p15+dfsg-2~1.2.1+dfsg1-8 pn ufw pn winbind -- no debconf information # # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which # are not shown in this example # # Some options that are often worth tuning have been included as # commented-out examples in this file. # - When such options are commented with ";", the proposed setting #differs from the default Samba behaviour # - When commented with "#", the proposed setting is the default #behaviour of Samba but the option is considered important #enough to be mentioned here # # NOTE: Whenever you modify this file you should run the command # "testparm" to check that you have not made any basic syntactic # errors. #=== Global Settings === [global] ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP Networking # The specific set of interfaces / networks to bind to # This can be either the interface name or an IP address/netmask; # interface names are normally preferred ; interfaces = 127.0.0.0/8 eth0 # Only bind to the named interfaces and/or networks; you must use the # 'interfaces' option above to use this. # It is recommended that you enable this feature if your Samba machine is # not protected by a firewall or is a firewall itself. However, this # option cannot handle dynamic or non-broadcast interfaces correctly. ; bind interfaces only = ye
Bug#1013952: qemu: issue passing prop_array parameter
hi, On 6/28/22 07:01, Michael Tokarev wrote: It is much better to bring this issue upstream instead of using Debian BTS. okk, i'll do so... thanks, cs
Bug#1013952: qemu: issue passing prop_array parameter
Package: qemu Version: 1:7.0+dfsg-1 Severity: normal Dear Maintainer, i'm trying to bring up a dev env for route offloading. linux switchdev offers an emulated switch called rocker. qemu also supports it, but i have issues passing the array paraemter for the front panel ports: mc36@noti:~$ qemu-system-x86_64 -enable-kvm -m 1g -cpu host -cdrom Downloads/debian-11.3.0-amd64-netinst.iso -netdev socket,id=dev0,udp=10.10.10.227:30042,localaddr=:30042 -device rocker,len- ports=4,name=sw,len-ports=2,ports[0]=dev0 qemu-system-x86_64: -device rocker,len-ports=4,name=sw,len- ports=2,ports[0]=dev0: Property 'rocker.ports[0]' not found mc36@noti:~$ thanks, csaba -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#1013951: linux-image-5.18.0-2-amd64: please enable CONFIG_ROCKER properly
Package: src:linux Version: 5.18.5-1 Severity: wishlist Dear Maintainer, trying to bring up a dev env to offload routing. one solution is the emulated switchdev called rocker. during my experimentation i noticed that the named driver is partially enabled... so my question is, could you please compile the future kernels with CONFIG_ROCKER=m? thanks, csaba mc36@noti:~$ cat /boot/config-5.18.0-2-amd64 | grep ROCKER CONFIG_NET_VENDOR_ROCKER=y # CONFIG_ROCKER is not set mc36@noti:~$ -- Package-specific info: ** Version: Linux version 5.18.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-3) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.50.20220615) #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1 (2022-06-16) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.18.0-2-amd64 root=UUID=9e3f4c2b-0bb2-4ff1-b204-ff83d95d443e ro panic=10 snd_hda_intel.dmic_detect=0 ** Not tainted ** Kernel log: [593376.643226] CIFS: Status code returned 0xc0d0 STATUS_REQUEST_NOT_ACCEPTED [597024.532429] CIFS: Status code returned 0xc0d0 STATUS_REQUEST_NOT_ACCEPTED [597024.532459] cifs_setup_session: 2 callbacks suppressed [597024.532465] CIFS: VFS: \\nas.mchome.nop.hu Send error in SessSetup = -5 [597024.552683] CIFS: Status code returned 0xc0d0 STATUS_REQUEST_NOT_ACCEPTED [597024.552703] CIFS: VFS: \\nas.mchome.nop.hu Send error in SessSetup = -5 [597024.571723] CIFS: Status code returned 0xc0d0 STATUS_REQUEST_NOT_ACCEPTED [597024.571749] CIFS: VFS: \\nas.mchome.nop.hu Send error in SessSetup = -5 [597024.591757] CIFS: Status code returned 0xc0d0 STATUS_REQUEST_NOT_ACCEPTED [597024.591776] CIFS: VFS: \\nas.mchome.nop.hu Send error in SessSetup = -5 [597024.611400] CIFS: Status code returned 0xc0d0 STATUS_REQUEST_NOT_ACCEPTED [597024.611426] CIFS: VFS: \\nas.mchome.nop.hu Send error in SessSetup = -5 [599200.912059] atkbd serio0: Unknown key pressed (translated set 2, code 0x6d on isa0060/serio0). [599200.912076] atkbd serio0: Use 'setkeycodes 6d ' to make it known. [599200.974484] atkbd serio0: Unknown key released (translated set 2, code 0x6d on isa0060/serio0). [599200.974498] atkbd serio0: Use 'setkeycodes 6d ' to make it known. [612095.552353] Process accounting resumed [612096.660322] Process accounting resumed [649936.230490] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649936.230498] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649936.257692] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649936.257700] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649936.384571] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649936.384595] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649936.419813] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649936.419820] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649936.557799] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649936.557807] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649936.634336] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649936.634343] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649936.866973] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649936.866981] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649937.000889] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649937.000896] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649990.974854] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649990.974873] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.004051] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649991.004071] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.093685] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649991.093704] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.137000] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649991.137020] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.218560] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649991.218576] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.296099] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649991.296114] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.383719] atkbd serio0: Unknown key pressed (translated set 2, code 0x65 on isa0060/serio0). [649991.383734] atkbd serio0: Use 'setkeycodes 65 ' to make it known. [649991.426012] atkbd serio0: Unknown key released (translated set 2, code 0x65 on isa0060/serio0). [649991.426027] atkbd serio0: Use 'setkeycodes 65 ' to make it known
Bug#1003757: busybox ip ignores peer name on veth pair creation
Package: busybox Version: 1:1.30.1-7+b2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? i need to create multiple veth pair interfaces, preferably from busybox... * What exactly did you do (or not do) that was effective (or ineffective)? mc36@noti:~$ mc36@noti:~$ sudo ip link add veth9a type veth peer name veth9b mc36@noti:~$ ip link show veth9a 9: veth9a@veth9b: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:65:ad:1b:c4:da brd ff:ff:ff:ff:ff:ff mc36@noti:~$ sudo ip link del veth9a mc36@noti:~$ sudo /bin/busybox ip link add veth9a type veth peer name veth9b mc36@noti:~$ ip link show veth9a 11: veth9a@veth0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:65:ad:1b:c4:da brd ff:ff:ff:ff:ff:ff mc36@noti:~$ sudo ip link del veth9a mc36@noti:~$ * What was the outcome of this action? as you can see when i used iproute2 then it freates veth9a-veth9b pair, but when i used busybox, it created veth9a-veth0 pair * What outcome did you expect instead? busybox's ip should honor peer name as iproute2's ip does *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages busybox depends on: ii libc6 2.33-2 busybox recommends no packages. busybox suggests no packages. -- no debconf information
Bug#1003450: qemu-system: dns resolution does not work within the guest if the host have only nameserver in /etc/resolv.conf
Package: qemu-system Version: 1:6.2+dfsg-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? i recently moved to an ipv6-only network for testing purposes... * What exactly did you do (or not do) that was effective (or ineffective)? i ceased ipv4 completely from my desktop for a while... * What was the outcome of this action? for example "qemu-system-x86_64 -enable-kvm -cdrom debian-11.2.0-amd64-netinst.iso" cannot complete mirror selection because dns resolution does not work within the guest when resolt.conf have only ipv6 entries... * What outcome did you expect instead? qemu should notice that it have only ipv6 recursive resolver available and use that when forwarding guest's requests... *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages qemu-system depends on: ii qemu-system-arm1:6.2+dfsg-1 ii qemu-system-mips 1:6.2+dfsg-1 ii qemu-system-misc 1:6.2+dfsg-1 ii qemu-system-ppc1:6.2+dfsg-1 ii qemu-system-sparc 1:6.2+dfsg-1 ii qemu-system-x861:6.2+dfsg-1 qemu-system recommends no packages. qemu-system suggests no packages. -- no debconf information
Bug#979657: firmware-sof-signed: sof-audio-pci 0000:00:1f.3: error: failed to boot DSP firmware -110
Package: firmware-sof-signed Version: 1.6~rc3-1 Severity: normal Dear Maintainer, just noticed that this package is arrived so i given it a try. (before i used the snd_hda_intel.dmic_detect=0 as workaround) with the package installed, the missing firmware lines are gone now, but the sound hw still does not initialize with the error messages below. any advise is welcome! thanks, csaba mc36@noti:~$ lspci | grep udio 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Lake PCH cAVS (rev 10) 01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1) mc36@noti:~$ sudo dmesg | egrep "audio|sof|snd" [4.860004] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [4.860007] software IO TLB: mapped [mem 0x6b677000-0x6f677000] (64MB) [4.980339] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' [4.981926] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' [ 10.434556] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 10.437032] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 10.439451] snd_hda_intel :01:00.1: enabling device ( -> 0002) [ 10.441944] snd_hda_intel :01:00.1: Disabling MSI [ 10.444361] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 10.464273] snd_soc_skl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 10.466330] snd_hda_intel :01:00.1: bound :01:00.0 (ops nv50_audio_component_bind_ops [nouveau]) [ 10.466689] snd_soc_skl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 10.749977] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 10.749992] sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 10.754926] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [ 10.755154] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 10.759853] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 10.766183] sof-audio-pci :00:1f.3: use msi interrupt mode [ 10.825106] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [ 10.826885] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 10.828738] sof-audio-pci :00:1f.3: DMICs detected in NHLT tables: 4 [ 10.831607] sof-audio-pci :00:1f.3: firmware: direct-loading firmware intel/sof/sof-cfl.ri [ 11.738030] sof-audio-pci :00:1f.3: error: cl_dsp_init: timeout HDA_DSP_SRAM_REG_ROM_STATUS read [ 11.738046] sof-audio-pci :00:1f.3: error: status = 0x panic = 0x [ 11.738071] sof-audio-pci :00:1f.3: error: extended rom status: 0x621 0x0 0x0 0x0 0x0 0x0 0x183011b 0x0 [ 11.738097] sof-audio-pci :00:1f.3: error: dsp init failed after 3 attempts with err: -110 [ 11.738103] sof-audio-pci :00:1f.3: ROM error=0x: FW status=0x [ 11.738131] sof-audio-pci :00:1f.3: error: status = 0x panic = 0x [ 11.738169] sof-audio-pci :00:1f.3: error: extended rom status: 0x 0x 0x 0x 0x 0x 0x 0x [ 11.738178] sof-audio-pci :00:1f.3: error: failed to reset DSP [ 11.738180] sof-audio-pci :00:1f.3: error: failed to boot DSP firmware -110 [ 11.788563] sof-audio-pci :00:1f.3: error: hda_dsp_core_reset_enter: timeout on HDA_DSP_REG_ADSPCS read [ 11.788567] sof-audio-pci :00:1f.3: error: dsp core reset failed: core_mask f [ 11.788748] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -110 mc36@noti:~$ -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#977372: linux-image-cloud-amd64: please add e1000 module to the cloud image
Package: linux-image-cloud-amd64 Version: 5.9.0-4 Severity: wishlist Dear Maintainer, please enable e1000 module in the cloud images the rationale here is that qemu, virtualbox and openstack defaults to this device so it would ease the life... thank you very much! cs -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-cloud-amd64 depends on: pn linux-image-5.10.0-rc6-cloud-amd64 pn linux-image-5.9.0-4-cloud-amd64 linux-image-cloud-amd64 recommends no packages. linux-image-cloud-amd64 suggests no packages.
Bug#976667: openjdk-16-jre-headless: too low prioriry for it to be used by default
Package: openjdk-16-jre-headless Version: 16~27-2 Severity: normal Dear Maintainer, the package works fine for my project however it have to low priority assigned to be used by default. please increase! mc36@noti:~$ sudo update-alternatives --config java There are 6 choices for the alternative java (providing /usr/bin/java). SelectionPathPriority Status * 0/usr/lib/jvm/java-15-openjdk-amd64/bin/java 1511 auto mode 1/usr/lib/jvm/java-11-openjdk-amd64/bin/java manual mode 2/usr/lib/jvm/java-13-openjdk-amd64/bin/java 1311 manual mode 3/usr/lib/jvm/java-14-openjdk-amd64/bin/java 1411 manual mode 4/usr/lib/jvm/java-15-openjdk-amd64/bin/java 1511 manual mode 5/usr/lib/jvm/java-16-openjdk-amd64/bin/java 1511 manual mode 6/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode Press to keep the current choice[*], or type selection number: ^C mc36@noti:~$ *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages openjdk-16-jre-headless depends on: ii ca-certificates-java 20190909 ii java-common 0.72 ii libasound21.2.3.2-1+b1 ii libc6 2.31-5 ii libcups2 2.3.3op1-3 ii libfontconfig12.13.1-4.2 ii libfreetype6 2.10.2+dfsg-4 ii libgcc-s1 10.2.0-23 ii libharfbuzz0b 2.6.7-1 ii libjpeg62-turbo 1:2.0.5-1.1 ii liblcms2-22.9-4+b1 ii libnss3 2:3.59-1 ii libpcsclite1 1.9.0-1 ii libstdc++610.2.0-23 ii libx11-6 2:1.6.12-1 ii libxext6 2:1.3.3-1+b2 ii libxi62:1.7.10-1 ii libxrender1 1:0.9.10-1 ii libxtst6 2:1.2.3-1 ii util-linux2.36.1-2 ii zlib1g1:1.2.11.dfsg-2 openjdk-16-jre-headless recommends no packages. Versions of packages openjdk-16-jre-headless suggests: ii fonts-dejavu-extra 2.37-2 pn fonts-indic pn fonts-ipafont-gothic pn fonts-ipafont-mincho pn fonts-wqy-microhei | fonts-wqy-zenhei ii libnss-mdns0.14.1-2 -- no debconf information
Bug#975003: mount refuses to mount cifs from fstab with Unknown mount option "symfollow"
Package: mount Version: 2.36.1-1 Severity: normal Dear Maintainer, i rebooted my sid today and noticed that my cifs mounts from fstab not came up. dmesg indicates " Unknown mount option "symfollow" ". manually mounting them (sudo mount.cifs //mount /point -o opts) did the trick. nevertheless to note that it's the first time this happened. [ 50.143880] CIFS: Attempting to mount //devel.mchome.nop.hu/mc36 [ 50.143902] CIFS: Unknown mount option "symfollow" [ 50.146561] CIFS: Attempting to mount //nas.mchome.nop.hu/mc36 [ 50.146578] CIFS: Unknown mount option "symfollow" -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-2-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mount depends on: ii libblkid1 2.36.1-1 ii libc6 2.31-4 ii libmount1 2.36.1-1 ii libsmartcols1 2.36.1-1 ii util-linux 2.36.1-1 mount recommends no packages. Versions of packages mount suggests: ii nfs-common 1:1.3.4-4 -- no debconf information
Bug#963730: linux-image-5.7.0-1-amd64: i915 gpu hangs under gnome plus firefox
Package: src:linux
Version: 5.7.6-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
gpu hangs occur on i915 with acceleration turned on.
gnome starts normally but as soon as i start firefox,
only ctrl+alt+backspace helps to get out of the situation.
the issue happens regardless of i'm using wayland or x11.
the known workaround is to disable wayland in gdm3,
and disable acceleration in x config.
please find also the log from the gpu.
mc36@acer:~$ sudo cat /sys/class/drm/card0/error
[sudo] password for mc36:
GPU HANG: ecode 7:1:85ddfffd, in Xwayland [5107]
Kernel: 5.7.0-1-amd64 x86_64
Driver: 20200313
Time: 1593152924 s 716145 us
Boottime: 362 s 45315 us
Uptime: 358 s 811552 us
Capture: 4294982784 jiffies; 1241536 ms ago
Active process (on ring rcs0): Xwayland [5107]
Reset count: 0
Suspend count: 0
Platform: HASWELL
Subplatform: 0x1
PCI ID: 0x0a06
PCI Revision: 0x0b
PCI Subsystem: 1025:0775
IOMMU enabled?: 0
RPM wakelock: yes
PM suspended: no
GT awake: yes
EIR: 0x
IER: 0xfc080421
GTIER[0]: 0x00401821
PGTBL_ER: 0x
FORCEWAKE: 0x
DERRMR: 0x
fence[0] =
fence[1] =
fence[2] = 2c5a02b02754001
fence[3] = 4d4102b0483b001
fence[4] =
fence[5] =
fence[6] =
fence[7] =
fence[8] =
fence[9] =
fence[10] =
fence[11] =
fence[12] =
fence[13] =
fence[14] =
fence[15] =
fence[16] =
fence[17] =
fence[18] =
fence[19] =
fence[20] =
fence[21] =
fence[22] =
fence[23] =
fence[24] =
fence[25] =
fence[26] =
fence[27] =
fence[28] =
fence[29] =
fence[30] =
fence[31] =
ERROR: 0x
DONE_REG: 0x
ERR_INT: 0x
rcs0 command stream:
CCID: 0x7fe94101
START: 0x1000
HEAD: 0x014022d8 [0x21d0]
TAIL: 0x2830 [0x23d8, 0x23f0]
CTL: 0x3001
MODE: 0x4000
HWS: 0x7fffe000
ACTHD: 0x 014022d8
IPEIR: 0x
IPEHR: 0x7a02
ESR: 0x
INSTDONE: 0xffdd
SC_INSTDONE: 0x
SAMPLER_INSTDONE[0][0]: 0x
ROW_INSTDONE[0][0]: 0xfc10efff
batch: [0x_0054c000, 0x_0054d000]
BBADDR: 0x_7ff9bad4
BB_STATE: 0x0020
INSTPS: 0x810b
INSTPM: 0x6280
FADDR: 0x 34c0
RC PSMI: 0x0010
FAULT_REG: 0x
GFX_MODE: 0x2a00
PP_DIR_BASE: 0x7fc9
engine reset count: 0
Active context: Xwayland[5107] prio 0, guilty 0 active 0, runtime total 0ns,
avg 0ns
rcs0 --- NULL context = 0x
:g$G5RbHB:5$FKNnXh/HU(VX#_>88H'p6WJZ):gmb@lRXVScCP>A^m/XCW2mC.)2B2^7M]B2("j.?Z4pnP`E2F[cY'gL%XVRNcdHml2okC#F*HL8!")BV9nSM21')\5eQK#BY-aJbg*GQY9\",)U><+=7?:_[f?MUXD=l31iN5,5#Ad8^sh)XKKb%!j_qA3=f_7Wnn7qd#r[\KPZ!4iNSV-n>)#o/:caV6#H/@Td/'1Gl(oPVCq]b,PlL4Of,+2?L!XjV*gGg-427lqJlhI$lg`eLG*h_3:%Mam(MI`3^4U9tE)18_.<"_]BFUSgEC<>Mr*6lH'Qg(;UMMk`1`"M-;7L#.Picmtj!eIoG!^SK(DUD[18$Za1HkYa!'5*FI6/2&79n;n/n%37+;q5E%pLE-JqOg28/_V5E=e6ebRI#)0P+8?n=f75of%[koV=.d9Vt-Cer/!Y'/%AUE^d5T*9I1`mch=]>HcI*pWU/@$Ef(Da.qDu>,j?1]oI5t%pCd5Z'?D,Z]@Uh??cpRRmLrt(hgn96S>o77o>=1#p1^_P`2+4U!dDgntG(DJFP1s@*4jKF),\L/=4:,>$7Bd,kgk`&#
Bug#790556: systemctl crashes, systemd setup fails
hi, i've having the same issues... i've noticed that systemd 222-1 is out so i've given it a try, but the same happens. i've commented out the machine id generation from install script of systemd and that time systemd installed. i've generated an initramfs, but didn't boot up correctly. regard, cs root@(none):/var/cache/apt/archives# dpkg --install systemd_222-1_sparc.deb (Reading database ... 95336 files and directories currently installed.) Preparing to unpack systemd_222-1_sparc.deb ... [ 831.840725] systemctl[1531]: segfault at fbad2408 ip f76d8d94 (rpc f76d8d6c) sp ffc8b788 error 30001 in li] [ 832.040734] systemctl[1532]: segfault at fbad2408 ip f77ecd94 (rpc f77ecd6c) sp ffe75788 error 30001 in li] [ 832.240723] systemctl[1533]: segfault at fbad2408 ip f795cd94 (rpc f795cd6c) sp ffd9d788 error 30001 in li] [ 832.440911] systemctl[1534]: segfault at fbad2408 ip f7958d94 (rpc f7958d6c) sp ff967788 error 30001 in li] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
