Difference between revisions of "Talk:Kernel Panics"
(→Intent to update Kernel Panics article: re)
(→Intent to update Kernel Panics article: Moved this article to its own section in "General troubleshooting".)
|(3 intermediate revisions by 2 users not shown)|
|Line 40:||Line 40:|
21:01, 3 October 2017 (UTC)
21:01, 3 October 2017 (UTC)
:Feel free to proceed, though since this will be a full rewrite I'd like to remind that [[ArchWiki:Contributing#The_3_fundamental_rules]] should be followed. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:13, 3 October 2017 (UTC)
:Feel free to proceed, though since this will be a full rewrite I'd like to remind that [[ArchWiki:Contributing#The_3_fundamental_rules]] should be followed. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:13, 3
October 2017 (UTC)
Latest revision as of 22:27, 17 October 2017
How do I make computer automaticaly restart after kernel panic? Obsrv 22:53, 30 September 2008 (EDT)
- http://www.google.com/search?hl=en&q=linux+restart+%22kernel+panic%22 --byte 20:28, 2 October 2008 (EDT)
If one uses arch to login, the response to the mount command is "mount: only root can do that". You might want to try root instead. - KitchM 00:14, 22 October 2009 (EDT)
Need to explain how to identify the last kernel used. - KitchM 00:38, 22 October 2009 (EDT)
"Recovery Console" evolved
It would be nice to add that as a sort of countermeasure there is the possibility of add init=/bin/sh to the grub's kernel line in order to quickly access the battlefield and solve some things without a rescue cd.
I'm having some troubles with a possible kernel panic. I found this page disagrees with the actual Chroot page. So while I procrastinate on my own problem and attempt to take a breather before all my hair falls out, I thought I would make this suggestion. Either one of these pages should be updated to agree with the other. The Chroot article has a newer edit date so I tend to think it should be the standard.
- Chroot article reads
mount -t proc proc proc/ mount -t sysfs sys sys/ mount -o bind /dev dev/(user has already "cd /mnt/arch" hence no leading /mnt/)
- Kernel Panics article reads
# mount -t proc none /mnt/proc # mount -t sysfs none /mnt/sys # mount --bind /dev /mnt/dev"
Perhaps the end result is equal or insignificant but it is a bit confusing for someone who relies on these articles, e.g. me.
Intent to update Kernel Panics article
Hi. I would like to take a stab at updating this article with consideration given to the above comments. My approach would be to write the article here under Kernel Panics with the final goal of integrating it into General troubleshooting once it passes muster. 21:01, 3 October 2017 (UTC)
- Feel free to proceed, though since this will be a full rewrite I'd like to remind that ArchWiki:Contributing#The_3_fundamental_rules should be followed. #3 already accomplished ;) -- Lahwaacz (talk) 21:13, 3 October 2017 (UTC)
- Got it: use edit summary, and make many small edits rather than few large ones so its easier to check. Okay. 21:40, 3 October 2017 (UTC)
- I have completed my revison of this article and will post it shortly. I have change the focus somewhat, from general procedures like re-installing a kernel and rolling back faulty software to info specific to kernel panics--what they are, what causes them, how to read an oops crash dump, and how to get back "into" the machine after a panic happens. This seems to make sense in the context of the proposal to merge this article into General troubleshooting. I think it would fit well as a 2nd level section immediately following General troubleshooting#Boot problems. Mcnster (talk) 20:26, 8 October 2017 (UTC)
- Its been 9 days since I posted my edits. I'll assume silence equals a consensus of "That's fine. Proceed." So I am moving this article into a 2nd level section immediately following General troubleshooting#Boot problems, as directed in the Merge template. 22:26, 17 October 2017 (UTC)