Find the answer to your Linux question:
Results 1 to 4 of 4
Hi all, I deployed a Redhat 9 (kernel: 2.4.20-8smp) on a Dell 2650 (2 Xeon CPUs) to act as a file server. I also setup a cron job to run ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Apr 2004
    Location
    Hong Kong
    Posts
    3

    Error Message on Login Screen


    Hi all,

    I deployed a Redhat 9 (kernel: 2.4.20-8smp) on a Dell 2650 (2 Xeon CPUs) to act as a file server. I also setup a cron job to run every minute of rsync for copying files from one location to another location.

    However I sometimes found error message on the login screen like the following quote. What is the possible cause for it? How to solve it?

    Thank you very much.

    Regards,
    Raymond


    --------- Start Quote --------------

    Unable to handle kernel NULL pointer dereference at virtual address 00000080
    printing eip:
    c012c897
    *pde = 00000000
    Oops: 0000
    autofs tg3 ipt_multiport ipt_state ip_conntrack iptable_filter ip_tables keybdev mousedev hid input usb-ohci usbcore ext3 jbd aacraid sd_mod scsi_mod
    CPU: 2
    EIP: 0060:[<c012c897>] Not tainted
    EFLAGS: 00010202

    EIP is at access_process_vm [kernel] 0x27 (2.4.20-8smp)
    eax: 00000000 ebx: e97b7380 ecx: e8eb2000 edx: e9267000
    esi: 00000000 edi: e9267000 ebp: e9267000 esp: e8e43ef0
    ds: 0068 es: 0068 ss: 0068
    Process ps (pid: 6010, stackpage=e8e43000)
    Stack: c015f946 e8d28300 e8e43f10 00000202 00000001 00000000 e8e43f84 e9c2fe00
    f06e600b 00000202 00000000 e9267000 00000000 000002ff 000001f0 e97b7380
    00000000 e9267000 e8eb2000 c017a2b9 e8eb2000 bfffff8f e9267000 00000008
    Call Trace: [<c015f946>] link_path_walk [kernel] 0x656 (0xe8e43ef0))
    [<c017a2b9>] proc_pid_cmdline [kernel] 0x69 (0xe8e43f3c))
    [<c017a6e7>] proc_info_read [kernel] 0x77 (0xe8e43f6c))
    [<c0152457>] sys_read [kernel] 0x97 (0xe8e43f94))
    [<c01517e2>] sys_open [kernel] 0xa2 (0xe8e43fa)
    [<c01098cf>] system_call [kernel] 0x33 (0xe8e43fc0))


    Code: f6 80 80 00 00 00 01 74 2e 81 7c 24 30 40 a2 33 c0 74 24 f0
    <1>Unable to handle kernel NULL pointer dereference at virtual address 00000080
    printing eip:
    c012c897
    *pde = 00000000
    Oops: 0000
    autofs tg3 ipt_multiport ipt_state ip_conntrack iptable_filter ip_tables keybdev mousedev hid input usb-ohci usbcore ext3 jbd aacraid sd_mod scsi_mod
    CPU: 1
    EIP: 0060:[<c012c897>] Not tainted
    EFLAGS: 00010202

    EIP is at access_process_vm [kernel] 0x27 (2.4.20-8smp)
    eax: 00000000 ebx: eda11180 ecx: e5aec000 edx: f34d9000
    esi: 00000000 edi: f34d9000 ebp: f34d9000 esp: e9963ef0
    ds: 0068 es: 0068 ss: 0068
    Process ps (pid: 12821, stackpage=e9963000)
    Stack: c015f946 edb03200 e9963f10 00000202 00000001 00000000 e9963f84 e512f680
    f617400c 00000202 00000000 f34d9000 00000000 000002ff 000001f0 eda11180
    00000000 f34d9000 e5aec000 c017a2b9 e5aec000 bfffff91 f34d9000 00000006
    Call Trace: [<c015f946>] link_path_walk [kernel] 0x656 (0xe9963ef0))
    [<c017a2b9>] proc_pid_cmdline [kernel] 0x69 (0xe9963f3c))
    [<c017a6e7>] proc_info_read [kernel] 0x77 (0xe9963f6c))
    [<c0152457>] sys_read [kernel] 0x97 (0xe9963f94))
    [<c01517e2>] sys_open [kernel] 0xa2 (0xe9963fa)
    [<c01098cf>] system_call [kernel] 0x33 (0xe9963fc0))


    Code: f6 80 80 00 00 00 01 74 2e 81 7c 24 30 40 a2 33 c0 74 24 f0
    <1>Unable to handle kernel NULL pointer dereference at virtual address 00000080
    printing eip:
    c012c897
    *pde = 00000000
    Oops: 0000
    autofs tg3 ipt_multiport ipt_state ip_conntrack iptable_filter ip_tables keybdev mousedev hid input usb-ohci usbcore ext3 jbd aacraid sd_mod scsi_mod
    CPU: 0
    EIP: 0060:[<c012c897>] Not tainted
    EFLAGS: 00010202

    EIP is at access_process_vm [kernel] 0x27 (2.4.20-8smp)
    eax: 00000000 ebx: ef219780 ecx: e50c2000 edx: f42f7000
    esi: 00000000 edi: f42f7000 ebp: f42f7000 esp: e5a21ef0
    ds: 0068 es: 0068 ss: 0068
    Process ps (pid: 13863, stackpage=e5a21000)
    Stack: c015f946 ee2f5600 e5a21f10 00000202 00000001 00000000 e5a21f84 ede20480
    f0b5700c 00000202 00000000 f42f7000 00000000 000002ff 000001f0 ef219780
    00000000 f42f7000 e50c2000 c017a2b9 e50c2000 bfffff54 f42f7000 00000025
    Call Trace: [<c015f946>] link_path_walk [kernel] 0x656 (0xe5a21ef0))
    [<c017a2b9>] proc_pid_cmdline [kernel] 0x69 (0xe5a21f3c))
    [<c017a6e7>] proc_info_read [kernel] 0x77 (0xe5a21f6c))
    [<c0152457>] sys_read [kernel] 0x97 (0xe5a21f94))
    [<c01517e2>] sys_open [kernel] 0xa2 (0xe5a21fa)
    [<c01098cf>] system_call [kernel] 0x33 (0xe5a21fc0))


    Code: f6 80 80 00 00 00 01 74 2e 81 7c 24 30 40 a2 33 c0 74 24 f0
    <4>aacraid:Battery is Charging
    aacraid:Battery charge is now OK
    Unable to handle kernel NULL pointer dereference at virtual address 00000080
    printing eip:
    c012c897
    *pde = 00000000
    Oops: 0000
    autofs tg3 ipt_multiport ipt_state ip_conntrack iptable_filter ip_tables keybdev mousedev hid input usb-ohci usbcore ext3 jbd aacraid sd_mod scsi_mod
    CPU: 0
    EIP: 0060:[<c012c897>] Not tainted
    EFLAGS: 00010202

    EIP is at access_process_vm [kernel] 0x27 (2.4.20-8smp)
    eax: 00000000 ebx: e7c7a580 ecx: eb046000 edx: ec879000
    esi: 00000000 edi: ec879000 ebp: ec879000 esp: ea6e5ef0
    ds: 0068 es: 0068 ss: 0068
    Process ps (pid: 14132, stackpage=ea6e5000)
    Stack: c015f946 f2edf700 ea6e5f10 00000202 00000001 00000000 ea6e5f84 e56e1280
    f689d00c 00000202 00000000 ec879000 00000000 000002ff 000001f0 e7c7a580
    00000000 ec879000 eb046000 c017a2b9 eb046000 bfffff6d ec879000 00000032
    Call Trace: [<c015f946>] link_path_walk [kernel] 0x656 (0xea6e5ef0))
    [<c017a2b9>] proc_pid_cmdline [kernel] 0x69 (0xea6e5f3c))
    [<c017a6e7>] proc_info_read [kernel] 0x77 (0xea6e5f6c))
    [<c0152457>] sys_read [kernel] 0x97 (0xea6e5f94))
    [<c01517e2>] sys_open [kernel] 0xa2 (0xea6e5fa)
    [<c01098cf>] system_call [kernel] 0x33 (0xea6e5fc0))


    Code: f6 80 80 00 00 00 01 74 2e 81 7c 24 30 40 a2 33 c0 74 24 f0

    -------- End Quote -------------------------

  2. #2
    Linux Guru
    Join Date
    Apr 2003
    Location
    London, UK
    Posts
    3,284
    its something to do with the kernel

    I would post it on the kernel mailing list - see here for details: http://www.kernel.org/

    btw, when posting on linuxforums.org, you only need to post your question once.

    Thanks,

    Jason

  3. #3
    Just Joined!
    Join Date
    Apr 2004
    Location
    Hong Kong
    Posts
    3
    Thank you James.

    I will keep an eye on the mailing list archive at http://www.ussg.iu.edu/hypermail/linux/kernel/

    But what would be the subject when you post it? So I can notice your thread easily.

    Thanks again.

    Regards,
    Raymond

  4. #4
    Linux Guru
    Join Date
    Apr 2003
    Location
    London, UK
    Posts
    3,284
    Quote Originally Posted by rayle
    Thank you James.

    I will keep an eye on the mailing list archive at http://www.ussg.iu.edu/hypermail/linux/kernel/

    But what would be the subject when you post it? So I can notice your thread easily.

    Thanks again.

    Regards,
    Raymond
    When i said "I would post it on xxxxx" i meant "If i was you, try posting it on xxxx", & my name is Jason, not James

    sorry for the confusion.

    Jason

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •