Date: Fri, 25 May 2001 11:08:30 -0700 From: "Steve Brown" <steve@napanet.net> To: "Thomas T. Veldhouse" <veldy@veldy.net>, "Michael Tang Helmeste" <glassfish@frogbox.dyndns.org>, <freebsd-security@freebsd.org> Subject: RE: Qmail + FreeBSD 4.3 Message-ID: <027f01c0e545$b4407080$3da2169d@napanet.net> In-Reply-To: <019b01c0e2fe$eb384d40$3028680a@tgt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Same here, I have found that random sig 11's are often caused by memory or CPU problems. One thing to try is underclocking - if you are running 133 underclock to 100 Steve > -----Original Message----- > From: owner-freebsd-security@FreeBSD.ORG > [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Thomas T. > Veldhouse > Sent: Tuesday, May 22, 2001 1:37 PM > To: Michael Tang Helmeste; freebsd-security@freebsd.org > Subject: Re: Qmail + FreeBSD 4.3 > > > Swap memory and see. I had the same problem (different program). Apache > kept dying was my first symptom. Then postfix died occassionally. MySQL > dumped when used. A few things like that. It started happening > on a system > that had been working for the better part of a year. It was the CPU. > > Sig 11 more often than not is a hardware problem. There is only > one case I > know of that I can reproducibly create a sig 11 when it is not > hardware. If > you run ncftp3 against a server and download a large directory using the > "tar on the fly option", it will often dump core. This could be the case > with qmail, but I have not seen it reported, thus I think he should check > his hardware. > > Tom Veldhouse > > ----- Original Message ----- > From: "Michael Tang Helmeste" <glassfish@glassfish.net> > To: "Thomas T. Veldhouse" <veldy@veldy.net>; > <freebsd-security@freebsd.org> > Sent: Tuesday, May 22, 2001 3:31 PM > Subject: RE: Qmail + FreeBSD 4.3 > > > > Well bad hardware is less likely than its trying to overwrite memory it > > doesn't own. If he is being attacked, and it is a buffer > overflow exploit, > > than overwriting memory it doesn't own is more likely than it being > > repeatidly hardware, especially after his system has been > working fine all > > this time. > > > > -----Original Message----- > > From: Thomas T. Veldhouse [mailto:veldy@veldy.net] > > Sent: Tuesday, May 22, 2001 9:16 AM > > To: Michael Tang Helmeste > > Subject: Re: Qmail + FreeBSD 4.3 > > > > > > Signal 11 (and often10) very often signal bad hardware. Memory > and/or CPU > > are usually the cause, followed by the main board. Corruption occurs in > > memory and a signal 11 results. > > > > Tom Veldhouse > > veldy@veldy.net > > > > ----- Original Message ----- > > From: "Michael Tang Helmeste" <glassfish@glassfish.net> > > To: <freebsd-security@freebsd.org> > > Sent: Monday, May 21, 2001 8:35 PM > > Subject: RE: Qmail + FreeBSD 4.3 > > > > > > > actually it just means segmentation fault > > > > > > it happens when a program accesses some memory that it doesn't own > > > > > > -----Original Message----- > > > From: owner-freebsd-security@FreeBSD.ORG > > > [mailto:owner-freebsd-security@FreeBSD.ORG]On Behalf Of Olivier Nicole > > > Sent: Monday, May 21, 2001 9:17 PM > > > To: subscribed@de-net.org > > > Cc: freebsd-security@FreeBSD.ORG > > > Subject: Re: Qmail + FreeBSD 4.3 > > > > > > > > > Hi Dan, > > > > > > Signa 11 often denotes some hardware problem I guess, something like > > > overheating. > > > > > > Olivier > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-security" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-security" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?027f01c0e545$b4407080$3da2169d>