On 2023/04/24 16:05, Klemens Nanni wrote:
> On Mon, Apr 24, 2023 at 04:58:08PM +0100, Stuart Henderson wrote:
> > On 2023/04/24 15:50, Klemens Nanni wrote:
> > > cpu0: 12th Gen Intel(R) Core(TM) i7-1270P, 2095.31 MHz, 06-9a-03
> >
> > ah you got one of the warm CPU versions then :)
>
> what does
On Mon, Apr 24, 2023 at 04:58:08PM +0100, Stuart Henderson wrote:
> On 2023/04/24 15:50, Klemens Nanni wrote:
> > cpu0: 12th Gen Intel(R) Core(TM) i7-1270P, 2095.31 MHz, 06-9a-03
>
> ah you got one of the warm CPU versions then :)
what does that mean?
On 2023/04/24 15:50, Klemens Nanni wrote:
> cpu0: 12th Gen Intel(R) Core(TM) i7-1270P, 2095.31 MHz, 06-9a-03
ah you got one of the warm CPU versions then :)
Saw this in /var/log/messages on a clean -current GENERIC.MP with WITNESS
and kern.witness.watch=2
Rebooted, zzz and ZZZ a few times, but can't reproduce it so far.
Apr 24 16:16:45 atar /bsd: OpenBSD 7.3-current (GENERIC.MP) #2: Mon Apr
24 13:46:43 WEST 2023
...
root on
On 2023/04/24 15:00, Stuart Henderson wrote:
> > Looking over the local changes to i915_scatterlist.h the segment size
> > could be larger, I'm not sure if that would help.
>
> I will try that and report back after lunch.
Doesn't help.
>
> > Index: dev/pci/drm/i915/i915_scatterlist.h
> >
On 2023/04/24 23:53, Jonathan Gray wrote:
> On Mon, Apr 24, 2023 at 01:49:32PM +0100, Stuart Henderson wrote:
> > Running picom (with no special config or command line flags) on intel
> > T14 gen 3 fairly easily triggers a crash in drm. If it doesn't fail the
> > first time, exiting and restarting
On Mon, Apr 24, 2023 at 01:49:32PM +0100, Stuart Henderson wrote:
> Running picom (with no special config or command line flags) on intel
> T14 gen 3 fairly easily triggers a crash in drm. If it doesn't fail the
> first time, exiting and restarting a few times pretty much always
> triggers it.
>
Running picom (with no special config or command line flags) on intel
T14 gen 3 fairly easily triggers a crash in drm. If it doesn't fail the
first time, exiting and restarting a few times pretty much always
triggers it.
Full proc listing below after dmesg, Xorg is the only active process
at the
Was testing dv's latest BTI fix for unhibernate.
Fresh boot into -current bsd.mp, run top in xterm, ZZZ, unhibernate,
ssh somewhere to say unhibernate is working, then I got the panic.
System was locked up, had to hard reset.
Typed from photo:
OpenBSD/amd64 (atar.my.domain) (ttyC0)
login:
