Date: Wed, 26 Jul 2006 20:09:26 -0700 From: "Rob Connon (Info)" <rob.info@vfs.com> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6 Hard Lock no logs Message-ID: <44C82E66.8070405@vfs.com> In-Reply-To: <44lkqgpo1u.fsf@be-well.ilk.org> References: <44C660AF.5040206@vfs.com> <44lkqgpo1u.fsf@be-well.ilk.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] HI, The system completly locks up, attached keyboard is useless.. and as mentioned no errors.. the only pattern is tuesday/wednesday it freezes.. other days of the week it's fine under heavy load.. buildworlds are not a problem.. Rob. Lowell Gilbert wrote: >"Rob Connon (Info)" <rob.info@vfs.com> writes: > > > >>Hi, >> >>I have a web/mail server thats running the lastest version of FreeBSD >>6.0-RELEASE-p9 #4. In the last month or so it's started hard locking.. >>when the machine locks up i can still ping it and get connects from >>telneting to 80,22,etc sometimes i get a banner and sometimes i >>dont.. but there are >>no errors on the console or in the logs. >> >>The odd thing is the locking seems to happen within a certain time >>window (mon,tues) and never end of the week or weekend.. i suspected >>it could have been >>a bad cron job but nothing falls into that time frame. >> >>As a test i've been rebooting the server everynight to see if that >>would help the machine get past the begining of the week with out a >>hang and again this morning >>even though i rebooted last night at 10pm hung around 9:47am. >> >>The machine is a Dell PowerEdge 2550, I've had dell come and replace >>the MB and have ran all their diagnostics aswell with no errors >>reported.. >>I've been reading alot about APIC and ACPI and people having similar >>issues but nothing that fits the bill... below is the dmesg and output >>of vmstat -i.. another odd thing is the rate for the CPU timer is >>extremely high compared to other machines with similar hardware or >>faster hardware. >> >>Any help on where to look next would be awesome. >> >> > >Try a debugging kernel and see if you can break to the debugger after >the freeze. If so, youcan look at task states. >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > [-- Attachment #2 --] 0 *H 010 + 0 *H 0I00 *H 0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 051020181657Z 061020181657Z0B10UThawte Freemail Member10 *H rob.info@vfs.com00 *H 0 bkN<d5f1{f5#ju{ wmz# 4(PyURpHp27c<ȳ0?P!~ ïot"O( -0+0U0rob.info@vfs.com0U0 0 *H zD4$#/o5%HAu% 'GW_͟1!X}:nB!Z?m;to/QQsla70I00 *H 0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 051020181657Z 061020181657Z0B10UThawte Freemail Member10 *H rob.info@vfs.com00 *H 0 bkN<d5f1{f5#ju{ wmz# 4(PyURpHp27c<ȳ0?P!~ ïot"O( -0+0U0rob.info@vfs.com0U0 0 *H zD4$#/o5%HAu% 'GW_͟1!X}:nB!Z?m;to/QQsla70?0 0 *H 010 UZA10UWestern Cape10U Cape Town10U Thawte Consulting1(0&UCertification Services Division1$0"UThawte Personal Freemail CA1+0) *H personal-freemail@thawte.com0 030717000000Z 130716235959Z0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00 *H 0 Ħ<UsUNʙZhup[v:aQP 0cZ,p+Z?qV˯<6$*+w=+>@dקe*TH<a@dr` 00U0 0CU<0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0U0)U"0 010UPrivateLabel2-1380 *H HP. fgCL!6-6/P p<ab:~ t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$F]_eO100i0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 + 0 *H 1 *H 0 *H 1 060727030926Z0# *H 1b?:`Zc؛-R^ 0R *H 1E0C0 *H 0*H 0 *H @0+0 *H (0x +71k0i0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0z*H 1ki0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 *H %ALJ ؕe6!۸}w e{( E98#~7t3X283r'V > "\/1hv4-4|#ǯ6[$Thome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C82E66.8070405>
