Random Crashes

Maybe it´s hardware related.

When did that start to happen?

- After a kernel upgrade? In this case, please try with the previous kernel version.
- Spontaneously? Please do a RAM test (in the boot menu).

It´s currently package "2.6.15-26.47". There were some package updates.. some kernel changes over the time.

RAMs should be fine.

Any idea what excatly this is about ?

I see how dozens of errors happens first, until the server crashes.

Well, some suggestions please. It´s kinda urgent.

Some Update:

http://www.animemanga.de/test/5.jpg
http://www.animemanga.de/test/6.jpg

Maybe this shows more.

What does "Unable to handle kernel Null pointer" should tell me ?

Triaged to Invalid. Links to log file images no longer valid. Probably hardware related, not enough info to troubleshoot further.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!