From owner-freebsd-stable Mon Jul 26 14:13:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f261.hotmail.com [207.82.251.152]) by hub.freebsd.org (Postfix) with SMTP id 0FCB814CFB for ; Mon, 26 Jul 1999 14:13:47 -0700 (PDT) (envelope-from showboat@hotmail.com) Received: (qmail 56446 invoked by uid 0); 26 Jul 1999 21:12:15 -0000 Message-ID: <19990726211215.56445.qmail@hotmail.com> Received: from 207.202.146.16 by www.hotmail.com with HTTP; Mon, 26 Jul 1999 14:12:14 PDT X-Originating-IP: [207.202.146.16] From: "Show Boat" To: freebsd-stable@FreeBSD.ORG Subject: Re: repeated mysql oriented crashes Date: Mon, 26 Jul 1999 14:12:14 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We upgraded the uthreads as recommended, but to no avail. :( It appears that the on screen console errors (before the mandatory hard reboot) haven't been the same every time. This time (according to the TECH at our ISP) the screen was full of scrolling 'busy count' and 'pack count' errors. It was scrolling too quickly for him to make out more, but he did mention da0. I'm beginning to question the RAID system. Even though all crashes have been directly linked to mysql queries, the onscreen errors seem to always refer to da0. (running a DPT PM3334UW/2) I can't find any indications that the DPT drivers have been upgraded. I'm banging my head against a wall here. Any suggestions (other than finding a softer wall) would be really appreciated. Thanks, Jeremy >From: Ludwig Pummer >To: "Show Boat" >CC: freebsd-stable@FreeBSD.ORG >Subject: Re: repeated mysql oriented crashes >Date: Tue, 20 Jul 1999 22:13:18 -0700 > >At 06:01 PM 7/20/1999 -0700, Show Boat wrote: >>Some hunting and searching has led us to believe that we are encountering >>a driver failure and that we should bring the OS back to -stable. >> >>As I said, I haven't done this before, so I'm a little anxious. Before I >>take that step, I would be very greatful to hear some input from those who >>surely know more about this than I do. >> >>Is bringing the system back to -stable likely to correct our problem? Am >>I missing some indicator in the error above? Has someone else >>encountered similar trouble (and found a fix?) > >I don't know if bringing it to -stable would fix your driver problem. I do >remember the odd message on one of the lists regarding problems with the >DPT driver. > >However, I _do_ know that FreeBSD 3.1-Stable sometime after May 14 (that >was the last make world I did on a production server before hearing rumors >of the pthreads breakage) has broken pthreads support, meaning that if you >want to run mysql with native pthreads, it will crash. I don't know if this >has been fixed in -stable since it was last brought up in this list (end of >June/early July). A fixed pthreads library is available at >ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz , if it hasn't been >fixed in -stable yet. Your 2 options (if -stable's pthreads hasn't been >fixed yet) are to either use MIT pthreads (included with mysql) or use the >fixed pthreads tarball listed above. > >--Ludwig Pummer > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message