Hi Ben-- Thanks for the prompt followup! On 01/22/2012 11:21 PM, Ben Hutchings wrote: > On Sun, 2012-01-22 at 15:11 -0500, Daniel Kahn Gillmor wrote: > It looks like we got to the memcpy() in vsnprintf() with str == NULL. > Which seems to mean that seq_file is seriously broken. But it hasn't > changed between 3.1 and 3.2, so I doubt it's really the source of the > problem. yes, agreed that this seems unlikely. > Have you seen any more of these? Do you remember doing anything in > particular before this crash (aside from running ps)? well, i'd only just booted them machine and hadn't really done much regular work on it. I'd rebooted it because it had crashed earlier with a horrible graphics malfunction (which left me unable to get any good data for a backtrace), but i haven't seen any filesystem errors. The graphics had crashed while i was futzing with the wireless on a moving train, though, so the one thing that i had done since this boot was to cycle the rfkill trigger on the machine a couple times, which disabled and enabled the wirless (you can see the ath and wlan0 business earlier in the log). But i hadn't done that in several minutes when it OOPSed. So i'm a bit at a loss. I subsequently rebooted and tested all 2GiB RAM with memtest86+, and it showed no errors. I've actually had the same graphics failure since then, but no more OOPSes. i don't know how to gather data to debug the graphics failure, though, or i'd send in separate report for that one. Maybe i'll carry around a camera to snap a picture of the screen if it happens again. If you have any other ideas about the OOPS, i'd be happy to investigate them. --dkg
Attachment:
signature.asc
Description: OpenPGP digital signature