LinuxLists.cc - next-0519 on thinkpad x60: sound related? window manager crash

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Wed, 20 May 2020 13:11:37 +0200,
Pavel Machek wrote:
>
> Hi!
>
> My window manager stopped responding. I was able to recover machine
> using sysrq-k.
>
> I started writing nice report, when session failed second time. And
> then third time on next attempt.
>
> Any ideas?

Do you know when the regression started?
There have been significant code changes regarding the sound buffer
management, and it's merged in 5.6-rc1. Other than that, I have no
idea yet.

Takashi

>
> I'll send this out before this locks up...
>
> Best regards,
> Pavel
>
> [ 2801.147411] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
> [ 2801.187449] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
> [ 2801.192260] usb 1-2: new high-speed USB device number 5 using ehci-pci
> [ 2801.240241] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
> [ 2801.300663] sdhci-pci 0000:15:00.2: Will use DMA mode even though HW doesn't fully claim to support it.
> [ 2801.352181] usb 1-2: New USB device found, idVendor=0525, idProduct=a4a1, bcdDevice= 5.07
> [ 2801.352192] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 2801.352200] usb 1-2: Product: Ethernet Gadget
> [ 2801.352207] usb 1-2: Manufacturer: Linux 5.7.0-rc4-00046-g6d7c0f75a522 with musb-hdrc
> [ 2801.419872] e1000e 0000:02:00.0 eth1: NIC Link is Down
> [ 2801.428760] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-0000:00:1d.7-2, CDC Ethernet Device, 72:ed:12:23:c9:c2
> [ 2804.020289] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> [ 2804.020451] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [ 2804.022385] wlan0: authenticated
> [ 2804.024243] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [ 2804.026985] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> [ 2804.028961] wlan0: associated
> [ 2874.520955] perf: interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
> [ 3730.016148] perf: interrupt took too long (3135 > 3133), lowering kernel.perf_event_max_sample_rate to 63750
> [ 4274.984810] BUG: unable to handle page fault for address: f8600000
> [ 4274.984821] #PF: supervisor write access in kernel mode
> [ 4274.984827] #PF: error_code(0x0002) - not-present page
> [ 4274.984833] *pdpt = 000000002c0b2001 *pde = 0000000000000000
> [ 4274.984843] Oops: 0002 [#1] PREEMPT SMP PTI
> [ 4274.984853] CPU: 1 PID: 3351 Comm: marco Not tainted 5.7.0-rc6-next-20200519+ #115
> [ 4274.984859] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011
> [ 4274.984871] EIP: memset+0xb/0x20
> [ 4274.984878] Code: f9 01 72 0b 8a 0e 88 0f 8d b4 26 00 00 00 00 8b 45 f0 83 c4 04 5b 5e 5f 5d c3 8d 74 26 00 90 55 89 e5 57 89 c7 53 89 c3 89 d0 <f3> aa 89 d8 5b 5f 5d c3 cc cc cc cc cc cc cc cc cc cc cc cc cc 89
> [ 4274.984885] EAX: 00000000 EBX: f85fe000 ECX: 0001e000 EDX: 00000000
> [ 4274.984892] ESI: ed158400 EDI: f8600000 EBP: edcc9e6c ESP: edcc9e64
> [ 4274.984898] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210246
> [ 4274.984905] CR0: 80050033 CR2: f8600000 CR3: 2c114000 CR4: 000006b0
> [ 4274.984910] Call Trace:
> [ 4274.984923] snd_pcm_hw_params+0x38d/0x400
> [ 4274.984930] snd_pcm_ioctl+0x187/0xe80
> [ 4274.984940] ? __fget_files+0x86/0xc0
> [ 4274.984947] ? __fget_light+0x6b/0x80
> [ 4274.984954] ? snd_pcm_status_user64+0x90/0x90
> [ 4274.984962] ksys_ioctl+0x1cd/0x880
> [ 4274.984971] ? ksys_mmap_pgoff+0x81/0xc0
> [ 4274.984978] ? fput+0xd/0x10
> [ 4274.984984] ? ksys_mmap_pgoff+0x8d/0xc0
> [ 4274.984991] __ia32_sys_ioctl+0x10/0x12
> [ 4274.985000] do_int80_syscall_32+0x3c/0x100
> [ 4274.985010] entry_INT80_32+0x116/0x116
> [ 4274.985016] EIP: 0xb7f17092
> [ 4274.985023] Code: 00 00 00 e9 90 ff ff ff ff a3 24 00 00 00 68 30 00 00 00 e9 80 ff ff ff ff a3 e8 ff ff ff 66 90 00 00 00 00 00 00 00 00 cd 80 <c3> 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 1c 24 c3 8d b4 26 00
> [ 4274.985030] EAX: ffffffda EBX: 00000011 ECX: c25c4111 EDX: bf8d5280
> [ 4274.985036] ESI: 08250880 EDI: bf8d5280 EBP: 082a4150 ESP: bf8d50a4
> [ 4274.985042] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00200292
> [ 4274.985051] ? nmi+0xcc/0x2bc
> [ 4274.985055] Modules linked in:
> [ 4274.985063] CR2: 00000000f8600000
> [ 4274.985072] ---[ end trace 61b0852711d6de1d ]---
> [ 4274.985079] EIP: memset+0xb/0x20
> [ 4274.985086] Code: f9 01 72 0b 8a 0e 88 0f 8d b4 26 00 00 00 00 8b 45 f0 83 c4 04 5b 5e 5f 5d c3 8d 74 26 00 90 55 89 e5 57 89 c7 53 89 c3 89 d0 <f3> aa 89 d8 5b 5f 5d c3 cc cc cc cc cc cc cc cc cc cc cc cc cc 89
> [ 4274.985092] EAX: 00000000 EBX: f85fe000 ECX: 0001e000 EDX: 00000000
> [ 4274.985099] ESI: ed158400 EDI: f8600000 EBP: edcc9e6c ESP: edcc9e64
> [ 4274.985105] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210246
> [ 4274.985112] CR0: 80050033 CR2: f8600000 CR3: 2c114000 CR4: 000006b0
> [ 4337.396551] sysrq: SAK
> [ 4337.397010] tty tty7: SAK: killed process 2963 (Xorg): by session
> [ 4337.397282] tty tty7: SAK: killed process 2963 (Xorg): by controlling tty
> [ 4337.397621] tty tty7: SAK: killed process 3484 (console-kit-dae): by fd#9
> [ 4337.397934] tty tty7: SAK: killed process 3485 (console-kit-dae): by fd#9
> [ 4337.397940] tty tty7: SAK: killed process 3486 (console-kit-dae): by fd#9
> [ 4337.397945] tty tty7: SAK: killed process 3487 (console-kit-dae): by fd#9
> [ 4337.397951] tty tty7: SAK: killed process 3488 (console-kit-dae): by fd#9
> [ 4337.397956] tty tty7: SAK: killed process 3489 (console-kit-dae): by fd#9
> [ 4337.397961] tty tty7: SAK: killed process 3490 (console-kit-dae): by fd#9
> [ 4337.397967] tty tty7: SAK: killed process 3491 (console-kit-dae): by fd#9
> [ 4337.397972] tty tty7: SAK: killed process 3492 (console-kit-dae): by fd#9
> [ 4337.397978] tty tty7: SAK: killed process 3493 (console-kit-dae): by fd#9
> [ 4337.397983] tty tty7: SAK: killed process 3494 (console-kit-dae): by fd#9
> [ 4337.397989] tty tty7: SAK: killed process 3495 (console-kit-dae): by fd#9
> [ 4337.397994] tty tty7: SAK: killed process 3496 (console-kit-dae): by fd#9
> [ 4337.397999] tty tty7: SAK: killed process 3497 (console-kit-dae): by fd#9
> [ 4337.398005] tty tty7: SAK: killed process 3498 (console-kit-dae): by fd#9
> [ 4337.398010] tty tty7: SAK: killed process 3499 (console-kit-dae): by fd#9
> [ 4337.398015] tty tty7: SAK: killed process 3500 (console-kit-dae): by fd#9
> [ 4337.398021] tty tty7: SAK: killed process 3501 (console-kit-dae): by fd#9
> [ 4337.398026] tty tty7: SAK: killed process 3502 (console-kit-dae): by fd#9
> [ 4337.398032] tty tty7: SAK: killed process 3503 (console-kit-dae): by fd#9
> [ 4337.398037] tty tty7: SAK: killed process 3504 (console-kit-dae): by fd#9
> [ 4337.398042] tty tty7: SAK: killed process 3505 (console-kit-dae): by fd#9
> [ 4337.398048] tty tty7: SAK: killed process 3506 (console-kit-dae): by fd#9
> [ 4337.398053] tty tty7: SAK: killed process 3507 (console-kit-dae): by fd#9
> [ 4337.398059] tty tty7: SAK: killed process 3508 (console-kit-dae): by fd#9
> [ 4337.398064] tty tty7: SAK: killed process 3509 (console-kit-dae): by fd#9
> [ 4337.398070] tty tty7: SAK: killed process 3510 (console-kit-dae): by fd#9
> [ 4337.398075] tty tty7: SAK: killed process 3511 (console-kit-dae): by fd#9
> [ 4337.398080] tty tty7: SAK: killed process 3512 (console-kit-dae): by fd#9
> [ 4337.398086] tty tty7: SAK: killed process 3513 (console-kit-dae): by fd#9
> [ 4337.398091] tty tty7: SAK: killed process 3514 (console-kit-dae): by fd#9
> [ 4337.398097] tty tty7: SAK: killed process 3515 (console-kit-dae): by fd#9
> [ 4337.398102] tty tty7: SAK: killed process 3516 (console-kit-dae): by fd#9
> [ 4337.398107] tty tty7: SAK: killed process 3517 (console-kit-dae): by fd#9
> [ 4337.398113] tty tty7: SAK: killed process 3518 (console-kit-dae): by fd#9
> [ 4337.398118] tty tty7: SAK: killed process 3519 (console-kit-dae): by fd#9
> [ 4337.398124] tty tty7: SAK: killed process 3520 (console-kit-dae): by fd#9
> [ 4337.398129] tty tty7: SAK: killed process 3521 (console-kit-dae): by fd#9
> [ 4337.398135] tty tty7: SAK: killed process 3522 (console-kit-dae): by fd#9
> [ 4337.398141] tty tty7: SAK: killed process 3523 (console-kit-dae): by fd#9
> [ 4337.398146] tty tty7: SAK: killed process 3524 (console-kit-dae): by fd#9
> [ 4337.398151] tty tty7: SAK: killed process 3525 (console-kit-dae): by fd#9
> [ 4337.398157] tty tty7: SAK: killed process 3526 (console-kit-dae): by fd#9
> [ 4337.398162] tty tty7: SAK: killed process 3527 (console-kit-dae): by fd#9
> [ 4337.398168] tty tty7: SAK: killed process 3528 (console-kit-dae): by fd#9
> [ 4337.398173] tty tty7: SAK: killed process 3529 (console-kit-dae): by fd#9
> [ 4337.398178] tty tty7: SAK: killed process 3530 (console-kit-dae): by fd#9
> [ 4337.398184] tty tty7: SAK: killed process 3531 (console-kit-dae): by fd#9
> [ 4337.398189] tty tty7: SAK: killed process 3532 (console-kit-dae): by fd#9
> [ 4337.398194] tty tty7: SAK: killed process 3533 (console-kit-dae): by fd#9
> [ 4337.398200] tty tty7: SAK: killed process 3534 (console-kit-dae): by fd#9
> [ 4337.398205] tty tty7: SAK: killed process 3535 (console-kit-dae): by fd#9
> [ 4337.398210] tty tty7: SAK: killed process 3536 (console-kit-dae): by fd#9
> [ 4337.398216] tty tty7: SAK: killed process 3537 (console-kit-dae): by fd#9
> [ 4337.398221] tty tty7: SAK: killed process 3538 (console-kit-dae): by fd#9
> [ 4337.398227] tty tty7: SAK: killed process 3539 (console-kit-dae): by fd#9
> [ 4337.398232] tty tty7: SAK: killed process 3540 (console-kit-dae): by fd#9
> [ 4337.398237] tty tty7: SAK: killed process 3541 (console-kit-dae): by fd#9
> [ 4337.398243] tty tty7: SAK: killed process 3542 (console-kit-dae): by fd#9
> [ 4337.398248] tty tty7: SAK: killed process 3543 (console-kit-dae): by fd#9
> [ 4337.398253] tty tty7: SAK: killed process 3544 (console-kit-dae): by fd#9
> [ 4337.398260] tty tty7: SAK: killed process 3545 (console-kit-dae): by fd#9
> [ 4337.398265] tty tty7: SAK: killed process 3546 (console-kit-dae): by fd#9
> [ 4337.398270] tty tty7: SAK: killed process 3548 (gmain): by fd#9
> [ 4337.398276] tty tty7: SAK: killed process 3549 (gdbus): by fd#9
> [ 4337.743402] wlan0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> [ 4349.750345] traps: clock-applet[7160] trap int3 ip:b71bafc0 sp:bffdd3b0 error:0 in libglib-2.0.so.0.5000.3[b716e000+12a000]
> [ 4349.751834] traps: mateweather-app[7164] trap int3 ip:b729ffc0 sp:bfc45bf0 error:0 in libglib-2.0.so.0.5000.3[b7253000+12a000]
> [ 4352.181317] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> [ 4352.183330] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [ 4352.187927] wlan0: authenticated
> [ 4352.192203] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [ 4352.194932] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> [ 4352.199395] wlan0: associated
> [ 4688.523006] sysrq: SAK
> [ 4688.523318] tty tty7: SAK: killed process 6791 (Xorg): by session
> [ 4688.523683] tty tty7: SAK: killed process 6791 (Xorg): by controlling tty
> [ 4688.523930] tty tty7: SAK: killed process 7017 (console-kit-dae): by fd#9
> [ 4688.524330] tty tty7: SAK: killed process 7018 (console-kit-dae): by fd#9
> [ 4688.524337] tty tty7: SAK: killed process 7019 (console-kit-dae): by fd#9
> [ 4688.524342] tty tty7: SAK: killed process 7020 (console-kit-dae): by fd#9
> [ 4688.524347] tty tty7: SAK: killed process 7021 (console-kit-dae): by fd#9
> [ 4688.524353] tty tty7: SAK: killed process 7022 (console-kit-dae): by fd#9
> [ 4688.524358] tty tty7: SAK: killed process 7023 (console-kit-dae): by fd#9
> [ 4688.524363] tty tty7: SAK: killed process 7024 (console-kit-dae): by fd#9
> [ 4688.524369] tty tty7: SAK: killed process 7025 (console-kit-dae): by fd#9
> [ 4688.524374] tty tty7: SAK: killed process 7026 (console-kit-dae): by fd#9
> [ 4688.524380] tty tty7: SAK: killed process 7027 (console-kit-dae): by fd#9
> [ 4688.524385] tty tty7: SAK: killed process 7028 (console-kit-dae): by fd#9
> [ 4688.524391] tty tty7: SAK: killed process 7029 (console-kit-dae): by fd#9
> [ 4688.524396] tty tty7: SAK: killed process 7030 (console-kit-dae): by fd#9
> [ 4688.524402] tty tty7: SAK: killed process 7031 (console-kit-dae): by fd#9
> [ 4688.524407] tty tty7: SAK: killed process 7032 (console-kit-dae): by fd#9
> [ 4688.524412] tty tty7: SAK: killed process 7033 (console-kit-dae): by fd#9
> [ 4688.524419] tty tty7: SAK: killed process 7034 (console-kit-dae): by fd#9
> [ 4688.524424] tty tty7: SAK: killed process 7035 (console-kit-dae): by fd#9
> [ 4688.524429] tty tty7: SAK: killed process 7036 (console-kit-dae): by fd#9
> [ 4688.524435] tty tty7: SAK: killed process 7037 (console-kit-dae): by fd#9
> [ 4688.524440] tty tty7: SAK: killed process 7038 (console-kit-dae): by fd#9
> [ 4688.524446] tty tty7: SAK: killed process 7039 (console-kit-dae): by fd#9
> [ 4688.524451] tty tty7: SAK: killed process 7040 (console-kit-dae): by fd#9
> [ 4688.524456] tty tty7: SAK: killed process 7041 (console-kit-dae): by fd#9
> [ 4688.524462] tty tty7: SAK: killed process 7042 (console-kit-dae): by fd#9
> [ 4688.524467] tty tty7: SAK: killed process 7043 (console-kit-dae): by fd#9
> [ 4688.524473] tty tty7: SAK: killed process 7044 (console-kit-dae): by fd#9
> [ 4688.524478] tty tty7: SAK: killed process 7045 (console-kit-dae): by fd#9
> [ 4688.524483] tty tty7: SAK: killed process 7046 (console-kit-dae): by fd#9
> [ 4688.524489] tty tty7: SAK: killed process 7047 (console-kit-dae): by fd#9
> [ 4688.524494] tty tty7: SAK: killed process 7048 (console-kit-dae): by fd#9
> [ 4688.524500] tty tty7: SAK: killed process 7049 (console-kit-dae): by fd#9
> [ 4688.524505] tty tty7: SAK: killed process 7050 (console-kit-dae): by fd#9
> [ 4688.524511] tty tty7: SAK: killed process 7051 (console-kit-dae): by fd#9
> [ 4688.524516] tty tty7: SAK: killed process 7052 (console-kit-dae): by fd#9
> [ 4688.524521] tty tty7: SAK: killed process 7053 (console-kit-dae): by fd#9
> [ 4688.524527] tty tty7: SAK: killed process 7054 (console-kit-dae): by fd#9
> [ 4688.524532] tty tty7: SAK: killed process 7055 (console-kit-dae): by fd#9
> [ 4688.524538] tty tty7: SAK: killed process 7056 (console-kit-dae): by fd#9
> [ 4688.524543] tty tty7: SAK: killed process 7057 (console-kit-dae): by fd#9
> [ 4688.524549] tty tty7: SAK: killed process 7058 (console-kit-dae): by fd#9
> [ 4688.524554] tty tty7: SAK: killed process 7059 (console-kit-dae): by fd#9
> [ 4688.524560] tty tty7: SAK: killed process 7060 (console-kit-dae): by fd#9
> [ 4688.524565] tty tty7: SAK: killed process 7061 (console-kit-dae): by fd#9
> [ 4688.524570] tty tty7: SAK: killed process 7062 (console-kit-dae): by fd#9
> [ 4688.524576] tty tty7: SAK: killed process 7063 (console-kit-dae): by fd#9
> [ 4688.524581] tty tty7: SAK: killed process 7064 (console-kit-dae): by fd#9
> [ 4688.524587] tty tty7: SAK: killed process 7065 (console-kit-dae): by fd#9
> [ 4688.524593] tty tty7: SAK: killed process 7066 (console-kit-dae): by fd#9
> [ 4688.524598] tty tty7: SAK: killed process 7067 (console-kit-dae): by fd#9
> [ 4688.524603] tty tty7: SAK: killed process 7068 (console-kit-dae): by fd#9
> [ 4688.524609] tty tty7: SAK: killed process 7069 (console-kit-dae): by fd#9
> [ 4688.524614] tty tty7: SAK: killed process 7070 (console-kit-dae): by fd#9
> [ 4688.524620] tty tty7: SAK: killed process 7071 (console-kit-dae): by fd#9
> [ 4688.524625] tty tty7: SAK: killed process 7072 (console-kit-dae): by fd#9
> [ 4688.524631] tty tty7: SAK: killed process 7073 (console-kit-dae): by fd#9
> [ 4688.524636] tty tty7: SAK: killed process 7074 (console-kit-dae): by fd#9
> [ 4688.524642] tty tty7: SAK: killed process 7075 (console-kit-dae): by fd#9
> [ 4688.524648] tty tty7: SAK: killed process 7076 (console-kit-dae): by fd#9
> [ 4688.524653] tty tty7: SAK: killed process 7077 (console-kit-dae): by fd#9
> [ 4688.524659] tty tty7: SAK: killed process 7078 (console-kit-dae): by fd#9
> [ 4688.524664] tty tty7: SAK: killed process 7079 (console-kit-dae): by fd#9
> [ 4688.524670] tty tty7: SAK: killed process 7083 (gmain): by fd#9
> [ 4688.524675] tty tty7: SAK: killed process 7085 (gdbus): by fd#9
> [ 4688.780517] wlan0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> [ 4698.601308] traps: clock-applet[7813] trap int3 ip:b71e9fc0 sp:bf901050 error:0 in libglib-2.0.so.0.5000.3[b719d000+12a000]
> [ 4698.676549] traps: mateweather-app[7814] trap int3 ip:b7260fc0 sp:bfcfb9d0 error:0 in libglib-2.0.so.0.5000.3[b7214000+12a000]
> [ 4700.456620] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> [ 4700.456710] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> [ 4700.459606] wlan0: authenticated
> [ 4700.460449] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> [ 4700.463153] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> [ 4700.465007] wlan0: associated
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> [2 Digital signature <application/pgp-signature (7bit)>]
>

2020-05-20 11:42:01

by Pavel Machek

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Wed 2020-05-20 13:37:02, Takashi Iwai wrote:
> On Wed, 20 May 2020 13:11:37 +0200,
> Pavel Machek wrote:
> >
> > Hi!
> >
> > My window manager stopped responding. I was able to recover machine
> > using sysrq-k.
> >
> > I started writing nice report, when session failed second time. And
> > then third time on next attempt.
> >
> > Any ideas?
>
> Do you know when the regression started?
> There have been significant code changes regarding the sound buffer
> management, and it's merged in 5.6-rc1. Other than that, I have no
> idea yet.

It is first time I seen this. I may have missed the oops in the logs,
but I would not miss marco dying.

So... AFAICT this was not there in -next20200505 or so.

Best regard,
Pavel

> > [ 3730.016148] perf: interrupt took too long (3135 > 3133), lowering kernel.perf_event_max_sample_rate to 63750
> > [ 4274.984810] BUG: unable to handle page fault for address: f8600000
> > [ 4274.984821] #PF: supervisor write access in kernel mode
> > [ 4274.984827] #PF: error_code(0x0002) - not-present page
> > [ 4274.984833] *pdpt = 000000002c0b2001 *pde = 0000000000000000
> > [ 4274.984843] Oops: 0002 [#1] PREEMPT SMP PTI
> > [ 4274.984853] CPU: 1 PID: 3351 Comm: marco Not tainted 5.7.0-rc6-next-20200519+ #115
> > [ 4274.984859] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011
> > [ 4274.984871] EIP: memset+0xb/0x20
> > [ 4274.984878] Code: f9 01 72 0b 8a 0e 88 0f 8d b4 26 00 00 00 00 8b 45 f0 83 c4 04 5b 5e 5f 5d c3 8d 74 26 00 90 55 89 e5 57 89 c7 53 89 c3 89 d0 <f3> aa 89 d8 5b 5f 5d c3 cc cc cc cc cc cc cc cc cc cc cc cc cc 89
> > [ 4274.984885] EAX: 00000000 EBX: f85fe000 ECX: 0001e000 EDX: 00000000
> > [ 4274.984892] ESI: ed158400 EDI: f8600000 EBP: edcc9e6c ESP: edcc9e64
> > [ 4274.984898] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210246
> > [ 4274.984905] CR0: 80050033 CR2: f8600000 CR3: 2c114000 CR4: 000006b0
> > [ 4274.984910] Call Trace:
> > [ 4274.984923] snd_pcm_hw_params+0x38d/0x400
> > [ 4274.984930] snd_pcm_ioctl+0x187/0xe80
> > [ 4274.984940] ? __fget_files+0x86/0xc0
> > [ 4274.984947] ? __fget_light+0x6b/0x80
> > [ 4274.984954] ? snd_pcm_status_user64+0x90/0x90
> > [ 4274.984962] ksys_ioctl+0x1cd/0x880
> > [ 4274.984971] ? ksys_mmap_pgoff+0x81/0xc0
> > [ 4274.984978] ? fput+0xd/0x10
> > [ 4274.984984] ? ksys_mmap_pgoff+0x8d/0xc0
> > [ 4274.984991] __ia32_sys_ioctl+0x10/0x12
> > [ 4274.985000] do_int80_syscall_32+0x3c/0x100
> > [ 4274.985010] entry_INT80_32+0x116/0x116
> > [ 4274.985016] EIP: 0xb7f17092
> > [ 4274.985023] Code: 00 00 00 e9 90 ff ff ff ff a3 24 00 00 00 68 30 00 00 00 e9 80 ff ff ff ff a3 e8 ff ff ff 66 90 00 00 00 00 00 00 00 00 cd 80 <c3> 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 1c 24 c3 8d b4 26 00
> > [ 4274.985030] EAX: ffffffda EBX: 00000011 ECX: c25c4111 EDX: bf8d5280
> > [ 4274.985036] ESI: 08250880 EDI: bf8d5280 EBP: 082a4150 ESP: bf8d50a4
> > [ 4274.985042] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00200292
> > [ 4274.985051] ? nmi+0xcc/0x2bc
> > [ 4274.985055] Modules linked in:
> > [ 4274.985063] CR2: 00000000f8600000
> > [ 4274.985072] ---[ end trace 61b0852711d6de1d ]---
> > [ 4274.985079] EIP: memset+0xb/0x20
> > [ 4274.985086] Code: f9 01 72 0b 8a 0e 88 0f 8d b4 26 00 00 00 00 8b 45 f0 83 c4 04 5b 5e 5f 5d c3 8d 74 26 00 90 55 89 e5 57 89 c7 53 89 c3 89 d0 <f3> aa 89 d8 5b 5f 5d c3 cc cc cc cc cc cc cc cc cc cc cc cc cc 89
> > [ 4274.985092] EAX: 00000000 EBX: f85fe000 ECX: 0001e000 EDX: 00000000
> > [ 4274.985099] ESI: ed158400 EDI: f8600000 EBP: edcc9e6c ESP: edcc9e64
> > [ 4274.985105] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210246
> > [ 4274.985112] CR0: 80050033 CR2: f8600000 CR3: 2c114000 CR4: 000006b0
> > [ 4337.396551] sysrq: SAK
> > [ 4337.397010] tty tty7: SAK: killed process 2963 (Xorg): by session
> > [ 4337.397282] tty tty7: SAK: killed process 2963 (Xorg): by controlling tty
> > [ 4337.397621] tty tty7: SAK: killed process 3484 (console-kit-dae): by fd#9
> > [ 4337.397934] tty tty7: SAK: killed process 3485 (console-kit-dae): by fd#9
> > [ 4337.397940] tty tty7: SAK: killed process 3486 (console-kit-dae): by fd#9
> > [ 4337.397945] tty tty7: SAK: killed process 3487 (console-kit-dae): by fd#9
> > [ 4337.397951] tty tty7: SAK: killed process 3488 (console-kit-dae): by fd#9
> > [ 4337.397956] tty tty7: SAK: killed process 3489 (console-kit-dae): by fd#9
> > [ 4337.397961] tty tty7: SAK: killed process 3490 (console-kit-dae): by fd#9
> > [ 4337.397967] tty tty7: SAK: killed process 3491 (console-kit-dae): by fd#9
> > [ 4337.397972] tty tty7: SAK: killed process 3492 (console-kit-dae): by fd#9
> > [ 4337.397978] tty tty7: SAK: killed process 3493 (console-kit-dae): by fd#9
> > [ 4337.397983] tty tty7: SAK: killed process 3494 (console-kit-dae): by fd#9
> > [ 4337.397989] tty tty7: SAK: killed process 3495 (console-kit-dae): by fd#9
> > [ 4337.397994] tty tty7: SAK: killed process 3496 (console-kit-dae): by fd#9
> > [ 4337.397999] tty tty7: SAK: killed process 3497 (console-kit-dae): by fd#9
> > [ 4337.398005] tty tty7: SAK: killed process 3498 (console-kit-dae): by fd#9
> > [ 4337.398010] tty tty7: SAK: killed process 3499 (console-kit-dae): by fd#9
> > [ 4337.398015] tty tty7: SAK: killed process 3500 (console-kit-dae): by fd#9
> > [ 4337.398021] tty tty7: SAK: killed process 3501 (console-kit-dae): by fd#9
> > [ 4337.398026] tty tty7: SAK: killed process 3502 (console-kit-dae): by fd#9
> > [ 4337.398032] tty tty7: SAK: killed process 3503 (console-kit-dae): by fd#9
> > [ 4337.398037] tty tty7: SAK: killed process 3504 (console-kit-dae): by fd#9
> > [ 4337.398042] tty tty7: SAK: killed process 3505 (console-kit-dae): by fd#9
> > [ 4337.398048] tty tty7: SAK: killed process 3506 (console-kit-dae): by fd#9
> > [ 4337.398053] tty tty7: SAK: killed process 3507 (console-kit-dae): by fd#9
> > [ 4337.398059] tty tty7: SAK: killed process 3508 (console-kit-dae): by fd#9
> > [ 4337.398064] tty tty7: SAK: killed process 3509 (console-kit-dae): by fd#9
> > [ 4337.398070] tty tty7: SAK: killed process 3510 (console-kit-dae): by fd#9
> > [ 4337.398075] tty tty7: SAK: killed process 3511 (console-kit-dae): by fd#9
> > [ 4337.398080] tty tty7: SAK: killed process 3512 (console-kit-dae): by fd#9
> > [ 4337.398086] tty tty7: SAK: killed process 3513 (console-kit-dae): by fd#9
> > [ 4337.398091] tty tty7: SAK: killed process 3514 (console-kit-dae): by fd#9
> > [ 4337.398097] tty tty7: SAK: killed process 3515 (console-kit-dae): by fd#9
> > [ 4337.398102] tty tty7: SAK: killed process 3516 (console-kit-dae): by fd#9
> > [ 4337.398107] tty tty7: SAK: killed process 3517 (console-kit-dae): by fd#9
> > [ 4337.398113] tty tty7: SAK: killed process 3518 (console-kit-dae): by fd#9
> > [ 4337.398118] tty tty7: SAK: killed process 3519 (console-kit-dae): by fd#9
> > [ 4337.398124] tty tty7: SAK: killed process 3520 (console-kit-dae): by fd#9
> > [ 4337.398129] tty tty7: SAK: killed process 3521 (console-kit-dae): by fd#9
> > [ 4337.398135] tty tty7: SAK: killed process 3522 (console-kit-dae): by fd#9
> > [ 4337.398141] tty tty7: SAK: killed process 3523 (console-kit-dae): by fd#9
> > [ 4337.398146] tty tty7: SAK: killed process 3524 (console-kit-dae): by fd#9
> > [ 4337.398151] tty tty7: SAK: killed process 3525 (console-kit-dae): by fd#9
> > [ 4337.398157] tty tty7: SAK: killed process 3526 (console-kit-dae): by fd#9
> > [ 4337.398162] tty tty7: SAK: killed process 3527 (console-kit-dae): by fd#9
> > [ 4337.398168] tty tty7: SAK: killed process 3528 (console-kit-dae): by fd#9
> > [ 4337.398173] tty tty7: SAK: killed process 3529 (console-kit-dae): by fd#9
> > [ 4337.398178] tty tty7: SAK: killed process 3530 (console-kit-dae): by fd#9
> > [ 4337.398184] tty tty7: SAK: killed process 3531 (console-kit-dae): by fd#9
> > [ 4337.398189] tty tty7: SAK: killed process 3532 (console-kit-dae): by fd#9
> > [ 4337.398194] tty tty7: SAK: killed process 3533 (console-kit-dae): by fd#9
> > [ 4337.398200] tty tty7: SAK: killed process 3534 (console-kit-dae): by fd#9
> > [ 4337.398205] tty tty7: SAK: killed process 3535 (console-kit-dae): by fd#9
> > [ 4337.398210] tty tty7: SAK: killed process 3536 (console-kit-dae): by fd#9
> > [ 4337.398216] tty tty7: SAK: killed process 3537 (console-kit-dae): by fd#9
> > [ 4337.398221] tty tty7: SAK: killed process 3538 (console-kit-dae): by fd#9
> > [ 4337.398227] tty tty7: SAK: killed process 3539 (console-kit-dae): by fd#9
> > [ 4337.398232] tty tty7: SAK: killed process 3540 (console-kit-dae): by fd#9
> > [ 4337.398237] tty tty7: SAK: killed process 3541 (console-kit-dae): by fd#9
> > [ 4337.398243] tty tty7: SAK: killed process 3542 (console-kit-dae): by fd#9
> > [ 4337.398248] tty tty7: SAK: killed process 3543 (console-kit-dae): by fd#9
> > [ 4337.398253] tty tty7: SAK: killed process 3544 (console-kit-dae): by fd#9
> > [ 4337.398260] tty tty7: SAK: killed process 3545 (console-kit-dae): by fd#9
> > [ 4337.398265] tty tty7: SAK: killed process 3546 (console-kit-dae): by fd#9
> > [ 4337.398270] tty tty7: SAK: killed process 3548 (gmain): by fd#9
> > [ 4337.398276] tty tty7: SAK: killed process 3549 (gdbus): by fd#9
> > [ 4337.743402] wlan0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> > [ 4349.750345] traps: clock-applet[7160] trap int3 ip:b71bafc0 sp:bffdd3b0 error:0 in libglib-2.0.so.0.5000.3[b716e000+12a000]
> > [ 4349.751834] traps: mateweather-app[7164] trap int3 ip:b729ffc0 sp:bfc45bf0 error:0 in libglib-2.0.so.0.5000.3[b7253000+12a000]
> > [ 4352.181317] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> > [ 4352.183330] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> > [ 4352.187927] wlan0: authenticated
> > [ 4352.192203] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> > [ 4352.194932] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> > [ 4352.199395] wlan0: associated
> > [ 4688.523006] sysrq: SAK
> > [ 4688.523318] tty tty7: SAK: killed process 6791 (Xorg): by session
> > [ 4688.523683] tty tty7: SAK: killed process 6791 (Xorg): by controlling tty
> > [ 4688.523930] tty tty7: SAK: killed process 7017 (console-kit-dae): by fd#9
> > [ 4688.524330] tty tty7: SAK: killed process 7018 (console-kit-dae): by fd#9
> > [ 4688.524337] tty tty7: SAK: killed process 7019 (console-kit-dae): by fd#9
> > [ 4688.524342] tty tty7: SAK: killed process 7020 (console-kit-dae): by fd#9
> > [ 4688.524347] tty tty7: SAK: killed process 7021 (console-kit-dae): by fd#9
> > [ 4688.524353] tty tty7: SAK: killed process 7022 (console-kit-dae): by fd#9
> > [ 4688.524358] tty tty7: SAK: killed process 7023 (console-kit-dae): by fd#9
> > [ 4688.524363] tty tty7: SAK: killed process 7024 (console-kit-dae): by fd#9
> > [ 4688.524369] tty tty7: SAK: killed process 7025 (console-kit-dae): by fd#9
> > [ 4688.524374] tty tty7: SAK: killed process 7026 (console-kit-dae): by fd#9
> > [ 4688.524380] tty tty7: SAK: killed process 7027 (console-kit-dae): by fd#9
> > [ 4688.524385] tty tty7: SAK: killed process 7028 (console-kit-dae): by fd#9
> > [ 4688.524391] tty tty7: SAK: killed process 7029 (console-kit-dae): by fd#9
> > [ 4688.524396] tty tty7: SAK: killed process 7030 (console-kit-dae): by fd#9
> > [ 4688.524402] tty tty7: SAK: killed process 7031 (console-kit-dae): by fd#9
> > [ 4688.524407] tty tty7: SAK: killed process 7032 (console-kit-dae): by fd#9
> > [ 4688.524412] tty tty7: SAK: killed process 7033 (console-kit-dae): by fd#9
> > [ 4688.524419] tty tty7: SAK: killed process 7034 (console-kit-dae): by fd#9
> > [ 4688.524424] tty tty7: SAK: killed process 7035 (console-kit-dae): by fd#9
> > [ 4688.524429] tty tty7: SAK: killed process 7036 (console-kit-dae): by fd#9
> > [ 4688.524435] tty tty7: SAK: killed process 7037 (console-kit-dae): by fd#9
> > [ 4688.524440] tty tty7: SAK: killed process 7038 (console-kit-dae): by fd#9
> > [ 4688.524446] tty tty7: SAK: killed process 7039 (console-kit-dae): by fd#9
> > [ 4688.524451] tty tty7: SAK: killed process 7040 (console-kit-dae): by fd#9
> > [ 4688.524456] tty tty7: SAK: killed process 7041 (console-kit-dae): by fd#9
> > [ 4688.524462] tty tty7: SAK: killed process 7042 (console-kit-dae): by fd#9
> > [ 4688.524467] tty tty7: SAK: killed process 7043 (console-kit-dae): by fd#9
> > [ 4688.524473] tty tty7: SAK: killed process 7044 (console-kit-dae): by fd#9
> > [ 4688.524478] tty tty7: SAK: killed process 7045 (console-kit-dae): by fd#9
> > [ 4688.524483] tty tty7: SAK: killed process 7046 (console-kit-dae): by fd#9
> > [ 4688.524489] tty tty7: SAK: killed process 7047 (console-kit-dae): by fd#9
> > [ 4688.524494] tty tty7: SAK: killed process 7048 (console-kit-dae): by fd#9
> > [ 4688.524500] tty tty7: SAK: killed process 7049 (console-kit-dae): by fd#9
> > [ 4688.524505] tty tty7: SAK: killed process 7050 (console-kit-dae): by fd#9
> > [ 4688.524511] tty tty7: SAK: killed process 7051 (console-kit-dae): by fd#9
> > [ 4688.524516] tty tty7: SAK: killed process 7052 (console-kit-dae): by fd#9
> > [ 4688.524521] tty tty7: SAK: killed process 7053 (console-kit-dae): by fd#9
> > [ 4688.524527] tty tty7: SAK: killed process 7054 (console-kit-dae): by fd#9
> > [ 4688.524532] tty tty7: SAK: killed process 7055 (console-kit-dae): by fd#9
> > [ 4688.524538] tty tty7: SAK: killed process 7056 (console-kit-dae): by fd#9
> > [ 4688.524543] tty tty7: SAK: killed process 7057 (console-kit-dae): by fd#9
> > [ 4688.524549] tty tty7: SAK: killed process 7058 (console-kit-dae): by fd#9
> > [ 4688.524554] tty tty7: SAK: killed process 7059 (console-kit-dae): by fd#9
> > [ 4688.524560] tty tty7: SAK: killed process 7060 (console-kit-dae): by fd#9
> > [ 4688.524565] tty tty7: SAK: killed process 7061 (console-kit-dae): by fd#9
> > [ 4688.524570] tty tty7: SAK: killed process 7062 (console-kit-dae): by fd#9
> > [ 4688.524576] tty tty7: SAK: killed process 7063 (console-kit-dae): by fd#9
> > [ 4688.524581] tty tty7: SAK: killed process 7064 (console-kit-dae): by fd#9
> > [ 4688.524587] tty tty7: SAK: killed process 7065 (console-kit-dae): by fd#9
> > [ 4688.524593] tty tty7: SAK: killed process 7066 (console-kit-dae): by fd#9
> > [ 4688.524598] tty tty7: SAK: killed process 7067 (console-kit-dae): by fd#9
> > [ 4688.524603] tty tty7: SAK: killed process 7068 (console-kit-dae): by fd#9
> > [ 4688.524609] tty tty7: SAK: killed process 7069 (console-kit-dae): by fd#9
> > [ 4688.524614] tty tty7: SAK: killed process 7070 (console-kit-dae): by fd#9
> > [ 4688.524620] tty tty7: SAK: killed process 7071 (console-kit-dae): by fd#9
> > [ 4688.524625] tty tty7: SAK: killed process 7072 (console-kit-dae): by fd#9
> > [ 4688.524631] tty tty7: SAK: killed process 7073 (console-kit-dae): by fd#9
> > [ 4688.524636] tty tty7: SAK: killed process 7074 (console-kit-dae): by fd#9
> > [ 4688.524642] tty tty7: SAK: killed process 7075 (console-kit-dae): by fd#9
> > [ 4688.524648] tty tty7: SAK: killed process 7076 (console-kit-dae): by fd#9
> > [ 4688.524653] tty tty7: SAK: killed process 7077 (console-kit-dae): by fd#9
> > [ 4688.524659] tty tty7: SAK: killed process 7078 (console-kit-dae): by fd#9
> > [ 4688.524664] tty tty7: SAK: killed process 7079 (console-kit-dae): by fd#9
> > [ 4688.524670] tty tty7: SAK: killed process 7083 (gmain): by fd#9
> > [ 4688.524675] tty tty7: SAK: killed process 7085 (gdbus): by fd#9
> > [ 4688.780517] wlan0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> > [ 4698.601308] traps: clock-applet[7813] trap int3 ip:b71e9fc0 sp:bf901050 error:0 in libglib-2.0.so.0.5000.3[b719d000+12a000]
> > [ 4698.676549] traps: mateweather-app[7814] trap int3 ip:b7260fc0 sp:bfcfb9d0 error:0 in libglib-2.0.so.0.5000.3[b7214000+12a000]
> > [ 4700.456620] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> > [ 4700.456710] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> > [ 4700.459606] wlan0: authenticated
> > [ 4700.460449] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> > [ 4700.463153] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> > [ 4700.465007] wlan0: associated
> >
> > --
> > (english) http://www.livejournal.com/~pavelmachek
> > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> > [2 Digital signature <application/pgp-signature (7bit)>]
> >

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachments:

(No filename) (16.28 kB)
signature.asc (201.00 B)
Download all attachments

2020-05-20 11:46:09

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Wed, 20 May 2020 13:39:06 +0200,
Pavel Machek wrote:
>
> On Wed 2020-05-20 13:37:02, Takashi Iwai wrote:
> > On Wed, 20 May 2020 13:11:37 +0200,
> > Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > My window manager stopped responding. I was able to recover machine
> > > using sysrq-k.
> > >
> > > I started writing nice report, when session failed second time. And
> > > then third time on next attempt.
> > >
> > > Any ideas?
> >
> > Do you know when the regression started?
> > There have been significant code changes regarding the sound buffer
> > management, and it's merged in 5.6-rc1. Other than that, I have no
> > idea yet.
>
> It is first time I seen this. I may have missed the oops in the logs,
> but I would not miss marco dying.
>
> So... AFAICT this was not there in -next20200505 or so.

Ah so it's so new. Then I don't think it's from the sound driver code
change; there haven't been much changes in the core part that may lead
to such an error.

Takashi

> Best regard,
> Pavel
>
>
> > > [ 3730.016148] perf: interrupt took too long (3135 > 3133), lowering kernel.perf_event_max_sample_rate to 63750
> > > [ 4274.984810] BUG: unable to handle page fault for address: f8600000
> > > [ 4274.984821] #PF: supervisor write access in kernel mode
> > > [ 4274.984827] #PF: error_code(0x0002) - not-present page
> > > [ 4274.984833] *pdpt = 000000002c0b2001 *pde = 0000000000000000
> > > [ 4274.984843] Oops: 0002 [#1] PREEMPT SMP PTI
> > > [ 4274.984853] CPU: 1 PID: 3351 Comm: marco Not tainted 5.7.0-rc6-next-20200519+ #115
> > > [ 4274.984859] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW (2.19 ) 03/31/2011
> > > [ 4274.984871] EIP: memset+0xb/0x20
> > > [ 4274.984878] Code: f9 01 72 0b 8a 0e 88 0f 8d b4 26 00 00 00 00 8b 45 f0 83 c4 04 5b 5e 5f 5d c3 8d 74 26 00 90 55 89 e5 57 89 c7 53 89 c3 89 d0 <f3> aa 89 d8 5b 5f 5d c3 cc cc cc cc cc cc cc cc cc cc cc cc cc 89
> > > [ 4274.984885] EAX: 00000000 EBX: f85fe000 ECX: 0001e000 EDX: 00000000
> > > [ 4274.984892] ESI: ed158400 EDI: f8600000 EBP: edcc9e6c ESP: edcc9e64
> > > [ 4274.984898] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210246
> > > [ 4274.984905] CR0: 80050033 CR2: f8600000 CR3: 2c114000 CR4: 000006b0
> > > [ 4274.984910] Call Trace:
> > > [ 4274.984923] snd_pcm_hw_params+0x38d/0x400
> > > [ 4274.984930] snd_pcm_ioctl+0x187/0xe80
> > > [ 4274.984940] ? __fget_files+0x86/0xc0
> > > [ 4274.984947] ? __fget_light+0x6b/0x80
> > > [ 4274.984954] ? snd_pcm_status_user64+0x90/0x90
> > > [ 4274.984962] ksys_ioctl+0x1cd/0x880
> > > [ 4274.984971] ? ksys_mmap_pgoff+0x81/0xc0
> > > [ 4274.984978] ? fput+0xd/0x10
> > > [ 4274.984984] ? ksys_mmap_pgoff+0x8d/0xc0
> > > [ 4274.984991] __ia32_sys_ioctl+0x10/0x12
> > > [ 4274.985000] do_int80_syscall_32+0x3c/0x100
> > > [ 4274.985010] entry_INT80_32+0x116/0x116
> > > [ 4274.985016] EIP: 0xb7f17092
> > > [ 4274.985023] Code: 00 00 00 e9 90 ff ff ff ff a3 24 00 00 00 68 30 00 00 00 e9 80 ff ff ff ff a3 e8 ff ff ff 66 90 00 00 00 00 00 00 00 00 cd 80 <c3> 8d b4 26 00 00 00 00 8d b6 00 00 00 00 8b 1c 24 c3 8d b4 26 00
> > > [ 4274.985030] EAX: ffffffda EBX: 00000011 ECX: c25c4111 EDX: bf8d5280
> > > [ 4274.985036] ESI: 08250880 EDI: bf8d5280 EBP: 082a4150 ESP: bf8d50a4
> > > [ 4274.985042] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00200292
> > > [ 4274.985051] ? nmi+0xcc/0x2bc
> > > [ 4274.985055] Modules linked in:
> > > [ 4274.985063] CR2: 00000000f8600000
> > > [ 4274.985072] ---[ end trace 61b0852711d6de1d ]---
> > > [ 4274.985079] EIP: memset+0xb/0x20
> > > [ 4274.985086] Code: f9 01 72 0b 8a 0e 88 0f 8d b4 26 00 00 00 00 8b 45 f0 83 c4 04 5b 5e 5f 5d c3 8d 74 26 00 90 55 89 e5 57 89 c7 53 89 c3 89 d0 <f3> aa 89 d8 5b 5f 5d c3 cc cc cc cc cc cc cc cc cc cc cc cc cc 89
> > > [ 4274.985092] EAX: 00000000 EBX: f85fe000 ECX: 0001e000 EDX: 00000000
> > > [ 4274.985099] ESI: ed158400 EDI: f8600000 EBP: edcc9e6c ESP: edcc9e64
> > > [ 4274.985105] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210246
> > > [ 4274.985112] CR0: 80050033 CR2: f8600000 CR3: 2c114000 CR4: 000006b0
> > > [ 4337.396551] sysrq: SAK
> > > [ 4337.397010] tty tty7: SAK: killed process 2963 (Xorg): by session
> > > [ 4337.397282] tty tty7: SAK: killed process 2963 (Xorg): by controlling tty
> > > [ 4337.397621] tty tty7: SAK: killed process 3484 (console-kit-dae): by fd#9
> > > [ 4337.397934] tty tty7: SAK: killed process 3485 (console-kit-dae): by fd#9
> > > [ 4337.397940] tty tty7: SAK: killed process 3486 (console-kit-dae): by fd#9
> > > [ 4337.397945] tty tty7: SAK: killed process 3487 (console-kit-dae): by fd#9
> > > [ 4337.397951] tty tty7: SAK: killed process 3488 (console-kit-dae): by fd#9
> > > [ 4337.397956] tty tty7: SAK: killed process 3489 (console-kit-dae): by fd#9
> > > [ 4337.397961] tty tty7: SAK: killed process 3490 (console-kit-dae): by fd#9
> > > [ 4337.397967] tty tty7: SAK: killed process 3491 (console-kit-dae): by fd#9
> > > [ 4337.397972] tty tty7: SAK: killed process 3492 (console-kit-dae): by fd#9
> > > [ 4337.397978] tty tty7: SAK: killed process 3493 (console-kit-dae): by fd#9
> > > [ 4337.397983] tty tty7: SAK: killed process 3494 (console-kit-dae): by fd#9
> > > [ 4337.397989] tty tty7: SAK: killed process 3495 (console-kit-dae): by fd#9
> > > [ 4337.397994] tty tty7: SAK: killed process 3496 (console-kit-dae): by fd#9
> > > [ 4337.397999] tty tty7: SAK: killed process 3497 (console-kit-dae): by fd#9
> > > [ 4337.398005] tty tty7: SAK: killed process 3498 (console-kit-dae): by fd#9
> > > [ 4337.398010] tty tty7: SAK: killed process 3499 (console-kit-dae): by fd#9
> > > [ 4337.398015] tty tty7: SAK: killed process 3500 (console-kit-dae): by fd#9
> > > [ 4337.398021] tty tty7: SAK: killed process 3501 (console-kit-dae): by fd#9
> > > [ 4337.398026] tty tty7: SAK: killed process 3502 (console-kit-dae): by fd#9
> > > [ 4337.398032] tty tty7: SAK: killed process 3503 (console-kit-dae): by fd#9
> > > [ 4337.398037] tty tty7: SAK: killed process 3504 (console-kit-dae): by fd#9
> > > [ 4337.398042] tty tty7: SAK: killed process 3505 (console-kit-dae): by fd#9
> > > [ 4337.398048] tty tty7: SAK: killed process 3506 (console-kit-dae): by fd#9
> > > [ 4337.398053] tty tty7: SAK: killed process 3507 (console-kit-dae): by fd#9
> > > [ 4337.398059] tty tty7: SAK: killed process 3508 (console-kit-dae): by fd#9
> > > [ 4337.398064] tty tty7: SAK: killed process 3509 (console-kit-dae): by fd#9
> > > [ 4337.398070] tty tty7: SAK: killed process 3510 (console-kit-dae): by fd#9
> > > [ 4337.398075] tty tty7: SAK: killed process 3511 (console-kit-dae): by fd#9
> > > [ 4337.398080] tty tty7: SAK: killed process 3512 (console-kit-dae): by fd#9
> > > [ 4337.398086] tty tty7: SAK: killed process 3513 (console-kit-dae): by fd#9
> > > [ 4337.398091] tty tty7: SAK: killed process 3514 (console-kit-dae): by fd#9
> > > [ 4337.398097] tty tty7: SAK: killed process 3515 (console-kit-dae): by fd#9
> > > [ 4337.398102] tty tty7: SAK: killed process 3516 (console-kit-dae): by fd#9
> > > [ 4337.398107] tty tty7: SAK: killed process 3517 (console-kit-dae): by fd#9
> > > [ 4337.398113] tty tty7: SAK: killed process 3518 (console-kit-dae): by fd#9
> > > [ 4337.398118] tty tty7: SAK: killed process 3519 (console-kit-dae): by fd#9
> > > [ 4337.398124] tty tty7: SAK: killed process 3520 (console-kit-dae): by fd#9
> > > [ 4337.398129] tty tty7: SAK: killed process 3521 (console-kit-dae): by fd#9
> > > [ 4337.398135] tty tty7: SAK: killed process 3522 (console-kit-dae): by fd#9
> > > [ 4337.398141] tty tty7: SAK: killed process 3523 (console-kit-dae): by fd#9
> > > [ 4337.398146] tty tty7: SAK: killed process 3524 (console-kit-dae): by fd#9
> > > [ 4337.398151] tty tty7: SAK: killed process 3525 (console-kit-dae): by fd#9
> > > [ 4337.398157] tty tty7: SAK: killed process 3526 (console-kit-dae): by fd#9
> > > [ 4337.398162] tty tty7: SAK: killed process 3527 (console-kit-dae): by fd#9
> > > [ 4337.398168] tty tty7: SAK: killed process 3528 (console-kit-dae): by fd#9
> > > [ 4337.398173] tty tty7: SAK: killed process 3529 (console-kit-dae): by fd#9
> > > [ 4337.398178] tty tty7: SAK: killed process 3530 (console-kit-dae): by fd#9
> > > [ 4337.398184] tty tty7: SAK: killed process 3531 (console-kit-dae): by fd#9
> > > [ 4337.398189] tty tty7: SAK: killed process 3532 (console-kit-dae): by fd#9
> > > [ 4337.398194] tty tty7: SAK: killed process 3533 (console-kit-dae): by fd#9
> > > [ 4337.398200] tty tty7: SAK: killed process 3534 (console-kit-dae): by fd#9
> > > [ 4337.398205] tty tty7: SAK: killed process 3535 (console-kit-dae): by fd#9
> > > [ 4337.398210] tty tty7: SAK: killed process 3536 (console-kit-dae): by fd#9
> > > [ 4337.398216] tty tty7: SAK: killed process 3537 (console-kit-dae): by fd#9
> > > [ 4337.398221] tty tty7: SAK: killed process 3538 (console-kit-dae): by fd#9
> > > [ 4337.398227] tty tty7: SAK: killed process 3539 (console-kit-dae): by fd#9
> > > [ 4337.398232] tty tty7: SAK: killed process 3540 (console-kit-dae): by fd#9
> > > [ 4337.398237] tty tty7: SAK: killed process 3541 (console-kit-dae): by fd#9
> > > [ 4337.398243] tty tty7: SAK: killed process 3542 (console-kit-dae): by fd#9
> > > [ 4337.398248] tty tty7: SAK: killed process 3543 (console-kit-dae): by fd#9
> > > [ 4337.398253] tty tty7: SAK: killed process 3544 (console-kit-dae): by fd#9
> > > [ 4337.398260] tty tty7: SAK: killed process 3545 (console-kit-dae): by fd#9
> > > [ 4337.398265] tty tty7: SAK: killed process 3546 (console-kit-dae): by fd#9
> > > [ 4337.398270] tty tty7: SAK: killed process 3548 (gmain): by fd#9
> > > [ 4337.398276] tty tty7: SAK: killed process 3549 (gdbus): by fd#9
> > > [ 4337.743402] wlan0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> > > [ 4349.750345] traps: clock-applet[7160] trap int3 ip:b71bafc0 sp:bffdd3b0 error:0 in libglib-2.0.so.0.5000.3[b716e000+12a000]
> > > [ 4349.751834] traps: mateweather-app[7164] trap int3 ip:b729ffc0 sp:bfc45bf0 error:0 in libglib-2.0.so.0.5000.3[b7253000+12a000]
> > > [ 4352.181317] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> > > [ 4352.183330] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> > > [ 4352.187927] wlan0: authenticated
> > > [ 4352.192203] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> > > [ 4352.194932] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> > > [ 4352.199395] wlan0: associated
> > > [ 4688.523006] sysrq: SAK
> > > [ 4688.523318] tty tty7: SAK: killed process 6791 (Xorg): by session
> > > [ 4688.523683] tty tty7: SAK: killed process 6791 (Xorg): by controlling tty
> > > [ 4688.523930] tty tty7: SAK: killed process 7017 (console-kit-dae): by fd#9
> > > [ 4688.524330] tty tty7: SAK: killed process 7018 (console-kit-dae): by fd#9
> > > [ 4688.524337] tty tty7: SAK: killed process 7019 (console-kit-dae): by fd#9
> > > [ 4688.524342] tty tty7: SAK: killed process 7020 (console-kit-dae): by fd#9
> > > [ 4688.524347] tty tty7: SAK: killed process 7021 (console-kit-dae): by fd#9
> > > [ 4688.524353] tty tty7: SAK: killed process 7022 (console-kit-dae): by fd#9
> > > [ 4688.524358] tty tty7: SAK: killed process 7023 (console-kit-dae): by fd#9
> > > [ 4688.524363] tty tty7: SAK: killed process 7024 (console-kit-dae): by fd#9
> > > [ 4688.524369] tty tty7: SAK: killed process 7025 (console-kit-dae): by fd#9
> > > [ 4688.524374] tty tty7: SAK: killed process 7026 (console-kit-dae): by fd#9
> > > [ 4688.524380] tty tty7: SAK: killed process 7027 (console-kit-dae): by fd#9
> > > [ 4688.524385] tty tty7: SAK: killed process 7028 (console-kit-dae): by fd#9
> > > [ 4688.524391] tty tty7: SAK: killed process 7029 (console-kit-dae): by fd#9
> > > [ 4688.524396] tty tty7: SAK: killed process 7030 (console-kit-dae): by fd#9
> > > [ 4688.524402] tty tty7: SAK: killed process 7031 (console-kit-dae): by fd#9
> > > [ 4688.524407] tty tty7: SAK: killed process 7032 (console-kit-dae): by fd#9
> > > [ 4688.524412] tty tty7: SAK: killed process 7033 (console-kit-dae): by fd#9
> > > [ 4688.524419] tty tty7: SAK: killed process 7034 (console-kit-dae): by fd#9
> > > [ 4688.524424] tty tty7: SAK: killed process 7035 (console-kit-dae): by fd#9
> > > [ 4688.524429] tty tty7: SAK: killed process 7036 (console-kit-dae): by fd#9
> > > [ 4688.524435] tty tty7: SAK: killed process 7037 (console-kit-dae): by fd#9
> > > [ 4688.524440] tty tty7: SAK: killed process 7038 (console-kit-dae): by fd#9
> > > [ 4688.524446] tty tty7: SAK: killed process 7039 (console-kit-dae): by fd#9
> > > [ 4688.524451] tty tty7: SAK: killed process 7040 (console-kit-dae): by fd#9
> > > [ 4688.524456] tty tty7: SAK: killed process 7041 (console-kit-dae): by fd#9
> > > [ 4688.524462] tty tty7: SAK: killed process 7042 (console-kit-dae): by fd#9
> > > [ 4688.524467] tty tty7: SAK: killed process 7043 (console-kit-dae): by fd#9
> > > [ 4688.524473] tty tty7: SAK: killed process 7044 (console-kit-dae): by fd#9
> > > [ 4688.524478] tty tty7: SAK: killed process 7045 (console-kit-dae): by fd#9
> > > [ 4688.524483] tty tty7: SAK: killed process 7046 (console-kit-dae): by fd#9
> > > [ 4688.524489] tty tty7: SAK: killed process 7047 (console-kit-dae): by fd#9
> > > [ 4688.524494] tty tty7: SAK: killed process 7048 (console-kit-dae): by fd#9
> > > [ 4688.524500] tty tty7: SAK: killed process 7049 (console-kit-dae): by fd#9
> > > [ 4688.524505] tty tty7: SAK: killed process 7050 (console-kit-dae): by fd#9
> > > [ 4688.524511] tty tty7: SAK: killed process 7051 (console-kit-dae): by fd#9
> > > [ 4688.524516] tty tty7: SAK: killed process 7052 (console-kit-dae): by fd#9
> > > [ 4688.524521] tty tty7: SAK: killed process 7053 (console-kit-dae): by fd#9
> > > [ 4688.524527] tty tty7: SAK: killed process 7054 (console-kit-dae): by fd#9
> > > [ 4688.524532] tty tty7: SAK: killed process 7055 (console-kit-dae): by fd#9
> > > [ 4688.524538] tty tty7: SAK: killed process 7056 (console-kit-dae): by fd#9
> > > [ 4688.524543] tty tty7: SAK: killed process 7057 (console-kit-dae): by fd#9
> > > [ 4688.524549] tty tty7: SAK: killed process 7058 (console-kit-dae): by fd#9
> > > [ 4688.524554] tty tty7: SAK: killed process 7059 (console-kit-dae): by fd#9
> > > [ 4688.524560] tty tty7: SAK: killed process 7060 (console-kit-dae): by fd#9
> > > [ 4688.524565] tty tty7: SAK: killed process 7061 (console-kit-dae): by fd#9
> > > [ 4688.524570] tty tty7: SAK: killed process 7062 (console-kit-dae): by fd#9
> > > [ 4688.524576] tty tty7: SAK: killed process 7063 (console-kit-dae): by fd#9
> > > [ 4688.524581] tty tty7: SAK: killed process 7064 (console-kit-dae): by fd#9
> > > [ 4688.524587] tty tty7: SAK: killed process 7065 (console-kit-dae): by fd#9
> > > [ 4688.524593] tty tty7: SAK: killed process 7066 (console-kit-dae): by fd#9
> > > [ 4688.524598] tty tty7: SAK: killed process 7067 (console-kit-dae): by fd#9
> > > [ 4688.524603] tty tty7: SAK: killed process 7068 (console-kit-dae): by fd#9
> > > [ 4688.524609] tty tty7: SAK: killed process 7069 (console-kit-dae): by fd#9
> > > [ 4688.524614] tty tty7: SAK: killed process 7070 (console-kit-dae): by fd#9
> > > [ 4688.524620] tty tty7: SAK: killed process 7071 (console-kit-dae): by fd#9
> > > [ 4688.524625] tty tty7: SAK: killed process 7072 (console-kit-dae): by fd#9
> > > [ 4688.524631] tty tty7: SAK: killed process 7073 (console-kit-dae): by fd#9
> > > [ 4688.524636] tty tty7: SAK: killed process 7074 (console-kit-dae): by fd#9
> > > [ 4688.524642] tty tty7: SAK: killed process 7075 (console-kit-dae): by fd#9
> > > [ 4688.524648] tty tty7: SAK: killed process 7076 (console-kit-dae): by fd#9
> > > [ 4688.524653] tty tty7: SAK: killed process 7077 (console-kit-dae): by fd#9
> > > [ 4688.524659] tty tty7: SAK: killed process 7078 (console-kit-dae): by fd#9
> > > [ 4688.524664] tty tty7: SAK: killed process 7079 (console-kit-dae): by fd#9
> > > [ 4688.524670] tty tty7: SAK: killed process 7083 (gmain): by fd#9
> > > [ 4688.524675] tty tty7: SAK: killed process 7085 (gdbus): by fd#9
> > > [ 4688.780517] wlan0: deauthenticating from 5c:f4:ab:10:d2:bb by local choice (Reason: 3=DEAUTH_LEAVING)
> > > [ 4698.601308] traps: clock-applet[7813] trap int3 ip:b71e9fc0 sp:bf901050 error:0 in libglib-2.0.so.0.5000.3[b719d000+12a000]
> > > [ 4698.676549] traps: mateweather-app[7814] trap int3 ip:b7260fc0 sp:bfcfb9d0 error:0 in libglib-2.0.so.0.5000.3[b7214000+12a000]
> > > [ 4700.456620] wlan0: authenticate with 5c:f4:ab:10:d2:bb
> > > [ 4700.456710] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
> > > [ 4700.459606] wlan0: authenticated
> > > [ 4700.460449] wlan0: associate with 5c:f4:ab:10:d2:bb (try 1/3)
> > > [ 4700.463153] wlan0: RX AssocResp from 5c:f4:ab:10:d2:bb (capab=0x411 status=0 aid=2)
> > > [ 4700.465007] wlan0: associated
> > >
> > > --
> > > (english) http://www.livejournal.com/~pavelmachek
> > > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> > > [2 Digital signature <application/pgp-signature (7bit)>]
> > >
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> [2 signature.asc <application/pgp-signature (7bit)>]
>

2020-05-21 07:44:24

by Pavel Machek

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Hi!

> My window manager stopped responding. I was able to recover machine
> using sysrq-k.
>
> I started writing nice report, when session failed second time. And
> then third time on next attempt.
>
> Any ideas?
>
> I'll send this out before this locks up...

Today it crashed again, with similar oops in the log.

My records say:

fb57b1fabcb2 (HEAD, tag: next-20200519, origin/master, origin/HEAD) HEAD@{0}: checkout: moving from bdecf38f228bcca73b31ada98b5b7ba1215eb9c9 to next-20200519
bdecf38f228b (tag: next-20200515) HEAD@{1}: checkout: moving from 30e2206e11ce27ae910cc0dab21472429e400a87 to next-20200515

So it is well possible that 0515 worked okay for few
days. Hmm. Perhaps I'll try going to 0516 and see if it is stable?

Best regards,
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachments:

(No filename) (935.00 B)
signature.asc (201.00 B)
Download all attachments

2020-06-07 16:01:01

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.

[ 20.263098] BUG: unable to handle page fault for address: ffffb2b582cc2000
[ 20.263104] #PF: supervisor write access in kernel mode
[ 20.263105] #PF: error_code(0x000b) - reserved bit violation
[ 20.263107] PGD 3fd03b067 P4D 3fd03b067 PUD 3fd03c067 PMD 3f8822067 PTE 8000273942ab2163
[ 20.263113] Oops: 000b [#1] PREEMPT SMP
[ 20.263117] CPU: 3 PID: 691 Comm: mpv Not tainted 5.7.0-11262-gb170290c2836 #1
[ 20.263119] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.10 03/05/2020
[ 20.263125] RIP: 0010:__memset+0x24/0x30
[ 20.263128] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
[ 20.263131] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
[ 20.263133] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
[ 20.263134] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
[ 20.263136] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
[ 20.263137] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
[ 20.263139] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
[ 20.263141] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
[ 20.263143] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 20.263144] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
[ 20.263146] Call Trace:
[ 20.263151] ? snd_pcm_hw_params+0x3f3/0x47a
[ 20.263154] ? snd_pcm_common_ioctl+0xf2/0xf73
[ 20.263158] ? snd_pcm_ioctl+0x1e/0x29
[ 20.263161] ? ksys_ioctl+0x77/0x91
[ 20.263163] ? __x64_sys_ioctl+0x11/0x14
[ 20.263166] ? do_syscall_64+0x3d/0xf5
[ 20.263170] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 20.263173] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev snd_usb_audio videobuf2_common snd_hwdep snd_usbmidi_lib input_leds snd_rawmidi led_class
[ 20.263182] CR2: ffffb2b582cc2000
[ 20.263184] ---[ end trace c6b47a774b91f0a0 ]---
[ 20.263187] RIP: 0010:__memset+0x24/0x30
[ 20.263190] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
[ 20.263192] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
[ 20.263193] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
[ 20.263195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
[ 20.263196] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
[ 20.263197] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
[ 20.263199] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
[ 20.263201] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
[ 20.263202] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 20.263204] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0

I bisected this to 82fef0ad811f "x86/mm: unencrypted non-blocking DMA
allocations use coherent pools". Reverting 1ee18de92927 resolves the
issue.

Looks like Thinkpad X60 doesn't have VT-d, but could still be DMA
related.

2020-06-07 16:41:01

by Pavel Machek

[permalink] [raw]

Subject: 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was Re: next-0519 on thinkpad x60: sound related? window manager crash

Hi!

> I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
>
> [ 20.263098] BUG: unable to handle page fault for address: ffffb2b582cc2000
> [ 20.263104] #PF: supervisor write access in kernel mode
> [ 20.263105] #PF: error_code(0x000b) - reserved bit violation
> [ 20.263107] PGD 3fd03b067 P4D 3fd03b067 PUD 3fd03c067 PMD 3f8822067 PTE 8000273942ab2163
> [ 20.263113] Oops: 000b [#1] PREEMPT SMP
> [ 20.263117] CPU: 3 PID: 691 Comm: mpv Not tainted 5.7.0-11262-gb170290c2836 #1
> [ 20.263119] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.10 03/05/2020
> [ 20.263125] RIP: 0010:__memset+0x24/0x30
> [ 20.263128] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> [ 20.263131] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> [ 20.263133] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> [ 20.263134] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> [ 20.263136] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> [ 20.263137] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> [ 20.263139] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> [ 20.263141] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> [ 20.263143] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 20.263144] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
> [ 20.263146] Call Trace:
> [ 20.263151] ? snd_pcm_hw_params+0x3f3/0x47a
> [ 20.263154] ? snd_pcm_common_ioctl+0xf2/0xf73
> [ 20.263158] ? snd_pcm_ioctl+0x1e/0x29
> [ 20.263161] ? ksys_ioctl+0x77/0x91
> [ 20.263163] ? __x64_sys_ioctl+0x11/0x14
> [ 20.263166] ? do_syscall_64+0x3d/0xf5
> [ 20.263170] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 20.263173] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev snd_usb_audio videobuf2_common snd_hwdep snd_usbmidi_lib input_leds snd_rawmidi led_class
> [ 20.263182] CR2: ffffb2b582cc2000
> [ 20.263184] ---[ end trace c6b47a774b91f0a0 ]---
> [ 20.263187] RIP: 0010:__memset+0x24/0x30
> [ 20.263190] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> [ 20.263192] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> [ 20.263193] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> [ 20.263195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> [ 20.263196] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> [ 20.263197] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> [ 20.263199] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> [ 20.263201] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> [ 20.263202] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 20.263204] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
>
> I bisected this to 82fef0ad811f "x86/mm: unencrypted non-blocking DMA
> allocations use coherent pools". Reverting 1ee18de92927 resolves the
> issue.
>
> Looks like Thinkpad X60 doesn't have VT-d, but could still be DMA
> related.

Note that newer -next releases seem to behave okay for me. The commit
pointed out by siection is really simple:

AFAIK you could verify it is responsible by turning off
CONFIG_AMD_MEM_ENCRYPT on latest kernel...

Best regards,
Pavel

index 1d6104ea8af0..2bf2222819d3 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1520,6 +1520,7 @@ config X86_CPA_STATISTICS
config AMD_MEM_ENCRYPT
bool "AMD Secure Memory Encryption (SME) support"
depends on X86_64 && CPU_SUP_AMD
+ select DMA_COHERENT_POOL
select DYNAMIC_PHYSICAL_MASK
select ARCH_USE_MEMREMAP_PROT
select ARCH_HAS_FORCE_DMA_UNENCRYPTED

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Attachments:

(No filename) (4.25 kB)
signature.asc (201.00 B)
Download all attachments

2020-06-07 19:44:51

[permalink] [raw]

Subject: Re: 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was Re: next-0519 on thinkpad x60: sound related? window manager crash

On Sun, 7 Jun 2020, Pavel Machek wrote:

> > I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
> >
> > [ 20.263098] BUG: unable to handle page fault for address: ffffb2b582cc2000
> > [ 20.263104] #PF: supervisor write access in kernel mode
> > [ 20.263105] #PF: error_code(0x000b) - reserved bit violation
> > [ 20.263107] PGD 3fd03b067 P4D 3fd03b067 PUD 3fd03c067 PMD 3f8822067 PTE 8000273942ab2163
> > [ 20.263113] Oops: 000b [#1] PREEMPT SMP
> > [ 20.263117] CPU: 3 PID: 691 Comm: mpv Not tainted 5.7.0-11262-gb170290c2836 #1
> > [ 20.263119] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.10 03/05/2020
> > [ 20.263125] RIP: 0010:__memset+0x24/0x30
> > [ 20.263128] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> > [ 20.263131] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> > [ 20.263133] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> > [ 20.263134] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> > [ 20.263136] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> > [ 20.263137] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> > [ 20.263139] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> > [ 20.263141] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> > [ 20.263143] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 20.263144] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
> > [ 20.263146] Call Trace:
> > [ 20.263151] ? snd_pcm_hw_params+0x3f3/0x47a
> > [ 20.263154] ? snd_pcm_common_ioctl+0xf2/0xf73
> > [ 20.263158] ? snd_pcm_ioctl+0x1e/0x29
> > [ 20.263161] ? ksys_ioctl+0x77/0x91
> > [ 20.263163] ? __x64_sys_ioctl+0x11/0x14
> > [ 20.263166] ? do_syscall_64+0x3d/0xf5
> > [ 20.263170] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> > [ 20.263173] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev snd_usb_audio videobuf2_common snd_hwdep snd_usbmidi_lib input_leds snd_rawmidi led_class
> > [ 20.263182] CR2: ffffb2b582cc2000
> > [ 20.263184] ---[ end trace c6b47a774b91f0a0 ]---
> > [ 20.263187] RIP: 0010:__memset+0x24/0x30
> > [ 20.263190] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> > [ 20.263192] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> > [ 20.263193] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> > [ 20.263195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> > [ 20.263196] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> > [ 20.263197] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> > [ 20.263199] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> > [ 20.263201] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> > [ 20.263202] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > [ 20.263204] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
> >
> > I bisected this to 82fef0ad811f "x86/mm: unencrypted non-blocking DMA
> > allocations use coherent pools". Reverting 1ee18de92927 resolves the
> > issue.
> >
> > Looks like Thinkpad X60 doesn't have VT-d, but could still be DMA
> > related.
>
> Note that newer -next releases seem to behave okay for me. The commit
> pointed out by siection is really simple:
>
> AFAIK you could verify it is responsible by turning off
> CONFIG_AMD_MEM_ENCRYPT on latest kernel...
>
> Best regards,
> Pavel
>
> index 1d6104ea8af0..2bf2222819d3 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1520,6 +1520,7 @@ config X86_CPA_STATISTICS
> config AMD_MEM_ENCRYPT
> bool "AMD Secure Memory Encryption (SME) support"
> depends on X86_64 && CPU_SUP_AMD
> + select DMA_COHERENT_POOL
> select DYNAMIC_PHYSICAL_MASK
> select ARCH_USE_MEMREMAP_PROT
> select ARCH_HAS_FORCE_DMA_UNENCRYPTED

Thanks for the report!

Besides CONFIG_AMD_MEM_ENCRYPT, do you have CONFIG_DMA_DIRECT_REMAP
enabled? If so, it may be caused by the virtual address passed to the
set_memory_{decrypted,encrypted}() functions.

And I assume you are enabling SME by using mem_encrypt=on on the kernel
command line or CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is enabled.

We likely need an atomic pool for devices that support DMA to addresses in
sme_me_mask as well. I can test this tomorrow, but wanted to get it out
early to see if it helps?
---
diff --git a/kernel/dma/pool.c b/kernel/dma/pool.c
--- a/kernel/dma/pool.c
+++ b/kernel/dma/pool.c
@@ -13,6 +13,8 @@
#include <linux/slab.h>
#include <linux/workqueue.h>

+static struct gen_pool *atomic_pool __ro_after_init;
+static unsigned long pool_size;
static struct gen_pool *atomic_pool_dma __ro_after_init;
static unsigned long pool_size_dma;
static struct gen_pool *atomic_pool_dma32 __ro_after_init;
@@ -41,24 +43,37 @@ static void __init dma_atomic_pool_debugfs_init(void)
if (IS_ERR_OR_NULL(root))
return;

+ debugfs_create_ulong("pool_size", 0400, root, &pool_size);
debugfs_create_ulong("pool_size_dma", 0400, root, &pool_size_dma);
debugfs_create_ulong("pool_size_dma32", 0400, root, &pool_size_dma32);
debugfs_create_ulong("pool_size_kernel", 0400, root, &pool_size_kernel);
}

-static void dma_atomic_pool_size_add(gfp_t gfp, size_t size)
+static gfp_t dma_atomic_pool_gfp(void)
{
- if (gfp & __GFP_DMA)
+ if (IS_ENABLED(CONFIG_ZONE_DMA))
+ return GFP_KERNEL | GFP_DMA;
+ if (IS_ENABLED(CONFIG_ZONE_DMA32))
+ return GFP_KERNEL | GFP_DMA32;
+ return GFP_KERNEL;
+}
+
+static void dma_atomic_pool_size_add(struct gen_pool *pool, size_t size)
+{
+ if (pool == atomic_pool)
+ pool_size += size;
+ else if (pool == atomic_pool_dma)
pool_size_dma += size;
- else if (gfp & __GFP_DMA32)
+ else if (pool == atomic_pool_dma32)
pool_size_dma32 += size;
- else
+ else if (pool == atomic_pool_kernel)
pool_size_kernel += size;
}

static int atomic_pool_expand(struct gen_pool *pool, size_t pool_size,
gfp_t gfp)
{
+ bool decrypt = pool != atomic_pool;
unsigned int order;
struct page *page;
void *addr;
@@ -94,8 +109,9 @@ static int atomic_pool_expand(struct gen_pool *pool, size_t pool_size,
* Memory in the atomic DMA pools must be unencrypted, the pools do not
* shrink so no re-encryption occurs in dma_direct_free_pages().
*/
- ret = set_memory_decrypted((unsigned long)page_to_virt(page),
- 1 << order);
+ if (decrypt)
+ ret = set_memory_decrypted((unsigned long)page_to_virt(page),
+ 1 << order);
if (ret)
goto remove_mapping;
ret = gen_pool_add_virt(pool, (unsigned long)addr, page_to_phys(page),
@@ -103,12 +119,13 @@ static int atomic_pool_expand(struct gen_pool *pool, size_t pool_size,
if (ret)
goto encrypt_mapping;

- dma_atomic_pool_size_add(gfp, pool_size);
+ dma_atomic_pool_size_add(pool, pool_size);
return 0;

encrypt_mapping:
- ret = set_memory_encrypted((unsigned long)page_to_virt(page),
- 1 << order);
+ if (decrypt)
+ ret = set_memory_encrypted((unsigned long)page_to_virt(page),
+ 1 << order);
if (WARN_ON_ONCE(ret)) {
/* Decrypt succeeded but encrypt failed, purposely leak */
goto out;
@@ -132,6 +149,7 @@ static void atomic_pool_resize(struct gen_pool *pool, gfp_t gfp)

static void atomic_pool_work_fn(struct work_struct *work)
{
+ atomic_pool_resize(atomic_pool, dma_atomic_pool_gfp());
if (IS_ENABLED(CONFIG_ZONE_DMA))
atomic_pool_resize(atomic_pool_dma,
GFP_KERNEL | GFP_DMA);
@@ -182,6 +200,10 @@ static int __init dma_atomic_pool_init(void)
}
INIT_WORK(&atomic_pool_work, atomic_pool_work_fn);

+ atomic_pool = __dma_atomic_pool_init(atomic_pool_size,
+ dma_atomic_pool_gfp());
+ if (!atomic_pool)
+ ret = -ENOMEM;
atomic_pool_kernel = __dma_atomic_pool_init(atomic_pool_size,
GFP_KERNEL);
if (!atomic_pool_kernel)
@@ -209,6 +231,9 @@ static inline struct gen_pool *dev_to_pool(struct device *dev)
u64 phys_mask;
gfp_t gfp;

+ if (!force_dma_unencrypted(dev))
+ return atomic_pool;
+
gfp = dma_direct_optimal_gfp_mask(dev, dev->coherent_dma_mask,
&phys_mask);
if (IS_ENABLED(CONFIG_ZONE_DMA) && gfp == GFP_DMA)

2020-06-07 22:57:15

[permalink] [raw]

Subject: Re: 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from David Rientjes's message of June 7, 2020 3:41 pm:
> On Sun, 7 Jun 2020, Pavel Machek wrote:
>
>> > I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
>> >
>> > [ 20.263098] BUG: unable to handle page fault for address: ffffb2b582cc2000
>> > [ 20.263104] #PF: supervisor write access in kernel mode
>> > [ 20.263105] #PF: error_code(0x000b) - reserved bit violation
>> > [ 20.263107] PGD 3fd03b067 P4D 3fd03b067 PUD 3fd03c067 PMD 3f8822067 PTE 8000273942ab2163
>> > [ 20.263113] Oops: 000b [#1] PREEMPT SMP
>> > [ 20.263117] CPU: 3 PID: 691 Comm: mpv Not tainted 5.7.0-11262-gb170290c2836 #1
>> > [ 20.263119] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.10 03/05/2020
>> > [ 20.263125] RIP: 0010:__memset+0x24/0x30
>> > [ 20.263128] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
>> > [ 20.263131] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
>> > [ 20.263133] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
>> > [ 20.263134] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
>> > [ 20.263136] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
>> > [ 20.263137] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
>> > [ 20.263139] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
>> > [ 20.263141] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
>> > [ 20.263143] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> > [ 20.263144] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
>> > [ 20.263146] Call Trace:
>> > [ 20.263151] ? snd_pcm_hw_params+0x3f3/0x47a
>> > [ 20.263154] ? snd_pcm_common_ioctl+0xf2/0xf73
>> > [ 20.263158] ? snd_pcm_ioctl+0x1e/0x29
>> > [ 20.263161] ? ksys_ioctl+0x77/0x91
>> > [ 20.263163] ? __x64_sys_ioctl+0x11/0x14
>> > [ 20.263166] ? do_syscall_64+0x3d/0xf5
>> > [ 20.263170] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
>> > [ 20.263173] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev snd_usb_audio videobuf2_common snd_hwdep snd_usbmidi_lib input_leds snd_rawmidi led_class
>> > [ 20.263182] CR2: ffffb2b582cc2000
>> > [ 20.263184] ---[ end trace c6b47a774b91f0a0 ]---
>> > [ 20.263187] RIP: 0010:__memset+0x24/0x30
>> > [ 20.263190] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
>> > [ 20.263192] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
>> > [ 20.263193] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
>> > [ 20.263195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
>> > [ 20.263196] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
>> > [ 20.263197] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
>> > [ 20.263199] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
>> > [ 20.263201] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
>> > [ 20.263202] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> > [ 20.263204] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
>> >
>> > I bisected this to 82fef0ad811f "x86/mm: unencrypted non-blocking DMA
>> > allocations use coherent pools". Reverting 1ee18de92927 resolves the
>> > issue.
>> >
>> > Looks like Thinkpad X60 doesn't have VT-d, but could still be DMA
>> > related.
>>
>> Note that newer -next releases seem to behave okay for me. The commit
>> pointed out by siection is really simple:
>>
>> AFAIK you could verify it is responsible by turning off
>> CONFIG_AMD_MEM_ENCRYPT on latest kernel...
>>
>> Best regards,
>> Pavel
>>
>> index 1d6104ea8af0..2bf2222819d3 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -1520,6 +1520,7 @@ config X86_CPA_STATISTICS
>> config AMD_MEM_ENCRYPT
>> bool "AMD Secure Memory Encryption (SME) support"
>> depends on X86_64 && CPU_SUP_AMD
>> + select DMA_COHERENT_POOL
>> select DYNAMIC_PHYSICAL_MASK
>> select ARCH_USE_MEMREMAP_PROT
>> select ARCH_HAS_FORCE_DMA_UNENCRYPTED
>
> Thanks for the report!
>
> Besides CONFIG_AMD_MEM_ENCRYPT, do you have CONFIG_DMA_DIRECT_REMAP
> enabled? If so, it may be caused by the virtual address passed to the
> set_memory_{decrypted,encrypted}() functions.
>
> And I assume you are enabling SME by using mem_encrypt=on on the kernel
> command line or CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is enabled.
>
> We likely need an atomic pool for devices that support DMA to addresses in
> sme_me_mask as well. I can test this tomorrow, but wanted to get it out
> early to see if it helps?

This patch doesn't seem to help. I have the same problem (kernel page
fault, __memset, snd_pcm_hw_params...).

I don't have CONFIG_DMA_DIRECT_REMAP enabled, and AFAICT it doesn't seem
to be selectable currently on x86, unless there are some patches
floating around for that.

2020-06-08 00:59:37

[permalink] [raw]

Subject: Re: 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was Re: next-0519 on thinkpad x60: sound related? window manager crash

On Sun, 7 Jun 2020, Alex Xu (Hello71) wrote:

> > On Sun, 7 Jun 2020, Pavel Machek wrote:
> >
> >> > I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
> >> >
> >> > [ 20.263098] BUG: unable to handle page fault for address: ffffb2b582cc2000
> >> > [ 20.263104] #PF: supervisor write access in kernel mode
> >> > [ 20.263105] #PF: error_code(0x000b) - reserved bit violation
> >> > [ 20.263107] PGD 3fd03b067 P4D 3fd03b067 PUD 3fd03c067 PMD 3f8822067 PTE 8000273942ab2163
> >> > [ 20.263113] Oops: 000b [#1] PREEMPT SMP
> >> > [ 20.263117] CPU: 3 PID: 691 Comm: mpv Not tainted 5.7.0-11262-gb170290c2836 #1
> >> > [ 20.263119] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.10 03/05/2020
> >> > [ 20.263125] RIP: 0010:__memset+0x24/0x30
> >> > [ 20.263128] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> >> > [ 20.263131] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> >> > [ 20.263133] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> >> > [ 20.263134] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> >> > [ 20.263136] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> >> > [ 20.263137] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> >> > [ 20.263139] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> >> > [ 20.263141] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> >> > [ 20.263143] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> > [ 20.263144] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
> >> > [ 20.263146] Call Trace:
> >> > [ 20.263151] ? snd_pcm_hw_params+0x3f3/0x47a
> >> > [ 20.263154] ? snd_pcm_common_ioctl+0xf2/0xf73
> >> > [ 20.263158] ? snd_pcm_ioctl+0x1e/0x29
> >> > [ 20.263161] ? ksys_ioctl+0x77/0x91
> >> > [ 20.263163] ? __x64_sys_ioctl+0x11/0x14
> >> > [ 20.263166] ? do_syscall_64+0x3d/0xf5
> >> > [ 20.263170] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> >> > [ 20.263173] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev snd_usb_audio videobuf2_common snd_hwdep snd_usbmidi_lib input_leds snd_rawmidi led_class
> >> > [ 20.263182] CR2: ffffb2b582cc2000
> >> > [ 20.263184] ---[ end trace c6b47a774b91f0a0 ]---
> >> > [ 20.263187] RIP: 0010:__memset+0x24/0x30
> >> > [ 20.263190] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> >> > [ 20.263192] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> >> > [ 20.263193] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> >> > [ 20.263195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> >> > [ 20.263196] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> >> > [ 20.263197] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> >> > [ 20.263199] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> >> > [ 20.263201] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> >> > [ 20.263202] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> > [ 20.263204] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
> >> >
> >> > I bisected this to 82fef0ad811f "x86/mm: unencrypted non-blocking DMA
> >> > allocations use coherent pools". Reverting 1ee18de92927 resolves the
> >> > issue.
> >> >
> >> > Looks like Thinkpad X60 doesn't have VT-d, but could still be DMA
> >> > related.
> >>
> >> Note that newer -next releases seem to behave okay for me. The commit
> >> pointed out by siection is really simple:
> >>
> >> AFAIK you could verify it is responsible by turning off
> >> CONFIG_AMD_MEM_ENCRYPT on latest kernel...
> >>
> >> Best regards,
> >> Pavel
> >>
> >> index 1d6104ea8af0..2bf2222819d3 100644
> >> --- a/arch/x86/Kconfig
> >> +++ b/arch/x86/Kconfig
> >> @@ -1520,6 +1520,7 @@ config X86_CPA_STATISTICS
> >> config AMD_MEM_ENCRYPT
> >> bool "AMD Secure Memory Encryption (SME) support"
> >> depends on X86_64 && CPU_SUP_AMD
> >> + select DMA_COHERENT_POOL
> >> select DYNAMIC_PHYSICAL_MASK
> >> select ARCH_USE_MEMREMAP_PROT
> >> select ARCH_HAS_FORCE_DMA_UNENCRYPTED
> >
> > Thanks for the report!
> >
> > Besides CONFIG_AMD_MEM_ENCRYPT, do you have CONFIG_DMA_DIRECT_REMAP
> > enabled? If so, it may be caused by the virtual address passed to the
> > set_memory_{decrypted,encrypted}() functions.
> >
> > And I assume you are enabling SME by using mem_encrypt=on on the kernel
> > command line or CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is enabled.
> >
> > We likely need an atomic pool for devices that support DMA to addresses in
> > sme_me_mask as well. I can test this tomorrow, but wanted to get it out
> > early to see if it helps?
>
> This patch doesn't seem to help. I have the same problem (kernel page
> fault, __memset, snd_pcm_hw_params...).
>
> I don't have CONFIG_DMA_DIRECT_REMAP enabled, and AFAICT it doesn't seem
> to be selectable currently on x86, unless there are some patches
> floating around for that.
>

Thanks for trying it out, Alex. Would you mind sending your .config and
command line? I assume either mem_encrypt=on or
CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is enabled.

Could you also give this a try?

diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
--- a/kernel/dma/direct.c
+++ b/kernel/dma/direct.c
@@ -99,10 +99,11 @@ static inline bool dma_should_alloc_from_pool(struct device *dev, gfp_t gfp,
static inline bool dma_should_free_from_pool(struct device *dev,
unsigned long attrs)
{
- if (IS_ENABLED(CONFIG_DMA_COHERENT_POOL))
+ if (!IS_ENABLED(CONFIG_DMA_COHERENT_POOL))
+ return false;
+ if (force_dma_unencrypted(dev))
return true;
- if ((attrs & DMA_ATTR_NO_KERNEL_MAPPING) &&
- !force_dma_unencrypted(dev))
+ if (attrs & DMA_ATTR_NO_KERNEL_MAPPING)
return false;
if (IS_ENABLED(CONFIG_DMA_DIRECT_REMAP))
return true;

2020-06-08 02:17:57

[permalink] [raw]

Subject: Re: 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from David Rientjes's message of June 7, 2020 8:57 pm:
> Thanks for trying it out, Alex. Would you mind sending your .config and
> command line? I assume either mem_encrypt=on or
> CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is enabled.
>
> Could you also give this a try?
>
> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> --- a/kernel/dma/direct.c
> +++ b/kernel/dma/direct.c
> @@ -99,10 +99,11 @@ static inline bool dma_should_alloc_from_pool(struct device *dev, gfp_t gfp,
> static inline bool dma_should_free_from_pool(struct device *dev,
> unsigned long attrs)
> {
> - if (IS_ENABLED(CONFIG_DMA_COHERENT_POOL))
> + if (!IS_ENABLED(CONFIG_DMA_COHERENT_POOL))
> + return false;
> + if (force_dma_unencrypted(dev))
> return true;
> - if ((attrs & DMA_ATTR_NO_KERNEL_MAPPING) &&
> - !force_dma_unencrypted(dev))
> + if (attrs & DMA_ATTR_NO_KERNEL_MAPPING)
> return false;
> if (IS_ENABLED(CONFIG_DMA_DIRECT_REMAP))
> return true;
>

This patch doesn't work for me either. It has since occurred to me that
while I do have CONFIG_AMD_MEM_ENCYRPT=y, I have
CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=n, because it was broken with
amdgpu (unfortunately a downgrade from radeon in this respect). Tried it
again just now and it looks like it's now able to enable KMS, but all it
displays is serious-looking errors.

Sorry for not mentioning that earlier. I'll send you my .config and
command line off-list.

Thanks,
Alex.

2020-06-08 06:22:08

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Can you do a listing using gdb where this happens?

gdb vmlinux

l *(snd_pcm_hw_params+0x3f3)

?

On Sun, Jun 07, 2020 at 11:58:21AM -0400, Alex Xu (Hello71) wrote:
> I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
>
> [ 20.263098] BUG: unable to handle page fault for address: ffffb2b582cc2000
> [ 20.263104] #PF: supervisor write access in kernel mode
> [ 20.263105] #PF: error_code(0x000b) - reserved bit violation
> [ 20.263107] PGD 3fd03b067 P4D 3fd03b067 PUD 3fd03c067 PMD 3f8822067 PTE 8000273942ab2163
> [ 20.263113] Oops: 000b [#1] PREEMPT SMP
> [ 20.263117] CPU: 3 PID: 691 Comm: mpv Not tainted 5.7.0-11262-gb170290c2836 #1
> [ 20.263119] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B450 Pro4, BIOS P4.10 03/05/2020
> [ 20.263125] RIP: 0010:__memset+0x24/0x30
> [ 20.263128] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> [ 20.263131] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> [ 20.263133] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> [ 20.263134] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> [ 20.263136] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> [ 20.263137] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> [ 20.263139] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> [ 20.263141] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> [ 20.263143] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 20.263144] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
> [ 20.263146] Call Trace:
> [ 20.263151] ? snd_pcm_hw_params+0x3f3/0x47a
> [ 20.263154] ? snd_pcm_common_ioctl+0xf2/0xf73
> [ 20.263158] ? snd_pcm_ioctl+0x1e/0x29
> [ 20.263161] ? ksys_ioctl+0x77/0x91
> [ 20.263163] ? __x64_sys_ioctl+0x11/0x14
> [ 20.263166] ? do_syscall_64+0x3d/0xf5
> [ 20.263170] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 20.263173] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videodev snd_usb_audio videobuf2_common snd_hwdep snd_usbmidi_lib input_leds snd_rawmidi led_class
> [ 20.263182] CR2: ffffb2b582cc2000
> [ 20.263184] ---[ end trace c6b47a774b91f0a0 ]---
> [ 20.263187] RIP: 0010:__memset+0x24/0x30
> [ 20.263190] Code: cc cc cc cc cc cc 0f 1f 44 00 00 49 89 f9 48 89 d1 83 e2 07 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 <f3> 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 f3
> [ 20.263192] RSP: 0018:ffffb2b583d07e10 EFLAGS: 00010216
> [ 20.263193] RAX: 0000000000000000 RBX: ffff8b8000102c00 RCX: 0000000000004000
> [ 20.263195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffb2b582cc2000
> [ 20.263196] RBP: ffff8b8000101000 R08: 0000000000000000 R09: ffffb2b582cc2000
> [ 20.263197] R10: 0000000000005356 R11: ffff8b8000102c18 R12: 0000000000000000
> [ 20.263199] R13: 0000000000000000 R14: ffff8b8039944200 R15: ffffffff9794daa0
> [ 20.263201] FS: 00007f41aa4b4200(0000) GS:ffff8b803ecc0000(0000) knlGS:0000000000000000
> [ 20.263202] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 20.263204] CR2: ffffb2b582cc2000 CR3: 00000003b6731000 CR4: 00000000003406e0
>
> I bisected this to 82fef0ad811f "x86/mm: unencrypted non-blocking DMA
> allocations use coherent pools". Reverting 1ee18de92927 resolves the
> issue.
>
> Looks like Thinkpad X60 doesn't have VT-d, but could still be DMA
> related.
---end quoted text---

2020-06-08 13:57:50

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from Christoph Hellwig's message of June 8, 2020 2:19 am:
> Can you do a listing using gdb where this happens?
>
> gdb vmlinux
>
> l *(snd_pcm_hw_params+0x3f3)
>
> ?
>

(gdb) l *(snd_pcm_hw_params+0x3f3)
0xffffffff817efc85 is in snd_pcm_hw_params (.../linux/sound/core/pcm_native.c:749).
744 while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
745 runtime->boundary *= 2;
746
747 /* clear the buffer for avoiding possible kernel info leaks */
748 if (runtime->dma_area && !substream->ops->copy_user)
749 memset(runtime->dma_area, 0, runtime->dma_bytes);
750
751 snd_pcm_timer_resolution_change(substream);
752 snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);
753

2020-06-09 02:34:53

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Mon, 8 Jun 2020, Alex Xu (Hello71) wrote:

> Excerpts from Christoph Hellwig's message of June 8, 2020 2:19 am:
> > Can you do a listing using gdb where this happens?
> >
> > gdb vmlinux
> >
> > l *(snd_pcm_hw_params+0x3f3)
> >
> > ?
> >
>
> (gdb) l *(snd_pcm_hw_params+0x3f3)
> 0xffffffff817efc85 is in snd_pcm_hw_params (.../linux/sound/core/pcm_native.c:749).
> 744 while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
> 745 runtime->boundary *= 2;
> 746
> 747 /* clear the buffer for avoiding possible kernel info leaks */
> 748 if (runtime->dma_area && !substream->ops->copy_user)
> 749 memset(runtime->dma_area, 0, runtime->dma_bytes);
> 750
> 751 snd_pcm_timer_resolution_change(substream);
> 752 snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);
> 753
>

Working theory is that CONFIG_DMA_NONCOHERENT_MMAP getting set is causing
the error_code in the page fault path. Debugging with Alex off-thread we
found that dma_{alloc,free}_from_pool() are not getting called from the
new code in dma_direct_{alloc,free}_pages() and he has not enabled
mem_encrypt.

So the issue is related to setting CONFIG_DMA_COHERENT_POOL, and not
anything else related to AMD SME. He has a patch to try out, but I wanted
to update the thread in case there are other ideas to try other than
selecting CONFIG_DMA_NONCOHERENT_MMAP only when CONFIG_DMA_REMAP is set
(and not CONFIG_DMA_COHERENT_POOL).

2020-06-09 05:46:07

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Mon, Jun 08, 2020 at 07:31:47PM -0700, David Rientjes wrote:
> On Mon, 8 Jun 2020, Alex Xu (Hello71) wrote:
>
> > Excerpts from Christoph Hellwig's message of June 8, 2020 2:19 am:
> > > Can you do a listing using gdb where this happens?
> > >
> > > gdb vmlinux
> > >
> > > l *(snd_pcm_hw_params+0x3f3)
> > >
> > > ?
> > >
> >
> > (gdb) l *(snd_pcm_hw_params+0x3f3)
> > 0xffffffff817efc85 is in snd_pcm_hw_params (.../linux/sound/core/pcm_native.c:749).
> > 744 while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
> > 745 runtime->boundary *= 2;
> > 746
> > 747 /* clear the buffer for avoiding possible kernel info leaks */
> > 748 if (runtime->dma_area && !substream->ops->copy_user)
> > 749 memset(runtime->dma_area, 0, runtime->dma_bytes);
> > 750
> > 751 snd_pcm_timer_resolution_change(substream);
> > 752 snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);
> > 753
> >
>
> Working theory is that CONFIG_DMA_NONCOHERENT_MMAP getting set is causing
> the error_code in the page fault path. Debugging with Alex off-thread we
> found that dma_{alloc,free}_from_pool() are not getting called from the
> new code in dma_direct_{alloc,free}_pages() and he has not enabled
> mem_encrypt.

While DMA_COHERENT_POOL absolutely should not select DMA_NONCOHERENT_MMAP
(and you should send your patch either way), I don't think it is going
to make a difference here, as DMA_NONCOHERENT_MMAP just means we
allows mmaps even for non-coherent devices, and we do not support
non-coherent devices on x86.

From the disassembly it seems like a vmalloc allocation is NULL, which
seems really weird as this patch shouldn't make a difference for them,
and I also only see a single places that allocates the field, and that
checks for an allocation failure. But the sound code is a little
hard to unwind sometimes.

2020-06-09 08:09:02

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 07:43:06 +0200,
Christoph Hellwig wrote:
>
> On Mon, Jun 08, 2020 at 07:31:47PM -0700, David Rientjes wrote:
> > On Mon, 8 Jun 2020, Alex Xu (Hello71) wrote:
> >
> > > Excerpts from Christoph Hellwig's message of June 8, 2020 2:19 am:
> > > > Can you do a listing using gdb where this happens?
> > > >
> > > > gdb vmlinux
> > > >
> > > > l *(snd_pcm_hw_params+0x3f3)
> > > >
> > > > ?
> > > >
> > >
> > > (gdb) l *(snd_pcm_hw_params+0x3f3)
> > > 0xffffffff817efc85 is in snd_pcm_hw_params (.../linux/sound/core/pcm_native.c:749).
> > > 744 while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
> > > 745 runtime->boundary *= 2;
> > > 746
> > > 747 /* clear the buffer for avoiding possible kernel info leaks */
> > > 748 if (runtime->dma_area && !substream->ops->copy_user)
> > > 749 memset(runtime->dma_area, 0, runtime->dma_bytes);
> > > 750
> > > 751 snd_pcm_timer_resolution_change(substream);
> > > 752 snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);
> > > 753
> > >
> >
> > Working theory is that CONFIG_DMA_NONCOHERENT_MMAP getting set is causing
> > the error_code in the page fault path. Debugging with Alex off-thread we
> > found that dma_{alloc,free}_from_pool() are not getting called from the
> > new code in dma_direct_{alloc,free}_pages() and he has not enabled
> > mem_encrypt.
>
> While DMA_COHERENT_POOL absolutely should not select DMA_NONCOHERENT_MMAP
> (and you should send your patch either way), I don't think it is going
> to make a difference here, as DMA_NONCOHERENT_MMAP just means we
> allows mmaps even for non-coherent devices, and we do not support
> non-coherent devices on x86.
>
> >From the disassembly it seems like a vmalloc allocation is NULL, which
> seems really weird as this patch shouldn't make a difference for them,
> and I also only see a single places that allocates the field, and that
> checks for an allocation failure. But the sound code is a little
> hard to unwind sometimes.

It's not clear which sound device being affected, but if it's
HD-audio on x86, runtime->dma_area points to a vmapped buffer from
SG-pages allocated by dma_alloc_coherent().

OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
vmalloc().

Takashi

2020-06-09 08:47:52

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, Jun 09, 2020 at 10:05:26AM +0200, Takashi Iwai wrote:
> > >From the disassembly it seems like a vmalloc allocation is NULL, which
> > seems really weird as this patch shouldn't make a difference for them,
> > and I also only see a single places that allocates the field, and that
> > checks for an allocation failure. But the sound code is a little
> > hard to unwind sometimes.
>
> It's not clear which sound device being affected, but if it's
> HD-audio on x86, runtime->dma_area points to a vmapped buffer from
> SG-pages allocated by dma_alloc_coherent().
>
> OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
> vmalloc().

Err, you can't just vmap a buffer returned from dma_alloc_coherent,
dma_alloc_coherent returns values are opaque and can't be used
for virt_to_page. Whatever that code did has already been broken
per the DMA API contract and on many architectures and just happend
to work on x86 by accident.

2020-06-09 09:37:31

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 11:17:27 +0200,
Christoph Hellwig wrote:
>
> On Tue, Jun 09, 2020 at 11:09:14AM +0200, Takashi Iwai wrote:
> > On Tue, 09 Jun 2020 10:43:05 +0200,
> > Christoph Hellwig wrote:
> > >
> > > On Tue, Jun 09, 2020 at 10:05:26AM +0200, Takashi Iwai wrote:
> > > > > >From the disassembly it seems like a vmalloc allocation is NULL, which
> > > > > seems really weird as this patch shouldn't make a difference for them,
> > > > > and I also only see a single places that allocates the field, and that
> > > > > checks for an allocation failure. But the sound code is a little
> > > > > hard to unwind sometimes.
> > > >
> > > > It's not clear which sound device being affected, but if it's
> > > > HD-audio on x86, runtime->dma_area points to a vmapped buffer from
> > > > SG-pages allocated by dma_alloc_coherent().
> > > >
> > > > OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
> > > > vmalloc().
> > >
> > > Err, you can't just vmap a buffer returned from dma_alloc_coherent,
> > > dma_alloc_coherent returns values are opaque and can't be used
> > > for virt_to_page. Whatever that code did has already been broken
> > > per the DMA API contract and on many architectures and just happend
> > > to work on x86 by accident.
> >
> > Hmm, that's bad.
> >
> > How would be a proper way to get the virtually mapped SG-buffer pages
> > with coherent memory? (Also allowing user-space mmap, too)
>
> dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> have a good way for kernel space mappings.

And that's the missing piece right now... :-<

Takashi

2020-06-09 10:47:20

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 10:43:05 +0200,
Christoph Hellwig wrote:
>
> On Tue, Jun 09, 2020 at 10:05:26AM +0200, Takashi Iwai wrote:
> > > >From the disassembly it seems like a vmalloc allocation is NULL, which
> > > seems really weird as this patch shouldn't make a difference for them,
> > > and I also only see a single places that allocates the field, and that
> > > checks for an allocation failure. But the sound code is a little
> > > hard to unwind sometimes.
> >
> > It's not clear which sound device being affected, but if it's
> > HD-audio on x86, runtime->dma_area points to a vmapped buffer from
> > SG-pages allocated by dma_alloc_coherent().
> >
> > OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
> > vmalloc().
>
> Err, you can't just vmap a buffer returned from dma_alloc_coherent,
> dma_alloc_coherent returns values are opaque and can't be used
> for virt_to_page. Whatever that code did has already been broken
> per the DMA API contract and on many architectures and just happend
> to work on x86 by accident.

Hmm, that's bad.

How would be a proper way to get the virtually mapped SG-buffer pages
with coherent memory? (Also allowing user-space mmap, too)

thanks,

Takashi

2020-06-09 10:48:36

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, Jun 09, 2020 at 11:09:14AM +0200, Takashi Iwai wrote:
> On Tue, 09 Jun 2020 10:43:05 +0200,
> Christoph Hellwig wrote:
> >
> > On Tue, Jun 09, 2020 at 10:05:26AM +0200, Takashi Iwai wrote:
> > > > >From the disassembly it seems like a vmalloc allocation is NULL, which
> > > > seems really weird as this patch shouldn't make a difference for them,
> > > > and I also only see a single places that allocates the field, and that
> > > > checks for an allocation failure. But the sound code is a little
> > > > hard to unwind sometimes.
> > >
> > > It's not clear which sound device being affected, but if it's
> > > HD-audio on x86, runtime->dma_area points to a vmapped buffer from
> > > SG-pages allocated by dma_alloc_coherent().
> > >
> > > OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
> > > vmalloc().
> >
> > Err, you can't just vmap a buffer returned from dma_alloc_coherent,
> > dma_alloc_coherent returns values are opaque and can't be used
> > for virt_to_page. Whatever that code did has already been broken
> > per the DMA API contract and on many architectures and just happend
> > to work on x86 by accident.
>
> Hmm, that's bad.
>
> How would be a proper way to get the virtually mapped SG-buffer pages
> with coherent memory? (Also allowing user-space mmap, too)

dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
have a good way for kernel space mappings.

2020-06-09 11:06:03

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 11:31:20 +0200,
Takashi Iwai wrote:
>
> On Tue, 09 Jun 2020 11:17:27 +0200,
> Christoph Hellwig wrote:
> >
> > On Tue, Jun 09, 2020 at 11:09:14AM +0200, Takashi Iwai wrote:
> > > On Tue, 09 Jun 2020 10:43:05 +0200,
> > > Christoph Hellwig wrote:
> > > >
> > > > On Tue, Jun 09, 2020 at 10:05:26AM +0200, Takashi Iwai wrote:
> > > > > > >From the disassembly it seems like a vmalloc allocation is NULL, which
> > > > > > seems really weird as this patch shouldn't make a difference for them,
> > > > > > and I also only see a single places that allocates the field, and that
> > > > > > checks for an allocation failure. But the sound code is a little
> > > > > > hard to unwind sometimes.
> > > > >
> > > > > It's not clear which sound device being affected, but if it's
> > > > > HD-audio on x86, runtime->dma_area points to a vmapped buffer from
> > > > > SG-pages allocated by dma_alloc_coherent().
> > > > >
> > > > > OTOH, if it's a USB-audio, runtime->dma_area is a buffer by
> > > > > vmalloc().
> > > >
> > > > Err, you can't just vmap a buffer returned from dma_alloc_coherent,
> > > > dma_alloc_coherent returns values are opaque and can't be used
> > > > for virt_to_page. Whatever that code did has already been broken
> > > > per the DMA API contract and on many architectures and just happend
> > > > to work on x86 by accident.
> > >
> > > Hmm, that's bad.
> > >
> > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > with coherent memory? (Also allowing user-space mmap, too)
> >
> > dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> > have a good way for kernel space mappings.
>
> And that's the missing piece right now... :-<

BTW, this kind of usage is not specific to sound, but also V4L also
does vmap() over SG pages from dma_alloc_coherent(). It seems done
only on selected devices, though.

Takashi

2020-06-09 11:50:42

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Alex, can you try this patch?

diff --git a/sound/core/Kconfig b/sound/core/Kconfig
index d4554f376160a9..10b06e575a7fc5 100644
--- a/sound/core/Kconfig
+++ b/sound/core/Kconfig
@@ -192,6 +192,6 @@ config SND_VMASTER

config SND_DMA_SGBUF
def_bool y
- depends on X86
+ depends on BROKEN

source "sound/core/seq/Kconfig"

2020-06-09 11:52:30

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, Jun 09, 2020 at 01:45:34PM +0200, Takashi Iwai wrote:
> Yes, for the sound stuff, something below should make things working.
> But it means that we'll lose the SG-buffer allocation and the
> allocation of large buffers might fail on some machines.

We crossed lines there. In general due to better memory compaction and
CMA we have better chances to get larger contiguous allocations these
days, so this might not be too much of an issue in practice.

2020-06-09 12:49:40

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, Jun 09, 2020 at 11:31:20AM +0200, Takashi Iwai wrote:
> > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > with coherent memory? (Also allowing user-space mmap, too)
> >
> > dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> > have a good way for kernel space mappings.
>
> And that's the missing piece right now... :-<

Can you point me to the relevant places (allocation and vmap mostly)
so that I can take a look at how to fix this mess?

2020-06-09 12:49:49

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, Jun 09, 2020 at 01:38:46PM +0200, Takashi Iwai wrote:
> On Tue, 09 Jun 2020 13:31:23 +0200,
> Christoph Hellwig wrote:
> >
> > On Tue, Jun 09, 2020 at 11:31:20AM +0200, Takashi Iwai wrote:
> > > > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > > > with coherent memory? (Also allowing user-space mmap, too)
> > > >
> > > > dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> > > > have a good way for kernel space mappings.
> > >
> > > And that's the missing piece right now... :-<
> >
> > Can you point me to the relevant places (allocation and vmap mostly)
> > so that I can take a look at how to fix this mess?
>
> Found in sound/core/sgbuf.c. It's specific to x86.

So it looks like we could just turn off CONFIG_SND_DMA_SGBUF and
be done with it? After all this works on other architectures
just fine..

2020-06-09 12:50:00

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 13:40:59 +0200,
Christoph Hellwig wrote:
>
> On Tue, Jun 09, 2020 at 01:38:46PM +0200, Takashi Iwai wrote:
> > On Tue, 09 Jun 2020 13:31:23 +0200,
> > Christoph Hellwig wrote:
> > >
> > > On Tue, Jun 09, 2020 at 11:31:20AM +0200, Takashi Iwai wrote:
> > > > > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > > > > with coherent memory? (Also allowing user-space mmap, too)
> > > > >
> > > > > dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> > > > > have a good way for kernel space mappings.
> > > >
> > > > And that's the missing piece right now... :-<
> > >
> > > Can you point me to the relevant places (allocation and vmap mostly)
> > > so that I can take a look at how to fix this mess?
> >
> > Found in sound/core/sgbuf.c. It's specific to x86.
>
> So it looks like we could just turn off CONFIG_SND_DMA_SGBUF and
> be done with it? After all this works on other architectures
> just fine..

Yes, for the sound stuff, something below should make things working.
But it means that we'll lose the SG-buffer allocation and the
allocation of large buffers might fail on some machines.

Takashi

--- a/sound/core/Kconfig
+++ b/sound/core/Kconfig
@@ -192,6 +192,6 @@ config SND_VMASTER

config SND_DMA_SGBUF
def_bool y
- depends on X86
+ depends on X86 && BROKEN

source "sound/core/seq/Kconfig"

2020-06-09 13:19:58

by Jaroslav Kysela

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Dne 09. 06. 20 v 13:49 Christoph Hellwig napsal(a):
> On Tue, Jun 09, 2020 at 01:45:34PM +0200, Takashi Iwai wrote:
>> Yes, for the sound stuff, something below should make things working.
>> But it means that we'll lose the SG-buffer allocation and the
>> allocation of large buffers might fail on some machines.
>
> We crossed lines there. In general due to better memory compaction and
> CMA we have better chances to get larger contiguous allocations these
> days, so this might not be too much of an issue in practice.
>

But turning off the SG DMA scheme seems like a step back. Would be possible to
fix this kind of memory mapping?

Jaroslav

--
Jaroslav Kysela <[email protected]>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

2020-06-09 15:15:37

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 13:47:33 +0200,
Christoph Hellwig wrote:
>
> Alex, can you try this patch?

Also could you check whether just papering over the memset() call
alone avoids the crash like below? For PulseAudio and dmix/dsnoop,
it's the only code path that accesses the vmapped buffer, I believe.

If this works more or less, I'll cook a more comprehensive fix.

thanks,

Takashi

--- a/sound/core/pcm_native.c
+++ b/sound/core/pcm_native.c
@@ -754,9 +754,11 @@ static int snd_pcm_hw_params(struct snd_pcm_substream *substream,
while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
runtime->boundary *= 2;

+#if 0
/* clear the buffer for avoiding possible kernel info leaks */
if (runtime->dma_area && !substream->ops->copy_user)
memset(runtime->dma_area, 0, runtime->dma_bytes);
+#endif

snd_pcm_timer_resolution_change(substream);
snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);

2020-06-09 18:36:15

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 09 Jun 2020 13:31:23 +0200,
Christoph Hellwig wrote:
>
> On Tue, Jun 09, 2020 at 11:31:20AM +0200, Takashi Iwai wrote:
> > > > How would be a proper way to get the virtually mapped SG-buffer pages
> > > > with coherent memory? (Also allowing user-space mmap, too)
> > >
> > > dma_mmap_coherent / dma_mmap_attrs for userspace. We don't really
> > > have a good way for kernel space mappings.
> >
> > And that's the missing piece right now... :-<
>
> Can you point me to the relevant places (allocation and vmap mostly)
> so that I can take a look at how to fix this mess?

Found in sound/core/sgbuf.c. It's specific to x86.
Also, for V4L, drivers/media/v4l2-core/videobuf-dma-sg.c.

thanks,

Takashi

2020-06-10 05:30:04

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, 9 Jun 2020, Christoph Hellwig wrote:

> > Working theory is that CONFIG_DMA_NONCOHERENT_MMAP getting set is causing
> > the error_code in the page fault path. Debugging with Alex off-thread we
> > found that dma_{alloc,free}_from_pool() are not getting called from the
> > new code in dma_direct_{alloc,free}_pages() and he has not enabled
> > mem_encrypt.
>
> While DMA_COHERENT_POOL absolutely should not select DMA_NONCOHERENT_MMAP
> (and you should send your patch either way), I don't think it is going
> to make a difference here, as DMA_NONCOHERENT_MMAP just means we
> allows mmaps even for non-coherent devices, and we do not support
> non-coherent devices on x86.
>

We haven't heard yet whether the disabling of DMA_NONCOHERENT_MMAP fixes
Aaron's BUG(), and the patch included some other debugging hints that will
be printed out in case it didn't, but I'll share what we figured out:

In 5.7, his config didn't have DMA_DIRECT_REMAP or DMA_REMAP (it did have
GENERIC_ALLOCATOR already). AMD_MEM_ENCRYPT is set.

In Linus HEAD, AMD_MEM_ENCRYPT now selects DMA_COHERENT_POOL so it sets
the two aforementioned options.

We also figured out that dma_should_alloc_from_pool() is always false up
until the BUG(). So what else changed? Only the selection of DMA_REMAP
and DMA_NONCOHERENT_MMAP.

The comment in the Kconfig about setting "an uncached bit in the
pagetables" led me to believe it may be related to the splat he's seeing
(reserved bit violation). So I suggested dropping DMA_NONCOHERENT_MMAP
from his Kconfig for testing purposes.

If this option should not implicitly be set for DMA_COHERENT_POOL, then I
assume we need yet another Kconfig option since DMA_REMAP selected it
before and DMA_COHERENT_POOL selects DMA_REMAP :)

So do we want a DMA_REMAP_BUT_NO_DMA_NONCOHERENT_MMAP? Decouple DMA_REMAP
from DMA_NONCOHERENT_MMAP and select the latter wherever the former was
set (but not DMA_COHERENT_POOL)? Something else?

2020-06-10 07:20:32

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Tue, Jun 09, 2020 at 10:26:45PM -0700, David Rientjes wrote:
> If this option should not implicitly be set for DMA_COHERENT_POOL, then I
> assume we need yet another Kconfig option since DMA_REMAP selected it
> before and DMA_COHERENT_POOL selects DMA_REMAP :)

Yes, but what do we actually need DMA_REMAP for just for the coherent
pool? We shuldn't really remap anything for AMD-SEV. Sorry for not
noticing this earlier.

2020-06-11 14:54:16

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from Christoph Hellwig's message of June 9, 2020 7:47 am:
> Alex, can you try this patch?
>
> diff --git a/sound/core/Kconfig b/sound/core/Kconfig
> index d4554f376160a9..10b06e575a7fc5 100644
> --- a/sound/core/Kconfig
> +++ b/sound/core/Kconfig
> @@ -192,6 +192,6 @@ config SND_VMASTER
>
> config SND_DMA_SGBUF
> def_bool y
> - depends on X86
> + depends on BROKEN
>
> source "sound/core/seq/Kconfig"
>

Sorry, this patch doesn't work for me with SME off using abfbb29297c2.
David's newest submitted patch works for me, which I already replied to
separately.

Thanks,
Alex.

2020-06-11 14:54:38

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from Takashi Iwai's message of June 9, 2020 11:12 am:
> On Tue, 09 Jun 2020 13:47:33 +0200,
> Christoph Hellwig wrote:
>>
>> Alex, can you try this patch?
>
> Also could you check whether just papering over the memset() call
> alone avoids the crash like below? For PulseAudio and dmix/dsnoop,
> it's the only code path that accesses the vmapped buffer, I believe.
>
> If this works more or less, I'll cook a more comprehensive fix.
>
>
> thanks,
>
> Takashi
>
> --- a/sound/core/pcm_native.c
> +++ b/sound/core/pcm_native.c
> @@ -754,9 +754,11 @@ static int snd_pcm_hw_params(struct snd_pcm_substream *substream,
> while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
> runtime->boundary *= 2;
>
> +#if 0
> /* clear the buffer for avoiding possible kernel info leaks */
> if (runtime->dma_area && !substream->ops->copy_user)
> memset(runtime->dma_area, 0, runtime->dma_bytes);
> +#endif
>
> snd_pcm_timer_resolution_change(substream);
> snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);
>

Sorry, this patch doesn't work for me with SME off using abfbb29297c2.
David's newest submitted patch works for me, which I already replied to
separately.

Thanks,
Alex.

2020-06-11 17:16:05

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Thu, 11 Jun 2020 16:51:55 +0200,
Alex Xu (Hello71) wrote:
>
> Excerpts from Takashi Iwai's message of June 9, 2020 11:12 am:
> > On Tue, 09 Jun 2020 13:47:33 +0200,
> > Christoph Hellwig wrote:
> >>
> >> Alex, can you try this patch?
> >
> > Also could you check whether just papering over the memset() call
> > alone avoids the crash like below? For PulseAudio and dmix/dsnoop,
> > it's the only code path that accesses the vmapped buffer, I believe.
> >
> > If this works more or less, I'll cook a more comprehensive fix.
> >
> >
> > thanks,
> >
> > Takashi
> >
> > --- a/sound/core/pcm_native.c
> > +++ b/sound/core/pcm_native.c
> > @@ -754,9 +754,11 @@ static int snd_pcm_hw_params(struct snd_pcm_substream *substream,
> > while (runtime->boundary * 2 <= LONG_MAX - runtime->buffer_size)
> > runtime->boundary *= 2;
> >
> > +#if 0
> > /* clear the buffer for avoiding possible kernel info leaks */
> > if (runtime->dma_area && !substream->ops->copy_user)
> > memset(runtime->dma_area, 0, runtime->dma_bytes);
> > +#endif
> >
> > snd_pcm_timer_resolution_change(substream);
> > snd_pcm_set_state(substream, SNDRV_PCM_STATE_SETUP);
> >
>
> Sorry, this patch doesn't work for me with SME off using abfbb29297c2.
> David's newest submitted patch works for me, which I already replied to
> separately.

Thanks, so something still missing in the mmap handling, I guess.

I've worked on two different branches for potential fixes of your
problems. Could you test topic/dma-fix and topic/dma-fix2 branches?
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
Just pull one of them onto Linus' git HEAD.

I guess we'll go with David's new patch, but still it's interesting
whether my changes do anything good actually.

Takashi

2020-06-13 16:30:18

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from Takashi Iwai's message of June 11, 2020 1:11 pm:
> Thanks, so something still missing in the mmap handling, I guess.
>
> I've worked on two different branches for potential fixes of your
> problems. Could you test topic/dma-fix and topic/dma-fix2 branches?
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> Just pull one of them onto Linus' git HEAD.
>
> I guess we'll go with David's new patch, but still it's interesting
> whether my changes do anything good actually.
>
>
> Takashi
>

On torvalds 623f6dc593, topic/dma-fix causes sound to be output as
alternating half-second bursts of noise and a few seconds of silence.
topic/dma-fix2 appears to work properly.

Thanks,
Alex.

2020-06-14 09:59:31

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

On Sat, 13 Jun 2020 18:25:22 +0200,
Alex Xu (Hello71) wrote:
>
> Excerpts from Takashi Iwai's message of June 11, 2020 1:11 pm:
> > Thanks, so something still missing in the mmap handling, I guess.
> >
> > I've worked on two different branches for potential fixes of your
> > problems. Could you test topic/dma-fix and topic/dma-fix2 branches?
> > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> > Just pull one of them onto Linus' git HEAD.
> >
> > I guess we'll go with David's new patch, but still it's interesting
> > whether my changes do anything good actually.
> >
> >
> > Takashi
> >
>
> On torvalds 623f6dc593, topic/dma-fix causes sound to be output as
> alternating half-second bursts of noise and a few seconds of silence.
> topic/dma-fix2 appears to work properly.

OK, thanks for the feedback! Just to make sure, you're using
PulseAudio, right?
If so, it was still something wrong about mmap, and the secondary
method (the fallback to the continuous page) looks like a safer
approach in the end.

I suppose that David's fix will be merged sooner or later. Meanwhile
I'll work on the change in the sound driver side to make things a bit
more robust. They don't conflict and both good applicable.

thanks,

Takashi

2020-06-14 12:13:13

[permalink] [raw]

Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash

Excerpts from Takashi Iwai's message of June 14, 2020 5:54 am:
> On Sat, 13 Jun 2020 18:25:22 +0200,
> Alex Xu (Hello71) wrote:
>>
>> Excerpts from Takashi Iwai's message of June 11, 2020 1:11 pm:
>> > Thanks, so something still missing in the mmap handling, I guess.
>> >
>> > I've worked on two different branches for potential fixes of your
>> > problems. Could you test topic/dma-fix and topic/dma-fix2 branches?
>> > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
>> > Just pull one of them onto Linus' git HEAD.
>> >
>> > I guess we'll go with David's new patch, but still it's interesting
>> > whether my changes do anything good actually.
>> >
>> >
>> > Takashi
>> >
>>
>> On torvalds 623f6dc593, topic/dma-fix causes sound to be output as
>> alternating half-second bursts of noise and a few seconds of silence.
>> topic/dma-fix2 appears to work properly.
>
> OK, thanks for the feedback! Just to make sure, you're using
> PulseAudio, right?
> If so, it was still something wrong about mmap, and the secondary
> method (the fallback to the continuous page) looks like a safer
> approach in the end.
>
> I suppose that David's fix will be merged sooner or later. Meanwhile
> I'll work on the change in the sound driver side to make things a bit
> more robust. They don't conflict and both good applicable.
>
>
> thanks,
>
> Takashi
>

Ah, no, I think that wasn't clear. I use ALSA directly with mostly
default configuration, except an asym sets separate default playback and
record devices.

asound.conf:

defaults.pcm.card 1
defaults.ctl.card 1

pcm.!default {
type asym
playback.pcm
{
type plug
slave.pcm "dmix"
}
capture.pcm
{
type plug
slave.pcm {
type dsnoop
ipc_key 6793
slave.pcm "hw:U0x46d0x81d"
}
}
}

I think I wasn't able to set defaults.pcm.dmix.card and
defaults.pcm.dsnoop.card for some reason, not sure why. I can try that,
but I don't think it will affect this mmap issue.

Thanks,
Alex.

2020-06-14 15:43:30