Re: 1352 NUL bytes at the end of a page? (was Re: Assertion `s && s->tree' failed: The saga continues.)

From: Steven Cole
Date: Sat May 15 2004 - 23:32:57 EST

On Saturday 15 May 2004 09:44 pm, Linus Torvalds wrote:
> On Sat, 15 May 2004, Linus Torvalds wrote:
> >
> >
> > On Sat, 15 May 2004, Steven Cole wrote:
> > >
> > > In the spirit of 'rounding up the usual suspects', I'll unset CONFIG_PREEMT
> > > and try again.
> >
> > Or it could be any number of other config options. Do you have anything
> > else interesting enabled?
> Ahh, looking at an earlier email I see that you have CONFIG_REGPARM=y too.
> That could easily be pretty dangerous - there have been both compiler bugs
> in this area, and just kernel bugs (missing "asmlinkage" things causing
> bad calling conventions and really nasty bugs).
> So please try without both PREEMPT and REGPARM. Considering that it's
> apparently very repeatable for you, I'd be more inclined to worry about
> REGPARM than PREEMPT, but it's best to try with both disabled.
> I also worry about that PDC202XX controller, but that 1352 is a strange
> number (divisible by 8, but not by a cacheline or 512-byte sector or
> something like that), so it doesn't _sound_ like something like DMA
> failure or chipset programming, but who the hell knows..
> Linus

OK, will do. I ran the bk exerciser script for over an hour with 2.6.6-current
and no CONFIG_PREEMPT and no errors. The script only reported one
iteration finished, while I got it to do 36 iterations over several hours earlier
today (with a 2.6.3-4mdk vendor kernel), so I'm going to add some timing
tests to the script to see if things are really slowing down with current kernels,
or if it's just my worried imaginings.

Going back through my sent mail, it looks like I first reported the originally
noticed failture as a bk bug to LM on 4/15/04 if that helps with kernel versions.
I usually do a bk pull and kernel build every night or so "just for fun".

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at