Method and system for dealing with kernel panic of home gateway system

Abstract

The invention discloses a method and a system for dealing with kernel panic of a home gateway system, and relates to the technical field of Linux kernel exception handling. The method includes following steps: checking and recording register pointer variables of all stacks corresponding to the current system in a CPU register which is abnormal after the system kernel panic; reading kernel panic information in each register pointer variable and saving the information to a global cache area; writing all the kernel panic information of the global cache area into a designated file of a Flash memory; and printing abnormity prompt information to a system terminal according to the kernel panic state of the system, and performing debugging according to the abnormity prompt information and the kernel panic information in the Flash memory by users. According to the method and the system, the kernel panic information is completely captured without depending on serial ports, the handling process is highly-efficient and convenient, and the reusability is high.

Description

technical field [0001] The invention relates to the technical field of Linux kernel exception processing, in particular to a method and system for processing a kernel crash of a home gateway system. Background technique [0002] The Linux system is a multi-user, multi-task, multi-thread and multi-CPU operating system based on POSIX (Portable Operating System Interface of Unix) and Unix. Today, there are already many hardware devices installed with a full version or a cut-down version of the Linux system, such as home gateways, mobile phones, tablets, computers, large servers, etc. [0003] As a user-side terminal product of triple play integration, Linux-based home gateway is widely used and demanded more and more. When developers are developing drivers or users are applying products, they often encounter some kernel panics (Kernel Panic). The so-called kernel panic refers to the action taken by the operating system when it detects an internal fatal error and cannot safely...

AI Technical Summary

Problems solved by technology

If the serial port is not connected in time before the kernel crashes or the serial port is faulty, because the system has crashed and cannot perform any effective input and output, the system cannot effectively output oops information at all, and developers (or users) cannot proceed without oops information. The capture of kernel crash information makes it impossible to accurately locate the problem

[0006] (2) In this processing method, the oops information can only be output to the console or the screen once, and cannot be viewed again after the power is turned off. The developer (or user) can only record it by handwriting or taking pictures. It is more difficult; at the same time, because the screen can only display one page of Oops information (because the information displayed cannot be adjusted through input and output), when there is too much Oops information, the complete content cannot be displayed at all, and the lack of complete oops information is also a problem. Cannot proceed further

Images