Hi, Thank you for giving your comments. >So what is the problem you are trying to avoid, and why can't we do >something in the kernels initialization path to avoid initializing >when there is a problem? Kdump gets a dump disk identifier based on information from memory. So, kdump may receive wrong identifier when it starts after MCE occurred, because MCE is reported by memory, cache, and TLB errors In the worst case, kdump will overwrite user data if it recognizes a disk saving user data as a dump disk. Kdump shouldn't write any data to disk when information from hardware is incredible because saving user data is always first priority. Seiji -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href