Munin-graph cause kernel problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am running munin on a AMD64 box widget op146 AMD CPU, 1G memeory. at the beginning evry thing is ok, but after hours or days, dmesg shows message like below. and htop, ps will freeze on execution. reboot command will not work, only can restart the machine with hardware switch. This problem happens since I upgraded the machine from 7.10 to 8.04. and until 2.6.24-19-server kernel of 8.04, it still exists.
[33526.249351] Unable to handle kernel NULL pointer dereference at 0000000000000010 RIP:
[33526.249356] [<ffffffff80351
[33526.249362] PGD 3d552067 PUD 35a61067 PMD 0
[33526.249365] Oops: 0000 [1] SMP
[33526.249368] CPU 0
[33526.249369] Modules linked in: rfcomm l2cap bluetooth af_packet nfsd auth_rpcgss exportfs powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_
[33526.249435] Pid: 31031, comm: munin-graph Not tainted 2.6.24-19-server #1
[33526.249437] RIP: 0010:[<
[33526.249441] RSP: 0018:ffff81003a
[33526.249443] RAX: 0000000000000000 RBX: ffff81003ccad9d0 RCX: ffff81003ccada80
[33526.249445] RDX: 0000000000000000 RSI: ffff81002b598008 RDI: 0000000000000000
[33526.249447] RBP: ffff81002b598008 R08: ffff81003ccadb30 R09: 0000000000000012
[33526.249449] R10: 0000000000000000 R11: 0000000000000206 R12: ffff81003ccad8f0
[33526.249451] R13: ffff81003ccad8f0 R14: ffff81003ccad9a0 R15: ffff81003ccad9b8
[33526.249453] FS: 00007f525b1466e
[33526.249455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[33526.249457] CR2: 0000000000000010 CR3: 000000003d8a0000 CR4: 00000000000006e0
[33526.249459] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[33526.249461] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[33526.249463] Process munin-graph (pid: 31031, threadinfo ffff81003a1a2000, task ffff810010014000)
[33526.249465] Stack: 00007f5257d03000 ffff81002b598000 ffffffff8029aacd ffff810025c3a3c8
[33526.249469] ffff81002b598008 00007f5257d10000 ffffffff80470762 ffff81003ccad9a0
[33526.249472] ffff81002b598000 0000000000000000 ffff81002b598060 00007f5257d03000
[33526.249475] Call Trace:
[33526.249483] [<ffffffff8029a
[33526.249492] [<ffffffff80470
[33526.249506] [<ffffffff8029a
[33526.249517] [<ffffffff8020c
[33526.249542]
[33526.249543]
[33526.249544] Code: 48 8b 4f 10 48 85 c9 74 09 f6 01 01 0f 84 5d 01 00 00 48 8b
[33526.249550] RIP [<ffffffff80351
[33526.249553] RSP <ffff81003a1a3ee0>
[33526.249554] CR2: 0000000000000010
[33526.249559] ---[ end trace 14e3ffe35fc4e7aa ]---
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.