Date: Sat, 11 Jul 2015 19:56:49 +0200 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: freebsd-stable@freebsd.org Cc: =?UTF-8?B?RWR3YXJkIFRvbWFzeiBOYXBpZXJhxYJh?= <trasz@freebsd.org>, kib@freebsd.org Subject: r284665 causes MSI problems -> ahcich2: Timeout in slot 11 port 0 Message-ID: <55A158E1.3000905@omnilan.de>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Hello, r284665 causes ahci(4) to fail with timeouts when using MSI (the default). '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? Thanks, -Harry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlWhWOYACgkQLDqVQ9VXb8gIMgCfQECqAbUSiE2Htldz5KzKCLxA eoIAnR9jtlgIs1XEeuLKXvkaOh9j2HFa =BDMT -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A158E1.3000905>