Date: Wed, 20 Jun 2001 09:05:42 +0300 From: Odhiambo Washington <wash@wananchi.com> To: FBSD-Q <freebsd-questions@FreeBSD.org> Subject: Re: How to troubleshoot freezing? Message-ID: <20010620090542.D29279@everest.wananchi.com> In-Reply-To: <3B2FE5CF.8ED52928@iowna.com>; from "Bill Moran" on Tue, Jun 19, 2001 at 07:52:47PM -0400 References: <20010619164732.D680-100000@zoraida.reyes.somos.net> <3B2FE5CF.8ED52928@iowna.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--jho1yZJdad60DJr+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Bill Moran <wmoran@iowna.com> [20010620 02:54]: writing on the subject 'R= e: How to troubleshoot freezing?' Bill> Francisco Reyes wrote: Bill>=20 Bill> > Something may have gotten corrupted with the HD during all the prob= lems. Bill> > Now I am getting: Bill> >=20 Bill> > ad0s1f: UDMA ICRC error reading fsbn 35802032 of 16724440-16724503 Bill> > (ad0s1 bn 35802032; cn 7103 tn 46 sn 14) retrying Bill> >=20 Bill> > ad0s1f: UDMA ICRC error reading fsbn 35802032 of 16724440-16724503 Bill> > (ad0s1 bn 35802032; cn 7103 tn 46 sn 14) retrying Bill> >=20 Bill> > ad0s1f: UDMA ICRC error reading fsbn 35802032 of 16724440-16724503 Bill> > (ad0s1 bn 35802032; cn 7103 tn 46 sn 14) retrying Bill> >=20 Bill> > ad0s1f: UDMA ICRC error reading fsbn 35802032 of 16724440-16724503 Bill> > (ad0s1 bn 35802032; cn 7103 tn 46 sn 14) falling back to PIO mode Bill>=20 Bill> This looks like something with the ata driver ... since it's dropping Bill> out of DMA mode into PIO. Waht does "sysctl hw.atamodes" reveal? If t= he Bill> mode for the HDD is PIO, you may have an incorrect cable. Bill>=20 Please allow me to join the thread with my own version of freezing ;-) I have an Intel box, 450MHz, SMP, 128MB RAM which also gives a funny 'freeze'. I don't have a keyb and monitor onto this rack-mounted box. I only connect to it via ssh.=20 What happens is that ocassionally (more often) it would freeze for a minute or so. I wouldn't be able to do a thing on it but from another vty on the machine I am using to ssh to it, I can ping it and get responses. How do I go about diagnostics for such a "lock"? Is there an application I can use to monitor the system and report a reason for the "lock" in some log file? I've checked the logs but no clue. All pointers would be highly appreciated. MTIA -Wash -- Odhiambo Washington Wananchi Online Ltd., wash@wananchi.com 1st Flr Loita Hse. Tel: 254 2 313985 Loita Street., Fax: 254 2 313922 PO Box 10286,00100-NAIROBI,KE. To do good things in the world, first you must know who you are and what gi= ves=20 meaning to your life.=20 -Paula P. Brownlee=20 --jho1yZJdad60DJr+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7MD02n7LIsuxjem8RAjdwAJ4xCUam+Q4C2MrK2bVtOJRK28SnTACfU/JZ GZi+SLWvx2WrH7a4o6TmNko= =OXH5 -----END PGP SIGNATURE----- --jho1yZJdad60DJr+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010620090542.D29279>