Re: Machine is 'hanging'.
On Mon, 28 Feb 2000, Dave J. Boers wrote: > It is rumoured that Stefan Schmidt had the courage to say: > > i have got a problem with a router running FreeBSD 3.4-REL: > > Every three days or so it hangs, whiche means that the console is not > > responding any more, open tcp ports don't respond == are timing-out just > > like they're filtered. I guess the machine is just unable to start a > > shell. Oh and well it is appearently able to route as the machines behind > > it are reachable, and it does repond to pings. > Are you by any chance running SMP? I am having very similar problems with > -current (time to die is approx 10 days) on a box which does firewalling > and nat. erm, no not really , it is a 486 dunno how fast actually but somewhere over 100Mhz with PCI-Bus, two NICs on the PCI and one 10mbit card on the ISA-Bus for outgoing traffic. It does some firewalling, stealth-forwarding and softupdates. > And by the way, I do have DDB in my kernel, but the hang is really hard. > The box just freezes and there's no way to get to the debugger. Even serial > console is dead. dito, i mean i didn't compile DDB into the kernel but all consoles are dead. Stefan Schmidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Machine is 'hanging'.
It is rumoured that Stefan Schmidt had the courage to say: > i have got a problem with a router running FreeBSD 3.4-REL: > Every three days or so it hangs, whiche means that the console is not > responding any more, open tcp ports don't respond == are timing-out just > like they're filtered. I guess the machine is just unable to start a > shell. Oh and well it is appearently able to route as the machines behind > it are reachable, and it does repond to pings. Are you by any chance running SMP? I am having very similar problems with -current (time to die is approx 10 days) on a box which does firewalling and nat. And by the way, I do have DDB in my kernel, but the hang is really hard. The box just freezes and there's no way to get to the debugger. Even serial console is dead. Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Machine is 'hanging'.
:hi there, :i have got a problem with a router running FreeBSD 3.4-REL: :Every three days or so it hangs, whiche means that the console is not :responding any more, open tcp ports don't respond == are timing-out just :like they're filtered. I guess the machine is just unable to start a :shell. Oh and well it is appearently able to route as the machines behind :it are reachable, and it does repond to pings. :Which brings me to my question: :okay this sounds like a hardware problem, but what could it be, the board :, the memory. If anyone here has seen something similar i'd be glad if you :could help me. : :regards, : Stefan Schmidt Sounds like a kernel bug to me. If you can compile and install a kernel with DDB enabled, you should be able to ctl-alt-esc it on the console when it hangs, then from the DDB prompt do a 'trace' command and a 'ps' command and maybe we can figure out why it hung from that. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Machine is 'hanging'.
hi there, i have got a problem with a router running FreeBSD 3.4-REL: Every three days or so it hangs, whiche means that the console is not responding any more, open tcp ports don't respond == are timing-out just like they're filtered. I guess the machine is just unable to start a shell. Oh and well it is appearently able to route as the machines behind it are reachable, and it does repond to pings. Which brings me to my question: okay this sounds like a hardware problem, but what could it be, the board , the memory. If anyone here has seen something similar i'd be glad if you could help me. regards, Stefan Schmidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
