From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 19 11:23:42 2010 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89150106567D for ; Sat, 19 Jun 2010 11:23:42 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3D4008FC19 for ; Sat, 19 Jun 2010 11:23:41 +0000 (UTC) Received: by qyk11 with SMTP id 11so578114qyk.13 for ; Sat, 19 Jun 2010 04:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=f9VBiZapZ1UmDLyZyEfmFm0WH9Fy6Sa1GEIyj+m6J30=; b=RMuICKayF04hEyWt5CEqK07m5CEEgE2SHtWJs5taV+LwEjTEcG4W18cqR3Jh5IGEj0 sNDbiC16NlWlR741O4pQPTf/aSrScr8eRWfh9xoBZezCAZeeAy/ImuCgwPyMV1RYQ3Pe 15IwDq8k+CZT+1hetnDgDT5hipzl3w7fwzgGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=cEAFIdEaP0ryM8CuVnlCorODNSTpL2I8qFn0PUQ9fjtBoilGNYJMKB6L96q0F8ttmt hbzILXx5HFdA5y67hSacOmA+7ZJHUSnFh8guUVLsmFw8wHCHnJHx83FN4kWnc0pAqIy/ 0mt8ML+lrMl+tm/4a6kOkYSA5QLflBYUXKf2g= MIME-Version: 1.0 Received: by 10.224.53.135 with SMTP id m7mr1522769qag.380.1276946621128; Sat, 19 Jun 2010 04:23:41 -0700 (PDT) Received: by 10.229.80.75 with HTTP; Sat, 19 Jun 2010 04:23:41 -0700 (PDT) In-Reply-To: <201006190800.o5J80AO8079952@freefall.freebsd.org> References: <201006190800.o5J80AO8079952@freefall.freebsd.org> Date: Sat, 19 Jun 2010 04:23:41 -0700 Message-ID: From: Garrett Cooper To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/147926: system freezes due to heavy io to the disks X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jun 2010 11:23:42 -0000 On Sat, Jun 19, 2010 at 1:00 AM, Andriy Gapon wrote: > The following reply was made to PR amd64/147926; it has been noted by GNA= TS. > > From: Andriy Gapon > To: Dominic Duklas > Cc: bug-followup@FreeBSD.org > Subject: Re: amd64/147926: system freezes due to heavy io to the disks > Date: Sat, 19 Jun 2010 10:55:22 +0300 > > =A0on 17/06/2010 03:36 Dominic Duklas said the following: > =A0>> Number: =A0 =A0 =A0 =A0 147926 > =A0>> Category: =A0 =A0 =A0 amd64 > =A0>> Synopsis: =A0 =A0 =A0 system freezes due to heavy io to the disks > =A0>> Confidential: =A0 no > =A0>> Severity: =A0 =A0 =A0 non-critical > =A0>> Priority: =A0 =A0 =A0 low > =A0>> Responsible: =A0 =A0freebsd-amd64 > =A0>> State: =A0 =A0 =A0 =A0 =A0open > =A0>> Quarter: > =A0>> Keywords: > =A0>> Date-Required: > =A0>> Class: =A0 =A0 =A0 =A0 =A0sw-bug > =A0>> Submitter-Id: =A0 current-users > =A0>> Arrival-Date: =A0 Thu Jun 17 00:40:00 UTC 2010 > =A0>> Closed-Date: > =A0>> Last-Modified: > =A0>> Originator: =A0 =A0 Dominic Duklas > =A0>> Release: =A0 =A0 =A0 =A09.0-CURRENT > =A0>> Organization: > =A0>> Environment: > =A0> FreeBSD lain 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r209225: Wed Jun 16 = 01:47:01 BST 2010 root@lain:/usr/obj/usr/src/sys/LAIN amd64 > =A0> > =A0>> Description: > =A0> I'm currently running freebsd on my desktop (core i7 920, 6gb of ram= ). Since around January I'm having problems with the system freezing for sh= ort periods of time and eventually locking up due to heavy reads/writes to = the disk. > =A0> The cursor would freeze for a split second and songs in my music pla= yer (quodlibet) would skip completely (the error logs say that the music pl= ayer was unable to access the song which was currently playing, even though= my music collection is on a completely different hard drive than the os). > =A0> After 10-20 minutes of the occasional freezes (the frequency is rand= om, sometimes it can go without any freeze for some minutes or it can freez= e many times in a short period of time) the system locks up completely and = reboots itself. There is no crash dump produced by the kernel, nor anything= shows in dmesg when the short freezes occur. > =A0> I tried putting freebsd on a different hard drive, changing filesyst= ems from zfs which I currently use to ufs but the issue doesn't go away. > =A0> Today I tried using the geom rr sched which was recently committed t= o current to see whether it would make a difference, but it didn't help. > =A0> This issue is not related to swapping as ram usage never gets high e= nough, and is also not directly caused by heavy cpu usage, although it migh= t be part of the problem. > =A0> I've done several clean installs of freebsd current since the issue = first appeared. > =A0>> How-To-Repeat: > =A0> make -j8 buildworld would trigger it in my case, or 2 simultaneous w= hile loops with extracting a large file archive or compiling something big = like openoffice/gcc/boost from ports. > =A0>> Fix: > > =A0You haven't let us know some important details. > =A0What disk controller do you have? > =A0What driver do you use for it (if there are multiple choices)? > > =A0P.S. Why did you file this bug under amd64 category? =A0Have you teste= d how i386 > =A0version of FreeBSD works on the same machine and came to conclusion th= at it's > =A0only amd64 version that is affected? Disk controllers would be helpful, but a full kldstat -v would suffice as there might be some other GIANT locked drivers (like nvidia-driver) causing issues. I say this because I do see a sporadic performance hit with concurrent accesses via UFS2+SU when transferring files and compiling applications using an ada(4) enabled setup, plus mfi(4), but that is apart from the issue, but that is primarily because UFS2 is giant locked within itself and the fact that there's other contention arising from me running GUI applications like Firefox on my machine. Andriy is correct though... we need more details as to what you're running on the machine driver wise, your machine's stats, and/or a mean number of running processes, threads, etc. If we don't have that kind of data we can't possibly triage the issue and make a recommendation on how you should improve your machine's hardware topology and/or software config. Thanks, -Garrett