> Since this is a 2.6.17->2.6.18 regression narrowing the problem down to > the specific changeset (or at least -git or even -rc) seems like a most > promising way in discovering the source of the issue.
Dunno... unless I missed something in the logs, both 2.6.17 and .18 seem to report initially the wrong size (2GB), but the kernel seems to ignore the size from the IDE layer and use the one in the partition map in .17 and not in .18 ... To me at least, it looks like it's not a regression per-se but a latent bug made visible. Cheers, Ben. - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
