From owner-freebsd-stable Sat Dec 22 10: 7:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jkkn.jkkn.net (cpe.atm2-0-1031198.0x503eea76.odnxx2.customer.tele.dk [80.62.234.118]) by hub.freebsd.org (Postfix) with ESMTP id 14D1537B416 for ; Sat, 22 Dec 2001 10:07:50 -0800 (PST) Received: from jkkn (ns1.jkkn.net [80.62.234.118]) (authenticated) by jkkn.jkkn.net (8.11.6/8.11.6) with ESMTP id fBMI7Lu43667; Sat, 22 Dec 2001 19:07:21 +0100 (CET) (envelope-from jkkn@jkkn.dk) From: "Kristian K. Nielsen" To: "'Matthew Dillon'" Cc: , , , , , Subject: RE: RE: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers Date: Sat, 22 Dec 2001 19:07:22 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <200112221714.fBMHEX195032@apollo.backplane.com> Importance: Normal Disposition-Notification-To: "Kristian K. Nielsen" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, Thanks for the quick responds. I am not sure that it IS the ata-driver, but it is typically accouring for people using this driver. Maybe it uses vm or kernel in a speciel heavy way that trickers the bug?! I have tried with and without softupdates - there does not seem to be any major difference. Still crashing doing high io/cpu. "clean; make buildworld" in a loop will crash my box as well within 3-6 hours. An other way of trickering the crash is to move a large positions of files and data from one IDE harddrive to another - that nearly always causes that crash as well. I have read one state that he upgraded to -current and that fixed the bug? - do you know if anybody have any overview of what type of issues or things that have implemented in -current that could be possible to move to -stable to fix this issue? Regards, Kristian > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: 22. december 2001 18:15 > To: Kristian K. Nielsen > Cc: bradym@mail.hydrologue.com; peter.jeremy@alcatel.com.au; > davidc@acns.ab.ca; rnyberg@it.su.se; david@catwhisker.org; > freebsd-stable@FreeBSD.ORG > Subject: Re: RE: 4.4-STABLE crashes - suspects new ata-driver > over wd-drivers > > > :I did in the bug report at: > :http://www.freebsd.org/cgi/query-pr.cgi?pr=31233 > : > :Is that enough information? > : > :/Kristian > > Yah. I've been analyzing the thread and focusing on Brady's > kernel cores to try to track this down, but it's tough going. > This is what I see so far: > > * Cpu does not appear to matter (P3, P4, and AMD have > been indicated) > * All machines are doing heavy IDE I/O > * All machines are running the new ATA drivers > * DMA vs PIO does not seem to matter > * All or most machines appear to be running softupdates ?? > * None of the disk activity is over SCSI > * VM system is not necessarily being stressed, just the disks. > > I would like you to turn off softupdates if you have it on and > see if that makes a difference. > > I do not know whether the problem is the ATA driver or whether it > is simply a side effect - for example, heavy disk I/O creating > backlogs and delays that are causing another bug to rear its ugly > head. > > So far I haven't been able to track down the cause - the problem > appears to be random corruption. Each of Brady's three > kernel cores > are corrupted in different places - Most typically different > portions of the vm_page_array[] which is the absolute > *last* thing I > would every expect to get corrupted considering their > static, fixed > ram. > > The only bug I know about that could have an effect is the > BUF_TIMELOCK bug which I fixed two days go in -current (not yet > in stable), but a number of people have already reported > -current working prior to the fix. Of course, the timing is > very different in -current so that might not matter. Longer > IDE delays could cause this bug to rear its ugly head but it's > a long shot. I am pursuing this with Brady since he seems to be > able to reliably reproduce the crash. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message