Yup, it was I/O problem.  I couldn't find anything in the log, so I decided to 
go to data center and take a look.  Kernel panic messages were on the screen:

panic: ffs_alloccg: map corrupted
Fatal trap 12: page fault while in kernel mode
fault code:    = supervisor write, page not present

Upon inspection, I found out that it had seagate 1tb hard drive with known 
firmware issue.  Replaced the drive and it looks OK so far.  Hopefully that was 

Thanks for the help!


----- Original Message ----
From: Mel <fbsd.questi...@rachie.is-a-geek.net>
To: freebsd-questions@freebsd.org
Cc: joe park <hjj...@yahoo.com>
Sent: Thursday, January 29, 2009 2:53:47 PM
Subject: Re: ssh login problem

On Thursday 29 January 2009 12:48:03 joe park wrote:

> $ ssh -vvv us...@
> OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.8e 23 Feb 2007
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to [] port 22.
> debug1: Connection established.
> debug1: identity file /home/user1/.ssh/identity type -1
> debug1: identity file /home/user1/.ssh/id_rsa type -1
> debug1: identity file /home/user1/.ssh/id_dsa type -1
> It just waits infinitely at this point.  There is no other way to access
> and troubleshoot the machine B remotely (telnet is not enabled) and only
> thing I can do is call and ask for hard reset.

I/O problems on B. Disk blocks all processes needing it. Console login would 
not work either. grep TIMEOUT /var/log/messages on B should provide some 


Problem with today's modular software: they start with the modules
    and never get to the software part.

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to