All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Nishanth Menon <nm@ti.com>,
	"Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: mysterious crashes on OMAP5 uevm
Date: Tue, 8 Sep 2015 07:38:11 -0700	[thread overview]
Message-ID: <20150908143810.GD4215@atomide.com> (raw)
In-Reply-To: <CANOLnOO3NdK1r1jZQtS=TcHEE7SQwhGHh0YsqqoCJpFW3NO05Q@mail.gmail.com>

* Grazvydas Ignotas <notasas@gmail.com> [150908 05:50]:
> Hi,
> 
> this is a longstanding problem I'm seeing since the very beginning,
> which was around 3.12 or so (when I've first got the hardware) and it
> seems 4.2 is affected by it still. Basically what happens is Xorg
> randomly segfaults at some "impossible" location. I don't have the
> details at the moment (could get them is needed), but from what I
> examined with gdb some time ago the situation did not make any sense.
> 
> There are 2 workarounds that I know which make the problem go away
> (one is enough):
> - recompile Xorg with -marm (I'm using Debian armhf so it's thumb2 by default)
> - disable ARCH_MULTI_V6 in the kernel config
> 
> Because of the above workarounds I have forgotten about it several
> times, but it regularly comes back and bites again. It would look like
> some missing erratum workaround, but I have all of them enabled in the
> kernel.
> 
> Does anyone know about this? Perhaps some missing erratum workaround
> in the bootloader? u-boot isn't too old here (2015.07).

Seems like some incorrect handling with CONFIG_CPU_V6 compiled in.. 
Maybe try to narrow it down by commenting out some CONFIG_CPU_V6 and
__LINUX_ARM_ARCH__ = 6 ifdefs in the git grep CONFIG_CPU_V6
places ignoring uncompress and davinci code.

Do you have some easy way to reproduce this issue?

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: mysterious crashes on OMAP5 uevm
Date: Tue, 8 Sep 2015 07:38:11 -0700	[thread overview]
Message-ID: <20150908143810.GD4215@atomide.com> (raw)
In-Reply-To: <CANOLnOO3NdK1r1jZQtS=TcHEE7SQwhGHh0YsqqoCJpFW3NO05Q@mail.gmail.com>

* Grazvydas Ignotas <notasas@gmail.com> [150908 05:50]:
> Hi,
> 
> this is a longstanding problem I'm seeing since the very beginning,
> which was around 3.12 or so (when I've first got the hardware) and it
> seems 4.2 is affected by it still. Basically what happens is Xorg
> randomly segfaults at some "impossible" location. I don't have the
> details at the moment (could get them is needed), but from what I
> examined with gdb some time ago the situation did not make any sense.
> 
> There are 2 workarounds that I know which make the problem go away
> (one is enough):
> - recompile Xorg with -marm (I'm using Debian armhf so it's thumb2 by default)
> - disable ARCH_MULTI_V6 in the kernel config
> 
> Because of the above workarounds I have forgotten about it several
> times, but it regularly comes back and bites again. It would look like
> some missing erratum workaround, but I have all of them enabled in the
> kernel.
> 
> Does anyone know about this? Perhaps some missing erratum workaround
> in the bootloader? u-boot isn't too old here (2015.07).

Seems like some incorrect handling with CONFIG_CPU_V6 compiled in.. 
Maybe try to narrow it down by commenting out some CONFIG_CPU_V6 and
__LINUX_ARM_ARCH__ = 6 ifdefs in the git grep CONFIG_CPU_V6
places ignoring uncompress and davinci code.

Do you have some easy way to reproduce this issue?

Regards,

Tony

  reply	other threads:[~2015-09-08 14:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 12:46 mysterious crashes on OMAP5 uevm Grazvydas Ignotas
2015-09-08 12:46 ` Grazvydas Ignotas
2015-09-08 14:38 ` Tony Lindgren [this message]
2015-09-08 14:38   ` Tony Lindgren
2015-09-08 20:41   ` Grazvydas Ignotas
2015-09-08 20:41     ` Grazvydas Ignotas
2015-09-08 21:07     ` Tony Lindgren
2015-09-08 21:07       ` Tony Lindgren
2015-09-10  6:42       ` Dr. H. Nikolaus Schaller
2015-09-10  6:42         ` Dr. H. Nikolaus Schaller
2015-09-10  8:30         ` Russell King - ARM Linux
2015-09-10  8:30           ` Russell King - ARM Linux
2015-09-10  8:57           ` Dr. H. Nikolaus Schaller
2015-09-10  8:57             ` Dr. H. Nikolaus Schaller
2015-09-10 23:33           ` Woodruff, Richard
2015-09-10 23:33             ` Woodruff, Richard
2015-09-11 13:27           ` Grazvydas Ignotas
2015-09-11 13:27             ` Grazvydas Ignotas
2015-09-11 14:03             ` Russell King - ARM Linux
2015-09-11 14:03               ` Russell King - ARM Linux
2015-09-11 16:12               ` Woodruff, Richard
2015-09-11 16:12                 ` Woodruff, Richard
2015-09-11 17:48                 ` Russell King - ARM Linux
2015-09-11 17:48                   ` Russell King - ARM Linux
2015-09-11 18:34                   ` Woodruff, Richard
2015-09-11 18:34                     ` Woodruff, Richard
2015-09-14 12:12               ` Russell King - ARM Linux
2015-09-14 12:12                 ` Russell King - ARM Linux
2015-09-14 19:02                 ` Tony Lindgren
2015-09-14 19:02                   ` Tony Lindgren
2015-09-14 19:35                   ` Dr. H. Nikolaus Schaller
2015-09-14 19:35                     ` Dr. H. Nikolaus Schaller
2015-09-15 17:31                     ` Grazvydas Ignotas
2015-09-15 17:31                       ` Grazvydas Ignotas
2015-09-16 10:07                       ` Russell King - ARM Linux
2015-09-16 10:07                         ` Russell King - ARM Linux
2015-09-18 17:48       ` Tony Lindgren
2015-09-18 17:48         ` Tony Lindgren

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=20150908143810.GD4215@atomide.com \
    --to=tony@atomide.com \
    --cc=hns@goldelico.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nm@ti.com \
    --cc=notasas@gmail.com \
    /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.