Theodore Tso writes: > On Fri, Oct 09, 2009 at 10:01:44PM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > > Not fixed in 2.6.32-rc3. A glibc rebuild + install triggered the > > > exact same bug on the third machine. > > Can you isolate this down to something simpler? Will "make install" > followed by a reboot be sufficient to replicate the assertion failure? I've done repeated glibc downgrades and upgrades, using pre-built binary packages, followed by reboots, but they have so far not triggered the bug. My guess is that something in the build process or the test suite run triggers the bug. FWIW, the systems are rpm-based derived from Fedora, so the rebuilds are just "rpmbuild --rebuild glibc-<version>.src.rpm", and the installs are "rpm -Uvh" on the binary rpms, with --force if I'm doing a downgrade. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
