From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932494AbdLRKLf (ORCPT ); Mon, 18 Dec 2017 05:11:35 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:51765 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757956AbdLRKLe (ORCPT ); Mon, 18 Dec 2017 05:11:34 -0500 Date: Mon, 18 Dec 2017 11:11:31 +0100 From: Pavel Machek To: Alexandru Chirvasitu , kernel list Cc: Ingo Molnar , "Maciej W. Rozycki" , Mikael Pettersson Subject: Re: PROBLEM: 4.15.0-rc3 APIC causes lockups on Core 2 Duo laptop Message-ID: <20171218101131.GA5338@amd> References: <20171218082011.GA24638@arch-chirva.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20171218082011.GA24638@arch-chirva.localdomain> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! On Mon 2017-12-18 03:20:11, Alexandru Chirvasitu wrote: > Short description of the problem: latest rc kernel results in seemingly A= PIC-caused hard lockups, whereas latest stable kernel works fine. >=20 > I have an old ASUS F5RL laptop with an Intel Core 2 Duo CPU T5450 @1.66GH= z. It is currently running Debian 9.3 stable 32 bit (by default on a 4.9-se= ries kernel), but I have been compiling and installing the latest kernels. >=20 Thanks for doing that. > The latest rc kernel at the time of this writing (4.15.0-rc3) boots but t= hen results in hard lockups on both CPUs after login. Starting in recovery = mode returns the error >=20 > "spurious APIC interrupt through vector ff on CPU#0, should never happen" >=20 > before lockip up the CPUs again. A hard reboot is necessary.=20 >=20 > Starting with kernel option noapic logs me in uneventfully, but for some = reason has the effect of rendering my ethrenet card inoperable. It is a Qua= lcomm Atheros Attansic L2 Fast Ethernet (rev a0), handled by kernel module = atl2. In noapic mode the card is still seen by the system, can be brought u= p / down, etc., but dhclient never manages to acquire a lease. >=20 > Starting with kernel option nolapic instead brings up the network and log= s me in, but only sees one CPU instead of two, as usual. >=20 > The latest kernel that exhibits none of these issues is the latest stable= one as of this writing: 4.14.7. >=20 > --- >=20 > As this seems to be APIC-related, I am sending the message to the maintai= ners mentioned in arch/x86/kernel/apic/apic.c. I am unsure whether this is = the correct procedure however. >=20 Good enough procedure. You want to always copy linux-kernel mailing list, and you should probably look for X86 maintainers in MAINTAINERS file, and cc them, too. If you run out of other options, you can always do "git bisect"... Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlo3lFMACgkQMOfwapXb+vJavwCfaHHUVWnBuaYsVyrhm7TllLOr LhYAn3ZgqCaGHKB7JTpafk+t/NnHrVfr =JC8y -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--