Munin-graph cause kernel problem

Bug #238457 reported by ty_2000
4
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] [<ffffffff803517d0>] rb_erase+0xd0/0x2f0
[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_conservative video output sbs sbshc dock container battery ip6table_filter iptable_raw xt_comment xt_policy ipt_ULOG ipt_TTL ipt_ttl ipt_TOS ipt_tos ipt_SAME ipt_REJECT ipt_REDIRECT ipt_recent ipt_owner ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_iprange ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_NFQUEUE xt_NFLOG xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_helper xt_hashlimit ip6_tables xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables ipv6 ac w83627ehf hwmon_vid ip_vs sbp2 ieee1394 parport_pc lp parport nfs lockd nfs_acl sunrpc psmouse serio_raw button i2c_nforce2 i2c_core shpchp pci_hotplug k8temp evdev pcspkr ext3 jbd mbcache sg sd_mod sata_nv pata_amd pata_acpi floppy ata_generic skge ehci_hcd ohci_hcd forcedeth libata usbcore scsi_mod raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod dm_mirror dm_snapshot dm_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse loop
[33526.249435] Pid: 31031, comm: munin-graph Not tainted 2.6.24-19-server #1
[33526.249437] RIP: 0010:[<ffffffff803517d0>] [<ffffffff803517d0>] rb_erase+0xd0/0x2f0
[33526.249441] RSP: 0018:ffff81003a1a3ee0 EFLAGS: 00010282
[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: 00007f525b1466e0(0000) GS:ffffffff805c4000(0000) knlGS:0000000000000000
[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] [<ffffffff8029aacd>] do_munmap+0x1cd/0x2f0
[33526.249492] [<ffffffff80470762>] __down_write_nested+0x12/0xb0
[33526.249506] [<ffffffff8029ac3d>] sys_munmap+0x4d/0x80
[33526.249517] [<ffffffff8020c37e>] system_call+0x7e/0x83
[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 [<ffffffff803517d0>] rb_erase+0xd0/0x2f0
[33526.249553] RSP <ffff81003a1a3ee0>
[33526.249554] CR2: 0000000000000010
[33526.249559] ---[ end trace 14e3ffe35fc4e7aa ]---

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi tangy,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 238457

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
ty_2000 (tangy) wrote :

Maybe it is a problem of hard disk. Since we experienced crash for several times, we changed a new disk, installed 9.04, and still let it doing the same work as before. No such problem happens any more for a week now. Thank you so much.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update. Indeed this sounds like it was a hw issue. I'll go ahead and close this bug. Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.