Prev: drm fixes + agp + one fb patch (bisected)
Next: x86: enlightenment for ticket spin locks - Xen implementation
From: Christoph Hellwig on 8 Jul 2010 17:00
> > I can see the crash with vanilla x86/irq as well, with the config i sent.
>
> Ping?

Sorry, got preempted by a few important things when bisecting when it
broke over my tested config. Give me another day or two.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 14 Jul 2010 11:20
Turns out this wasn't a regression introduced by a commit, but it
happens when CONFIG_FUNCTION_GRAPH_TRACER is enabled. From a quick
look I have no idea why these would interact badly, especially as
CONFIG_FUNCTION_GRAPH_TRACER works fine with irq stacks if the
CONFIG_4KSTACKS options is set.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Thomas Gleixner on 14 Jul 2010 11:30
On Wed, 14 Jul 2010, Christoph Hellwig wrote:

> Turns out this wasn't a regression introduced by a commit, but it
> happens when CONFIG_FUNCTION_GRAPH_TRACER is enabled. From a quick
> look I have no idea why these would interact badly, especially as
> CONFIG_FUNCTION_GRAPH_TRACER works fine with irq stacks if the
> CONFIG_4KSTACKS options is set.

So you're saying, that the problem appears when
CONFIG_FUNCTION_GRAPH_TRACER is enabled w/o being used and that it
exists prior to your patches with irq stacks and 8k stack size, but
works with 4k stacks. That's definitely more than odd.

Thanks,

tglx

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 14 Jul 2010 11:50
On Wed, Jul 14, 2010 at 05:27:01PM +0200, Thomas Gleixner wrote:
> On Wed, 14 Jul 2010, Christoph Hellwig wrote:
>
> > Turns out this wasn't a regression introduced by a commit, but it
> > happens when CONFIG_FUNCTION_GRAPH_TRACER is enabled. From a quick
> > look I have no idea why these would interact badly, especially as
> > CONFIG_FUNCTION_GRAPH_TRACER works fine with irq stacks if the
> > CONFIG_4KSTACKS options is set.
>
> So you're saying, that the problem appears when
> CONFIG_FUNCTION_GRAPH_TRACER is enabled w/o being used and that it
> exists prior to your patches with irq stacks and 8k stack size, but
> works with 4k stacks. That's definitely more than odd.

No, the problem does not show up with 8k stack size without irqstacks,
and does not show up with 4k stacks with irq stacks, but does show up
with 8k stacks with irqstacks as long as CONFIG_FUNCTION_GRAPH_TRACER is
enabled. Just disabling it in Ingo's example config makes it work,
and enabling it in my usual test configs makes the boot fail with
similar messages to the one Ingo sees.

>
> Thanks,
>
> tglx
---end quoted text---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Steven Rostedt on 14 Jul 2010 14:30
On Wed, 2010-07-14 at 17:47 +0200, Christoph Hellwig wrote:
> On Wed, Jul 14, 2010 at 05:27:01PM +0200, Thomas Gleixner wrote:
> > On Wed, 14 Jul 2010, Christoph Hellwig wrote:
> >
> > > Turns out this wasn't a regression introduced by a commit, but it
> > > happens when CONFIG_FUNCTION_GRAPH_TRACER is enabled. From a quick
> > > look I have no idea why these would interact badly, especially as
> > > CONFIG_FUNCTION_GRAPH_TRACER works fine with irq stacks if the
> > > CONFIG_4KSTACKS options is set.
> >
> > So you're saying, that the problem appears when
> > CONFIG_FUNCTION_GRAPH_TRACER is enabled w/o being used and that it
> > exists prior to your patches with irq stacks and 8k stack size, but
> > works with 4k stacks. That's definitely more than odd.
>
> No, the problem does not show up with 8k stack size without irqstacks,
> and does not show up with 4k stacks with irq stacks, but does show up
> with 8k stacks with irqstacks as long as CONFIG_FUNCTION_GRAPH_TRACER is
> enabled. Just disabling it in Ingo's example config makes it work,
> and enabling it in my usual test configs makes the boot fail with
> similar messages to the one Ingo sees.

I'm currently at OLS, but I can take a look at this in more detail when
I get back on Monday.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: drm fixes + agp + one fb patch (bisected)
Next: x86: enlightenment for ticket spin locks - Xen implementation