Hello again everyone, I'm in the middle of doing some software testing on a pre-production clone of this system using some modified software configurations and a testing-only data volume, and I've managed to trigger this panic again.
The trigger was exactly the same; I had a bunch of queued emails from logcheck because my TLS configuration was wrong, then I fixed the TLS configuration and typed "postqueue -f" to send the queued mail. Ted, since this new iteration has no customer data, passwords, keys, or any other private data, I'm going to try to get approval to release an exact EC2 image of this system for you to test with, including the fake data volume that I triggered the problem on. If not I can certainly reproduce it now by stopping email delivery and generating a lot of fake syslog spam; I can try applying kernel patches and report what happens. Hopefully you're still willing to help out tracking down the problem? Thanks again! Cheers, Kyle Moffett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
