Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service
Well, I've discovered why makedumpfile continues to run even after the
dump files show up in the folder. It's failing to properly dump the
kernel log, and is continually appending the line "[ 0.000000] " to the
dmesg file. I just ended up with a 3 GB file, nano ended up kaput trying
to open it so I have no idea how many times it ended up printing that
line into the file. I am going to file a bug on makedumpfile about this
and hopefully it can be resolved, until then I am ceasing my dump
collection attempts.
(That said, the main dump file seems to be in alright shape, so some
information may be able to be gleaned from that... I've archived my
latest crash dump without the unnecessarily large, useless dmesg file
and the total size comes to 107.4 MB, if your mail server can handle a
file this size and you feel there may be something useful in the dump I
can send the file with my next message.)
(Also, apparently I was wrong about the previous dmesg dump files being
saved as binary files, apparently that was a permissions-related issue,
as they can only be viewed as root. Attempting to view them as a
non-root user seems to mistakenly identify them as binary files rather
than plain-text.)
Reply to: