https://bugs.kde.org/show_bug.cgi?id=375171
Julian Seward changed:
What|Removed |Added
CC||rick.ramstetter+kde@gmail.c
|
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #12 from Brandon ---
I am coming over from this closed bug:
https://bugs.kde.org/show_bug.cgi?id=375171
In response to whether my processor is Skylake, I believe it is.
laptop:
https://www.amazon.com/Dell-Inspiron-i7559-2512BLK-Generation-
https://bugs.kde.org/show_bug.cgi?id=375171
Tom Hughes changed:
What|Removed |Added
CC||caib...@gmail.com
--- Comment #11 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #10 from Patrik Nyberg ---
(In reply to Julian Seward from comment #8)
> (In reply to Patrik Nyberg from comment #5)
>
> Are you sure that the i5-6200U connection is the only thing in
> common? That processor is a mid-range Skylake, and I
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #9 from Patrik Nyberg ---
We just found this on the kernel bugzilla. Seems to be related
https://bugzilla.kernel.org/show_bug.cgi?id=190061
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #8 from Julian Seward ---
(In reply to Patrik Nyberg from comment #5)
Are you sure that the i5-6200U connection is the only thing in
common? That processor is a mid-range Skylake, and I am sure we
would have heard by now if there were prob
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #7 from Julian Seward ---
(In reply to Patrik Nyberg from comment #6)
> This patch will solve the problem (at least for the simple hello world case).
Sure. That just disables the assertion, though. It doesn't resolve the
underlying issue.
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #6 from Patrik Nyberg ---
This patch will solve the problem (at least for the simple hello world case).
--- valgrind-3.12.0/coregrind/m_dispatch/dispatch-x86-linux.S.org
2017-01-17 13:52:58.290661172 +0100
+++ valgrind-3.12.0/coregrin
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #5 from Patrik Nyberg ---
It might be, but it also seems to be a problem specific to the hardware.
Several of my colleagues have now tried and it seems that all running the same
kind of CPU as me (i5-6200U) are having the issue, while it is
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #4 from Julian Seward ---
I don't have any such problems with the 4.9.3 kernel that comes
with Fedora 25. Is it possible that this is a Gentoo-specific
problem?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #3 from Patrik Nyberg ---
Okej, sounds like you might be on to something. I just upgraded to 4.9.4 and
the error occurs again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #2 from Julian Seward ---
(In reply to Patrik Nyberg from comment #1)
> Downgrading kernel to version 4.4.39-gentoo and the error is no longer
> present.
Yeah, I did wonder if this is kernel specific. The same failure
happened some years a
https://bugs.kde.org/show_bug.cgi?id=375171
--- Comment #1 from Patrik Nyberg ---
Downgrading kernel to version 4.4.39-gentoo and the error is no longer present.
--
You are receiving this mail because:
You are watching all bug changes.
13 matches
Mail list logo
