Date: Sun, 12 Jul 2015 11:41:53 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@freebsd.org> To: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> 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> In-Reply-To: <55A158E1.3000905@omnilan.de> References: <55A158E1.3000905@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150712094153.GA1549>