If this truly is a software bug, our best shot at addressing this bug is via bisection, from lack of specific knowledge.
There are enough reports the we consider the ubuntu kernel 2.6.28-9(.31?) good and we know (at least) ubuntu kernel 2.6.28-11.42 is bad. We can rebuild intermediate kernels from [http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=tags]. First, it may be easier to see if we can bisect using the mainline kernels, since they are prebuilt at [http://kernel.ubuntu.com/~kernel- ppa/mainline/]. We get the ubuntu to mainline mapping from [http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html]. -> ubuntu 2.6.28-9.31 is based on mainline 2.6.28.7 ("A") http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.28.7/linux-image-2.6.28-02062807-generic_2.6.28-02062807_amd64.deb -> ubuntu 2.6.28-11.42 is based on mainline 2.6.28.9 ("Z") http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.28.9/linux-image-2.6.28-02062809-generic_2.6.28-02062809_amd64.deb ** Can at least two people who can reproduce this issue with 2.6.28-11.42, double-check they can/can't reproduce it with kernel Z please? ** We'll know if it's ubuntu patches/configuration, or upstream then. -- 2.6.28-11 causes massive data corruption on 64 bit installations https://bugs.launchpad.net/bugs/346691 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
