[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110325155821.GA1661@gentoo.trippels.de>
Date: Fri, 25 Mar 2011 16:58:21 +0100
From: Markus Trippelsdorf <markus@...ppelsdorf.de>
To: Jens Axboe <jaxboe@...ionio.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Chris Mason <chris.mason@...cle.com>
Subject: Re: [GIT PULL] Core block IO bits for 2.6.39 - early Oops
On 2011.03.25 at 16:51 +0100, Jens Axboe wrote:
> On 2011-03-25 15:28, Markus Trippelsdorf wrote:
> > On 2011.03.25 at 15:20 +0100, Jens Axboe wrote:
> >> On 2011-03-25 15:14, Markus Trippelsdorf wrote:
> >>> On 2011.03.25 at 15:10 +0100, Jens Axboe wrote:
> >>>> On 2011-03-25 14:09, Markus Trippelsdorf wrote:
> >>>>> On 2011.03.25 at 13:44 +0100, Jens Axboe wrote:
> >>>>>> On 2011-03-25 10:57, Markus Trippelsdorf wrote:
> >>>>>>>
> >>>>>>> Reverting it solves all problems here.
> >>>>>>
> >>>>>> Can you try this one?
> >>>>>
> >>>>> This one doesn't help; I still get the same BUG.
> >>>>>
> >>>>> BTW if you're having trouble reproducing this, here is the only non
> >>>>> stock xfs option that I use on the affected partitions:
> >>>>>
> >>>>> noatime,logbsize=262144
> >>>>
> >>>> This?
> >>>
> >>> No.
> >>
> >> Lets expand the scope a bit, this one?
> >
> > No. And setting CONFIG_PREEMPT_NONE also doesn't help.
> >
>
> Does this work? I'm actually relieved that the preempt was a red
> herring. I had earlier convinced myself that it was all safe without
> that mucking around with preempt counts.
Finally: YES.
Many thanks Jens.
--
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists