On Wed, 02 Feb 2022 at 08:50:28 +0100, Paul de Weerd wrote:
> On Wed, Feb 02, 2022 at 10:41:06AM +1100, Jonathan Gray wrote:
> | > does this diff to provide stolen memory data help?
> |
> | I have committed this minus the printf change
> | would still be interested to hear if it helps
>
> Just to
On Wed, Feb 02, 2022 at 10:41:06AM +1100, Jonathan Gray wrote:
| > does this diff to provide stolen memory data help?
|
| I have committed this minus the printf change
| would still be interested to hear if it helps
Just to publicly confirm - this fixes the panics I was seeing on my
Dell XPS 13 t
On Wed, 2 Feb 2022 10:41:06 +1100
Jonathan Gray wrote:
> > does this diff to provide stolen memory data help?
>
> I have committed this minus the printf change
> would still be interested to hear if it helps
This fixed it! I built a new kernel after checking out the latest
commits below, and
On Mon, Jan 31, 2022 at 11:17:01PM +1100, Jonathan Gray wrote:
> On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> > On Sat, 29 Jan 2022 12:15:10 -0300
> > Martin Pieuchot wrote:
> >
> > > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > > On Sat, 29 Jan 2022 15:19:20 +1100
>
On Tue, 1 Feb 2022 14:56:22 +1100
Jonathan Gray wrote:
> > I don't understand which process is triggering the fault. Maybe
> > somebody (jsg@?) could craft a diff to figure out if this same address
> > fault and which thread/context is faulting it in SP and/or with
> > pool_debug = 2.
>
> I'm
On Mon, Jan 31, 2022 at 12:14:32PM -0300, Martin Pieuchot wrote:
> On 31/01/22(Mon) 00:54, Thomas Frohwein wrote:
> > On Sat, 29 Jan 2022 12:15:10 -0300
> > Martin Pieuchot wrote:
> >
> > > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > > Jonathan
On 31/01/22(Mon) 19:18, Jonathan Gray wrote:
> On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> > On Sat, 29 Jan 2022 12:15:10 -0300
> > Martin Pieuchot wrote:
> >
> > > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > > Jonathan Gr
On 31/01/22(Mon) 00:54, Thomas Frohwein wrote:
> On Sat, 29 Jan 2022 12:15:10 -0300
> Martin Pieuchot wrote:
>
> > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > Jonathan Gray wrote:
> > >
> > > > does this diff to revert uvm_fault.c rev 1.124 ch
On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> On Sat, 29 Jan 2022 12:15:10 -0300
> Martin Pieuchot wrote:
>
> > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > Jonathan Gray wrote:
> > >
> > > > does this diff to revert uvm_fa
On Mon, Jan 31, 2022 at 12:54:53AM -0700, Thomas Frohwein wrote:
> On Sat, 29 Jan 2022 12:15:10 -0300
> Martin Pieuchot wrote:
>
> > On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > > On Sat, 29 Jan 2022 15:19:20 +1100
> > > Jonathan Gray wrote:
> > >
> > > > does this diff to revert uvm_fa
On Sat, 29 Jan 2022 12:15:10 -0300
Martin Pieuchot wrote:
> On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> > On Sat, 29 Jan 2022 15:19:20 +1100
> > Jonathan Gray wrote:
> >
> > > does this diff to revert uvm_fault.c rev 1.124 change anything?
> >
> > Unfortunately no. Same pmap error as
On 28/01/22(Fri) 23:03, Thomas Frohwein wrote:
> On Sat, 29 Jan 2022 15:19:20 +1100
> Jonathan Gray wrote:
>
> > does this diff to revert uvm_fault.c rev 1.124 change anything?
>
> Unfortunately no. Same pmap error as in the original bug report occurs
> with a kernel with this diff.
Could you s
On Sat, 29 Jan 2022 15:19:20 +1100
Jonathan Gray wrote:
> does this diff to revert uvm_fault.c rev 1.124 change anything?
Unfortunately no. Same pmap error as in the original bug report occurs
with a kernel with this diff.
>
> Index: sys/uvm/uvm_fault.c
> =
On Fri, Jan 28, 2022 at 06:17:58AM -0700, Thomas Frohwein wrote:
> On Thu, 27 Jan 2022 06:16:04 -0700
> Thomas Frohwein wrote:
>
> > > > Wanted to clarify my reddit post:
> > > > There is a problem when the install is encrypted (full disk encryption,
> > > > w
> > > > bioctl).
> > > > Unencrypte
On Thu, 27 Jan 2022 06:16:04 -0700
Thomas Frohwein wrote:
> > > Wanted to clarify my reddit post:
> > > There is a problem when the install is encrypted (full disk encryption, w
> > > bioctl).
> > > Unencrypted version works fine (got to the login).
> > >
> > > When finding this bug, I tried:
>
On Thu, 27 Jan 2022 21:15:12 +1100
Jonathan Gray wrote:
> thfr said those changes didn't help, I imagine it would be the same for
> you. Both were committed.
That is correct
>
> >
> > Wanted to clarify my reddit post:
> > There is a problem when the install is encrypted (full disk encryption,
On Thu, Jan 27, 2022 at 12:51:19PM +0300, Alex Beakes wrote:
> On Tue, Jan 25, 2022 at 2:25:23, Jonathan Gray wrote:
> > On Mon, Jan 24, 2022 at 05:57:01PM -0700, Thomas Frohwein wrote:
> > > On Tue, 25 Jan 2022 10:59:26 +1100
> > > Jonathan Gray wrote:
> > >
> > > > > if you revert the previous
On Mon, Jan 24, 2022 at 05:57:01PM -0700, Thomas Frohwein wrote:
> On Tue, 25 Jan 2022 10:59:26 +1100
> Jonathan Gray wrote:
>
> > > if you revert the previous and try this does it still boot?
> >
> > this would be more interesting to try
> >
> > corresponds to 'drm/i915: Add object locking t
On Tue, 25 Jan 2022 10:59:26 +1100
Jonathan Gray wrote:
> > if you revert the previous and try this does it still boot?
>
> this would be more interesting to try
>
> corresponds to 'drm/i915: Add object locking to vm_fault_cpu'
> 9fa1f4785f2a54286ccb8a850cda5661f0a3aaf9
>
> https://git.kerne
On Tue, Jan 25, 2022 at 08:27:19AM +1100, Jonathan Gray wrote:
> On Sun, Jan 23, 2022 at 02:40:21PM -0700, Thomas Frohwein wrote:
> > On Sun, Jan 23, 2022 at 10:19:24AM +1100, Jonathan Gray wrote:
> > > On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> > > > On Fri, Jan 21, 2022 at
On Sun, Jan 23, 2022 at 02:40:21PM -0700, Thomas Frohwein wrote:
> On Sun, Jan 23, 2022 at 10:19:24AM +1100, Jonathan Gray wrote:
> > On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> > > On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote:
> > > > On Thu, Jan 20, 2022 at
On Sun, Jan 23, 2022 at 10:19:24AM +1100, Jonathan Gray wrote:
> On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> > On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote:
> > > On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote:
> > > > On Fri, Jan 21, 2022 at
On Fri, Jan 21, 2022 at 03:31:14PM -0700, Thomas Frohwein wrote:
> On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote:
> > On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote:
> > > On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote:
> > > > On Wed, Jan 19, 2022 at
On Fri, Jan 21, 2022 at 07:54:29PM +1100, Jonathan Gray wrote:
> On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote:
> > On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote:
> > > On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote:
> > [...]
> > > > The back
On Thu, Jan 20, 2022 at 04:08:28PM -0700, Thomas Frohwein wrote:
> On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote:
> > On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote:
> [...]
> > > The backtrace is kinda nonsensical, showing a copyout() call with no
> > > prede
On Fri, Jan 21, 2022 at 12:22:49AM +1100, Jonathan Gray wrote:
> On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote:
[...]
> > The backtrace is kinda nonsensical, showing a copyout() call with no
> > predecessor, but maybe that's just from copy*() not setting up a proper
> > fra
On Wed, Jan 19, 2022 at 11:04:26PM -0800, guent...@openbsd.org wrote:
> On Wed, 19 Jan 2022, Thomas Frohwein wrote:
> > >Synopsis: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot
> > >Category: kernel amd64
> > >Environment:
> > Syste
On Wed, 19 Jan 2022, Thomas Frohwein wrote:
> >Synopsis: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot
> >Category:kernel amd64
> >Environment:
> System : OpenBSD 7.0
> Details : OpenBSD 7.0-current (GENERIC) #265: Wed Jan
>Synopsis: crash on booting GENERIC.MP since upgrade to Jan 18 snapshot
>Category: kernel amd64
>Environment:
System : OpenBSD 7.0
Details : OpenBSD 7.0-current (GENERIC) #265: Wed Jan 19 11:41:29
MST 2022
dera...@amd64.openbsd
29 matches
Mail list logo