Date: Sun, 12 Jul 2015 11:59:17 +0200 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= <trasz@freebsd.org>, FreeBSD Stable <freebsd-stable@freebsd.org>, kib@freebsd.org Subject: Re: r284665 causes MSI problems -> ahcich2: Timeout in slot 11 port 0 Message-ID: <55A23A75.8050003@omnilan.de> In-Reply-To: <20150712094153.GA1549@brick> References: <55A158E1.3000905@omnilan.de> <20150712094153.GA1549@brick>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4C2550AF81F2E20B268F139D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bez=C3=BCglich Edward Tomasz Napiera=C5=82a's Nachricht vom 12.07.2015 1= 1:41 (localtime): > On 0711T1956, Harald Schmalzbauer wrote: >> Hello, >> >> r284665 causes ahci(4) to fail with timeouts when using MSI (the defau= lt). > What's the hardware? Thanks for your attention, it's Intel Cougar Point (C204, 2x SATA6G+4xSATAII), via PCIe-Passthrough in an ESXi guest. Several of these setups have been in production with 9.2 and 10.1 for 2 years+ without ahcich timeouts. >> 'hint.ahci.0.msi=3D0' 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=3Drevision&sortby=3Ddate&revisio= n=3D282901) >> 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=3D1" doesn't make any difference, as soon a= s >> '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? Yes, I tried several times, and falsified that with r284665 the timeouts reproducably show up (which blocks the booting process, a major issue in my case). I also verified that several different revisions <284665 don't lead to that problem, and also that the changes in ahci code paths for the last year are not involved. I also can't see any relation, wich doesn't mean much since I don't have the kernel skills, but I'm sure the symptoms start with "options RACCT" Thanks, -Harry --------------enig4C2550AF81F2E20B268F139D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlWiOnsACgkQLDqVQ9VXb8iuVQCgq3n1kyvOG7FeoO/2lw9WvA/x ywYAnj2sy0/C/IYNtUs/vf1vdIPvMImO =pbJQ -----END PGP SIGNATURE----- --------------enig4C2550AF81F2E20B268F139D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A23A75.8050003>