Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #76982 > unrolled thread

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2022-11-09 16:30 +0100
Last post2022-11-10 14:30 +0100
Articles 14 — 3 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Salvatore Bonaccorso <carnil@debian.org> - 2022-11-09 16:30 +0100
    Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-09 17:10 +0100
      Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-09 17:30 +0100
        Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Salvatore Bonaccorso <carnil@debian.org> - 2022-11-09 17:50 +0100
          Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-09 18:10 +0100
            Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Salvatore Bonaccorso <carnil@debian.org> - 2022-11-09 19:30 +0100
              Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-10 18:30 +0100
                Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Salvatore Bonaccorso <carnil@debian.org> - 2022-11-10 20:50 +0100
      Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Salvatore Bonaccorso <carnil@debian.org> - 2022-11-09 17:50 +0100
        Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-10 09:50 +0100
          Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-10 11:40 +0100
            Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Diederik de Haas <didi.debian@cknow.org> - 2022-11-10 12:00 +0100
              Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Diederik de Haas <didi.debian@cknow.org> - 2022-11-10 12:20 +0100
                Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection Guy Durrieu <guy.durrieu@cegetel.net> - 2022-11-10 14:30 +0100

#76982 — Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

FromSalvatore Bonaccorso <carnil@debian.org>
Date2022-11-09 16:30 +0100
SubjectBug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection
Message-ID<FpVbz-2xrf-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi Guy,

On Wed, Nov 09, 2022 at 11:38:51AM +0100, Guy Durrieu wrote:
> Package: src:linux
> Version: 6.0.5-1
> Severity: normal (I would say serious...)
> 
> Dear Maintainer,
> 
> Until today, my linux-image-6.0.0-2-amd64 was OK. After the recent updates I
> get a serious problem: no more network connection (neither ethernet, wifi
> nor USB), and no more pulseaudio server connection.
> 
> When rebooting with the previous available version
> (linux-image-5.19.0-2-amd64) all work fine.
> 
> I thus send this report using thisversion of the kernel but you will find
> below the 200 lines of the kernel.log when booting
> linux-image-6.0.0-2-amd64. Hope it will help.
> 
> Thanks in advance for your help !
> 
> Best regards.
> 
> -- Guy Durrieu
> 
> 
> ----------------------------------------------------------------
> 2022-11-09T10:10:15.885062+01:00 ITI kernel: [    3.701731] amdgpu
> 0000:06:00.0: No more image in the PCI ROM
> 2022-11-09T10:10:15.885063+01:00 ITI kernel: [    3.701751] amdgpu
> 0000:06:00.0: amdgpu: Fetched VBIOS from ROM BAR
> 2022-11-09T10:10:15.885063+01:00 ITI kernel: [    3.701753] amdgpu: ATOM
> BIOS:
> 115-D009PI2-101
> 2022-11-09T10:10:15.885065+01:00 ITI kernel: [    3.701768] [drm] UVD is
> enabled in VM mode
> 2022-11-09T10:10:15.885066+01:00 ITI kernel: [    3.701769] [drm] UVD ENC is
> enabled in VM mode
> 2022-11-09T10:10:15.885066+01:00 ITI kernel: [    3.701770] [drm] VCE
> enabled
> in VM mode
> 2022-11-09T10:10:15.885066+01:00 ITI kernel: [    3.701771] amdgpu
> 0000:06:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
> 2022-11-09T10:10:15.885067+01:00 ITI kernel: [    3.701812] [drm] vm size is
> 64
> GB, 2 levels, block size is 10-bit, fragment size is 9-bit
> 2022-11-09T10:10:15.885067+01:00 ITI kernel: [    3.701850] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_mc.bin
> 2022-11-09T10:10:15.885069+01:00 ITI kernel: [    3.701856] amdgpu
> 0000:06:00.0: amdgpu: VRAM: 8192M 0x000000F400000000 - 0x000000F5FFFFFFFF
> (8192M used)
> 2022-11-09T10:10:15.885070+01:00 ITI kernel: [    3.701859] amdgpu
> 0000:06:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
> 2022-11-09T10:10:15.885070+01:00 ITI kernel: [    3.701863] [drm] Detected
> VRAM
> RAM=8192M, BAR=256M
> 2022-11-09T10:10:15.885070+01:00 ITI kernel: [    3.701865] [drm] RAM width
> 256bits GDDR5
> 2022-11-09T10:10:15.885071+01:00 ITI kernel: [    3.701900] [drm] amdgpu:
> 8192M
> of VRAM memory ready
> 2022-11-09T10:10:15.885071+01:00 ITI kernel: [    3.701901] [drm] amdgpu:
> 7975M
> of GTT memory ready.
> 2022-11-09T10:10:15.885072+01:00 ITI kernel: [    3.701911] [drm] GART: num
> cpu
> pages 65536, num gpu pages 65536
> 2022-11-09T10:10:15.885074+01:00 ITI kernel: [    3.702755] sr 15:0:0:0:
> Attached scsi CD-ROM sr0
> 2022-11-09T10:10:15.885074+01:00 ITI kernel: [    3.703580] [drm] PCIE GART
> of
> 256M enabled (table at 0x000000F400900000).
> 2022-11-09T10:10:15.885074+01:00 ITI kernel: [    3.703686] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_pfp_2.bin
> 2022-11-09T10:10:15.885075+01:00 ITI kernel: [    3.703702] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_me_2.bin
> 2022-11-09T10:10:15.885075+01:00 ITI kernel: [    3.703717] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_ce_2.bin
> 2022-11-09T10:10:15.885076+01:00 ITI kernel: [    3.703719] [drm] Chained IB
> support enabled!
> 2022-11-09T10:10:15.885078+01:00 ITI kernel: [    3.703738] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_rlc.bin
> 2022-11-09T10:10:15.885078+01:00 ITI kernel: [    3.703813] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec_2.bin
> 2022-11-09T10:10:15.885078+01:00 ITI kernel: [    3.703887] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec2_2.bin
> 2022-11-09T10:10:15.885079+01:00 ITI kernel: [    3.704362] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma.bin
> 2022-11-09T10:10:15.885116+01:00 ITI kernel: [    3.704383] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma1.bin
> 2022-11-09T10:10:15.885117+01:00 ITI kernel: [    3.704403] amdgpu:
> hwmgr_sw_init smu backed is polaris10_smu
> 2022-11-09T10:10:15.885119+01:00 ITI kernel: [    3.704495] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_uvd.bin
> 2022-11-09T10:10:15.885120+01:00 ITI kernel: [    3.704497] [drm] Found UVD
> firmware Version: 1.130 Family ID: 16
> 2022-11-09T10:10:15.885120+01:00 ITI kernel: [    3.705128] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_vce.bin
> 2022-11-09T10:10:15.885121+01:00 ITI kernel: [    3.705131] [drm] Found VCE
> firmware Version: 53.26 Binary ID: 3
> 2022-11-09T10:10:15.885121+01:00 ITI kernel: [    3.705702] amdgpu
> 0000:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_k_smc.bin
> 2022-11-09T10:10:15.885122+01:00 ITI kernel: [    3.759276] usbcore:
> registered
> new interface driver usbhid
> 2022-11-09T10:10:15.885122+01:00 ITI kernel: [    3.759280] usbhid: USB HID
> core driver
> 2022-11-09T10:10:15.885124+01:00 ITI kernel: [    3.761877] input: Logitech
> USB
> Receiver as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.0/0003:046D:C52B.0001/input/input2
> 2022-11-09T10:10:15.885125+01:00 ITI kernel: [    3.779978] scsi 13:0:0:1:
> Wrong diagnostic page; asked for 1 got 8
> 2022-11-09T10:10:15.885125+01:00 ITI kernel: [    3.779985] scsi 13:0:0:1:
> Failed to get diagnostic page 0x1
> 2022-11-09T10:10:15.885126+01:00 ITI kernel: [    3.779988] scsi 13:0:0:1:
> Failed to bind enclosure -19
> 2022-11-09T10:10:15.885126+01:00 ITI kernel: [    3.780011] ses 13:0:0:1:
> Attached Enclosure device
> 2022-11-09T10:10:15.885126+01:00 ITI kernel: [    3.824897] hid-generic
> 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB
> Receiver] on usb-0000:01:00.0-1/input0
> 2022-11-09T10:10:15.885130+01:00 ITI kernel: [    3.825091] input: Logitech
> USB
> Receiver Mouse as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.1/0003:046D:C52B.0002/input/input3
> 2022-11-09T10:10:15.885130+01:00 ITI kernel: [    3.825143] input: Logitech
> USB
> Receiver Consumer Control as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.1/0003:046D:C52B.0002/input/input4
> 2022-11-09T10:10:15.885131+01:00 ITI kernel: [    3.888825] input: Logitech
> USB
> Receiver System Control as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.1/0003:046D:C52B.0002/input/input5
> 2022-11-09T10:10:15.885131+01:00 ITI kernel: [    3.888890] hid-generic
> 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech
> USB
> Receiver] on usb-0000:01:00.0-1/input1
> 2022-11-09T10:10:15.885132+01:00 ITI kernel: [    3.889056] hid-generic
> 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB
> Receiver] on usb-0000:01:00.0-1/input2
> 2022-11-09T10:10:15.885134+01:00 ITI kernel: [    3.889182] input: Logitech
> USB
> Keyboard as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-5/1-5:1.0/0003:046D:C328.0004/input/input7
> 2022-11-09T10:10:15.885134+01:00 ITI kernel: [    3.948856] hid-generic
> 0003:046D:C328.0004: input,hidraw3: USB HID v1.10 Keyboard [Logitech USB
> Keyboard] on usb-0000:01:00.0-5/input0
> 2022-11-09T10:10:15.885135+01:00 ITI kernel: [    3.948989] input: Logitech
> USB
> Keyboard Consumer Control as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-5/1-5:1.1/0003:046D:C328.0005/input/input8
> 2022-11-09T10:10:15.885135+01:00 ITI kernel: [    4.008805] input: Logitech
> USB
> Keyboard System Control as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-5/1-5:1.1/0003:046D:C328.0005/input/input9
> 2022-11-09T10:10:15.885135+01:00 ITI kernel: [    4.008842] hid-generic
> 0003:046D:C328.0005: input,hiddev2,hidraw4: USB HID v1.10 Device [Logitech
> USB
> Keyboard] on usb-0000:01:00.0-5/input1
> 2022-11-09T10:10:15.885138+01:00 ITI kernel: [    4.020209] [drm] Display
> Core
> initialized with v3.2.198!
> 2022-11-09T10:10:15.885138+01:00 ITI kernel: [    4.098674] [drm] UVD and
> UVD
> ENC initialized successfully.
> 2022-11-09T10:10:15.885139+01:00 ITI kernel: [    4.198605] [drm] VCE
> initialized successfully.
> 2022-11-09T10:10:15.885140+01:00 ITI kernel: [    4.200050] kfd kfd: amdgpu:
> Allocated 3969056 bytes on gart
> 2022-11-09T10:10:15.885140+01:00 ITI kernel: [    4.200097] amdgpu:
> sdma_bitmap: f
> 2022-11-09T10:10:15.885141+01:00 ITI kernel: [    4.200132] amdgpu: SRAT
> table
> not found
> 2022-11-09T10:10:15.885143+01:00 ITI kernel: [    4.200133] amdgpu: Virtual
> CRAT table created for GPU
> 2022-11-09T10:10:15.885143+01:00 ITI kernel: [    4.200219] amdgpu:
> Topology:
> Add dGPU node [0x67df:0x1002]
> 2022-11-09T10:10:15.885144+01:00 ITI kernel: [    4.200221] kfd kfd: amdgpu:
> added device 1002:67df
> 2022-11-09T10:10:15.885144+01:00 ITI kernel: [    4.200235] amdgpu
> 0000:06:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 36
> 2022-11-09T10:10:15.885144+01:00 ITI kernel: [    4.204288] amdgpu
> 0000:06:00.0: amdgpu: Using BACO for runtime pm
> 2022-11-09T10:10:15.885145+01:00 ITI kernel: [    4.204644] [drm]
> Initialized
> amdgpu 3.48.0 20150101 for 0000:06:00.0 on minor 0
> 2022-11-09T10:10:15.885146+01:00 ITI kernel: [    4.209184]
> logitech-djreceiver
> 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB
> Receiver] on usb-0000:01:00.0-1/input2
> 2022-11-09T10:10:15.885148+01:00 ITI kernel: [    4.211859] fbcon:
> amdgpudrmfb
> (fb0) is primary device
> 2022-11-09T10:10:15.885149+01:00 ITI kernel: [    4.307359] Console:
> switching
> to colour frame buffer device 240x67
> 2022-11-09T10:10:15.885150+01:00 ITI kernel: [    4.324792] amdgpu
> 0000:06:00.0: [drm] fb0: amdgpudrmfb frame buffer device
> 2022-11-09T10:10:15.885150+01:00 ITI kernel: [    4.332254] input: Logitech
> Wireless Device PID:4055 Mouse as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0003/0003:046D:4055.0007/input/input10
> 2022-11-09T10:10:15.885151+01:00 ITI kernel: [    4.332544] hid-generic
> 0003:046D:4055.0007: input,hidraw1: USB HID v1.11 Mouse [Logitech Wireless
> Device PID:4055] on usb-0000:01:00.0-1/input2:1
> 2022-11-09T10:10:15.885153+01:00 ITI kernel: [    4.363247] input: Logitech
> Wireless Mouse as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-1/1-1:1.2/0003:046D:C52B.0003/0003:046D:4055.0007/input/input14
> 2022-11-09T10:10:15.885154+01:00 ITI kernel: [    4.363297] logitech-hidpp-
> device 0003:046D:4055.0007: input,hidraw1: USB HID v1.11 Mouse [Logitech
> Wireless Mouse] on usb-0000:01:00.0-1/input2:1
> 2022-11-09T10:10:15.885154+01:00 ITI kernel: [    4.405306] PM: Image not
> found
> (code -22)
> 2022-11-09T10:10:15.885154+01:00 ITI kernel: [    4.476556] EXT4-fs (sda1):
> mounted filesystem with ordered data mode. Quota mode: none.
> 2022-11-09T10:10:15.885155+01:00 ITI kernel: [    4.529527] Not activating
> Mandatory Access Control as /sbin/tomoyo-init does not exist.
> 2022-11-09T10:10:15.885198+01:00 ITI kernel: [    4.895488] fuse: init (API
> version 7.36)
> 2022-11-09T10:10:15.885201+01:00 ITI kernel: [    4.902011] EXT4-fs (sda1):
> re-
> mounted. Quota mode: none.
> 2022-11-09T10:10:15.885201+01:00 ITI kernel: [    4.912151] lp: driver
> loaded
> but no devices found
> 2022-11-09T10:10:15.885202+01:00 ITI kernel: [    4.915000] ppdev:
> user-space
> parallel port driver
> 2022-11-09T10:10:15.885202+01:00 ITI kernel: [    4.917698] parport_pc
> 00:03:
> reported by Plug and Play ACPI
> 2022-11-09T10:10:15.885202+01:00 ITI kernel: [    4.917774] parport0:
> PC-style
> at 0x378, irq 5 [PCSPP,TRISTATE,EPP]
> 2022-11-09T10:10:15.885203+01:00 ITI kernel: [    5.020899] lp0: using
> parport0
> (interrupt-driven).
> 2022-11-09T10:10:15.885204+01:00 ITI kernel: [    5.109808] sd 10:0:0:0:
> Attached scsi generic sg0 type 0
> 2022-11-09T10:10:15.885206+01:00 ITI kernel: [    5.109838] sd 11:0:0:0:
> Attached scsi generic sg1 type 0
> 2022-11-09T10:10:15.885206+01:00 ITI kernel: [    5.109870] sr 15:0:0:0:
> Attached scsi generic sg2 type 5
> 2022-11-09T10:10:15.885207+01:00 ITI kernel: [    5.109894] sd 12:0:0:0:
> Attached scsi generic sg3 type 0
> 2022-11-09T10:10:15.885208+01:00 ITI kernel: [    5.109922] sd 13:0:0:0:
> Attached scsi generic sg4 type 0
> 2022-11-09T10:10:15.885208+01:00 ITI kernel: [    5.109948] ses 13:0:0:1:
> Attached scsi generic sg5 type 13
> 2022-11-09T10:10:15.885208+01:00 ITI kernel: [    5.109975] sd 14:0:0:0:
> Attached scsi generic sg6 type 0
> 2022-11-09T10:10:15.885211+01:00 ITI kernel: [    5.130268] acpi_cpufreq:
> overriding BIOS provided _PSD data
> 2022-11-09T10:10:15.885211+01:00 ITI kernel: [    5.157071] it87: Found
> IT8733E
> chip at 0xa60, revision 3
> 2022-11-09T10:10:15.885212+01:00 ITI kernel: [    5.241151] input: GreenAsia
> Inc.    USB Joystick      as
> /devices/pci0000:00/0000:00:01.3/0000:01:00.0/usb1/1-10/1-10:1.0/0003:0E8F:0003.0006/input/input15
> 2022-11-09T10:10:15.885213+01:00 ITI kernel: [    5.280138] pantherlord
> 0003:0E8F:0003.0006: input,hidraw2: USB HID v1.10 Joystick [GreenAsia Inc.
> USB Joystick     ] on usb-0000:01:00.0-10/input0
> 2022-11-09T10:10:15.885214+01:00 ITI kernel: [    5.280162] pantherlord
> 0003:0E8F:0003.0006: Force feedback for PantherLord/GreenAsia devices by
> Anssi
> Hannula <anssi.hannula@gmail.com>
> 2022-11-09T10:10:15.885214+01:00 ITI kernel: [    5.291974] input: PC
> Speaker
> as /devices/platform/pcspkr/input/input16
> 2022-11-09T10:10:15.885216+01:00 ITI kernel: [    5.311795] ccp
> 0000:07:00.2:
> ccp enabled
> 2022-11-09T10:10:15.885217+01:00 ITI kernel: [    5.311827] ccp
> 0000:07:00.2:
> psp enabled
> 2022-11-09T10:10:15.885217+01:00 ITI kernel: [    5.313008] sp5100_tco:
> SP5100/SB800 TCO WatchDog Timer Driver
> 2022-11-09T10:10:15.885218+01:00 ITI kernel: [    5.313705] sp5100-tco
> sp5100-tco: Using 0xfeb00000 for watchdog MMIO address
> 2022-11-09T10:10:15.885218+01:00 ITI kernel: [    5.313842] sp5100-tco
> sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
> 2022-11-09T10:10:15.885219+01:00 ITI kernel: [    5.336812] Adding 4060156k
> swap on /dev/sda5.  Priority:-2 extents:1 across:4060156k SSFS
> 2022-11-09T10:10:15.885221+01:00 ITI kernel: [    5.337363] RAPL PMU: API
> unit
> is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer
> 2022-11-09T10:10:15.885221+01:00 ITI kernel: [    5.337368] RAPL PMU: hw
> unit
> of domain package 2^-16 Joules
> 2022-11-09T10:10:15.885222+01:00 ITI kernel: [    5.342158] cryptd:
> max_cpu_qlen set to 1000
> 2022-11-09T10:10:15.885222+01:00 ITI kernel: [    5.354872] AVX2 version of
> gcm_enc/dec engaged.
> 2022-11-09T10:10:15.885223+01:00 ITI kernel: [    5.354901] AES CTR mode by8
> optimization enabled
> 2022-11-09T10:10:15.885223+01:00 ITI kernel: [    5.402186] snd_hda_intel
> 0000:06:00.1: Force to non-snoop mode
> 2022-11-09T10:10:15.885225+01:00 ITI kernel: [    5.402196] snd_hda_intel
> 0000:06:00.1: Applying patch firmware 'hda-jack-retask.fw'
> 2022-11-09T10:10:15.885226+01:00 ITI kernel: [    5.402341] snd_hda_intel
> 0000:08:00.3: Applying patch firmware 'hda-jack-retask.fw'
> 2022-11-09T10:10:15.885226+01:00 ITI kernel: [    5.404988] snd_hda_intel
> 0000:06:00.1: firmware: direct-loading firmware hda-jack-retask.fw
> 2022-11-09T10:10:15.885226+01:00 ITI kernel: [    5.419198] snd_hda_intel
> 0000:06:00.1: bound 0000:06:00.0 (ops amdgpu_dm_audio_component_bind_ops
> [amdgpu])
> 2022-11-09T10:10:15.885227+01:00 ITI kernel: [    5.438500] input: HDA ATI
> HDMI
> HDMI/DP,pcm=3 as
> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input17
> 2022-11-09T10:10:15.885227+01:00 ITI kernel: [    5.438576] input: HDA ATI
> HDMI
> HDMI/DP,pcm=7 as
> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input18
> 2022-11-09T10:10:15.885229+01:00 ITI kernel: [    5.438629] input: HDA ATI
> HDMI
> HDMI/DP,pcm=8 as
> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input19
> 2022-11-09T10:10:15.885230+01:00 ITI kernel: [    5.438844] input: HDA ATI
> HDMI
> HDMI/DP,pcm=9 as
> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input20
> 2022-11-09T10:10:15.885230+01:00 ITI kernel: [    5.438891] input: HDA ATI
> HDMI
> HDMI/DP,pcm=10 as
> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input21
> 2022-11-09T10:10:15.885231+01:00 ITI kernel: [    5.438937] input: HDA ATI
> HDMI
> HDMI/DP,pcm=11 as
> /devices/pci0000:00/0000:00:03.1/0000:06:00.1/sound/card0/input22
> 2022-11-09T10:10:15.885231+01:00 ITI kernel: [    5.471956]
> snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1
> (0x14/0x0/0x0/0x0/0x0) type:line
> 2022-11-09T10:10:15.885231+01:00 ITI kernel: [    5.471962]
> snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> 2022-11-09T10:10:15.885234+01:00 ITI kernel: [    5.471964]
> snd_hda_codec_realtek hdaudioC1D0:    hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
> 2022-11-09T10:10:15.885234+01:00 ITI kernel: [    5.471966]
> snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
> 2022-11-09T10:10:15.885235+01:00 ITI kernel: [    5.471967]
> snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x11/0x0
> 2022-11-09T10:10:15.885235+01:00 ITI kernel: [    5.471968]
> snd_hda_codec_realtek hdaudioC1D0:    inputs:
> 2022-11-09T10:10:15.885236+01:00 ITI kernel: [    5.471969]
> snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
> 2022-11-09T10:10:15.885236+01:00 ITI kernel: [    5.471971]
> snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
> 2022-11-09T10:10:15.885238+01:00 ITI kernel: [    5.471972]
> snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
> 2022-11-09T10:10:15.885239+01:00 ITI kernel: [    5.506911] input: HD-Audio
> Generic Front Mic as
> /devices/pci0000:00/0000:00:08.1/0000:08:00.3/sound/card1/input23
> 2022-11-09T10:10:15.885239+01:00 ITI kernel: [    5.506961] input: HD-Audio
> Generic Rear Mic as
> /devices/pci0000:00/0000:00:08.1/0000:08:00.3/sound/card1/input24
> 2022-11-09T10:10:15.885240+01:00 ITI kernel: [    5.507004] input: HD-Audio
> Generic Line as
> /devices/pci0000:00/0000:00:08.1/0000:08:00.3/sound/card1/input25
> 2022-11-09T10:10:15.885240+01:00 ITI kernel: [    5.507038] input: HD-Audio
> Generic Line Out as
> /devices/pci0000:00/0000:00:08.1/0000:08:00.3/sound/card1/input26
> 2022-11-09T10:10:15.885240+01:00 ITI kernel: [    5.523877] kvm: support for
> 'kvm_amd' disabled by bios
> 2022-11-09T10:10:15.885244+01:00 ITI kernel: [    5.558645] MCE: In-kernel
> MCE
> decoding enabled.
> 2022-11-09T10:10:15.885245+01:00 ITI kernel: [    5.560146] kvm: support for
> 'kvm_amd' disabled by bios
> 2022-11-09T10:10:15.885245+01:00 ITI kernel: [    5.648560] kvm: support for
> 'kvm_amd' disabled by bios
> 2022-11-09T10:10:15.885245+01:00 ITI kernel: [    5.649165]
> intel_rapl_common:
> Found RAPL domain package
> 2022-11-09T10:10:15.885246+01:00 ITI kernel: [    5.649170]
> intel_rapl_common:
> Found RAPL domain core
> 2022-11-09T10:10:15.885246+01:00 ITI kernel: [    5.704769] kvm: support for
> 'kvm_amd' disabled by bios
> 2022-11-09T10:10:15.885249+01:00 ITI kernel: [    5.966438] EXT4-fs (sdb1):
> mounted filesystem with ordered data mode. Quota mode: none.
> 2022-11-09T10:10:15.885250+01:00 ITI kernel: [    6.017930] audit: type=1400
> audit(1667985015.722:2): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="lsb_release" pid=704 comm="apparmor_parser"
> 2022-11-09T10:10:15.885256+01:00 ITI kernel: [    6.019401] audit: type=1400
> audit(1667985015.722:3): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="nvidia_modprobe" pid=705 comm="apparmor_parser"
> 2022-11-09T10:10:15.885257+01:00 ITI kernel: [    6.019407] audit: type=1400
> audit(1667985015.722:4): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="nvidia_modprobe//kmod" pid=705
> comm="apparmor_parser"
> 2022-11-09T10:10:15.885257+01:00 ITI kernel: [    6.021517] audit: type=1400
> audit(1667985015.726:5): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="/usr/bin/man" pid=708 comm="apparmor_parser"
> 2022-11-09T10:10:15.885259+01:00 ITI kernel: [    6.021522] audit: type=1400
> audit(1667985015.726:6): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="man_filter" pid=708 comm="apparmor_parser"
> 2022-11-09T10:10:15.885260+01:00 ITI kernel: [    6.021526] audit: type=1400
> audit(1667985015.726:7): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="man_groff" pid=708 comm="apparmor_parser"
> 2022-11-09T10:10:15.885260+01:00 ITI kernel: [    6.023240] audit: type=1400
> audit(1667985015.726:8): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-
> session" pid=703 comm="apparmor_parser"
> 2022-11-09T10:10:15.885261+01:00 ITI kernel: [    6.023245] audit: type=1400
> audit(1667985015.726:9): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-
> session//chromium" pid=703 comm="apparmor_parser"
> 2022-11-09T10:10:15.885261+01:00 ITI kernel: [    6.023858] audit: type=1400
> audit(1667985015.726:10): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="libreoffice-oosplash" pid=710
> comm="apparmor_parser"
> 2022-11-09T10:10:15.885264+01:00 ITI kernel: [    6.025993] audit: type=1400
> audit(1667985015.730:11): apparmor="STATUS" operation="profile_load"
> profile="unconfined" name="libreoffice-senddoc" pid=711
> comm="apparmor_parser"
> 2022-11-09T10:10:15.885264+01:00 ITI kernel: [    6.136339] input: ACPI
> Virtual
> Keyboard Device as /devices/virtual/input/input27
> 2022-11-09T10:10:15.974723+01:00 ITI kernel: [    6.263330] BUG: kernel NULL
> pointer dereference, address: 00000000000001c8
> 2022-11-09T10:10:15.974741+01:00 ITI kernel: [    6.263334] #PF: supervisor
> write access in kernel mode
> 2022-11-09T10:10:15.974741+01:00 ITI kernel: [    6.263335] #PF:
> error_code(0x0002) - not-present page
> 2022-11-09T10:10:15.974742+01:00 ITI kernel: [    6.263337] PGD 0 P4D 0
> 2022-11-09T10:10:15.974743+01:00 ITI kernel: [    6.263339] Oops: 0002 [#1]
> PREEMPT SMP NOPTI
> 2022-11-09T10:10:15.974743+01:00 ITI kernel: [    6.263341] CPU: 2 PID: 767
> Comm: rasdaemon Not tainted 6.0.0-2-amd64 #1  Debian 6.0.5-1
> 2022-11-09T10:10:15.974744+01:00 ITI kernel: [    6.263343] Hardware name:
> Gigabyte Technology Co., Ltd. AB350M-Gaming 3/AB350M-Gaming 3-CF, BIOS F50d
> 07/02/2020
> 2022-11-09T10:10:15.974746+01:00 ITI kernel: [    6.263344] RIP:
> 0010:ring_buffer_wake_waiters+0x1c/0xa0
> 2022-11-09T10:10:15.974747+01:00 ITI kernel: [    6.263349] Code: 48 39 d0
> 73
> ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b
> 47
> 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20
> be
> 03 00 00 00 e8 5d b0 f4
> 2022-11-09T10:10:15.974749+01:00 ITI kernel: [    6.263351] RSP:
> 0018:ffffb10dc0cbfe98 EFLAGS: 00010206
> 2022-11-09T10:10:15.974749+01:00 ITI kernel: [    6.263353] RAX:
> ffff89f9a1160300 RBX: 0000000000000178 RCX: 0000000000000000
> 2022-11-09T10:10:15.974749+01:00 ITI kernel: [    6.263354] RDX:
> ffff89f982cd4000 RSI: 0000000000000004 RDI: ffff89f9a1160200
> 2022-11-09T10:10:15.974750+01:00 ITI kernel: [    6.263355] RBP:
> ffff89f9a1160200 R08: ffff89f964090740 R09: ffff89f945629180
> 2022-11-09T10:10:15.974751+01:00 ITI kernel: [    6.263356] R10:
> 0000000000000000 R11: 0000000000000000 R12: ffff89f945629180
> 2022-11-09T10:10:15.974751+01:00 ITI kernel: [    6.263356] R13:
> ffff89f947127ce0 R14: ffff89f9455bb300 R15: 0000000000000000
> 2022-11-09T10:10:15.974751+01:00 ITI kernel: [    6.263358] FS:
> 00007f2534190740(0000) GS:ffff89fc4e880000(0000) knlGS:0000000000000000
> 2022-11-09T10:10:15.974752+01:00 ITI kernel: [    6.263359] CS: 0010 DS:
> 0000
> ES: 0000 CR0: 0000000080050033
> 2022-11-09T10:10:15.974752+01:00 ITI kernel: [    6.263360] CR2:
> 00000000000001c8 CR3: 0000000107130000 CR4: 00000000003506e0
> 2022-11-09T10:10:15.974753+01:00 ITI kernel: [    6.263361] Call Trace:
> 2022-11-09T10:10:15.974753+01:00 ITI kernel: [    6.263364] <TASK>
> 2022-11-09T10:10:15.974754+01:00 ITI kernel: [    6.263367]
> tracing_buffers_release+0x49/0x90
> 2022-11-09T10:10:15.974755+01:00 ITI kernel: [    6.263370]
> __fput+0x91/0x250
> 2022-11-09T10:10:15.974755+01:00 ITI kernel: [    6.263374]
> task_work_run+0x5c/0x90
> 2022-11-09T10:10:15.974755+01:00 ITI kernel: [    6.263377]
> exit_to_user_mode_prepare+0x1cd/0x1e0
> 2022-11-09T10:10:15.974756+01:00 ITI kernel: [    6.263380]
> syscall_exit_to_user_mode+0x17/0x40
> 2022-11-09T10:10:15.974756+01:00 ITI kernel: [    6.263383]
> do_syscall_64+0x46/0xc0
> 2022-11-09T10:10:15.974757+01:00 ITI kernel: [    6.263386]
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> 2022-11-09T10:10:15.974758+01:00 ITI kernel: [    6.263389] RIP:
> 0033:0x7f253436a770
> 2022-11-09T10:10:15.974758+01:00 ITI kernel: [    6.263392] Code: 0d 00 00
> 00
> eb b2 e8 4f f7 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 80 3d 71
> 1e
> 0e 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00
> 00
> 00 00 48 83 ec 18 89 7c
> 2022-11-09T10:10:15.974759+01:00 ITI kernel: [    6.263393] RSP:
> 002b:00007ffd70e3da78 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
> 2022-11-09T10:10:15.974759+01:00 ITI kernel: [    6.263394] RAX:
> 0000000000000000 RBX: 0000000000000004 RCX: 00007f253436a770
> 2022-11-09T10:10:15.974759+01:00 ITI kernel: [    6.263395] RDX:
> 0000000000000021 RSI: 00007ffd70e3dd00 RDI: 0000000000000009
> 2022-11-09T10:10:15.974760+01:00 ITI kernel: [    6.263396] RBP:
> 00007ffd70e3f1d0 R08: 0000000000000007 R09: 000055ca57ae0700
> 2022-11-09T10:10:15.974760+01:00 ITI kernel: [    6.263397] R10:
> 0000000000000008 R11: 0000000000000202 R12: 00007ffd70e3db00
> 2022-11-09T10:10:15.974761+01:00 ITI kernel: [    6.263397] R13:
> 0000000000000001 R14: 0000000000000021 R15: 000055ca57ae06f0
> 2022-11-09T10:10:15.974761+01:00 ITI kernel: [    6.263400] </TASK>
> 2022-11-09T10:10:15.974762+01:00 ITI kernel: [    6.263400] Modules linked
> in:
> uinput binfmt_misc intel_rapl_msr intel_rapl_common edac_mce_amd kvm
> snd_hda_codec_realtek irqbypass snd_hda_codec_generic ledtrig_audio
> ghash_clmulni_intel snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg
> snd_intel_sdw_acpi snd_hda_codec aesni_intel snd_hda_core crypto_simd cryptd
> snd_hwdep snd_pcm wmi_bmof rapl pcspkr ccp snd_timer sp5100_tco snd watchdog
> k10temp soundcore rng_core hid_pl ff_memless it87 joydev hwmon_vid
> acpi_cpufreq
> sg evdev msr parport_pc ppdev lp parport fuse efi_pstore configfs ip_tables
> x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_logitech_hidpp
> hid_logitech_dj hid_generic ses sr_mod enclosure scsi_transport_sas cdrom
> usbhid hid amdgpu sd_mod t10_pi uas usb_storage crc64_rocksoft crc64
> crc_t10dif
> crct10dif_generic gpu_sched drm_buddy i2c_algo_bit drm_display_helper cec
> ahci
> rc_core r8169 drm_ttm_helper libahci xhci_pci crct10dif_pclmul
> crct10dif_common
> realtek ttm crc32_pclmul crc32c_intel xhci_hcd drm_kms_helper
> 2022-11-09T10:10:15.974763+01:00 ITI kernel: [    6.263453] mdio_devres
> libata
> libphy usbcore drm scsi_mod scsi_common usb_common i2c_piix4 wmi gpio_amdpt
> gpio_generic button
> 2022-11-09T10:10:15.974764+01:00 ITI kernel: [    6.263462] CR2:
> 00000000000001c8
> 2022-11-09T10:10:15.974764+01:00 ITI kernel: [    6.263463] ---[ end trace
> 0000000000000000 ]---
> 2022-11-09T10:10:15.974765+01:00 ITI kernel: [    6.263464] RIP:
> 0010:ring_buffer_wake_waiters+0x1c/0xa0
> 2022-11-09T10:10:15.974766+01:00 ITI kernel: [    6.263466] Code: 48 39 d0
> 73
> ed 0f 0b eb e9 0f 1f 44 00 00 55 48 89 fd 53 48 63 de 83 fb ff 74 36 48 8b
> 47
> 40 48 8b 1c d8 48 81 c3 78 01 00 00 <48> 83 43 50 01 31 c9 31 d2 48 8d 7b 20
> be
> 03 00 00 00 e8 5d b0 f4
> 2022-11-09T10:10:15.974766+01:00 ITI kernel: [    6.263467] RSP:
> 0018:ffffb10dc0cbfe98 EFLAGS: 00010206
> 2022-11-09T10:10:15.974767+01:00 ITI kernel: [    6.263469] RAX:
> ffff89f9a1160300 RBX: 0000000000000178 RCX: 0000000000000000
> 2022-11-09T10:10:15.974767+01:00 ITI kernel: [    6.263470] RDX:
> ffff89f982cd4000 RSI: 0000000000000004 RDI: ffff89f9a1160200
> 2022-11-09T10:10:15.974768+01:00 ITI kernel: [    6.263470] RBP:
> ffff89f9a1160200 R08: ffff89f964090740 R09: ffff89f945629180
> 2022-11-09T10:10:15.974768+01:00 ITI kernel: [    6.263471] R10:
> 0000000000000000 R11: 0000000000000000 R12: ffff89f945629180
> 2022-11-09T10:10:15.974769+01:00 ITI kernel: [    6.263472] R13:
> ffff89f947127ce0 R14: ffff89f9455bb300 R15: 0000000000000000
> 2022-11-09T10:10:15.974770+01:00 ITI kernel: [    6.263473] FS:
> 00007f2534190740(0000) GS:ffff89fc4e880000(0000) knlGS:0000000000000000
> 2022-11-09T10:10:15.974770+01:00 ITI kernel: [    6.263474] CS: 0010 DS:
> 0000
> ES: 0000 CR0: 0000000080050033
> 2022-11-09T10:10:15.974771+01:00 ITI kernel: [    6.263475] CR2:
> 00000000000001c8 CR3: 0000000107130000 CR4: 00000000003506e0
> 2022-11-09T10:10:22.130691+01:00 ITI kernel: [   12.419631] logitech-hidpp-
> device 0003:046D:4055.0007: HID++ 4.5 device connected.
> root@ITI:/var/log#

Looking through the above the issue seems to be the same as #1023726.

Can you verify if the issue disapears if you disable rasdaemon?

Can you verify if the attached patch fixes the problem as well for
you?

Regards,
Salvatore

[toc] | [next] | [standalone]

#76984

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-09 17:10 +0100
Message-ID<FpVOh-2xTg-9@gated-at.bofh.it>
In reply to#76982

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

Thanks for your quick answer !

I tried the command "rasdaemon --disable" (as sudoer) , but it blocks 
and apparently doesn't product any effect. I also tried to directly kill 
the rasdaemon process, without success.

Additionnally, I am not sure to know how to proceed in order to apply 
the patch you sent. Could you give me some hint ?

Thanks in advance for your help.

Best regards.

-- Guy Durrieu.

Le 09/11/2022 à 16:19, Salvatore Bonaccorso a écrit :
> Looking through the above the issue seems to be the same as #1023726.
>
> Can you verify if the issue disapears if you disable rasdaemon?
>
> Can you verify if the attached patch fixes the problem as well for
> you?
>
> Regards,
> Salvatore

[toc] | [prev] | [next] | [standalone]

#76985

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-09 17:30 +0100
Message-ID<FpW7D-2xZz-1@gated-at.bofh.it>
In reply to#76984

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

Sorry. My first attempt was under 6.0.0-2... I tried again disabling 
rasdaemon under 5.19.0-2 (it worked). Then I restarted 6.0.0-2 and the 
issue seems to have disapeared (after a first bad start).

Concerning the patch, my question remains (I don't have the source for 
ring_buffer).

Thanks for your help.

Best regards.

-- Guy Durrieu.


Le 09/11/2022 à 16:55, Guy Durrieu a écrit :
>
> Hi Salvatore,
>
> Thanks for your quick answer !
>
> I tried the command "rasdaemon --disable" (as sudoer) , but it blocks 
> and apparently doesn't product any effect. I also tried to directly 
> kill the rasdaemon process, without success.
>
> Additionnally, I am not sure to know how to proceed in order to apply 
> the patch you sent. Could you give me some hint ?
>
> Thanks in advance for your help.
>
> Best regards.
>
> -- Guy Durrieu.
>
> Le 09/11/2022 à 16:19, Salvatore Bonaccorso a écrit :
>> Looking through the above the issue seems to be the same as #1023726.
>>
>> Can you verify if the issue disapears if you disable rasdaemon?
>>
>> Can you verify if the attached patch fixes the problem as well for
>> you?
>>
>> Regards,
>> Salvatore

[toc] | [prev] | [next] | [standalone]

#76987

FromSalvatore Bonaccorso <carnil@debian.org>
Date2022-11-09 17:50 +0100
Message-ID<FpWqZ-2y6g-7@gated-at.bofh.it>
In reply to#76985
Hi Guy,

On Wed, Nov 09, 2022 at 05:20:25PM +0100, Guy Durrieu wrote:
> Hi Salvatore,
> 
> Sorry. My first attempt was under 6.0.0-2... I tried again disabling
> rasdaemon under 5.19.0-2 (it worked). Then I restarted 6.0.0-2 and the issue
> seems to have disapeared (after a first bad start).

Thanks for confirming, so there is good indication you are seeing the
same as #1023726 and will later merge those.

> Concerning the patch, my question remains (I don't have the source for
> ring_buffer).

It looks I was too slow, my answer was on the way and overlapped with
this followup. There are instructions on how to "simple test patches".
But I have uploaded as well intermediate deb files (unsigned) which
you can use if you have enough trust level on the path to fetch them.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#76989

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-09 18:10 +0100
Message-ID<FpWKl-2ysh-3@gated-at.bofh.it>
In reply to#76987
Hi Salvatore,

OK, I will try that as soon as possible. Am I supposed to re-enable the 
rasdeamon once the patch applied ? Anyway I will report you the result 
(f I don't make any mistake).

Thanks a lot for your help !

Best regards.


Le 09/11/2022 à 17:46, Salvatore Bonaccorso a écrit :
> Hi Guy,
>
> On Wed, Nov 09, 2022 at 05:20:25PM +0100, Guy Durrieu wrote:
>> Hi Salvatore,
>>
>> Sorry. My first attempt was under 6.0.0-2... I tried again disabling
>> rasdaemon under 5.19.0-2 (it worked). Then I restarted 6.0.0-2 and the issue
>> seems to have disapeared (after a first bad start).
> Thanks for confirming, so there is good indication you are seeing the
> same as #1023726 and will later merge those.
>
>> Concerning the patch, my question remains (I don't have the source for
>> ring_buffer).
> It looks I was too slow, my answer was on the way and overlapped with
> this followup. There are instructions on how to "simple test patches".
> But I have uploaded as well intermediate deb files (unsigned) which
> you can use if you have enough trust level on the path to fetch them.
>
> Regards,
> Salvatore

[toc] | [prev] | [next] | [standalone]

#76990

FromSalvatore Bonaccorso <carnil@debian.org>
Date2022-11-09 19:30 +0100
Message-ID<FpXZL-2zFs-1@gated-at.bofh.it>
In reply to#76989
Hi Guy,

On Wed, Nov 09, 2022 at 06:05:58PM +0100, Guy Durrieu wrote:
> Hi Salvatore,
> 
> OK, I will try that as soon as possible. Am I supposed to re-enable the
> rasdeamon once the patch applied ? Anyway I will report you the result (f I
> don't make any mistake).

Yes right, the idea would be to boot the new kernel with rasdeamon
enabled again and see if the system is stable again. 

Be aware though that rasdaemon itself might segfault, there is a
second issue, where rasdaemon needs fixing as well, see #1023725.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#77004

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-10 18:30 +0100
Message-ID<Fqjxf-2OnD-3@gated-at.bofh.it>
In reply to#76990

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

I did the test using the kernel image you built for me. After 
reactivating rasdaemon (and rebooting), all apparently work fine.

I have a last question: Do I keep this version, and what will happen 
when the next kernel update occurs ? And what about the 6.0.0.2 one ?

Thanks for your help !

Best regards.

-- Guy.

Le 09/11/2022 à 19:21, Salvatore Bonaccorso a écrit :
> Hi Guy,
>
> On Wed, Nov 09, 2022 at 06:05:58PM +0100, Guy Durrieu wrote:
>> Hi Salvatore,
>>
>> OK, I will try that as soon as possible. Am I supposed to re-enable the
>> rasdeamon once the patch applied ? Anyway I will report you the result (f I
>> don't make any mistake).
> Yes right, the idea would be to boot the new kernel with rasdeamon
> enabled again and see if the system is stable again.
>
> Be aware though that rasdaemon itself might segfault, there is a
> second issue, where rasdaemon needs fixing as well, see #1023725.
>
> Regards,
> Salvatore

[toc] | [prev] | [next] | [standalone]

#77006

FromSalvatore Bonaccorso <carnil@debian.org>
Date2022-11-10 20:50 +0100
Message-ID<FqlIJ-2PAP-5@gated-at.bofh.it>
In reply to#77004
Hi Guy, 

[Thanks to Diederik for taking time as well to contribute!]

On Thu, Nov 10, 2022 at 06:22:48PM +0100, Guy Durrieu wrote:
> Hi Salvatore,
> 
> I did the test using the kernel image you built for me. After reactivating
> rasdaemon (and rebooting), all apparently work fine.

Good news, thanks for your testing! So it's the same as #1023726.

> I have a last question: Do I keep this version, and what will happen when
> the next kernel update occurs ? And what about the 6.0.0.2 one ?

As it is an unofficial build, please do revert back to an official
one. I plan to upload 6.0.8-1 based on the today's released 6.0.8
"soonish" which will contain the fix as well.

Hope this helps so far,

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#76988

FromSalvatore Bonaccorso <carnil@debian.org>
Date2022-11-09 17:50 +0100
Message-ID<FpWqZ-2y6g-1@gated-at.bofh.it>
In reply to#76984
Hi Guy,

On Wed, Nov 09, 2022 at 04:55:36PM +0100, Guy Durrieu wrote:
> Hi Salvatore,
> 
> Thanks for your quick answer !
> 
> I tried the command "rasdaemon --disable" (as sudoer) , but it blocks and
> apparently doesn't product any effect. I also tried to directly kill the
> rasdaemon process, without success.

To test the behaviour without having rasdaemon started at all, do mask
the service and the reboot:

systemctl mask rasdaemon.service

(to unmask again, systemctl unmask rasdaemon.service).

> Additionnally, I am not sure to know how to proceed in order to apply the
> patch you sent. Could you give me some hint ?

There is our documentation at
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
. But would you be willing to test (but be aware, unsigned!) test
packages fetched by https://people.debian.org ?

https://people.debian.org/~carnil/tmp/linux/6.0.7-2/

I have put a sha256sum file with signature on it with my gpg key to
have an additional verification on those.

https://db.debian.org/fetchkey.cgi?fingerprint=04A4407CB9142C23030C17AE789D6F057FD863FE

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#76994

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-10 09:50 +0100
Message-ID<Fqbq1-2Jrb-1@gated-at.bofh.it>
In reply to#76988

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

Le 09/11/2022 à 17:42, Salvatore Bonaccorso a écrit :
> There is our documentation at
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
> . But would you be willing to test (but be aware, unsigned!) test
> packages fetched byhttps://people.debian.org  ?

I am not sure I am able to do that :)

The first thing to do would be to perform the check you suggested 
yesterday. Am I wrong or do I have to rebuild a whole kernel from the 
source code? In this case would it be possible to install the source 
code elsewhere than on my (relatively small) SSD ?

Excuse me for my maybe basic questions, I've never done this before, and 
thanks in advance for your help !

Best regards.

-- Guy

[toc] | [prev] | [next] | [standalone]

#76996

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-10 11:40 +0100
Message-ID<Fqd8t-2KvE-1@gated-at.bofh.it>
In reply to#76994

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

Le 10/11/2022 à 09:41, Guy Durrieu a écrit :
> I am not sure I am able to do that :) 

Perhaps I didn't understand what you meant... Does the linux image 
6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this 
case, is it sufficient to download the linux image and the linux headers 
in order to test the result ?

Thanks and my apologies !

Best regards.

-- Guy

[toc] | [prev] | [next] | [standalone]

#76999

FromDiederik de Haas <didi.debian@cknow.org>
Date2022-11-10 12:00 +0100
Message-ID<FqdrP-2KCp-1@gated-at.bofh.it>
In reply to#76996

[Multipart message — attachments visible in raw view] — view raw

Just a quick response to this question, but I'll leave it up to Salvatore for 
the rest of the bug handling/assistance :-)

On donderdag 10 november 2022 11:35:33 CET Guy Durrieu wrote:
> > I am not sure I am able to do that :)
> 
> Perhaps I didn't understand what you meant... Does the linux image
> 6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this
> case, is it sufficient to download the linux image and the linux headers
> in order to test the result ?

No. In order to test the patch, you do need to build a kernel.
The instructions from 4.2.2 is the simplest (relatively) way to build a kernel 
with a patch applied. But AFAIK, before you do the instructions from 4.2.2, 
you need to do the 'Preparation' steps from 4.2.1 first.

> Thanks and my apologies !

No need to apologize :-)
If you've never build a kernel before, it looks 'scary'. The instructions from 
4.2.2 are made to make it as simple as possible, but that doesn't mean it is 
simple (for everyone).

Good luck!

(Back to Salvatore now)

[toc] | [prev] | [next] | [standalone]

#77000

FromDiederik de Haas <didi.debian@cknow.org>
Date2022-11-10 12:20 +0100
Message-ID<FqdLb-2KYm-7@gated-at.bofh.it>
In reply to#76999

[Multipart message — attachments visible in raw view] — view raw

On donderdag 10 november 2022 11:54:59 CET Diederik de Haas wrote:
> > Perhaps I didn't understand what you meant... Does the linux image
> > 6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this
> > case, is it sufficient to download the linux image and the linux headers
> > in order to test the result ?
> 
> No. In order to test the patch, you do need to build a kernel.

Oh boy, I probably should've stayed out of it completely ...

In another response to this bug, Salvatore did provide an alternative means 
and that is using the kernel package he build for you.

See this part:

On woensdag 9 november 2022 17:42:44 CET Salvatore Bonaccorso wrote:
> > Additionnally, I am not sure to know how to proceed in order to apply the
> > patch you sent. Could you give me some hint ?
> 
> There is our documentation at
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4
> .2.2 . But would you be willing to test (but be aware, unsigned!) test
> packages fetched by https://people.debian.org ?
> 
> https://people.debian.org/~carnil/tmp/linux/6.0.7-2/
> 
> I have put a sha256sum file with signature on it with my gpg key to
> have an additional verification on those.
> 
> https://db.debian.org/fetchkey.cgi?fingerprint=04A4407CB9142C23030C17AE789D6
> F057FD863FE

So you have 2 options:
- build it yourself from source (with instructions from 4.2.2)
- Use the packages Salvatore build for you at the above location

Keep in mind that you normally shouldn't install programs ('deb' on Debian or 
'exe' if on Windows) from "strangers on the internet". Salvatore did provide a 
(gpg) signed file to provide some mitigation against the risks.
But you would still need to trust Salvatore.

If you build it yourself, then you don't download programs from "strangers on 
the internet". But that obviously is more work. Which can be daunting if you 
hadn't done that before.

HTH

(And now I'm really staying out of it ;-))

[toc] | [prev] | [next] | [standalone]

#77003

FromGuy Durrieu <guy.durrieu@cegetel.net>
Date2022-11-10 14:30 +0100
Message-ID<FqfMZ-2M98-3@gated-at.bofh.it>
In reply to#77000

[Multipart message — attachments visible in raw view] — view raw

Hi Diederik,

Thanks for your useful answer, that is what I more or less understood 
after thinking about it, but it's better to have a confirmation :)

And don't worry, my emails were a bit messy anyway !

Best regards.

-- Guy Durrieu.

Le 10/11/2022 à 12:15, Diederik de Haas a écrit :
> On donderdag 10 november 2022 11:54:59 CET Diederik de Haas wrote:
>>> Perhaps I didn't understand what you meant... Does the linux image
>>> 6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this
>>> case, is it sufficient to download the linux image and the linux headers
>>> in order to test the result ?
>> No. In order to test the patch, you do need to build a kernel.
> Oh boy, I probably should've stayed out of it completely ...
>
> In another response to this bug, Salvatore did provide an alternative means
> and that is using the kernel package he build for you.
>
> See this part:
>
> On woensdag 9 november 2022 17:42:44 CET Salvatore Bonaccorso wrote:
>>> Additionnally, I am not sure to know how to proceed in order to apply the
>>> patch you sent. Could you give me some hint ?
>> There is our documentation at
>> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4
>> .2.2 . But would you be willing to test (but be aware, unsigned!) test
>> packages fetched byhttps://people.debian.org  ?
>>
>> https://people.debian.org/~carnil/tmp/linux/6.0.7-2/
>>
>> I have put a sha256sum file with signature on it with my gpg key to
>> have an additional verification on those.
>>
>> https://db.debian.org/fetchkey.cgi?fingerprint=04A4407CB9142C23030C17AE789D6
>> F057FD863FE
> So you have 2 options:
> - build it yourself from source (with instructions from 4.2.2)
> - Use the packages Salvatore build for you at the above location
>
> Keep in mind that you normally shouldn't install programs ('deb' on Debian or
> 'exe' if on Windows) from "strangers on the internet". Salvatore did provide a
> (gpg) signed file to provide some mitigation against the risks.
> But you would still need to trust Salvatore.
>
> If you build it yourself, then you don't download programs from "strangers on
> the internet". But that obviously is more work. Which can be daunting if you
> hadn't done that before.
>
> HTH
>
> (And now I'm really staying out of it ;-))

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web