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

2017-08-27 Thread 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

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

2017-08-27 Thread 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

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

2017-08-27 Thread 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

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

2017-08-27 Thread 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

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

2017-08-27 Thread 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

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

2017-08-27 Thread 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