Sorry for the long delay. I now think that this bug was not fixed in any of these mainline kernels, but that, instead, it generally takes several suspend cycles for it to show up. Since I have been rebooting frequently into different kernels to test this and other bugs, I wasn't seeing the bug! But now I've had a chance to spend a good deal of time in all the kernels, and have seen it in all of them. I'm tempted to think it's a problem with network-manager, but not based on any really good grounds. Thanks, Matt
On 12-09-26 01:57 PM, Joseph Salisbury wrote: > I'd like to perform a reverse bisect to figure out which commit upstream > fixes this regression. It would be very helpful to know the last kernel > that had this issue and the first kernel that did not. > > Can you test the following kernels and report back? We are looking for > the first kernel version that doesn't have this bug: > > v3.6-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc1-quantal/ > v3.6-rc3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc3-quantal/ > v3.6-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc5-quantal/ > > You don't have to test every kernel, just up until the kernel that first > does not have this bug. > > Thanks in advance! > > > ** Tags added: performing-bisect > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052873 Title: network-manager tries to connect to eth0 when cable is unplugged -- Intel 82577LM e1000e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1052873/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
