Timeline for Determining cause of Linux kernel panic
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2024 at 14:40 | comment | added | G-Man Says 'Reinstate Monica' | @user643011: Thanks for catching the broken link and suggesting an edit — but, when you do this (in the future), please check the entire post for problems, and fix them all. | |
| S Feb 15, 2024 at 14:30 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 | Fixed more broken links; tweaked grammar and punctuation. |
| S Feb 15, 2024 at 14:30 | history | suggested | user643011 | CC BY-SA 4.0 | Fixes broken link |
| Feb 15, 2024 at 9:58 | review | Suggested edits | |||
| S Feb 15, 2024 at 14:30 | |||||
| S Jun 7, 2017 at 8:28 | history | suggested | PhoneixS | CC BY-SA 3.0 | Updated broken link |
| Jun 7, 2017 at 8:15 | review | Suggested edits | |||
| S Jun 7, 2017 at 8:28 | |||||
| Jan 14, 2013 at 7:26 | history | bounty awarded | Naftuli Kay | ||
| Jan 14, 2013 at 7:26 | vote | accept | Naftuli Kay | ||
| Jan 12, 2013 at 7:14 | comment | added | Scott Lamb | Not sure. I'm a software guy; this is the limit of my expertise. | |
| Jan 11, 2013 at 23:38 | comment | added | Naftuli Kay | Now that I know what's failing, is there a way for me to cause the crash with a given command? | |
| Jan 11, 2013 at 21:57 | comment | added | Soumyadip DM | I would second the "Overclock is culprit" thought. MCE mostly occurs due to hardware issues. But, a segmentation fault in any module code can cause the same too. Two years back, my new i7 2600k was giving me the same MCE issue, even when I was not doing anything on the computer. When I dug a little deeper, I found the BIOS version I was using with my Intel motherboard was not properly supporting the then new processor. I updated the BIOS and the problem was gone. So I will suggest you to check on that route too. | |
| Jan 11, 2013 at 6:15 | comment | added | Scott Lamb | All it means to me is that your processor isn't working. Probably the overclocking, maybe the other thing you mentioned (it's not something I've heard about), maybe a defective unit. | |
| Jan 11, 2013 at 2:50 | comment | added | Naftuli Kay | Got the log! Awesome help. I've updated the original post with the output of that log. I'm finally seeing the error now, any ideas on what might be causing it? | |
| Jan 11, 2013 at 2:35 | comment | added | Naftuli Kay | Thanks, I'll look into that. I've heard that this issue pops up sometimes on UEFI motherboards when booting into BIOS legacy mode, which is the case on this system. This could explain why I haven't seen the issue on Windows, as it boots EFI. I'm also running i7z as a daemon in the background and it's probably doing some devious stuff to get live processor frequencies, C-states, and other stuff. Needless to say, I've disabled that and I'll see if it crashes again. | |
| Jan 11, 2013 at 1:20 | comment | added | Scott Lamb | Sweet. Updated my answer as well. | |
| Jan 11, 2013 at 1:19 | history | edited | Scott Lamb | CC BY-SA 3.0 | more info |
| Jan 11, 2013 at 1:02 | history | edited | Scott Lamb | CC BY-SA 3.0 | more info |
| Jan 11, 2013 at 0:37 | comment | added | Naftuli Kay | I've updated the question, as I was able to crash the machine while running linux-crashdump and obtain a crash dump file which hopefully has enough information to determine the cause. | |
| Jan 10, 2013 at 22:21 | comment | added | Scott Lamb | Actually, I take that back. On Ubuntu, there is a linux-crashdump package you can install fairly easily to automatically put crashes in /var/crash. What distribution are you using? | |
| Jan 10, 2013 at 21:58 | comment | added | Scott Lamb | One of those little quirks. :-/ There's no fundamental reason Ubuntu or RedHat couldn't set up a nice kdump-based system for crash logging and display out of the box, but no one's done it as far as I know. | |
| Jan 10, 2013 at 21:51 | comment | added | Naftuli Kay | While I'm thankful to never ever encounter a BSOD in Linux, it would seem strange to me that while Windows would log and display a problem, Linux wouldn't be able to. | |
| Jan 10, 2013 at 21:45 | comment | added | Naftuli Kay | Okay, I'll do that after backing up my settings. I might first just see if I can reproduce the crash in Windows. | |
| Jan 10, 2013 at 21:28 | comment | added | Scott Lamb | I don't think overclocking failures are as obvious as that to spot in the logs; I'm not a processor expert, but it's not like the whole processor correctly handles the clock cycle or indicates to the OS somehow that it missed it. Let me know if you have trouble getting logs, but IMHO by far the easiest way to know if it's an overclocking problem is to see if it happens when not overclocking. | |
| Jan 10, 2013 at 21:03 | comment | added | Naftuli Kay | If the overclock is the problem, I'll be able to see a clock cycle get missed in crash logs, so at the end of the day, I'll know what the problem is. That's my goal: to figure out what's going wrong. If it's my overclock, then fine, I'd just like to know what the problem is. | |
| Jan 10, 2013 at 20:20 | history | answered | Scott Lamb | CC BY-SA 3.0 |