Date: Tue, 19 Oct 2004 15:43:32 -0700 From: Randy Bush <randy@psg.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: multi-user startup failure Pre-seeding PRNG: Message-ID: <16757.39060.602700.402490@ran.psg.com> References: <16757.28156.361400.647815@ran.psg.com> <20041019212148.GB93330@xor.obsecurity.org> <16757.35688.795976.719745@ran.psg.com> <20041019215625.GE83510@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Does it really lock up, or does sysctl just not return? Can you > hit ^C? it really locks up solid. while i can hit ^C, it has no effect:-). > Does ^T print anything? nope > Can you break into the debugger via Ctrl-Alt-ESC? nope > After you comment them out, does "sysctl -a" lock the system if > you run it after the system boots up? while in single-user, sysctl -a prints up to kern.diska: ad0 and then locks. no response to ^C <ctl><alt><esc>, ^T ... in multi-user, sysctl -a locks up after printing "net.inet.tcp.isn_reseed_interval: 0" > Something to try might be to change the script to run "truss > sysctl -a" easier to just run it manually, yes? and the result is at <http://rip.psg.com/~randy/041019.sysctl-lockup/>; run twice, it does not stop at the same place. a possible hint: when shutting down this host, it hangs at Stopping ACPI. this is also a revert. randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16757.39060.602700.402490>