https://bugzilla.novell.com/show_bug.cgi?id=671551
https://bugzilla.novell.com/show_bug.cgi?id=671551#c11
Jan Kara changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |jimoe@sohnen-moe.com
--- Comment #11 from Jan Kara 2011-04-20 16:57:43 UTC ---
Yeah. The traces are all over the mm/fs code and seem to be caused by memory
corruption. For example:
BUG: unable to handle kernel paging request at 000000000000ff18
IP: [<ffffffff81244674>] __lookup+0x94/0xc0
PGD 50bed067 PUD 55fad067 PMD 0
Oops: 0000 [#1] PREEMPT SMP
last sysfs file: /sys/devices/virtual/net/vboxnet0/statistics/collisions
CPU 3
Modules linked in: vboxnetadp vboxnetflt vboxdrv fuse ip6t_LOG xt_tcpudp
xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device
edd nls_utf8 cifs ip6t_REJECT nf_conntrack_ipv6 fglrx(P) ip6table_raw
xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter cpufreq_conservative
cpufreq_userspace cpufreq_powersave powernow_k8 mperf ip6table_mangle
nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables
ip6table_filter ip6_tables x_tables loop dm_mod firewire_ohci firewire_core
crc_itu_t ppdev parport_pc ohci1394 sr_mod cdc_acm parport
snd_hda_codec_atihdmi usb_storage cdrom sg k10temp pcspkr ieee1394 i2c_piix4
r8169 button floppy snd_hda_codec_realtek edac_core edac_mce_amd asus_atk0110
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore
snd_page_alloc wmi ext4 jbd2 crc16 sd_mod fan processor ata_generic sym53c8xx
scsi_transport_spi ahci pata_atiixp libata scsi_mod thermal thermal_sys [last
unloaded: vboxd rv]
Pid: 29453, comm: VBoxSVC Tainted: P 2.6.34.7-0.7-desktop #1
M3A78-EM/System Product Name
RIP: 0010:[<ffffffff81244674>] [<ffffffff81244674>] __lookup+0x94/0xc0
RSP: 0018:ffff88005a67fcb8 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000040 RCX: 0000000000000000
RDX: 0000000000324101 RSI: ffff88005a67fde0 RDI: 000000000000ff00
RBP: ffffffffffffffc0 R08: ffff88005a67fcd8 R09: 000000000000000b
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88005a67fdc8
R13: ffff88009edf08f0 R14: 0000000000ffffff R15: ffff88005a67fcd8
FS: 00007f5ae5864710(0000) GS:ffff880001f80000(0000) knlGS:00000000f39feb70
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000000000ff18 CR3: 000000003a622000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff4ff0 DR7: 0000000000000400
Process VBoxSVC (pid: 29453, threadinfo ffff88005a67e000, task
ffff88005a7e0700)
Stack:
0000000000000003 000000000000000e ffffffff812447d7 ffffea0002b8bb80
<0> 0000000000324000 ffff88005a67fdc8 ffff88012394c9f8 000000000000000e
<0> 00000000003206e7 0000000000000000 0000000000000000 ffffffff810da86c
Call Trace:
[<ffffffff812447d7>] radix_tree_gang_lookup_slot+0x67/0xa0
..
We have spotted 0xff00 where should have been either NULL or a pointer. Other
traces are similar (some trigger kernel assertions instead of making kernel
dereference invalid address).
Catching memory corruption is always tricky. I guess running without Virtual
Box is out of question since that is what puts the load to the machine, isn't
it? You could debug this a bit further by enabling some kernel debugging
options (I can tell you which if you are interested) so that we see whether
we'll be able to catch the code which is corrupting memory.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.