Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-11-02 Thread O. Hartmann
On Wed, 1 Nov 2017 10:12:59 +0200 Andriy Gapon wrote: > On 01/11/2017 09:33, O. Hartmann wrote: > > I have the same (or similar) probleme here on two boxes now, maybe more to > > come as I start updating CURRENT cyclic. > > > > Reverting r325227 solves to problem for now. > > Oliver, > > Dav

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-11-01 Thread Andriy Gapon
On 01/11/2017 10:12, Andriy Gapon wrote: > On 01/11/2017 09:33, O. Hartmann wrote: >> I have the same (or similar) probleme here on two boxes now, maybe more to >> come >> as I start updating CURRENT cyclic. >> >> Reverting r325227 solves to problem for now. > > Oliver, > > David and I have been

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-11-01 Thread O. Hartmann
On Tue, 31 Oct 2017 06:02:41 -0700 David Wolfskill wrote: > On Tue, Oct 31, 2017 at 02:35:19PM +0200, Andriy Gapon wrote: > > On 31/10/2017 14:32, David Wolfskill wrote: > > > Andriy, I "cloned" the slice before doing the above, so I can poke > > > at this a bit more (e.g., try to get a crash d

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-11-01 Thread Andriy Gapon
On 01/11/2017 09:33, O. Hartmann wrote: > I have the same (or similar) probleme here on two boxes now, maybe more to > come > as I start updating CURRENT cyclic. > > Reverting r325227 solves to problem for now. Oliver, David and I have been working on this and a fix is coming soon. Sorry for th

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread David Wolfskill
On Tue, Oct 31, 2017 at 02:35:19PM +0200, Andriy Gapon wrote: > On 31/10/2017 14:32, David Wolfskill wrote: > > Andriy, I "cloned" the slice before doing the above, so I can poke > > at this a bit more (e.g., try to get a crash dump), if that would > > still be useful. > > Yes, it would be, as I c

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread Andriy Gapon
On 31/10/2017 14:32, David Wolfskill wrote: > Andriy, I "cloned" the slice before doing the above, so I can poke > at this a bit more (e.g., try to get a crash dump), if that would > still be useful. Yes, it would be, as I currently do not see what the problem with r325227 is. -- Andriy Gapon __

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread David Wolfskill
On Tue, Oct 31, 2017 at 01:53:27PM +0200, Konstantin Belousov wrote: > ... > > db> > > Try to revert r325227. OK; did that, via "svn merge -c -r325227 ^/head"; rebuilt/installed kernel, and a reboot was ... boringly normal. :-) FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread Andriy Gapon
On 31/10/2017 13:37, David Wolfskill wrote: > Any suggestions for diagnosing or fixing it? Try setting a dump device via loader.conf (e.g. dumpdev="ada0p99") and obtaining a crash dump. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https

Re: panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread Konstantin Belousov
On Tue, Oct 31, 2017 at 04:37:10AM -0700, David Wolfskill wrote: > Performed the usual src update in head/amd64; today was from r325137 to > r325228. Laptop had no complaints; everything Just Worked (as usual). > > GEOM: new disk da1 > panic: vtopde on a uva/gpa 0x103 > cpuid = 5 > time = 15

panic: vtopde on a uva/gpa 0x1030000 @r325228 (amd64)

2017-10-31 Thread David Wolfskill
Performed the usual src update in head/amd64; today was from r325137 to r325228. Laptop had no complaints; everything Just Worked (as usual). This time, it was the build machine that whined -- rather less inconvenient for me. :-} Here's what it says currently: ... APIC: Using the MADT enumerato