From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Subject: Re: [REGRESSION] Xorg segfaults on Asus Chromebook CP101 with Linux v5.2 (was Asus C101P Chromeboot fails to boot with Linux 5.2) Date: Sat, 13 Jul 2019 16:47:00 +0200 Message-ID: <20190713144700.GF5982@kroah.com> References: <59042b09-7651-be1d-347f-0dc4aa02a91b@gmx.co.uk> <862e98f3-8a89-a05e-1e85-e6f6004da32b@gmx.co.uk> <5fe66d5d-0624-323f-3bf8-56134ca85eca@gmx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" To: Alex Dewar Cc: devel@driverdev.osuosl.org, Heiko Stuebner , Linux Kernel Mailing List , "open list:ARM/Rockchip SoC..." , Boris Brezillon , Philipp Zabel , Hans Verkuil , Mauro Carvalho Chehab , linux-arm-kernel , linux-media@vger.kernel.org List-Id: linux-rockchip.vger.kernel.org On Sat, Jul 13, 2019 at 12:38:45PM +0100, Alex Dewar wrote: > Hi all, > > I initially thought my machine was failing to boot entirely, but it > turns out it was just failing to start the display manager. I managed to > escape to a tty by hammering the keyboard a bit. > > I suspect the culprit is the rockchip_vpu driver (in staging/media), > which has been renamed to hantro in this merge window. When I run startx > from a terminal, X fails to start and Xorg segfaults (log here: > http://users.sussex.ac.uk/~ad374/xorg.log). X seems to work without any > issues in v5.1. > > I've also tried running trace on the Xorg process, but the output was > pretty verbose. I can share if that would be helpful though. Can you run 'git bisect' to find the offending commit? thanks, greg k-h