Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-25 Thread Alan Cox
On Sat, Oct 24, 2020 at 2:38 PM Mark Johnston wrote: > On Fri, Oct 23, 2020 at 06:32:25PM +0200, Michal Meloun wrote: > > > > > > On 19.10.2020 22:39, Mark Johnston wrote: > > > On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote: > > >> > > >> > > >> On 06.10.2020 15:37, Mark Johnston

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-24 Thread Mark Johnston
On Fri, Oct 23, 2020 at 06:32:25PM +0200, Michal Meloun wrote: > > > On 19.10.2020 22:39, Mark Johnston wrote: > > On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote: > >> > >> > >> On 06.10.2020 15:37, Mark Johnston wrote: > >>> On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-23 Thread Michal Meloun
On 19.10.2020 22:39, Mark Johnston wrote: > On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote: >> >> >> On 06.10.2020 15:37, Mark Johnston wrote: >>> On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: Still seeing non-current pmap panics on the Pi3, this time a B+

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-21 Thread Mark Johnston
On Tue, Oct 20, 2020 at 11:55:30AM -0700, bob prohaska wrote: > On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote: > > > > I set up a RPi3 to try and repro this and have so far managed to trigger > > it once using Peter Holm's stress2 suite, so I'll keep investigating. I > > hadn't

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-20 Thread bob prohaska
On Tue, Oct 20, 2020 at 12:30:05PM -0400, Mark Johnston wrote: > > I set up a RPi3 to try and repro this and have so far managed to trigger > it once using Peter Holm's stress2 suite, so I'll keep investigating. I > hadn't configured a dump device, but I was able to confirm from DDB that >

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-20 Thread Mark Johnston
On Mon, Oct 19, 2020 at 04:09:09PM -0700, bob prohaska wrote: > On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote: > > > > I think vmspace_exit() should issue a release fence with the cmpset and > > an acquire fence when handling the refcnt == 1 case, but I don't see why > > that

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-19 Thread bob prohaska
On Mon, Oct 19, 2020 at 04:39:54PM -0400, Mark Johnston wrote: > > I think vmspace_exit() should issue a release fence with the cmpset and > an acquire fence when handling the refcnt == 1 case, but I don't see why > that would make a difference here. So, if you can test a debug patch, > this one

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-19 Thread Mark Johnston
On Fri, Oct 16, 2020 at 11:53:56AM +0200, Michal Meloun wrote: > > > On 06.10.2020 15:37, Mark Johnston wrote: > > On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: > >> Still seeing non-current pmap panics on the Pi3, this time a B+ running > >> 13.0-CURRENT (GENERIC-MMCCAM) #0

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-16 Thread Michal Meloun
On 06.10.2020 15:37, Mark Johnston wrote: > On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: >> Still seeing non-current pmap panics on the Pi3, this time a B+ running >> 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) >> during a -j4 buildworld. The backtrace reports

Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-06 Thread Mark Johnston
On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: > Still seeing non-current pmap panics on the Pi3, this time a B+ running > 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) > during a -j4 buildworld. The backtrace reports > > panic: non-current pmap 0xa00020eab8f0

panic: non-current pmap 0xffffa00020eab8f0 on Rpi3

2020-10-05 Thread bob prohaska
Still seeing non-current pmap panics on the Pi3, this time a B+ running 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) during a -j4 buildworld. The backtrace reports panic: non-current pmap 0xa00020eab8f0 cpuid = 0 time = 1601947137 KDB: stack backtrace: db_trace_self() at