On Sun, 14 Jun 2020 14:07:48 +0200,
Alex Xu (Hello71) wrote:
>
> 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
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
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
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/p
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
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/d
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
>
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 nee
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 dm
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.
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 mac
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 t
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 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
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 cohere
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_coh
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
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
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 disasse
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
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
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
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 whe
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_para
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)
> 0x81
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)
0x817efc85 is in snd_pcm_hw_params
(.../linux/sound/core/pcm_native.c:749
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 addre
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
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:
> >> > b2b582cc2000
> >> > [ 20.263104] #PF:
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:
>> > b2b582cc2000
>> > [ 20.263104]
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:
> > b2b582cc2000
> > [ 20.263104] #PF: supervisor write access in kernel mode
> > [ 20.263105] #PF: error
Hi!
> I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
>
> [ 20.263098] BUG: unable to handle page fault for address: b2b582cc2000
> [ 20.263104] #PF: supervisor write access in kernel mode
> [ 20.263105] #PF: error_code(0x000b) - reserved bit violation
> [ 20.263
I have a similar issue, caused between aaa2faab4ed8 and b170290c2836.
[ 20.263098] BUG: unable to handle page fault for address: b2b582cc2000
[ 20.263104] #PF: supervisor write access in kernel mode
[ 20.263105] #PF: error_code(0x000b) - reserved bit violation
[ 20.263107] PGD 3fd03b06
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 simil
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.
> > >
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
> > t
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 th
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...
Best regards,
38 matches
Mail list logo
