* Martin Pieuchot <[email protected]> [2022-01-19 03:12]:
> 
> On 18/01/22(Tue) 22:46, Ralf Horstmann wrote:
...
> >     db_enter () at db_enter+0x10
> >     panic(ffffffff81e5053e) at panic+0xbf
> >     __assert(ffffffff81ebcdc6,ffffffff81e23741,428,ffffffff81e718b1) at 
> > __assert+0x25
> >     uvm_page_unbusy(ffff800022738d90,10) at uvm_page_unbusy+0x20e
> >     uvm_aio_aiodone(fffffd81cd592360) at uvm_aio_aiodone+0x252
> >     uvm_aiodone_daemon(ffff8000fffefa40) at uvm_aiodone_daemon+0x124
> >     end trace frame: 0x0, count: 9
> 
> This is caused by an incorrect lock assertion.  I just committed a fix.
> 
> The problem can be triggered when swapping anon.  It should be fixed in
> the next snapshot.

Thanks for the quick fix!

I am testing with a local kernel for now. I need a couple of days of stability
before I can jump onto the snapshots again :-)

Regards
Ralf

Reply via email to