Heyo Theo (and Mark),
On 2021-11-13 4:12 p.m., Theo de Raadt wrote:
If you say that 6.7 works, then the changes in the logs to look at are
the following.
It isn't that many diffs, see below.
I went through every diff to sys/arch/sparc64/stand between release 6.7
(working) until things
On Sun, Nov 14, 2021 at 10:44:40AM +0100, Peter N. M. Hansteen wrote:
> On Sat, Nov 13, 2021 at 12:16:22PM +0100, Matthieu Herrb wrote:
> >
> > did I miss something or is this still pending ?
>
> I just tested, the problem unfortunately persists.
Strange, it works for me... At least with
>Synopsis: Xorg segmentation fault
>Category: amd64
>Environment:
System : OpenBSD 7.0
Details : OpenBSD 7.0-current (GENERIC.MP) #87: Wed Nov 10 10:29:31
MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On Sun Nov 14, 2021 at 11:09 AM PST, Matthieu Herrb wrote:
> On Sun, Nov 14, 2021 at 10:19:43AM -0800, ariel a wrote:
> >
> > >Synopsis: Xorg segmentation fault
> > >Category: amd64
> > >Environment:
> > System : OpenBSD 7.0
> > Details : OpenBSD 7.0-current (GENERIC.MP) #87:
On Sun, 14 Nov 2021 at 11:10:31 -0800, ariel a wrote:
> Will do, thanks!
>
> The reason I have been using the intel driver is solve some tearing I
> was experiencing (with Option "TearFree" "true") so I will look into
> other fixes for that.
Running a compositor like compton or picom helps
Hi,
on my arm64 regress machine I saw this panic during syslogd regress:
OpenBSD 7.0-current (GENERIC.MP) #1391: Fri Nov 12 21:55:27 MST 2021
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
panic: kernel diagnostic assertion "TAILQ_EMPTY(>kq_head)" failed: file
On Sun, Nov 14, 2021 at 10:19:43AM -0800, ariel a wrote:
>
> >Synopsis:Xorg segmentation fault
> >Category:amd64
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC.MP) #87: Wed Nov 10 10:29:31
> MST 2021
>
>
On Sun, Nov 14, 2021 at 09:38:09PM -0500, David Hill wrote:
>
> This did not help my machine:
>
> quick gdb on Xorg.core:
>
> Loaded symbols for /usr/X11R6/lib/modules/input/kbd_drv.so
> Reading symbols from /usr/X11R6/lib/modules/input/ws_drv.so...done.
> Loaded symbols for
Ted Bullock wrote:
> On 2021-11-14 7:36 p.m., Theo de Raadt wrote:
> > So maybe the "write" operation is broken on these older roms.
>
> Is there any more verbose way of seeing what's happening as it starts?
> I'm fairly certain that ddb isn't available since this is happening
> before the
OK more specifics,
I repeated my tests from last night and the boot does indeed fail after
revision 1.35 on sys/arch/sparc64/stand/ofboot/boot.c
Random was added to the bootblocks before 6.7. But then code was
added to fchmod the random file, so that it would not be reused.
That fchmod is
Ted Bullock wrote:
> OK more specifics,
>
> I repeated my tests from last night and the boot does indeed fail
> after revision 1.35 on sys/arch/sparc64/stand/ofboot/boot.c
>
> >
> >> Random was added to the bootblocks before 6.7. But then code was
> >> added to fchmod the random file, so
On 2021-11-14 7:36 p.m., Theo de Raadt wrote:
So maybe the "write" operation is broken on these older roms.
Is there any more verbose way of seeing what's happening as it starts?
I'm fairly certain that ddb isn't available since this is happening
before the kernel is even loaded. I'm kind of
On 11/14/21 14:09, Matthieu Herrb wrote:
On Sun, Nov 14, 2021 at 10:19:43AM -0800, ariel a wrote:
Synopsis: Xorg segmentation fault
Category: amd64
Environment:
System : OpenBSD 7.0
Details : OpenBSD 7.0-current (GENERIC.MP) #87: Wed Nov 10 10:29:31
MST
13 matches
Mail list logo
