On Wed, 2003-02-05 at 21:03, Peter Kostouros wrote: > Hi > > I experienced the problem with kernels from last weekend. I rebuilt > yesterday, but have not undergone high loads since. I will do thorough tests > over the weekend. > > Keep in mind there have been some complaints recently, and there is new > scheduler code just implemented, so I guess at that at the moment CURRENT is > a place for the brave, well, braver than most. > > -----Original Message----- > From: Muhannad Asfour [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 6 February 2003 12:40 PM > To: Peter Kostouros > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: Server locking hard -- A LOT!!! > > > On Wed, 2003-02-05 at 20:03, Peter Kostouros wrote: > > Not sure this is much help, but I have been getting many hard locks too, > > from about a kernel I built around the 27th January. My symptoms are that > > under a relatively heavy CPU load, upon invoking or terminating an > > application, the machine occasionally terminates (abruptly). I do not even > > get core dumps. > > > > -----Original Message----- > > From: Muhannad Asfour [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, 6 February 2003 11:27 AM > > To: Peter Kostouros > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: Server locking hard -- A LOT!!! > > > > > > On Wed, 2003-02-05 at 19:23, Peter Kostouros wrote: > > > Hi Muhannad > > > > > > Your dmesg output had the following: > > > lock order reversal 1st 0xc2b5d230 process lock (process lock) @ > > > ../../../kern/kern_descrip.c:2104 > > > 2nd 0xc2b5bd34 filedesc structure (filedesc structure) @ > > > ../../../kern/kern_descrip.c:2111 > > > > > > These are indicative of the lock order reversals appearing recently. Do > > you > > > always get these? > > > > > > Regards > > > > > > Peter > > > > > > This e-mail and any attachment(s) is intended for the party to which it > is > > > addressed and may contain confidential information or be subject to > > > professional privilege. Its transmission in not intended to place the > > > contents into the public domain. If you have received this e-mail in > > error, > > > please notify us immediately and delete the email and all copies. > > > AWTA Ltd does not warrant that this e-mail is virus or error free. By > > > opening this e-mail and any attachment the user assumes all > responsibility > > > for any loss or damage resulting from such action, whether or not caused > > by > > > the negligence of AWTA Ltd. > > > The contents of this e-mail and any attachments are subject to copyright > > and > > > may not be reproduced, adapted or transmitted without the prior written > > > permission of the copyright owner. > > > > Yes, I always get these. > I am experiencing the same exact thing. Odd. Any idea if it still > occurs with a more recently built kernel?
I've felt like I tried everything so far, and I cannot figure out what the problem is, I've done numerous hardware tests, and every single one was passed with flying colours. I have narrowed it down to apache locking the box though. So I'm not sure what I can do to fix this, because it is very tedious to have to keep manually rebooting the box everytime it locks (sometimes 3 times a day!) Can anyone please suggest something to fix this issue? If any of the developers read this, I can give you ssh to the box if required so you can see what's happening. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message