Find the answer to your Linux question:
Results 1 to 6 of 6
Hi all Please help me to debug this issue. I have linux kernel2-6.20. I could compile the source with CONFIG_RTC_DRV_PCF8583=y . But while booting, kernel is throwing " Kernel panic ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined! sjremya's Avatar
    Join Date
    May 2010
    Location
    India
    Posts
    39

    Kernel panic - not syncing: Attempted to kill init! - with rtc configuration


    Hi all

    Please help me to debug this issue.

    I have linux kernel2-6.20.

    I could compile the source with CONFIG_RTC_DRV_PCF8583=y. But while booting, kernel is throwing "Kernel panic - not syncing: Attempted to kill init!" . Without RTC configuration, its booting fine.

    Help me to find what I am doing wrong.

    Regards
    SJR

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,601
    What board, processor, etc are you running on? Also, the 2.6.20 kernel tells me that you are probably running Debian Etch (or equivalent), so is this an ARM board?
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined! sjremya's Avatar
    Join Date
    May 2010
    Location
    India
    Posts
    39
    hi .. yes this is on ARM core ....

    The mentioned panic error is disappearing when i run the driver as a module , but getting segmentation fault.



    Code:
    Unable to handle kernel paging request at virtual address dead4eb9
    pgd = c36f8000
    [dead4eb9] *pgd=00000000
    Internal error: Oops: 1 [#1]
    Modules linked in: rtc_isl1221
    CPU: 0
    PC is at i2c_probe+0x194/0x3ac
    LR is at i2c_probe+0x198/0x3ac
    pc : [<c01b0d84>]    lr : [<c01b0d88>]    Not tainted
    sp : c36afe80  ip : 00000000  fp : c36afeb8
    r10: 00000124  r9 : 00000000  r8 : bf002478
    r7 : 00000004  r6 : c02d5a50  r5 : bf0025e8  r4 : c02d5a50
    r3 : dead4ead  r2 : c02c56e0  r1 : c0297e2c  r0 : c02d5a50
    Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  Segment user
    Control: 5317F
    Table: 236F8000  DAC: 00000015
    Process insmod (pid: 801, stack limit = 0xc36ae250)
    Stack: (0xc36afe80 to 0xc36b0000)
    fe80: c48ed000 c48fea94 bf000ae0 00000001 c02d5a50 bf002380 00000000 c3eb0498 
    fea0: 00000026 c48ed000 c48fea94 c36afecc c36afebc bf000074 c01b0c00 c02d5d14 
    fec0: c36afee8 c36afed0 c01b1cdc bf000050 c3eb046c c3eb02a8 bf002660 c36afef8 
    fee0: c36afeec bf00404c c01b1c00 c36affa4 c36afefc c00575b0 bf004010 00000000 
    ff00: 00094008 00000000 00000000 00000000 00000000 00000000 00000000 00000000 
    ff20: 00000000 00000000 00000000 00000000 00000000 0000000a c49057e4 c3eb8b3c 
    ff40: c48ff034 c48fecec c48ff05c 00000000 000000a9 000000a9 bf00266c c48fe959 
    ff60: 00000026 c023da18 c48ff084 0000003c 00000024 00000000 00000000 00018dee 
    ff80: 000909bc 0007bd78 00000080 c0022f04 c36ae000 bee5ee44 00000000 c36affa8 
    ffa0: c0022d60 c00562a4 000909bc 0007bd78 00900080 00094018 00018dee 00094008 
    ffc0: 00018dee 000909bc 0007bd78 00000000 bee5ef1a 00000002 bee5ee44 00000000 
    ffe0: bee5ec30 bee5ec24 0003fe6c 401e2520 60000010 00900080 00000000 00000000 
    Backtrace: 
    [<c01b0bf0>] (i2c_probe+0x0/0x3ac) from [<bf000074>] (isl1221_attach_adapter+0x34/0x50 [rtc_isl1221])
    [<bf000040>] (isl1221_attach_adapter+0x0/0x50 [rtc_isl1221]) from [<c01b1cdc>] (i2c_register_driver+0xec/0x154)
     r4 = C02D5D14 
    [<c01b1bf0>] (i2c_register_driver+0x0/0x154) from [<bf00404c>] (isl1221_init+0x4c/0x7c [rtc_isl1221])
     r6 = BF002660  r5 = C3EB02A8  r4 = C3EB046C 
    [<bf004000>] (isl1221_init+0x0/0x7c [rtc_isl1221]) from [<c00575b0>] (sys_init_module+0x131c/0x1428)
    [<c0056294>] (sys_init_module+0x0/0x1428) from [<c0022d60>] (ret_fast_syscall+0x0/0x2c)
    Code: ebfa1f76 e596300c e1a00006 e1a0e00f (e593f00c) 
     Segmentation fault

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,601
    Well, I think that configuration directive is for a specific hardware RTC, which some systems may not have, hence the panic and/or segfault - likely due to missing hardware. I have an ARM board where the hardware RTC (battery backed up) is an option, not part of the standard board. If your board has a hardware RTC, make sure it is what your configuration is specifying. It may be a different make/model and needs a different configuration option.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  5. #5
    Just Joined! sjremya's Avatar
    Join Date
    May 2010
    Location
    India
    Posts
    39
    Thanks for the response.

    I have isl 1221 rtc in my board, which doesnot have a driver in linux version 2.6.20. I have made a patch for the mentioned ic and altered the available driver for isl1208. I have changed the following files for obtaining configuration for isl 1221 chip
    drivers/rtc/Kconfig
    drivers/rtc/Makefile
    drivers/rtc/rtc-isl1221.c
    include/linux/i2c-id.h
    So I must dig into the driver s/w ? [ I have not done many changes in isl 1208 driver code to develop isl 1221 driver ]

    Have any body tried with ISL1221 RTC chip before?

    Regards
    SJR


  6. #6
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,601
    Sorry, but I'm not familiiar with this chip. I'd need full interfacing data in order to modify or develop a driver for this. Since you have done so, and yet the system is giving your a panic, you need to further analyze your code.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

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