From owner-freebsd-bugs@freebsd.org Tue Sep 10 23:08:54 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 48E26E7627 for ; Tue, 10 Sep 2019 23:08:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Sgh61BCkz48RJ for ; Tue, 10 Sep 2019 23:08:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 26DA9E7626; Tue, 10 Sep 2019 23:08:54 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 269FEE7625 for ; Tue, 10 Sep 2019 23:08:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Sgh60BMjz48RG for ; Tue, 10 Sep 2019 23:08:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DB3C92D509 for ; Tue, 10 Sep 2019 23:08:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8AN8rux049497 for ; Tue, 10 Sep 2019 23:08:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8AN8rIw049496 for bugs@FreeBSD.org; Tue, 10 Sep 2019 23:08:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH) Date: Tue, 10 Sep 2019 23:08:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: greg@unrelenting.technology X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2019 23:08:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240339 --- Comment #9 from Greg V --- (In reply to Vladimir Kondratyev from comment #7) oh cool, you already wrote the ACPI lookup of parameters, I was thinking ab= out doing that haha. Though the values that it ends up applying seem really high (564, 480 on i2c2 for SCL). I commented that out again Unfortunately the problem is still there. Some more testing: - after the lockup in FreeBSD, Linux cannot recover that i2c bus either =E2= =80=94 rebooting (not shutting down and powering up) into Chrome OS results in 'i2c_designware.2: controller timed out' and the touchpad not working; - the EC interface on the same bus allows reading the console of the touchp= ad's firmware, but that's impossible when the controller is locked up.. I'm wait= ing for a debug cable to ship, but the documentation doesn't say that it's poss= ible to access the touchpad console through that; - I added some logging to the error handling, on i2c0 (working touchscreen) after reading the touchscreen's descriptor for setup there's an RX underflo= w, but here (touchpad) that did not happen, none of these errors happened; - with HAVE_IG4_POLLING in iichid, there's no RX underflow there (obviously= ), but it does not fix the lockup. I wonder if it might actually be iichid/imt doing something that causes the touchpad to do something wrong with the bus=E2=80=A6 log: https://gist.github.com/myfreeweb/67b3ca690c22b31f502079b11263f0f4 --=20 You are receiving this mail because: You are the assignee for the bug.=