> 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. randyReceived on Tue Oct 19 2004 - 20:43:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC