BUG: unable to handle kernel paging request at 000001a400015ff4
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How did this system get to be the way it is today? Has it recently been updated? Have any new drivers been recently added? How long ago was the system last considered to be "stable," and exactly what has happened since then?
No one can help you, really, if all that you post is "one smear of blood on the pavement." Software exceptions can only be understood in context. You must weigh clues, and observations, to isolate a problem in a system of this size and complexity.
Messages such as "interrupt took too long" also suggest the possibility of a hardware failure or imminent-failure, which must also be considered.
Please provide some of this background information about this incident.
System is originally based on Kernel 3.4.2 on Fedora 16 and stable. Recently, I updated the system with kernel 4.4.0. Stock kernel drivers are being used and no customization except ported some latest TIPC patches to fix some TIPC issues.
All 6 routing CPUs went down over the course of the weekend. The noted output is from one CPU; others are unknown, but assumed to have gone down with the same cause. Also note that in addition, one of the routing cards (no output available) went down again on Monday. The issue is not reproducible on demand.
The new kernel 4.4.0 is being used in the system Since April 1st, and seen the issue 3 times so far. All these times, mostly heartbeat type traffic, not heavy traffic.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.