The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Possible kernel BUG

Discussion in 'General Discussion' started by ukagg, Mar 14, 2007.

  1. ukagg

    ukagg Active Member

    Joined:
    Aug 14, 2002
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Hi,

    My CentOS4.4 server (kernel 2.6.9-42.0.3.ELsmp) stopped responding. After reboot I found following were the last messages in /var/log/messages:-

    Mar 15 01:05:01 ns7 kernel: eip: c0120afc
    Mar 15 01:05:01 ns7 kernel: ------------[ cut here ]------------
    Mar 15 01:05:01 ns7 kernel: kernel BUG at include/asm/spinlock.h:133!
    Mar 15 01:05:01 ns7 kernel: invalid operand: 0000 [#1]
    Mar 15 01:05:01 ns7 kernel: SMP
    Mar 15 01:05:01 ns7 kernel: Modules linked in: loop ipt_owner iptable_mangle ip_conntrack_ftp ipt_conntrack ipt_REJECT ipt_LOG ipt_limit ipt_multiport ipt_state ip_conntrack md5 ipv6 autofs4 iptable_filter ip_tables dm_mirror dm_mod button battery ac uhci_hcd ehci_hcd hw_random snd_azx snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc tg3 floppy ext3 jbd ata_piix libata sd_mod scsi_mod
    Mar 15 01:05:01 ns7 kernel: CPU: 1
    Mar 15 01:05:01 ns7 kernel: EIP: 0060:[<c02d335a>] Not tainted VLI
    Mar 15 01:05:01 ns7 kernel: EFLAGS: 00010216 (2.6.9-42.0.3.ELsmp)
    Mar 15 01:05:01 ns7 kernel: EIP is at _spin_lock+0x1c/0x34
    Mar 15 01:05:01 ns7 kernel: eax: c02e7076 ebx: f6cd884c ecx: d8509f0c edx: c0120afc
    Mar 15 01:05:01 ns7 kernel: esi: d65f52dc edi: c83ddcd4 ebp: c31c5080 esp: d8509f10
    Mar 15 01:05:01 ns7 kernel: ds: 007b es: 007b ss: 0068
    Mar 15 01:05:01 ns7 kernel: Process lfd (pid: 14691, threadinfo=d8509000 task=f70f6130)
    Mar 15 01:05:01 ns7 kernel: Stack: f639be80 c0120afc 00000000 00000000 f7270f58 f7270f60 f7270f48 d8509000
    Mar 15 01:05:01 ns7 kernel: f64b6380 d6ee8c30 d5291980 00000000 00000000 d6ee8c30 c01216da d8509fc4
    Mar 15 01:05:01 ns7 kernel: bfeb1298 01200011 d8509fc4 01200011 00000000 00003b23 c0121c13 00000000
    Mar 15 01:05:01 ns7 kernel: Call Trace:
    Mar 15 01:05:01 ns7 kernel: [<c0120afc>] copy_mm+0x268/0x383
    Mar 15 01:05:01 ns7 kernel: [<c01216da>] copy_process+0x6ae/0xafb
    Mar 15 01:05:01 ns7 kernel: [<c0121c13>] do_fork+0x8e/0x175
    Mar 15 01:05:01 ns7 kernel: [<c010498a>] sys_clone+0x22/0x26
    Mar 15 01:05:01 ns7 kernel: [<c02d47cb>] syscall_call+0x7/0xb
    Mar 15 01:05:01 ns7 kernel: Code: 00 75 09 f0 81 02 00 00 00 01 30 c9 89 c8 c3 53 89 c3 81 78 04 ad 4e ad de 74 18 ff 74 24 04 68 76 70 2e c0 e8 46 f5 e4 ff 58 5a <0f> 0b 85 00 e1 60 2e c0 f0 fe 0b 79 09 f3 90 80 3b 00 7e f9 eb
    Mar 15 01:05:01 ns7 kernel: <0>Fatal exception: panic in 5 seconds


    Can someone suggest me if this can be fixed by updating the kernel with yum or is it some other (like hardware or firewall) issue?

    Thanks
    UKA
     
  2. AndyReed

    AndyReed Well-Known Member
    PartnerNOC

    Joined:
    May 29, 2004
    Messages:
    2,222
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Minneapolis, MN
  3. ukagg

    ukagg Active Member

    Joined:
    Aug 14, 2002
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Thanks!

    I understand I must upgrade to 2.6.9-42.0.10.ELsmp.

    Can you suggest me the commands to upgrade kernel using yum?

    UKA
     
  4. tanq

    tanq Member

    Joined:
    Nov 11, 2003
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    0
    Depends, do you have one or more CPU's -> 1st or 2nd command:
    yum install kernel
    yum install kernel-smp
     
  5. dalem

    dalem Well-Known Member
    PartnerNOC

    Joined:
    Oct 24, 2003
    Messages:
    2,577
    Likes Received:
    40
    Trophy Points:
    48
    Location:
    SLC
    cPanel Access Level:
    DataCenter Provider
    GruB loader
    yum install kernel-smp
    nano /etc/grub.conf and add the new kernel above the other kernels listed in same format (should have been done by using yum) changing kernel ver
    set your default to to your current working kernel
    save
    grub
    enter "savedefault --default=0 --once" at the promt without the quotes
    exit
    shutdown -r now

    if it does not come back on line power cycle the server to reboot to old kernel (if you do not have physical access or a remote reboot port have your data center reboot)

    if server comes on line and runs well with the new kernel nano /ect/grub.conf and set your default kernel
    default=0
    save


    using lilo boot loader
    yum install kernel-smp
    lilo -v -v
    lilo -R <latest kernel package>
    shutdown -r now

    make sure that no errors appear when you run lilo
    The lilo -R command will make it boot once to the new kernel
    if it does not come back on line power cycle the server to reboot to old kernel (if you do not have physical access or a remote reboot port have your data center reboot)

    if server comes on line and runs well with the new kernel edit lilo.conf to boot to the new kernel
    nano /etc/lilo.conf and set "default=" the new kernel label
     
Loading...

Share This Page