will this bug be addressed before test10?

will this bug be addressed before test10?

[Mr. Mailing List]

http://bugzilla.kernel.org/show_bug.cgi?id=1229

It's made it this far, and it's still just as horrible
a bug:(


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

Re: will this bug be addressed before test10?

[Oliver Hunt]

Hmmm,  i had something like that was happening a while ago (admittedly 
in 2.4.20) i could still ssh in from a seperate box but nothing short of 
a reboot fixed it.... however at the time many things were playing up so 
i couldn't blame anything specific...

--Oliver


Mr. Mailing List wrote:

>http://bugzilla.kernel.org/show_bug.cgi?id=1229
>
>It's made it this far, and it's still just as horrible
>a bug:(
>
>
>__________________________________
>Do you Yahoo!?
>Protect your identity with Yahoo! Mail AddressGuard
>http://antispam.yahoo.com/whatsnewfree
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>

Re: will this bug be addressed before test10?

[Andrew Morton]

"Mr. Mailing List" <mailinglistaddie@yahoo.com> wrote:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=1229
> 
>  It's made it this far, and it's still just as horrible
>  a bug:(

In the report you say that 2.6.0-test2 was OK and 2.6.0-test3 was not?

Over at

	http://www.zip.com.au/~akpm/linux/patches/test3/

you will find all the changesets between test2 and test3.  Each patch there
is against test2.  If you have the time, it would be useful to work out
which of those patches introduced the problem.  The chronological order of
those patches is

cset-20030727_1716.txt.gz
cset-20030801_0319.txt.gz
cset-20030801_0621.txt.gz
cset-20030801_1815.txt.gz
cset-20030801_1922.txt.gz
cset-20030801_2316.txt.gz
cset-20030802_0314.txt.gz
cset-20030802_0612.txt.gz
cset-20030802_1915.txt.gz
cset-20030803_0116.txt.gz
cset-20030803_0209.txt.gz
cset-20030803_2013.txt.gz
cset-20030804_2010.txt.gz
cset-20030804_2110.txt.gz
cset-20030805_0012.txt.gz
cset-20030805_1908.txt.gz
cset-20030805_2315.txt.gz
cset-20030806_0009.txt.gz
cset-20030806_0510.txt.gz
cset-20030806_0609.txt.gz
cset-20030806_0909.txt.gz
cset-20030807_0211.txt.gz
cset-20030807_0909.txt.gz
cset-20030807_1810.txt.gz
cset-20030807_1914.txt.gz
cset-20030807_2017.txt.gz
cset-20030807_2109.txt.gz
cset-20030807_2311.txt.gz
cset-20030808_0118.txt.gz
cset-20030808_0310.txt.gz
cset-20030808_1816.txt.gz
cset-20030809_0113.txt.gz
cset-20030809_0411.txt.gz

It should be possible to do this in six compile-n-boot cycles ;)

Thanks.