Date: Fri, 01 Nov 2013 17:48:54 +0100 From: Torbjorn Granlund <tg@gmplib.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/183397: Kernel panic at first incoming ssh Message-ID: <86y558ysnd.fsf@shell.gmplib.org> In-Reply-To: <201311010921.57769.jhb@freebsd.org> (John Baldwin's message of "Fri\, 1 Nov 2013 09\:21\:57 -0400") References: <201310312350.r9VNo1gE056086@freefall.freebsd.org> <201311010921.57769.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@freebsd.org> writes:
Can you fire up gdb against your 64-bit kernel file (e.g. gdb=20
/boot/kernel/kernel) and do 'l *xn_intr+0x7d'?
I'm afraid my ignorance of how to debug the kernel will show itself
here.
I did this:
1. booted the system.
2. logged in as root on the (vnc) console.
3. issued the command "gdb /boot/kernel/kernel"
4. Issued the above command and got this printout:
(gdb) l *xn_intr+0x7d
0xffffffff8079fb7d is in xn_intr (atomic.h:161).
156 atomic.h: No such file ot directory.
in atomic.h
(gdb)
This looks somewhat unsatisfactory to me...
If it would be beneficial to the freebsd project, I could bring this
NetBSD+Xen Haswell system to a public IP address and set up a temp
account. I'd then would like a public ssh key which I can download from
*.freebsd.org. But if that is not convenient for you, I'll certainly
follow through with any tests you will ask me to perform.
--=20
Torbj=C3=B6rn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y558ysnd.fsf>