Re: possible kernel bug?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hi,

thanks for the fast reply, but I didn't compile any modules myself.

it's a plain/minimal centos kvm-hostsystem - just libvirt/kvm/lvm.

Which module do you blame?

Fabian


2014-04-02 13:55 GMT+02:00 Mike McCarthy <sysop@xxxxxxxx>:

> My guess would be the video driver needs to be rebuilt to match the kernel.
>
> Mike
>
> On 04/02/2014 07:52 AM, Fabian Zimmermann wrote:
> > Hello,
> >
> > i'm using centos 6.5. It was running fine for months. 2-3 days ago I
> > updated the system incl. kernel, but now the system is restarting once a
> > day caused by a panic.
> >
> > --
> > <1>BUG: unable to handle kernel paging request at 000000004d000001
> > <1>IP: [<ffffffff810657f3>] load_balance_fair+0x2a3/0x300
> > <4>PGD 0
> > <4>Oops: 0000 [#1] SMP
> > <4>last sysfs file: /sys/kernel/mm/ksm/run
> > <4>CPU 0
> > <4>Modules linked in: ebtable_nat ebtables ipt_MASQUERADE iptable_nat
> > nf_nat xt_CHECKSUM iptable_mangle autofs4 cpufreq_ondemand acpi_cpufreq
> > freq_table mperf bridge stp llc ipt_REJECT nf_conntrack_ipv4
> nf_defrag_ipv4
> > iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
> > xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ext3 jbd vhost_net
> > macvtap macvlan tun kvm_intel kvm ppdev parport_pc parport iTCO_wdt
> > iTCO_vendor_support microcode r8169 mii i2c_i801 sg lpc_ich mfd_core
> shpchp
> > ext4 jbd2 mbcache raid1 sd_mod crc_t10dif ahci xhci_hcd wmi i915
> > drm_kms_helper drm i2c_algo_bit i2c_core video output dm_mirror
> > dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
> > <4>
> > <4>Pid: 23490, comm: qemu-kvm Not tainted 2.6.32-431.11.2.el6.x86_64 #1
> MSI
> > MS-7816/H87-G43 (MS-7816)
> > <4>RIP: 0010:[<ffffffff810657f3>]  [<ffffffff810657f3>]
> > load_balance_fair+0x2a3/0x300
> > <4>RSP: 0018:ffff8806c0045a98  EFLAGS: 00010046
> > <4>RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000002
> > <4>RDX: ffff8806c004d440 RSI: ffff88040e872200 RDI: ffff8806c004d400
> > <4>RBP: ffff8806c0045b58 R08: 0000000000000000 R09: 0000000000000001
> > <4>R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
> > <4>R13: 0000000000000000 R14: 0000000000000002 R15: ffff8806c004d400
> > <4>FS:  00007f6215948700(0000) GS:ffff880028200000(0000)
> > knlGS:0000000000000000
> > <4>CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
> > <4>CR2: 000000004d000001 CR3: 00000003ee2dd000 CR4: 00000000001427e0
> > <4>DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > <4>DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> > <4>Process qemu-kvm (pid: 23490, threadinfo ffff8806c0044000, task
> > ffff8803ee039540)
> > <4>Stack:
> > <4> 0000000000000402 00000000000001fc ffff88038d4ca000 00000000000001fc
> > <4><d> ffff880028216840 00000000000001fc 0000000100000000
> 000000000000002a
> > <4><d> 0000000000000002 ffff880028316840 0000000000000000
> ffff88002820fbe0
> > <4>Call Trace:
> > <4> [<ffffffff81528350>] thread_return+0x46e/0x76e
> > <4> [<ffffffffa0292db5>] kvm_vcpu_block+0x75/0xc0 [kvm]
> > <4> [<ffffffff8109b290>] ? autoremove_wake_function+0x0/0x40
> > <4> [<ffffffffa02a73d7>] kvm_arch_vcpu_ioctl_run+0x627/0x10b0 [kvm]
> > <4> [<ffffffffa028eb04>] kvm_vcpu_ioctl+0x434/0x580 [kvm]
> > <4> [<ffffffff81060b13>] ? perf_event_task_sched_out+0x33/0x70
> > <4> [<ffffffff8100bb8e>] ? apic_timer_interrupt+0xe/0x20
> > <4> [<ffffffff8119dc12>] vfs_ioctl+0x22/0xa0
> > <4> [<ffffffff8119e0da>] do_vfs_ioctl+0x3aa/0x580
> > <4> [<ffffffff8100bb8e>] ? apic_timer_interrupt+0xe/0x20
> > <4> [<ffffffffa029b6ab>] ? kvm_on_user_return+0x7b/0x90 [kvm]
> > <4> [<ffffffff8119e331>] sys_ioctl+0x81/0xa0
> > <4> [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
> > <4>Code: 8b 55 18 41 8b 45 20 3b 02 7d 02 89 02 4c 89 ff 4d 89 f4 e8 60
> ee
> > ff ff 49 89 c5 4d 85 ed 0f 85 78 ff ff ff 0f 1f 40 00 4c 89 e1 <4c> 8b b4
> > 58 ff ff ff 4c 8b a5 50 ff ff ff 4c 8b bd 48 ff ff ff
> > <1>RIP  [<ffffffff810657f3>] load_balance_fair+0x2a3/0x300
> > <4> RSP <ffff8806c0045a98>
> > <4>CR2: 000000004d000001
> > --
> >
> > Any hints/tipps how to pin down the problem?
> >
> > Thanks a lot,
> >
> > Fabian
> > _______________________________________________
> > CentOS mailing list
> > CentOS@xxxxxxxxxx
> > http://lists.centos.org/mailman/listinfo/centos
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos




[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux