Hi Bernardo (et al). Apologies - I've not been reading my account for
a wee while. Then again, I probably don't have much useful to add to
the debate right now ;-)
--- Bernardo Innocenti <[EMAIL PROTECTED]> wrote:
> Anders Saaby wrote:
> > Anyways if your server has only run with 2.6.10 - try 2.6.11.
>
> Thank you, I've finally nailed it down by upgrading the
> *server* kernel from 2.6.10-1.770_FC3 to 2.6.10-1.770_FC3.
Hmm, I will infer from a previous email you sent that you mean 766_FC3
for the "from" kernel.
> The latter is basically 2.6.10-ac12 plus a bunch of vendor
> specific patches.
766 -> 770 sounds like a "small" (ish) number of patches to check, if
we're lucky. Did you wade through 'em all yet? Any smoking guns?
Regards,
Neil
PS: oh bugger, just remembered that I also reproduced my bug with a
2.6.8 kernel on the server; admittedly though it was an FC2 kernel so
who knows what extra patches it had.
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
-
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/
