Hi, On Sun, 22.11.2009 at 23:03:10 +0100, Joachim Schipper <joac...@joachimschipper.nl> wrote: > On Sun, Nov 22, 2009 at 10:00:05PM +0100, Peter J. Philipp wrote: > > On Sun, Nov 22, 2009 at 09:20:46PM +0100, Toni Mueller wrote: > > > for several releases of OpenBSD, I now have encountered the problem > > > that I can say "shutdown -r now", or "halt", or "reboot", and nothing > > > appears to happen, except for some messages on the associated > > > terminals. > > > > > > Sometimes, it works after saying it multiple times, and literally after > > > minutes, and on otherwise idle boxen. > > > > I had something like this on vmware when switching from workstation 6 to > > workstation 7. Basically what happened was that vic1 (second ethernet) was > > left in "no carrier" state on a vmnet that didn't exist. When I finally > > noticed it and made a proper vmnet for it, the reboot or halt problem went > > away. > > > > Perhaps you have an interface in "no carrier" state? > > That alone isn't enough - I frequently halt my laptop with no network > cable attached (to re0), and never noticed any particularly long waits.
I forgot to say that I was only talking about real hardware machines, not virtual machines. On the machine I saw it last, there are two bge(4) and two em(4) interfaces, and they are all active (HP G380 or so). I also forgot to specify what "long" means. It means that there can easily be 5-15 minutes before the actual shutdown appears to finally trigger, but since I have my shell back in the meantime, and thus tried to issue the command several times in a row (usually, issuing the shutdown command immediately renders the shell unresponsive), I can't say which invocation actually did the trick. This is especially discomforting when already running on UPS battery and/or working with remote systems... TIA! -- Kind regards, --Toni++
