Tim Hartrick: >"The report was made again the natty 2.6.38-8 kernel. It was subsequently reproduced on upstream kernels out to 3.2. As I noted in my previous comment, I worked with the upstream developers to create a patch that works on the 2.6.38 kernel as well as newer kernels (see previous comment)."
We both knew this already. :D >"My testing indicated that this bug was also in the 2.6.32 based kernels used on 10.04 LTS." Ok. I'll add the lucid tag. >"Whether you should close the bug or not is a matter of policy that I can't comment on." Just to clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882340/comments/6 , I am asking if you personally or the environment you are in/responsible for, uses a release where this patch is not released in (ex. Hardy server, Lucid server, etc)? Hence, you desire a fix for this problem. If so, we can work together to get it addressed. Otherwise, we can close this report as per Ubuntu Bug Control policy https://wiki.ubuntu.com/Bugs/Responses#Bugs_resolved_after_update_or_config_change . ** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882340 Title: Invalid physical address encountered during vmcore_init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882340/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
