Re: Amd(8) Hangs at Boot

Am 12/30/12 20:41, schrieb David Wolfskill:
> 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
> 


I see a similar picture here and this AMD crap brought down my whole server.

I'm not able to install new buildworld, since I got stuck when mtree
accesses / and then the amd automounter mountpoint directory /extern is
reported

newnfs server pid767_at_telesto:/extern: not responding

I have no remote filesystems containing the sources for the OS, so I do
not understand whats going on. This is definitely a bug in the recent
system.