All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alex Dewar <alex.dewar@gmx.co.uk>
Cc: devel@driverdev.osuosl.org, Heiko Stuebner <heiko@sntech.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-media@vger.kernel.org
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	[thread overview]
Message-ID: <20190713144700.GF5982@kroah.com> (raw)
In-Reply-To: <f47f8759-8113-812a-b17a-4be09665369e@gmx.co.uk>

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

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alex Dewar <alex.dewar@gmx.co.uk>
Cc: devel@driverdev.osuosl.org, Heiko Stuebner <heiko@sntech.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-media@vger.kernel.org
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	[thread overview]
Message-ID: <20190713144700.GF5982@kroah.com> (raw)
In-Reply-To: <f47f8759-8113-812a-b17a-4be09665369e@gmx.co.uk>

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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alex Dewar <alex.dewar@gmx.co.uk>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-media@vger.kernel.org, devel@driverdev.osuosl.org
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	[thread overview]
Message-ID: <20190713144700.GF5982@kroah.com> (raw)
In-Reply-To: <f47f8759-8113-812a-b17a-4be09665369e@gmx.co.uk>

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

  reply	other threads:[~2019-07-13 14:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 15:00 Asus C101P Chromeboot fails to boot with Linux 5.2 Alex Dewar
2019-07-12 15:00 ` Alex Dewar
2019-07-12 15:44 ` Emil Renner Berthing
2019-07-12 15:44   ` Emil Renner Berthing
2019-07-12 16:27   ` Alex Dewar
2019-07-12 16:27     ` Alex Dewar
2019-07-12 22:07     ` Alex Dewar
2019-07-12 22:07       ` Alex Dewar
2019-07-13 11:38       ` [REGRESSION] Xorg segfaults on Asus Chromebook CP101 with Linux v5.2 (was Asus C101P Chromeboot fails to boot with Linux 5.2) Alex Dewar
2019-07-13 14:47         ` Greg Kroah-Hartman [this message]
2019-07-13 14:47           ` Greg Kroah-Hartman
2019-07-13 14:47           ` Greg Kroah-Hartman
2019-07-13 15:17         ` Heiko Stuebner
2019-07-13 15:17           ` Heiko Stuebner
2019-07-13 16:43           ` Alex Dewar
2019-07-13 16:43             ` Alex Dewar
2019-07-13 22:58             ` Ezequiel Garcia
2019-07-13 22:58               ` Ezequiel Garcia
2019-07-13 22:58               ` Ezequiel Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190713144700.GF5982@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alex.dewar@gmx.co.uk \
    --cc=boris.brezillon@collabora.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=heiko@sntech.de \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.