Re: Re: I need help to determine package name for a bug report.

[Zoltán Herman]

No, but since every one works in memory, one of its segments may be
defective.
Memtest writes and reads ... but not concurrent.

2017-08-27 23:16 GMT+02:00 Fungi4All :

>
> From: zoltan...@gmail.com
> To: Debian User 
>
> I would try to exchange the memories by swapping...
>
> 2017-08-27 16:36 GMT+02:00 Alexander V. Makartsev :
>
>> Package: linux-image-4.9.0-3-amd64
>> Version: 4.9.30-2+deb9u3
>> Maintainer: Debian Kernel Team 
>>
>> I've already checked memory with memtest86+ and found no errors. My
>> hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo)
>> Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted
>> page table at address", so I doubt it is hardware problem.
>>
>> On 27.08.2017 15:35, Zoltán Herman wrote:
>> > kernel team
>> > linux-image-
>> >
>> > May be a memory error?
>> >
>>
>
> Do sound cards have memory chips on them?  How can we tell?  If they do
> could this be a source of the above problem that memtest doesn't test?
>
>

Re: Re: I need help to determine package name for a bug report.

[Fungi4All]

> From: zoltan...@gmail.com
> To: Debian User 
>
> I would try to exchange the memories by swapping...
>
> 2017-08-27 16:36 GMT+02:00 Alexander V. Makartsev :
>
>> Package: linux-image-4.9.0-3-amd64
>> Version: 4.9.30-2+deb9u3
>> Maintainer: Debian Kernel Team 
>>
>> I've already checked memory with memtest86+ and found no errors. My
>> hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo)
>> Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted
>> page table at address", so I doubt it is hardware problem.
>>
>> On [27.08.2017 15](tel:27.08.2017%2015):35, Zoltán Herman wrote:
>>> kernel team
>>> linux-image-
>>>
>>> May be a memory error?
>>>

Do sound cards have memory chips on them?  How can we tell?  If they do
could this be a source of the above problem that memtest doesn't test?

Re: Re: I need help to determine package name for a bug report.

[Zoltán Herman]

I would try to exchange the memories by swapping...

2017-08-27 16:36 GMT+02:00 Alexander V. Makartsev :

> Package: linux-image-4.9.0-3-amd64
> Version: 4.9.30-2+deb9u3
> Maintainer: Debian Kernel Team 
>
> I've already checked memory with memtest86+ and found no errors. My
> hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo)
> Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted
> page table at address", so I doubt it is hardware problem.
>
> On 27.08.2017 15:35, Zoltán Herman wrote:
> > kernel team
> > linux-image-
> >
> > May be a memory error?
> >
>
>

Re: Re: I need help to determine package name for a bug report.

[Alexander V. Makartsev]

Package: linux-image-4.9.0-3-amd64
Version: 4.9.30-2+deb9u3
Maintainer: Debian Kernel Team 

I've already checked memory with memtest86+ and found no errors. My
hardware pretty recent (Skylake i5 CPU and H170 Chipset based mobo)
Also these errors always begin with "kernel: alsa-sink-ALC88: Corrupted
page table at address", so I doubt it is hardware problem.

On 27.08.2017 15:35, Zoltán Herman wrote:
> kernel team
> linux-image-
>
> May be a memory error?
>

Re: I need help to determine package name for a bug report.

[Zoltán Herman]

kernel team
linux-image-

May be a memory error?

2017. aug. 27. 12:13 ezt írta ("Alexander V. Makartsev" ):

Hello.

On rare occasion, I have these strange system lockups that seems to be
tied to "ALC88" sound driver\kernel module.
I am unable to determine package name to file a bug report.
All information I have is this syslog from previous boot. Got it with
"journalctl -b -1"
>From what I can tell it could be alsa, or pulseaudio, or kernel, or one
of its modules.
 cut 
авг 25 20:45:59 fortune kernel: alsa-sink-ALC88: Corrupted page table at
address 7f018fe0
авг 25 20:45:59 fortune kernel: PGD 442eb9067
авг 25 20:45:59 fortune kernel: PUD 423196067
авг 25 20:45:59 fortune kernel: PMD 80045fae08e7
 cut 
авг 25 20:45:59 fortune kernel: sched: RT throttling activated
авг 25 20:45:59 fortune kernel: BUG: unable to handle kernel paging
request at fffeffa0005f
авг 25 20:45:59 fortune kernel: IP: [] 0xfffeee19a725
авг 25 20:45:59 fortune kernel: PGD 346a0a067
авг 25 20:45:59 fortune kernel: PUD 0
авг 25 20:45:59 fortune kernel:
авг 25 20:45:59 fortune kernel: Oops:  [#2] SMP
 cut 
авг 25 20:46:33 fortune kernel: kernel BUG at
/build/linux-me40Ry/linux-4.9.30/mm/slab.c:2981!
авг 25 20:46:33 fortune kernel: invalid opcode:  [#3] SMP
 cut 
авг 25 20:46:33 fortune kernel: NMI watchdog: BUG: soft lockup - CPU#2
stuck for 22s! [psensor:1185]

 cut 

I need help to determine package name for a bug report.

[Alexander V. Makartsev]

Hello.

On rare occasion, I have these strange system lockups that seems to be
tied to "ALC88" sound driver\kernel module.
I am unable to determine package name to file a bug report.
All information I have is this syslog from previous boot. Got it with
"journalctl -b -1"
>From what I can tell it could be alsa, or pulseaudio, or kernel, or one
of its modules.
 cut 
авг 25 20:45:59 fortune kernel: alsa-sink-ALC88: Corrupted page table at
address 7f018fe0
авг 25 20:45:59 fortune kernel: PGD 442eb9067
авг 25 20:45:59 fortune kernel: PUD 423196067
авг 25 20:45:59 fortune kernel: PMD 80045fae08e7
 cut 
авг 25 20:45:59 fortune kernel: sched: RT throttling activated
авг 25 20:45:59 fortune kernel: BUG: unable to handle kernel paging
request at fffeffa0005f
авг 25 20:45:59 fortune kernel: IP: [] 0xfffeee19a725
авг 25 20:45:59 fortune kernel: PGD 346a0a067
авг 25 20:45:59 fortune kernel: PUD 0
авг 25 20:45:59 fortune kernel:
авг 25 20:45:59 fortune kernel: Oops:  [#2] SMP
 cut 
авг 25 20:46:33 fortune kernel: kernel BUG at
/build/linux-me40Ry/linux-4.9.30/mm/slab.c:2981!
авг 25 20:46:33 fortune kernel: invalid opcode:  [#3] SMP
 cut 
авг 25 20:46:33 fortune kernel: NMI watchdog: BUG: soft lockup - CPU#2
stuck for 22s! [psensor:1185]

 cut