Hi Grazvydas,
* Tony Lindgren [150908 14:11]:
> * Grazvydas Ignotas [150908 13:44]:
> > On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
> OK nice to hear you found it. Yeah looks like some runtime
> capability check is needed.
>
> > > Do you have some easy way to reproduce this issue?
>
On Tue, Sep 15, 2015 at 08:31:44PM +0300, Grazvydas Ignotas wrote:
> On Mon, Sep 14, 2015 at 10:35 PM, Dr. H. Nikolaus Schaller
> wrote:
> >
> > Am 14.09.2015 um 21:02 schrieb Tony Lindgren :
> >
> >> * Russell King - ARM Linux [150914 05:16]:
> >>> On Fri, Sep 11, 2015 at 03:03:07PM +0100, Russe
On Mon, Sep 14, 2015 at 10:35 PM, Dr. H. Nikolaus Schaller
wrote:
>
> Am 14.09.2015 um 21:02 schrieb Tony Lindgren :
>
>> * Russell King - ARM Linux [150914 05:16]:
>>> On Fri, Sep 11, 2015 at 03:03:07PM +0100, Russell King - ARM Linux wrote:
Merely changing __LINUX_ARM_ARCH__ >= 7 to >
Am 14.09.2015 um 21:02 schrieb Tony Lindgren :
> * Russell King - ARM Linux [150914 05:16]:
>> On Fri, Sep 11, 2015 at 03:03:07PM +0100, Russell King - ARM Linux wrote:
>>>
>>> Merely changing __LINUX_ARM_ARCH__ >= 7 to >= 6 should fix the problem,
>>> and I doubt there's any ARMv6 non-T2 syste
* Russell King - ARM Linux [150914 05:16]:
> On Fri, Sep 11, 2015 at 03:03:07PM +0100, Russell King - ARM Linux wrote:
> >
> > Merely changing __LINUX_ARM_ARCH__ >= 7 to >= 6 should fix the problem,
> > and I doubt there's any ARMv6 non-T2 systems out there that would be
> > affected by clearing
On Fri, Sep 11, 2015 at 03:03:07PM +0100, Russell King - ARM Linux wrote:
> On Fri, Sep 11, 2015 at 03:27:13PM +0200, Grazvydas Ignotas wrote:
> > On Thu, Sep 10, 2015 at 10:30 AM, Russell King - ARM Linux
> > wrote:
> > > On Thu, Sep 10, 2015 at 08:42:57AM +0200, Dr. H. Nikolaus Schaller wrote:
>
> From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
> Sent: Friday, September 11, 2015 12:49 PM
> Frankly, Richard, you're getting on my nerves in this thread - you seem to
> know all about this problem, yet you never reported the problem upstream,
> so people are effectively having t
On Fri, Sep 11, 2015 at 04:12:21PM +, Woodruff, Richard wrote:
> > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> > ow...@vger.kernel.org] On Behalf Of Russell King - ARM Linux
> > Sent: Friday, September 11, 2015 9:03 AM
> > To: Grazvydas Ignotas
>
> > However, even the idea tha
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Russell King - ARM Linux
> Sent: Friday, September 11, 2015 9:03 AM
> To: Grazvydas Ignotas
> However, even the idea that it's ARMv7 or later is wrong. According to
> the ARM ARM, the IT instruction
On Fri, Sep 11, 2015 at 03:27:13PM +0200, Grazvydas Ignotas wrote:
> On Thu, Sep 10, 2015 at 10:30 AM, Russell King - ARM Linux
> wrote:
> > On Thu, Sep 10, 2015 at 08:42:57AM +0200, Dr. H. Nikolaus Schaller wrote:
> >> ...
> >>
> >> Now, disabling CONFIG_ARCH_MULTI_V6 also makes the bug go away a
On Thu, Sep 10, 2015 at 10:30 AM, Russell King - ARM Linux
wrote:
> On Thu, Sep 10, 2015 at 08:42:57AM +0200, Dr. H. Nikolaus Schaller wrote:
>> ...
>>
>> Now, disabling CONFIG_ARCH_MULTI_V6 also makes the bug go away and adding the
>> >> #if 0 //__LINUX_ARM_ARCH__ >= 7
>> makes it re-appear.
>>
>
> From: linux-arm-kernel [mailto:linux-arm-kernel-
> boun...@lists.infradead.org] On Behalf Of Russell King - ARM Linux
> > 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
> > >>
Am 10.09.2015 um 10:30 schrieb Russell King - ARM Linux
:
> On Thu, Sep 10, 2015 at 08:42:57AM +0200, Dr. H. Nikolaus Schaller wrote:
>>
>> Am 08.09.2015 um 23:07 schrieb Tony Lindgren :
>>
>>> * Grazvydas Ignotas [150908 13:44]:
On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
On Thu, Sep 10, 2015 at 08:42:57AM +0200, Dr. H. Nikolaus Schaller wrote:
>
> Am 08.09.2015 um 23:07 schrieb Tony Lindgren :
>
> > * Grazvydas Ignotas [150908 13:44]:
> >> On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
> >>> * Grazvydas Ignotas [150908 05:50]:
> Hi,
>
> t
Am 08.09.2015 um 23:07 schrieb Tony Lindgren :
> * Grazvydas Ignotas [150908 13:44]:
>> On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
>>> * Grazvydas Ignotas [150908 05:50]:
Hi,
this is a longstanding problem I'm seeing since the very beginning,
which was around 3.1
* Grazvydas Ignotas [150908 13:44]:
> On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
> > * Grazvydas Ignotas [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
> >
On Tue, Sep 8, 2015 at 4:38 PM, Tony Lindgren wrote:
> * Grazvydas Ignotas [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
* Grazvydas Ignotas [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" l
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 (
19 matches
Mail list logo