Hi,
just a short note to report regular freezes with kernel 6.1.0 on a
haswell laptop quad core Intel Core i7-4750HQ (-MT MCP-) with integrated
graphics.
- system only freezes when launching the desktop environment (working on
a text console while having the sddm login screen up, without logging
in, does not seem to cause the issue);
- freezes happens a few seconds to a few minutes after getting to the
desktop environment (that uses opengl and composition). Freeze happens
both on X11 or Wayland.
- freeze seems to cause data loss (system not able to complete writes
when the freeze occurs, data structures on disk get corrupted, e.g.
system complained on broken btrfs snapshots made by timeshift-like app).
- system on freeze ceases responding to ping from the outside;
- upon reboot I cannot find any trace of any issue in the journal;
- on the same system booting kernels up to 6.0.14 is OK.
Seen using a distro kernel, but it should be fairly mainline (manjaro/arch).
Reported to the distro, but seems serious enough to report here too.
Thanks,
Sergio
Hi
Make us an offer on Original New sealed Box Cisco located in usa
C9400-LC-24XS
C9200L-48T-4G-A
C9200L-48T-4G-E
C9200L-48T-4X-E
WS-2960X 48-LPS-L New sealed box Cisco Qty 30
32GB2Rx4 PC4 2400T QTY: 100 $20 each
16GB 2RX8 PC4-3200AA-UB1-11 Qty 100 $18
...............................................
Take all memory for $1,400
4GB DDR3 DESKTOP 86PCS
4GB DDR4 DESKTOP 100PCS
4GB DDR4 LAPTOP 50PCS
8GB DDR3 DESKTOP 64PCS
8GB DDR4 DESKTOP 143PCS
8GB DDR4 LAPTOP 165 PCS.
16GB 2RX4 PC4-2133P-RBB-10 Qty 85
8GB DDR4 PC4-17000 CL15 260-PIN SODIMM Qty 190
We are looking for a buyer to move all @ $1000 USD
Regards,
Justin Gates
Server Rack Equipment
1343 No. 5 Road, Richmond,
British Columbia
V7A 4G1 Canada
Phone: +1 7783083945 | Fax: 778 308 4563
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 1993bf97992df2d560287f3c4120eda57426843d
Gitweb: https://git.kernel.org/tip/1993bf97992df2d560287f3c4120eda57426843d
Author: Masami Hiramatsu (Google) <mhiramat(a)kernel.org>
AuthorDate: Mon, 19 Dec 2022 23:35:10 +09:00
Committer: Peter Zijlstra <peterz(a)infradead.org>
CommitterDate: Tue, 27 Dec 2022 12:51:58 +01:00
x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK
Since the CONFIG_RETHUNK and CONFIG_SLS will use INT3 for stopping
speculative execution after RET instruction, kprobes always failes to
check the probed instruction boundary by decoding the function body if
the probed address is after such sequence. (Note that some conditional
code blocks will be placed after function return, if compiler decides
it is not on the hot path.)
This is because kprobes expects kgdb puts the INT3 as a software
breakpoint and it will replace the original instruction.
But these INT3 are not such purpose, it doesn't need to recover the
original instruction.
To avoid this issue, kprobes checks whether the INT3 is owned by
kgdb or not, and if so, stop decoding and make it fail. The other
INT3 will come from CONFIG_RETHUNK/CONFIG_SLS and those can be
treated as a one-byte instruction.
Fixes: e463a09af2f0 ("x86: Add straight-line-speculation mitigation")
Suggested-by: Peter Zijlstra <peterz(a)infradead.org>
Signed-off-by: Masami Hiramatsu (Google) <mhiramat(a)kernel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz(a)infradead.org>
Cc: stable(a)vger.kernel.org
Link: https://lore.kernel.org/r/167146051026.1374301.392728975473572291.stgit@dev…
---
arch/x86/kernel/kprobes/core.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c
index 6629968..b36f3c3 100644
--- a/arch/x86/kernel/kprobes/core.c
+++ b/arch/x86/kernel/kprobes/core.c
@@ -37,6 +37,7 @@
#include <linux/extable.h>
#include <linux/kdebug.h>
#include <linux/kallsyms.h>
+#include <linux/kgdb.h>
#include <linux/ftrace.h>
#include <linux/kasan.h>
#include <linux/moduleloader.h>
@@ -281,12 +282,15 @@ static int can_probe(unsigned long paddr)
if (ret < 0)
return 0;
+#ifdef CONFIG_KGDB
/*
- * Another debugging subsystem might insert this breakpoint.
- * In that case, we can't recover it.
+ * If there is a dynamically installed kgdb sw breakpoint,
+ * this function should not be probed.
*/
- if (insn.opcode.bytes[0] == INT3_INSN_OPCODE)
+ if (insn.opcode.bytes[0] == INT3_INSN_OPCODE &&
+ kgdb_has_hit_break(addr))
return 0;
+#endif
addr += insn.length;
}