Re: Amd(8) Hangs at Boot

David Wolfskill wrote:
> On Sat, Dec 29, 2012 at 09:38:42AM -0800, Cy Schubert wrote:
> > Just udated to the latest current and amd hangs at boot. Ideas?
> > ....
> 
> I don't see a problem _at_r244855. On my build machine, /usr/ports is a
> symlink to a "ports" working copy that resides on a ReadyNAS:
> 
> freebeast(10.0-C)[2] ls -F /usr/ports
> /usr/ports_at_
> freebeast(10.0-C)[3] ls -F /usr/ports/
> CHANGES accessibility/ emulators/ misc/ sysutils/
> COPYRIGHT arabic/ finance/ multimedia/ textproc/
> GIDs archivers/ french/ net/ ukrainian/
> INDEX-8 astro/ ftp/ net-im/ vietnamese/
> INDEX-8.bz2 audio/ games/ net-mgmt/ www/
> INDEX-9 benchmarks/ german/ net-p2p/ x11/
> INDEX-9.bz2 biology/ graphics/ news/ x11-clocks/
> KNOBS cad/ head/ packages/ x11-drivers/
> LEGAL chinese/ hebrew/ palm/ x11-fm/
> MOVED comms/ hungarian/ polish/ x11-fonts/
> Makefile converters/ irc/ ports-mgmt/ x11-servers/
> Mk/ databases/ japanese/ portuguese/ x11-themes/
> README deskutils/ java/ print/ x11-toolkits/
> Templates/ devel/ korean/ russian/ x11-wm/
> Tools/ distfiles/ lang/ science/
> UIDs dns/ mail/ security/
> UPDATING editors/ math/ shells/
> freebeast(10.0-C)[4] uname -a
> FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT
> #1029 r244855M/244856: Sun Dec 30 10:48:45 PST 2012
> root_at_freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386
> freebeast(10.0-C)[5] ps axwwl | grep -w amd
> 0 764 1 0 20 0 10024 10052 select Ss - 0:00.07 /usr/sbin/amd -p -c
> 1800 -k i386 -l syslog /net /etc/amd.map
> 1001 1878 964 0 23 0 10104 9916 - R+ 1 0:00.01 grep -w amd
> freebeast(10.0-C)[6]
> 
> Peace,
> david
> --
> David H. Wolfskill david_at_catwhisker.org
> Taliban: Evil men with guns afraid of truth from a 14-year old girl.
> 
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This message is basically for Cy and not David...

Since David doesn't see the problem with r244855, I'd suggest trying a
new kernel and seeing if the problem still exists. If you still see the
problem, I'd be suspicious of any recent commit done to the network
device driver for whatever network interface you are using.

Beyond that, Kostik recently pointed me at this:
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html
which covers the commands you can use under DB to try and figure out
why it is stuck in udp_bind().

You can also do the following to figure out what source line# it is
stuck at:
- go to wherever the kernel binaries are
# nm kernel | grep udp_bind
- add the offset to the address for udp_bind
# addr2line -e kernel.symbols
- type in the hex value for address + offset
--> it should give you a source line#

It never hurts to capture packets between the client and NFS server and
see if there what network traffic is occurring. If there is any traffic,
wireshark does a good job of decoding it.

Finally, there was an email w.r.t. loopback being broken, posted on Dec. 27,
but I haven't seen any followup email about this being fixed. (I don't know
if amd uses 127.0.0.1 or not?)

Good luck with it and please let us know when you have more information, rick