On Wed, Jan 6, 2021 at 11:54 AM David Woodhouse wrote:
>
> On Tue, 2021-01-05 at 16:40 +0100, Christian König wrote:
> > Am 05.01.21 um 13:20 schrieb Huang Rui:
> > > On Tue, Jan 05, 2021 at 07:43:51PM +0800, Borislav Petkov wrote:
> > > > On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui
On Tue, 2021-01-05 at 16:40 +0100, Christian König wrote:
> Am 05.01.21 um 13:20 schrieb Huang Rui:
> > On Tue, Jan 05, 2021 at 07:43:51PM +0800, Borislav Petkov wrote:
> > > On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui wrote:
> > > > Ah, this asic is a bit old and still use radeon driver.
Am 05.01.21 um 13:20 schrieb Huang Rui:
On Tue, Jan 05, 2021 at 07:43:51PM +0800, Borislav Petkov wrote:
On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui wrote:
Ah, this asic is a bit old and still use radeon driver. So we didn't
reproduce it on amdgpu driver. I don't have such the old asic
On Tue, Jan 05, 2021 at 07:43:51PM +0800, Borislav Petkov wrote:
> On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui wrote:
> > Ah, this asic is a bit old and still use radeon driver. So we didn't
> > reproduce it on amdgpu driver. I don't have such the old asic in my hand.
> > May we know
On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui wrote:
> Ah, this asic is a bit old and still use radeon driver. So we didn't
> reproduce it on amdgpu driver. I don't have such the old asic in my hand.
> May we know whether this issue can be duplicated after SI which is used
> amdgpu module
Am 05.01.21 um 12:08 schrieb Huang Rui:
On Tue, Jan 05, 2021 at 06:31:38PM +0800, Borislav Petkov wrote:
Hi,
On Tue, Jan 05, 2021 at 12:12:13PM +0800, Huang Rui wrote:
I am reproducing this issue as well, are you using a Raven board?
I have no clue what Raven is. The workstation I triggered
On Tue, Jan 05, 2021 at 06:31:38PM +0800, Borislav Petkov wrote:
> Hi,
>
> On Tue, Jan 05, 2021 at 12:12:13PM +0800, Huang Rui wrote:
> > I am reproducing this issue as well, are you using a Raven board?
>
> I have no clue what Raven is. The workstation I triggered it once on, has:
>
> [
Hi,
On Tue, Jan 05, 2021 at 12:12:13PM +0800, Huang Rui wrote:
> I am reproducing this issue as well, are you using a Raven board?
I have no clue what Raven is. The workstation I triggered it once on, has:
[7.563968] [drm] radeon kernel modesetting enabled.
[7.581417] [drm] initializing
On Mon, Jan 04, 2021 at 06:58:02PM +0800, Borislav Petkov wrote:
> On Fri, Jan 01, 2021 at 03:34:28PM +0100, Christian K?nig wrote:
> > Going to double check the code, but can you reproduce this issue
> > reliable?
>
> Lemme find a test box which can trigger it too - the splat happened
> on my
Am 04.01.21 um 11:58 schrieb Borislav Petkov:
On Fri, Jan 01, 2021 at 03:34:28PM +0100, Christian König wrote:
Going to double check the code, but can you reproduce this issue
reliable?
Lemme find a test box which can trigger it too - the splat happened
on my workstation and I'd like to avoid
On Fri, Jan 01, 2021 at 03:34:28PM +0100, Christian König wrote:
> Going to double check the code, but can you reproduce this issue
> reliable?
Lemme find a test box which can trigger it too - the splat happened
on my workstation and I'd like to avoid debugging there for obvious
reasons.
Thx.
Hi Borislav,
my best guess is that this is an use after free.
Going to double check the code, but can you reproduce this issue reliable?
Thanks,
Christian.
Am 31.12.20 um 11:40 schrieb Borislav Petkov:
Hi folks,
got this when trying to suspend my workstation to disk, it was still
responsive
Hi folks,
got this when trying to suspend my workstation to disk, it was still
responsive so I could catch the splat:
[22020.334381] [ cut here ]
[22020.339057] list_del corruption. next->prev should be 8b7a9a40, but
was 8881020bced0
[22020.347764] WARNING:
13 matches
Mail list logo
