All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: alsa-devel@alsa-project.org, bp@alien8.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	Pavel Machek <pavel@ucw.cz>,
	perex@perex.cz, tglx@linutronix.de, tiwai@suse.com,
	x86@kernel.org, rientjes@google.com, hch@lst.de,
	hch@infradead.org
Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash
Date: Sun, 07 Jun 2020 11:58:21 -0400	[thread overview]
Message-ID: <1591545088.74ii116nf2.none@localhost> (raw)
In-Reply-To: <20200520111136.GA3802@amd>

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.

  parent reply	other threads:[~2020-06-07 15:58 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 11:11 next-0519 on thinkpad x60: sound related? window manager crash Pavel Machek
2020-05-20 11:37 ` Takashi Iwai
2020-05-20 11:37   ` Takashi Iwai
2020-05-20 11:39   ` Pavel Machek
2020-05-20 11:39     ` Pavel Machek
2020-05-20 11:43     ` Takashi Iwai
2020-05-20 11:43       ` Takashi Iwai
2020-06-07 15:58 ` Alex Xu (Hello71) [this message]
2020-06-07 16:38   ` 82fef0ad811f "x86/mm: unencrypted non-blocking DMA allocations use coherent pools" was " Pavel Machek
2020-06-07 16:38     ` Pavel Machek
2020-06-07 19:41     ` David Rientjes
2020-06-07 19:41       ` David Rientjes
2020-06-07 22:53       ` Alex Xu (Hello71)
2020-06-07 22:53         ` Alex Xu (Hello71)
2020-06-08  0:57         ` David Rientjes
2020-06-08  0:57           ` David Rientjes
2020-06-08  2:13           ` Alex Xu (Hello71)
2020-06-08  2:13             ` Alex Xu (Hello71)
2020-06-08  6:19   ` Christoph Hellwig
2020-06-08  6:19     ` Christoph Hellwig
2020-06-08 13:53     ` Alex Xu (Hello71)
2020-06-08 13:53       ` Alex Xu (Hello71)
2020-06-09  2:31       ` David Rientjes
2020-06-09  2:31         ` David Rientjes
2020-06-09  5:43         ` Christoph Hellwig
2020-06-09  5:43           ` Christoph Hellwig
2020-06-09  8:05           ` Takashi Iwai
2020-06-09  8:05             ` Takashi Iwai
2020-06-09  8:43             ` Christoph Hellwig
2020-06-09  8:43               ` Christoph Hellwig
2020-06-09  9:09               ` Takashi Iwai
2020-06-09  9:09                 ` Takashi Iwai
2020-06-09  9:17                 ` Christoph Hellwig
2020-06-09  9:17                   ` Christoph Hellwig
2020-06-09  9:31                   ` Takashi Iwai
2020-06-09  9:31                     ` Takashi Iwai
2020-06-09 11:02                     ` Takashi Iwai
2020-06-09 11:02                       ` Takashi Iwai
2020-06-09 11:31                     ` Christoph Hellwig
2020-06-09 11:31                       ` Christoph Hellwig
2020-06-09 11:38                       ` Takashi Iwai
2020-06-09 11:38                         ` Takashi Iwai
2020-06-09 11:40                         ` Christoph Hellwig
2020-06-09 11:40                           ` Christoph Hellwig
2020-06-09 11:45                           ` Takashi Iwai
2020-06-09 11:45                             ` Takashi Iwai
2020-06-09 11:49                             ` Christoph Hellwig
2020-06-09 11:49                               ` Christoph Hellwig
2020-06-09 13:16                               ` Jaroslav Kysela
2020-06-09 13:16                                 ` Jaroslav Kysela
2020-06-10  5:26           ` David Rientjes
2020-06-10  5:26             ` David Rientjes
2020-06-10  7:14             ` Christoph Hellwig
2020-06-10  7:14               ` Christoph Hellwig
2020-06-09 11:47       ` Christoph Hellwig
2020-06-09 11:47         ` Christoph Hellwig
2020-06-09 15:12         ` Takashi Iwai
2020-06-09 15:12           ` Takashi Iwai
     [not found]           ` <<s5hr1uogtna.wl-tiwai@suse.de>
2020-06-11 14:51             ` Alex Xu (Hello71)
2020-06-11 14:51               ` Alex Xu (Hello71)
2020-06-11 17:11               ` Takashi Iwai
2020-06-11 17:11                 ` Takashi Iwai
2020-06-13 16:25                 ` Alex Xu (Hello71)
2020-06-13 16:25                   ` Alex Xu (Hello71)
2020-06-14  9:54                   ` Takashi Iwai
2020-06-14  9:54                     ` Takashi Iwai
2020-06-14 12:07                     ` Alex Xu (Hello71)
2020-06-14 12:07                       ` Alex Xu (Hello71)
2020-06-14 15:40                       ` Takashi Iwai
2020-06-14 15:40                         ` Takashi Iwai
2020-06-11 14:51         ` Alex Xu (Hello71)
2020-06-11 14:51           ` Alex Xu (Hello71)
     [not found] <20200520110900.GA8203@amd>
2020-05-21  7:41 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1591545088.74ii116nf2.none@localhost \
    --to=alex_y_xu@yahoo.ca \
    --cc=alsa-devel@alsa-project.org \
    --cc=bp@alien8.de \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=perex@perex.cz \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.