On Tue, 2018-10-23 at 14:54 +0200, Bernhard Übelacker wrote:
> Hello Ritesh Raj Sarraf,
>
> Am 23.10.2018 um 06:22 schrieb Ritesh Raj Sarraf:
> > Are you in a position to try the patch
> > out and confirm if it really mitigates the problem ?
>
> I have built a package with this patch applied
Hello Ritesh Raj Sarraf,
Am 23.10.2018 um 06:22 schrieb Ritesh Raj Sarraf:
> Are you in a position to try the patch
> out and confirm if it really mitigates the problem ?
I have built a package with this patch applied yesterday,
and it did not crash anymore in my test VM.
Kind regards,
Bernhard
Hello Bernhard,
On Mon, 2018-10-22 at 20:45 +0200, Bernhard Übelacker wrote:
>
> This looks like it got fixed upstream in patch [1].
> At least a version 0.7.7-3 built with this patch does not crash like
> before.
Thanks for looking into this bug. I'm glad you were able to reproduce
it in your
Hello Axel,
Am 21.10.2018 um 23:10 schrieb Axel Beckert:
> The system is about 2.5 years old.
...
> (I'd say this counts as a yes.)
Ok, will not do wild guesses next time ;-)
I think I were able to reproduce the issue in a buster amd64 qemu-VM,
by forwarding a real usb card reader with
Hi Bernhard,
Bernhard Übelacker wrote:
> what CPU is inside the machine producing this cores?
→ grep model /proc/cpuinfo
model : 94
model name : Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz
model : 94
model name : Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz
model
Hello Axel,
what CPU is inside the machine producing this cores?
Could you please check if your CPU supports avx2 instructions.
If an internet search tells me right this line should show
"avx2" for each core if yes:
grep -o 'avx[^ ]*' /proc/cpuinfo
Kind regards,
Bernhard
6 matches
Mail list logo
