Re: r320358 panics immediately on boot / AMD64-GENERIC kernel

2017-06-27 Thread Michael Jung

On 2017-06-27 12:16, Eric van Gyzen wrote:

On 06/27/2017 11:09, Michael Jung wrote:

Screen image with backtrace

https://pasteboard.co/dZRVG5Uo.jpg


After upgrading from 318959 to 320358 I immediately get the attached 
panic.


This is AMD64 / GENERIC kernel.

/boot/loader.conf is empty.

The system boots off a UFS2 partition.

This is a virtual guest and I do currently have a serial cable.

Short of figuring out how to virtualize a serial console from a ESXi
guest is
there any more information I can provide?


Someone else hit this.  Removing the contents of /usr/obj and 
rebuilding

fixed it for him.  Apparently, some of the objects didn't get rebuilt,
as needed.

Eric



Thank to all that replied.  Indeed removing the contents of /usr/obj and 
rebuilding

the kernel resolved the issue.

Thanks!

--mikej
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


r320358 panics immediately on boot / AMD64-GENERIC kernel

2017-06-27 Thread Michael Jung



After upgrading from 318959 to 320358 I immediately get the attached 
panic.


This is AMD64 / GENERIC kernel.

/boot/loader.conf is empty.

The system boots off a UFS2 partition.

This is a virtual guest and I do currently have a serial cable.

Short of figuring out how to virtualize a serial console from a ESXi 
guest is

there any more information I can provide?

Thanks.

Mike
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: r320358 panics immediately on boot / AMD64-GENERIC kernel

2017-06-27 Thread David Wolfskill
On Tue, Jun 27, 2017 at 12:09:56PM -0400, Michael Jung wrote:
> Screen image with backtrace
> 
> https://pasteboard.co/dZRVG5Uo.jpg
> 
> 
> After upgrading from 318959 to 320358 I immediately get the attached 
> panic.
> 
> This is AMD64 / GENERIC kernel.
> 
> /boot/loader.conf is empty.
> 
> The system boots off a UFS2 partition.
> 

If the object directory for your kernel (e.g.,
/usr/obj/usr/src/sys/GENERIC) had more in it than the "version" file,
you might try removing everything in that directory, then rebuilding the
kernel.

(Ref. the thread that starts at
http://docs.FreeBSD.org/cgi/mid.cgi?20170625120731.GE1241 .)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
I look forward to voting against Trump again at the earliest opportunity.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature


Re: r320358 panics immediately on boot / AMD64-GENERIC kernel

2017-06-27 Thread Konstantin Belousov
On Tue, Jun 27, 2017 at 12:09:56PM -0400, Michael Jung wrote:
> Screen image with backtrace
> 
> https://pasteboard.co/dZRVG5Uo.jpg
> 
> 
> After upgrading from 318959 to 320358 I immediately get the attached 
> panic.
> 
> This is AMD64 / GENERIC kernel.
> 
> /boot/loader.conf is empty.
> 
> The system boots off a UFS2 partition.
> 
> This is a virtual guest and I do currently have a serial cable.
> 
> Short of figuring out how to virtualize a serial console from a ESXi 
> guest is
> there any more information I can provide?

Rebuild the kernel after removing the kernel build directory.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: r320358 panics immediately on boot / AMD64-GENERIC kernel

2017-06-27 Thread Eric van Gyzen
On 06/27/2017 11:09, Michael Jung wrote:
> Screen image with backtrace
> 
> https://pasteboard.co/dZRVG5Uo.jpg
> 
> 
> After upgrading from 318959 to 320358 I immediately get the attached panic.
> 
> This is AMD64 / GENERIC kernel.
> 
> /boot/loader.conf is empty.
> 
> The system boots off a UFS2 partition.
> 
> This is a virtual guest and I do currently have a serial cable.
> 
> Short of figuring out how to virtualize a serial console from a ESXi
> guest is
> there any more information I can provide?

Someone else hit this.  Removing the contents of /usr/obj and rebuilding
fixed it for him.  Apparently, some of the objects didn't get rebuilt,
as needed.

Eric
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


r320358 panics immediately on boot / AMD64-GENERIC kernel

2017-06-27 Thread Michael Jung

Screen image with backtrace

https://pasteboard.co/dZRVG5Uo.jpg


After upgrading from 318959 to 320358 I immediately get the attached 
panic.


This is AMD64 / GENERIC kernel.

/boot/loader.conf is empty.

The system boots off a UFS2 partition.

This is a virtual guest and I do currently have a serial cable.

Short of figuring out how to virtualize a serial console from a ESXi 
guest is

there any more information I can provide?

Thanks.

Mike
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"