On Sun, 16 Dec 2007 00:08:52 +0100 (CET) Krzysztof Oledzki <[email protected]> wrote:
>
>
> On Sat, 15 Dec 2007, [email protected] wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9182
> >
> >
> > ------- Comment #33 from [email protected] 2007-12-15 14:19 -------
> > Krzysztof, I'd hate point you to a hard path (at least time consuming), but
> > you've done a lot of digging by now anyway. How about git bisecting between
> > 2.6.20-rc2 and rc1? Here is great info on bisecting:
> > http://www.kernel.org/doc/local/git-quick.html
>
> As I'm smarter than git-bistect I can tell that 2.6.20-rc1-git8 is as bad
> as 2.6.20-rc2 but 2.6.20-rc1-git8 with one patch reverted seems to be OK.
> So it took me only 2 reboots. ;)
>
> The guilty patch is the one I proposed just an hour ago:
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fstable%2Flinux-2.6.20.y.git;a=commitdiff_plain;h=fba2591bf4e418b6c3f9f8794c9dd8fe40ae7bd9
>
> So:
> - 2.6.20-rc1: OK
> - 2.6.20-rc1-git8 with fba2591bf4e418b6c3f9f8794c9dd8fe40ae7bd9 reverted: OK
> - 2.6.20-rc1-git8: very BAD
> - 2.6.20-rc2: very BAD
> - 2.6.20-rc4: very BAD
> - >= 2.6.20: BAD (but not *very* BAD!)
>
well.. We have code which has been used by *everyone* for a year and it's
misbehaving for you alone. I wonder what you're doing that is
different/special.
Which filesystem, which mount options, what sort of workload?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
