Sorry for not getting back to you sooner on this, the past few days have been a little bumpy operationally.
I was able to package a new ami to test your v2 kernel image with. I have only run one server so far with it, but it has taken a little longer to crash with output. Attached is the entire console output I receive on this server when it crashes. This is the same environment that I have been testing the other kernel images in. Just some more info about it in case it helps us debug this: - The server has apache running and is receiving traffic. It primarily serves PHP code which may query an external MySQL server. - There are PHP cron scripts that run to manage the server - Periodic Nagios checks are run that check the health/status of the server. These are perl/php/bash - Puppet runs periodically to check to ensure configuration consistency - SVN is frequently run checking repositories for updates - rsync is frequently run - A network filesystem is mounted using the Gluster client - No EBS volumes are attached There is a lot going on, so I'm sure its going to be a challenge trying to narrow this down. If there is anything else I can describe about the system that will help us let me know. ** Attachment added: "console-output-v2-image.txt" https://bugs.launchpad.net/ubuntu/hardy/+source/linux/+bug/705562/+attachment/2090759/+files/console-output-v2-image.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705562 Title: ami-6836dc01 8.04 32 bit AMI kernel lock bug -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
