Bug#1032876: linux: new stable upstream kernel release fixes some bugs

2023-03-13 Thread Renato Gallo 
: 1e51764a3c2ac0 ("UBIFS: add new flash file system")
-Fixes: 1e51764a3c2ac0 ("UBIFS: add new flash file system")
-Fixes: 1e51764a3c2ac0 ("UBIFS: add new flash file system")
-Fixes: 9ec64962afb170 ("ubifs: Implement RENAME_EXCHANGE")
-Fixes: ca7f85be8d6cf9 ("ubifs: Add support for encrypted symlinks")
-Fixes: 2e3cbf425804 ("ubifs: Export filesystem error counters")
-Fixes: 16a26b20d2af ("ubifs: authentication: Add hashes to index nodes")
-Fixes: 801c135ce73d ("UBI: Unsorted Block Images")
-Fixes: 49da7e64f33e ("High Performance UML Vector Network Driver")
-Fixes: 7a10f0177e11 ("f2fs: don't give partially written atomic data from
process crash")
-Fixes: e1e8debec656 ("f2fs: add F2FS_IOC_SET_COMPRESS_OPTION ioctl")
-Fixes: 95ae251fe828 ("f2fs: add fs-verity support")
-Fixes: 728400a1 ("f2fs: allocate the extent_cache by default")
-Fixes: 681a02e95000 ("soc: mediatek: SVS: introduce MTK SVS engine")
-Fixes: a825d72f74a3 ("soc: mediatek: fix missing clk_disable_unprepare()
on err in svs_resume()")
-Fixes: 681a02e95000 ("soc: mediatek: SVS: introduce MTK SVS engine")
-Fixes: 0bbb09b2af9d ("soc: mediatek: SVS: add mt8192 SVS GPU driver")
-Fixes: 7a10f0177e11 ("f2fs: don't give partially written atomic data from
process crash")
-Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
-Fixes: e70a540b4e02 ("pwm: Add STM32 LPTimer PWM driver")
-Fixes: 9e37a53eb051 ("pwm: sifive: Add a driver for SiFive SoC PWM")
-Fixes: ca7d8b980b67 ("memory: add Renesas RPC-IF driver")
-Fixes: ca7d8b980b67 ("memory: add Renesas RPC-IF driver")
-Fixes: de320c07da3d ("soc: qcom: socinfo: Add MSM8956/76 SoC IDs to the
soc_id table")
-Fixes: 147f6534b8ff ("soc: qcom: socinfo: Add SM8550 ID")
-Fixes: 88590cbc1703 ("soc: mediatek: pm-domains: Add support for
mt8186")
-Fixes: 1e7e47883830 ("x86/static_call: Add inline static call
implementation for x86-64")
-Fixes: 95fa90c9e5a7 ("f2fs: support recording errors into superblock")
-Fixes: 1517c1a7a445 ("f2fs: implement iomap operations")
-Fixes: 05e5ba40ea7a ("driver: soc: xilinx: Add support of multiple
callbacks for same event in event management driver")
-Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
-Fixes: 718e05ed92ec ("auxdisplay: Introduce hd44780_common.[ch]")


Thanks for all your work and attention.
Renato Gallo

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (500, 'testing-security'),
(499, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.2.2 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash

Bug#1028960: closed by Salvatore Bonaccorso (Re: Bug#1028960: linux: debuild fails with sphinx v6.1.3 on kernel latest stable 6.1.6)

2023-01-15 Thread Renato Gallo 
ad-RAM-found.patch
> Applying patch features/x86/x86-make-x32-syscall-support-conditional.patch
> Applying patch
> bugfix/arm64/arm64-dts-rockchip-fix-spdif-fe46-ordering-on-rk.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-RK356x-Add-I2S2-device-node.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-Enable-GPU-on-SOQuartz-CM4.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-Enable-video-output-and-HDMI-on-S.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-Enable-HDMI-sound-on-SOQuartz.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-Enable-PCIe-2-on-SOQuartz-CM4IO.patch
> Applying patch
> features/arm64/quartz64/dt-bindings-arm-rockchip-Add-SOQuartz-Blade.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-Add-SOQuartz-blade-board.patch
> Applying patch
> features/arm64/quartz64/dt-bindings-arm-rockchip-Add-SOQuartz-Model-A.patch
> Applying patch
> features/arm64/quartz64/arm64-dts-rockchip-Add-SOQuartz-Model-A-baseboard.patch
> Applying patch bugfix/all/disable-some-marvell-phys.patch
> Applying patch
> bugfix/all/fs-add-module_softdep-declarations-for-hard-coded-cr.patch
> Applying patch
> features/all/lockdown/efi-add-an-efi_secure_boot-flag-to-indicate-secure-b.patch
> Applying patch
> features/all/lockdown/efi-lock-down-the-kernel-if-booted-in-secure-boot-mo.patch
> Applying patch
> features/all/lockdown/mtd-disable-slram-and-phram-when-locked-down.patch
> Applying patch
> features/all/lockdown/arm64-add-kernel-config-option-to-lock-down-when.patch
> Applying patch
> features/all/db-mok-keyring/0003-MODSIGN-checking-the-blacklisted-hash-before-loading-a-kernel-module.patch
> Applying patch
> features/all/db-mok-keyring/trust-machine-keyring-by-default.patch
> Applying patch debian/i386-686-pae-pci-set-pci-nobios-by-default.patch
> Applying patch debian/ntfs-mark-it-as-broken.patch
> Applying patch bugfix/all/module-disable-matching-missing-version-crc.patch
> Applying patch bugfix/all/usbip-document-tcp-wrappers.patch
> Applying patch bugfix/all/kbuild-fix-recordmcount-dependency.patch
> Applying patch bugfix/all/tools-perf-man-date.patch
> Applying patch bugfix/all/tools-perf-remove-shebangs.patch
> Applying patch
> bugfix/x86/revert-perf-build-fix-libunwind-feature-detection-on.patch
> Applying patch
> bugfix/all/tools-build-remove-bpf-run-time-check-at-build-time.patch
> Applying patch bugfix/all/cpupower-bump-soname-version.patch
> Applying patch bugfix/all/cpupower-fix-checks-for-cpu-existence.patch
> Applying patch bugfix/all/tools-perf-pmu-events-fix-reproducibility.patch
> Applying patch
> bugfix/all/libapi-define-_fortify_source-as-2-not-empty.patch
> Applying patch
> bugfix/all/tools-perf-fix-missing-ldflags-for-some-programs.patch
> Now at patch
> bugfix/all/tools-perf-fix-missing-ldflags-for-some-programs.patch
> root@ghost:/usr/src/kernel/linux# debian/bin/gencontrol.py
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> root@ghost:/usr/src/kernel/linux# dpkg-buildpackage -j`nproc` -us -uc
> dpkg-buildpackage: info: source package linux
> dpkg-buildpackage: info: source version 6.1.6-1~exp1
> dpkg-buildpackage: info: source distribution UNRELEASED
> dpkg-buildpackage: info: source changed by Renato Gallo <
> vmxevils...@gmail.com>
> dpkg-buildpackage: info: host architecture amd64
>  dpkg-source --before-build .
> dpkg-source: info: using options from linux/debian/source/local-options:
> --abort-on-upstream-changes
>  debian/rules clean
> mkdir -p debian/build
> printf >debian/build/version-info 'Source: %s\nVersion: %s\n' linux
> 6.1.6-1~exp1
> /usr/bin/make -f debian/rules debian/control-real
> make[1]: Entering directory '/usr/src/kernel/linux'
> PYTHONHASHSEED=0 debian/bin/gencontrol.py
> md5sum debian/bin/gencontrol.py debian/build/version-info debian/templates/
> config.control.in debian/templates/docs.control.in debian/templates/
> docs.meta.control.in debian/templates/docs.meta.maintscript.in
> debian/templates/extra.control.in debian/templates/headers.control.in
> debian/templates/headers.featureset.control.in debian/templates/
> headers.meta.control.in debian/templates/headers.meta.maintscript.in
> debian/templates/headers.postinst.in debian/templates/
> headers.tests-control.in debian/templates/image-dbg.control.in
> debian/templates/image-dbg.meta.control.in debian/templates/
> image-dbg.meta.lintian-overrides.in debian/templates/
> image-dbg.meta.maintscript.in debian/templates/image-unsigned.control.in
> debian/templates/image-unsigned.postinst.in debian/templates/
> image-unsigned.postrm.in debian/templates/image-unsigned.preinst.in
> debian/templates

Bug#1027921: linux-image-5.10.0-20-amd64: aacraid's expose_physicals=-1 is not functional

2023-01-04 Thread Renato Gallo 
5.10 should be EOL by now

On Wed, Jan 4, 2023 at 3:51 PM Tim Düsterhus  wrote:

> Package: src:linux
> Version: 5.10.158-2
> Severity: normal
> X-Debbugs-Cc: duester...@woltlab.com
>
> Dear Maintainer,
>
> after upgrading my server from Debian Buster to Debian Bullseye, I
> noticed that the underlying devices attached to the Adaptec 6405E raid
> controller were no longer exposed via the /dev/sgX devices and thus
> reading the SMART values was no longer possible:
>
> $ lsscsi
> [0:0:0:0]diskAdaptec  *redacted*   V1.0  /dev/sda
> [0:3:0:0]enclosu ADAPTEC  Virtual SGPIO  -
>
> Booting into the Linux 4.19 kernel from Debian Buster correctly exposed
> the devices with the new userland, indicating a Kernel issue.
>
> I was able to work around the issue by adding the following
> configuration to /etc/modprobe.d/:
>
> options aacraid expose_physicals=1
>
> After setting this configuration and rebooting the server the devices
> are properly visible as they were before:
>
> $ lsscsi
> [0:0:0:0]diskAdaptec  *redacted*   V1.0  /dev/sda
> [0:1:0:0]diskATA  *redacted*     /dev/sdb
> [0:1:1:0]diskATA  *redacted*     /dev/sdc
> [0:3:0:0]enclosu ADAPTEC  Virtual SGPIO  -
>
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
>
> It appears that aacraid's `expose_physicals=-1` option got broken
> somewhere between Linux 4.19 and 5.10.
>
> Best regards
>
>
> -- Package-specific info:
> ** Version:
> Linux version 5.10.0-20-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.158-2 (2022-12-13)
>
> ** Command line:
> BOOT_IMAGE=/vmlinuz-5.10.0-20-amd64 root=ZFS=rpool/ROOT/debian ro boot=zfs
> swapaccount=1 quiet
>
> ** Tainted: POE (12289)
>  * proprietary module was loaded
>  * 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: Supermicro
> product_name: X10SLH-F/X10SLM+-F
> product_version: 0123456789
> chassis_vendor: Supermicro
> chassis_version: 0123456789
> bios_vendor: American Megatrends Inc.
> bios_version: 3.2a
> board_vendor: Supermicro
> board_name: X10SLH-F/X10SLM+-F
> board_version: 1.02
>
> ** Loaded modules:
> nft_reject_inet
> nf_reject_ipv4
> nf_reject_ipv6
> nft_reject
> nft_counter
> intel_rapl_msr
> intel_rapl_common
> ipmi_ssif
> nft_ct
> nf_conntrack
> nf_defrag_ipv6
> nf_defrag_ipv4
> x86_pkg_temp_thermal
> intel_powerclamp
> coretemp
> kvm_intel
> kvm
> ext4
> irqbypass
> ghash_clmulni_intel
> crc16
> mbcache
> jbd2
> aesni_intel
> libaes
> crypto_simd
> cryptd
> ast
> glue_helper
> drm_vram_helper
> drm_ttm_helper
> rapl
> ttm
> intel_cstate
> intel_uncore
> drm_kms_helper
> pcspkr
> joydev
> at24
> intel_pch_thermal
> evdev
> mei_me
> cec
> iTCO_wdt
> mei
> intel_pmc_bxt
> sg
> iTCO_vendor_support
> watchdog
> ie31200_edac
> acpi_ipmi
> ipmi_si
> ipmi_devintf
> ipmi_msghandler
> acpi_pad
> button
> nf_tables
> libcrc32c
> crc32c_generic
> nfnetlink
> drm
> fuse
> configfs
> ip_tables
> x_tables
> autofs4
> hid_generic
> usbhid
> hid
> zfs(POE)
> zunicode(POE)
> zzstd(OE)
> zlua(OE)
> zavl(POE)
> icp(POE)
> zcommon(POE)
> znvpair(POE)
> spl(OE)
> ses
> enclosure
> sd_mod
> scsi_transport_sas
> t10_pi
> crc_t10dif
> crct10dif_generic
> ahci
> libahci
> xhci_pci
> libata
> xhci_hcd
> ehci_pci
> crct10dif_pclmul
> crct10dif_common
> ehci_hcd
> aacraid
> crc32_pclmul
> lpc_ich
> igb
> i2c_i801
> usbcore
> i2c_smbus
> scsi_mod
> crc32c_intel
> i2c_algo_bit
> dca
> ptp
> pps_core
> usb_common
> fan
> video
>
> ** PCI devices:
> 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor
> DRAM Controller [8086:0c08] (rev 06)
> Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM
> Controller [15d9:0803]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 0
> IOMMU group: 0
> Capabilities: [e0] Vendor Specific Information: Len=0c 
> Kernel driver in use: ie31200_edac
> Kernel modules: ie31200_edac
>
> 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core
> Processor PCI Express x16 Controller [8086:0c01] (rev 06) (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-  Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 25
> IOMMU group

Bug#1013731: linux-image-5.10.0-13-amd64: 5.10.0-13-amd64 RTL8153 power management kernel hang

2022-12-06 Thread Renato Gallo 
have you tried with 6.0 ?

On Tue, Dec 6, 2022 at 12:27 PM Diederik de Haas 
wrote:

> Control: tag -1 moreinfo
>
> On Saturday, 25 June 2022 05:33:01 CET Ian Turner wrote:
> > On this kernel (linux-image-5.10.0-13-amd64 and previous) I experience
> > occasional kworker kernel hangs with numerous other associated
> > uninterruptable processes.
> >
> > * The issue is resolved in linux-image-5.16.0-0.bpo.4-rt-amd64
>
> What's the current status of this issue?
> As it was resolved in 5.16, there's a reasonable chance such a fix has now
> landed in 5.10 series too.

Bug#966218: firmware: failed to load iwl-debug-yoyo.bin (-2)

2022-11-22 Thread Renato Gallo 
Linux ghost 6.1.0-rc5 #1 SMP PREEMPT_DYNAMIC Mon Nov 21 10:45:11 CET 2022
x86_64 GNU/Linux

 dmesg|grep -i firmware
[0.083868] Spectre V2 : Enabling Restricted Speculation for firmware
calls
[0.588920] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.599850] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 
[bus 00-7f] only partially covers this bridge
[1.770657] ACPI: video: [Firmware Bug]: ACPI(PEGP) defines _DOD but not
_DOS
[5.333711] platform regulatory.0: firmware: direct-loading firmware
regulatory.db
[5.334476] platform regulatory.0: firmware: direct-loading firmware
regulatory.db.p7s
[5.350952] iwlwifi :04:00.0: firmware: direct-loading firmware
iwlwifi-cc-a0-72.ucode
[5.351201] iwlwifi :04:00.0: firmware: failed to load
iwl-debug-yoyo.bin (-2)



[5.351218] firmware_class: See https://wiki.debian.org/Firmware for
information about missing firmware
[5.351338] iwlwifi :04:00.0: firmware: failed to load
iwl-debug-yoyo.bin (-2)





[5.351351] iwlwifi :04:00.0: loaded firmware version 72.daa05125.0
cc-a0-72.ucode op_mode iwlmvm
[5.617756] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[5.619356] bluetooth hci0: firmware: direct-loading firmware
intel/ibt-20-1-3.sfi
[5.619359] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[5.619367] Bluetooth: hci0: Firmware Version: 106-39.22
[7.043546] Bluetooth: hci0: Waiting for firmware download to complete
[7.043737] Bluetooth: hci0: Firmware loaded in 1390992 usecs
[7.064205] bluetooth hci0: firmware: direct-loading firmware
intel/ibt-20-1-3.ddc
[7.072839] Bluetooth: hci0: Firmware revision 0.3 build 106 week 39 2022
[7.518824] r8169 :02:00.0: firmware: direct-loading firmware
rtl_nic/rtl8125b-2.fw

Bug#1011196: linux-image-5.17.0-2-amd64: Geek Out USB sound card fails to initialise

2022-08-24 Thread Renato Gallo 
Ok, thanks for the update.

On Wed, Aug 24, 2022 at 11:40 AM Lennert Van Alboom 
wrote:

> Will be difficult, I think. It's a device from... 2014, I believe. Long
> past end of sales. eBay still has a few:
> https://www.ebay.com/itm/265844830824,
> https://www.ebay.com/itm/14437678.
>
> Currently trying to setup a build environment to do kernel bisects because
> the current sid binutils makes a kernel build of 5.10 fail (yay). Fingers
> crossed.
> --- Original Message ---
> On Tuesday, August 23rd, 2022 at 17:33, Renato Gallo <
> vmxevils...@gmail.com> wrote:
>
> where can I buy one ?
> I am curious to test it on 6.0-rc2
>
> On Tue, Aug 23, 2022 at 5:30 PM Lennert Van Alboom 
> wrote:
>
>> Quick update, still broken in 5.18 (unstable) and 5.19 (experimental).
>>
>> Some potentially useful syslog from trying with 5.19.0-trunk-amd64:
>>
>> Aug 23 17:12:30 Nesbitt kernel: [ 188.154086] usb 3-6: new high-speed USB
>> device number 5 using xhci_hcd
>> Aug 23 17:12:30 Nesbitt kernel: [ 188.303314] usb 3-6: New USB device
>> found, idVendor=2522, idProduct=0007, bcdDevice=15.02
>> Aug 23 17:12:30 Nesbitt kernel: [ 188.303323] usb 3-6: New USB device
>> strings: Mfr=1, Product=3, SerialNumber=0
>> Aug 23 17:12:30 Nesbitt kernel: [ 188.303325] usb 3-6: Product: Geek Out
>> HD Audio 1V5
>> Aug 23 17:12:30 Nesbitt kernel: [ 188.303327] usb 3-6: Manufacturer: LH
>> Labs
>> Aug 23 17:12:30 Nesbitt mtp-probe: checking bus 3, device 5:
>> "/sys/devices/pci:00/:00:14.0/usb3/3-6"
>> Aug 23 17:12:30 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
>> Aug 23 17:12:30 Nesbitt kernel: [ 188.389783] usb 3-6: 1:2 : unsupported
>> format bits 0x1
>> Aug 23 17:12:31 Nesbitt kernel: [ 188.460882] usbcore: registered new
>> interface driver snd-usb-audio
>> Aug 23 17:12:31 Nesbitt mtp-probe: checking bus 3, device 5:
>> "/sys/devices/pci:00/:00:14.0/usb3/3-6"
>> Aug 23 17:12:31 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
>> Aug 23 17:12:31 Nesbitt systemd-udevd[2217]: controlC1: Process
>> '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime
>> restore 1' failed with exit code 99.
>> Aug 23 17:12:31 Nesbitt systemd[1208]: Reached target Sound Card.
>> Aug 23 17:12:36 Nesbitt kernel: [ 193.658813] usb 3-6: 1:1:
>> usb_set_interface failed (-110)
>> Aug 23 17:12:36 Nesbitt kernel: [ 193.659333] usb 3-6: 1:0:
>> usb_set_interface failed (-71)
>> Aug 23 17:12:36 Nesbitt kernel: [ 193.660249] usb 3-6: 1:0:
>> usb_set_interface failed (-71)
>> Aug 23 17:12:36 Nesbitt kernel: [ 193.661022] usb 3-6: 1:1:
>> usb_set_interface failed (-71)
>> Aug 23 17:12:36 Nesbitt kernel: [ 193.661169] usb 3-6: 1:0:
>> usb_set_interface failed (-71)
>>
>>
>> Relevant thread at Arch about what appears to be the same issue:
>> https://bugs.archlinux.org/task/70636
>>
>> Relevant thread on linux-usb mailinglist:
>> https://www.spinics.net/lists/linux-usb/msg228518.html
>
>
>

Bug#1011196: linux-image-5.17.0-2-amd64: Geek Out USB sound card fails to initialise

2022-08-23 Thread Renato Gallo 
where can I buy one ?
I am curious to test it on 6.0-rc2

On Tue, Aug 23, 2022 at 5:30 PM Lennert Van Alboom 
wrote:

> Quick update, still broken in 5.18 (unstable) and 5.19 (experimental).
>
> Some potentially useful syslog from trying with 5.19.0-trunk-amd64:
>
> Aug 23 17:12:30 Nesbitt kernel: [  188.154086] usb 3-6: new high-speed USB
> device number 5 using xhci_hcd
> Aug 23 17:12:30 Nesbitt kernel: [  188.303314] usb 3-6: New USB device
> found, idVendor=2522, idProduct=0007, bcdDevice=15.02
> Aug 23 17:12:30 Nesbitt kernel: [  188.303323] usb 3-6: New USB device
> strings: Mfr=1, Product=3, SerialNumber=0
> Aug 23 17:12:30 Nesbitt kernel: [  188.303325] usb 3-6: Product: Geek Out
> HD Audio 1V5
> Aug 23 17:12:30 Nesbitt kernel: [  188.303327] usb 3-6: Manufacturer: LH
> Labs
> Aug 23 17:12:30 Nesbitt mtp-probe: checking bus 3, device 5:
> "/sys/devices/pci:00/:00:14.0/usb3/3-6"
> Aug 23 17:12:30 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
> Aug 23 17:12:30 Nesbitt kernel: [  188.389783] usb 3-6: 1:2 : unsupported
> format bits 0x1
> Aug 23 17:12:31 Nesbitt kernel: [  188.460882] usbcore: registered new
> interface driver snd-usb-audio
> Aug 23 17:12:31 Nesbitt mtp-probe: checking bus 3, device 5:
> "/sys/devices/pci:00/:00:14.0/usb3/3-6"
> Aug 23 17:12:31 Nesbitt mtp-probe: bus: 3, device: 5 was not an MTP device
> Aug 23 17:12:31 Nesbitt systemd-udevd[2217]: controlC1: Process
> '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime
> restore 1' failed with exit code 99.
> Aug 23 17:12:31 Nesbitt systemd[1208]: Reached target Sound Card.
> Aug 23 17:12:36 Nesbitt kernel: [  193.658813] usb 3-6: 1:1:
> usb_set_interface failed (-110)
> Aug 23 17:12:36 Nesbitt kernel: [  193.659333] usb 3-6: 1:0:
> usb_set_interface failed (-71)
> Aug 23 17:12:36 Nesbitt kernel: [  193.660249] usb 3-6: 1:0:
> usb_set_interface failed (-71)
> Aug 23 17:12:36 Nesbitt kernel: [  193.661022] usb 3-6: 1:1:
> usb_set_interface failed (-71)
> Aug 23 17:12:36 Nesbitt kernel: [  193.661169] usb 3-6: 1:0:
> usb_set_interface failed (-71)
>
>
> Relevant thread at Arch about what appears to be the same issue:
> https://bugs.archlinux.org/task/70636
>
> Relevant thread on linux-usb mailinglist:
> https://www.spinics.net/lists/linux-usb/msg228518.html

Bug#1017972: (no subject)

2022-08-23 Thread Renato Gallo 
you generally cannot insmod a module compiled from another kernel 

On Tue, Aug 23, 2022 at 3:39 PM Roman Kalugin  wrote:

>
> Unfortunately I can't use patches yet. I can say that I tried to run the
> module from another kernel and I get an error.
>
> sudo insmod
>
> /lib/modules/5.18.0-3-amd64/kernel/drivers/platform/x86/nvidia-wmi-ec-backlight.ko
>
> [sudo] password for alter:
> insmod: ERROR: could not insert module
> /lib/modules/5.18.0-3-amd64/kernel/drivers/platform/x86/nvidia-wmi-ec-backlight.ko:
>
> Invalid module format
>
> I thought you could add it to the default kernel
>
> --
> Best regards, Roman Kalugin
>
> e-mail: kalugi...@gmail.com
>
>

Bug#1017894: linux-image-5.18.0-4-arm64: Kernel oops triggered by heavy network load on ax88179_178a

2022-08-22 Thread Renato Gallo 
try with the stable 5.19.0 or directly with 6.0

On Mon, Aug 22, 2022 at 10:39 AM Simon Tatham  wrote:

> Simon Tatham  wrote:
> > (I would be happy to go through a list of kernel git commits between
> > those two kernels and see if anything jumped out at me, but I'm sorry
> > to say that I have no idea how to get from a Debian kernel
> > package/version to a kernel git commit id.)
>
> Having said that...
>
> Cloning https://salsa.debian.org/kernel-team/linux.git and running
>
>   git log debian/5.18.14-1..debian/5.18.16-1 -G ax88179_178a
>
> identifies commit 6c1dd4fd0a9fb8a1c523c22ac30f76d2067d23dd, which bumps
> the upstream kernel version from 5.18.14 to 5.18.15 and mentions in the
> upstream changelog "net: usb: ax88179_178a needs FLAG_SEND_ZLP".
>
> I still haven't figured out how to directly look up a range of commit
> ids in the upstream kernel repo. However, searching for that message
> text in the upstream repo is enough to track down commit
> 36a15e1cb134c0395261ba1940762703f778438c (13th June) that seems to be
> the change in question - but also, commit
> 6fd2c17fb6e02a8c0ab51df1cfec82ce96b8e83d (8th August) reverting it
> again. So it looks as if this Debian kernel has the change but not the
> revert.
>
> Cheers,
> Simon
>
> --
> for k in [pow(x,37,0x1a1298d262b49c895d47f) for x in
> [0x50deb914257022de7fff,
> 0x213558f2215127d5a2d1, 0x90c99e86d08b91218630, 0x109f3d0cfbf640c0beee7,
> 0xc83e01379a5fbec5fdd1, 0x19d3d70a8d567e388600e, 0x534e2f6e8a4a33155123]]:
>  print("".join([chr(32+3*((k>>x)&1))for x in range(79)])) # <
> ana...@pobox.com>
>
>

kernel 5.16.3

2022-01-28 Thread Renato Gallo 
I have compiled the debs for amd64  are you interested?