On Sat, Oct 13, 2012 at 08:52:44AM +0900, Linus Torvalds wrote: > Also, why the *HELL* is that a BUG_ON() in the first place? Who was > the less-than-gifted person who decided "if this thing can happen, > let's just kill the whole machine"? Ahh, I've been away from the kernel too long. I miss that delicate management touch. > Larry, the stack trace and registers would be useful. Picture or a > full dump of the BUG_ON() if it got logged? If it gets eaten by the > machine being unresponsive after the event and since you can reproduce > it, you could just try to change it to the WARN_ON_ONCE() above, and > then it should be easier to just get out of the dmesg, since hopefully > the machine stays up despite the odd status value.. Been a while since I've built a kernel and this is our production file server, it goes down and our whole company stops. As surprising as it might sound, given git's success, we're still busy so crashing the server isn't fun :) pics of the stack trace at http://www.mcvoy.com/lm/nfs-lock-crash -- --- Larry McVoy lm at bitmover.com http://www.bitkeeper.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
