From owner-freebsd-stable@freebsd.org Sun Jul 12 09:42:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44109998380 for ; Sun, 12 Jul 2015 09:42:00 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD277894; Sun, 12 Jul 2015 09:41:59 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by lbbpo10 with SMTP id po10so110855821lbb.3; Sun, 12 Jul 2015 02:41:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=/OtBRNYX7R8k0AI9sLEfKjdHr1i3VSF/c0L3kZzubTw=; b=fH0n/E/6cW3X8HMmaxOVa09BESlFZuwptQiMcoy5CkOnSajwgeOOHSvPcntCFkXbVw dd/j15bchYqP2W2KwPAhZzVPAjmokh3vErDDpK+Oo4KCm2YEnDFj+8Z3NPa2I4yLS3/d VpfgbAwBEUa87G3raZ4Bc4ytbzHxVWMOo4bHH6EgwlkRSyiF2Bhe2w725qiZ8UjIh0Es IaYS6vpUcFoDbAnjymPW9AuDTEJkzv9YCSxmPtyygffJldCmzeLnYcrbYWjYwdTfsKFc /DTd4WwJJn5/dK44wSUuHumJCymCSwKCK19Gq+PDU2brVVM3ComAaGRjovzQ/qKKVc53 eFcw== X-Received: by 10.112.126.101 with SMTP id mx5mr27887688lbb.35.1436694117820; Sun, 12 Jul 2015 02:41:57 -0700 (PDT) Received: from brick ([46.229.149.194]) by smtp.gmail.com with ESMTPSA id w8sm3731598lal.38.2015.07.12.02.41.56 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Jul 2015 02:41:56 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Sun, 12 Jul 2015 11:41:53 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Harald Schmalzbauer Cc: freebsd-stable@freebsd.org, kib@freebsd.org Subject: Re: r284665 causes MSI problems -> ahcich2: Timeout in slot 11 port 0 Message-ID: <20150712094153.GA1549@brick> Mail-Followup-To: Harald Schmalzbauer , freebsd-stable@freebsd.org, kib@freebsd.org References: <55A158E1.3000905@omnilan.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55A158E1.3000905@omnilan.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 09:42:00 -0000 On 0711T1956, Harald Schmalzbauer wrote: > Hello, > > r284665 causes ahci(4) to fail with timeouts when using MSI (the default). What's the hardware? > 'hint.ahci.0.msi=0' is one way to make ahci(4) working with r284665, but > obviously not the desired solution, it just disables usage of an MSI. > > I can't find suspicious code in r282213 which could cause this strange > regression, but I verified carefully that problem arises with r284665. > Actually, r282901 > (https://svnweb.freebsd.org/base?view=revision&sortby=date&revision=282901) > is the real trigger, verified by putting > nooptions RACCT > nooptions RACCT_DEFAULT_TO_DISABLED > nooptions RCTL > into my kernel config -> problem vanishes! > > Setting "kern.racct.enable=1" doesn't make any difference, as soon as > 'kern.features.racct' exists, there's the ahci(4)/ahcich2 timeout and > machine doesn't finish booting. > > Unfortunately, I don't have any idea how to track this down to the > actual culprit, but I hope the RACCT hackers do have ;-) > > Shall I open a bugzilla ticket? That's... curious. I don't see how those two things could be related. What's the FreeBSD version? How reproducible it is? Have you tried compiling with and without those three lines a couple of times?