Re: [oselas] Kernel panic after electricity was away.
Hi Rudi, Lappies wrote: Hello Jörg, Nearly. My name is Jürgen... From the other mail: and here the bootlog, sorry Hmm, U-Boot 1.3.2-mini2440 (Feb 24 2010 - 13:04:49) [...] Seems no software from our Mini2440 BSP. [...] Linux version 2.6.39.1 (root@testbox) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 Sun Jun 19 22:32:25 CEST 2011 [...] Not a toolchain we support and not a kernel we support. Sorry, I must give up at this point, because I have no clue what software you are using. Regards, Juergen
Re: [oselas] Kernel panic after electricity was away.
Hello Jürgen, Am 05.03.2015 um 18:24 schrieb Juergen Borleis: Hi Rudi, Lappies wrote: Hello Jörg, Nearly. My name is Jürgen... Sorry for that! ;-) From the other mail: and here the bootlog, sorry Hmm, U-Boot 1.3.2-mini2440 (Feb 24 2010 - 13:04:49) [...] Seems no software from our Mini2440 BSP. [...] Linux version 2.6.39.1 (root@testbox) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 Sun Jun 19 22:32:25 CEST 2011 [...] Not a toolchain we support and not a kernel we support. Sorry, I must give up at this point, because I have no clue what software you are using. Ok, I understand, bad luck for me. :-( Thank you anyway for the answers! This baby must sleep now for a while, I don´t have the time to spend hours to get this going again. Wisch you all the best! Regards, Juergen Regards Rudi
Re: [oselas] Kernel panic after electricity was away.
Hi Rudi, On Saturday 28 February 2015 11:16:14 Lappies wrote: [...] Hm, hardware issue? SDCard or the mini itself? I dont have a nother SDCard to hand to test. [...] mmc: Probing for SDHC ... mmc: SD 2.0 or later card found trying to detect SD Card... Manufacturer: 0x03, OEM SD Product name: SD04G, revision 8.0 Serial number: 2156201412 Manufacturing date: 8/2009 CRC:0x56, b0 = 1 READ_BL_LEN=15, C_SIZE_MULT=0, C_SIZE=365 size = 0 SD Card detected RCA: 0x8c3b type: SDHC 1574144 bytes read [...] It seems you load the kernel from the SD card, don't you? If you do so, I guess now there is no hardware issue. [...] See attachment for whole boot log. [...] s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-rtc s3c2410-rtc: setting system clock to 2015-02-28 10:03:38 UTC (1425117818) Waiting for root device /dev/mmcblk0p3... s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz). s3c-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz). mmc0: new SDHC card at address 8c3b mmcblk0: mmc0:8c3b SD04G 3.69 GiB (ro) mmcblk0: p1 p2 p3 [...] Looks correctly to me. Please do the following: run ptxdist kernelconfig and enable General setup --- -*- Configure standard kernel features (expert users) --- [*] Load all symbols for debugging/ksymoops [*] Include all symbols in kallsyms Rebuild and boot this kernel. This will show the stack backstrace with symbols which may help to find the real cause of your kernel Oops. Regards, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ |
Re: [oselas] Kernel panic after electricity was away.
Hello Jürgen, Am 27.02.2015 um 09:10 schrieb Juergen Borleis: Hi Rudi, On Thursday 26 February 2015 21:42:53 Lappies wrote: Like I said I have setup my SDCard with new Partition and formated it new. Copy my Backups back on the SDCard. Here are the output of your command. testbox:/home/rudi/kernel/linux-2.6.39.1# addr2line -e vmlinux 0xc00b139c /home/rudi/kernel/linux-2.6.39.1/fs/block_dev.c:1275 Hm, hardware issue? SDCard or the mini itself? I dont have a nother SDCard to hand to test. Doesn´t say me much. :-( Just to make sure I unterstand where things broke. The System boot from my uImage, get to the point to where it should load the root FS and then things broke up, correct? Can you send us the whole boot log (from power on, until it fails)? See attachment for whole boot log. Regards, Juergen U-Boot 1.3.2-mini2440 (Feb 24 2010 - 13:04:49) I2C: ready DRAM: 64 MB Flash: 2 MB NAND: 256 MiB Found Environment offset in OOB.. USB: S3C2410 USB Deviced In:serial Out: serial Err: serial MAC: 08:08:11:18:12:27 Hit any key to stop autoboot: 0 mmc: Probing for SDHC ... mmc: SD 2.0 or later card found trying to detect SD Card... Manufacturer: 0x03, OEM SD Product name: SD04G, revision 8.0 Serial number: 2156201412 Manufacturing date: 8/2009 CRC:0x56, b0 = 1 READ_BL_LEN=15, C_SIZE_MULT=0, C_SIZE=365 size = 0 SD Card detected RCA: 0x8c3b type: SDHC 1574144 bytes read ## Booting kernel from Legacy Image at 3200 ... Image Name: Linux-2.6.39.1 Created: 2011-06-19 20:33:19 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1574080 Bytes = 1.5 MB Load Address: 30008000 Entry Point: 30008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.39.1 (root@testbox) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 Sun Jun 19 22:32:25 CEST 2011 CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177 CPU: VIVT data cache, VIVT instruction cache Machine: MINI2440 Memory policy: ECC disabled, Data cache writeback CPU S3C2440A (id 0x32440001) S3C24XX Clocks, Copyright 2004 Simtec Electronics S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: console=ttySAC0,115200 root=/dev/mmcblk0p3 rootfstype=ext3 mini2440=3tb rw rootwait PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 61612k/61612k available, 3924k reserved, 0K highmem Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xfff0 - 0xfffe ( 896 kB) DMA : 0xffc0 - 0xffe0 ( 2 MB) vmalloc : 0xc480 - 0xf600 ( 792 MB) lowmem : 0xc000 - 0xc400 ( 64 MB) modules : 0xbf00 - 0xc000 ( 16 MB) .init : 0xc0008000 - 0xc0022000 ( 104 kB) .text : 0xc0022000 - 0xc02e8470 (2842 kB) .data : 0xc02ea000 - 0xc0309760 ( 126 kB) SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:85 irq: clearing pending status 0200 irq: clearing subpending status 0002 Console: colour dummy device 80x30 console [ttySAC0] enabled Calibrating delay loop... 201.52 BogoMIPS (lpj=503808) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 MINI2440: Option string mini2440=3tb MINI2440: LCD 0:240x320 1:800x480 2:1024x768 [3:240x320] 4:640x480 5:240x320 S3C2440: Initialising architecture S3C2440: IRQ Support S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics DMA channel 0 at c4808000, irq 33 DMA channel 1 at c4808040, irq 34 DMA channel 2 at c4808080, irq 35 DMA channel 3 at c48080c0, irq 36 S3C244X: Clock Support, DVS off s3c-adc s3c24xx-adc: attached adc driver S3C24XX CPU Frequency driver, s3c244x cpu support bio: create slab bio-0 at 0 usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb s3c-i2c s3c2440-i2c: slave address 0x10 s3c-i2c s3c2440-i2c: bus frequency set to 98 KHz s3c-i2c s3c2440-i2c: i2c-0: S3C I2C adapter Advanced Linux Sound Architecture Driver Version 1.0.24. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 JFFS2 version
Re: [oselas] Kernel panic after electricity was away.
Hi Rudi, On Thursday 26 February 2015 21:42:53 Lappies wrote: Like I said I have setup my SDCard with new Partition and formated it new. Copy my Backups back on the SDCard. Here are the output of your command. testbox:/home/rudi/kernel/linux-2.6.39.1# addr2line -e vmlinux 0xc00b139c /home/rudi/kernel/linux-2.6.39.1/fs/block_dev.c:1275 Hm, hardware issue? Doesn´t say me much. :-( Just to make sure I unterstand where things broke. The System boot from my uImage, get to the point to where it should load the root FS and then things broke up, correct? Can you send us the whole boot log (from power on, until it fails)? Regards, Juergen -- Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ |
Re: [oselas] Kernel panic after electricity was away.
Hi Jürgen, Like I said I have setup my SDCard with new Partition and formated it new. Copy my Backups back on the SDCard. Here are the output of your command. testbox:/home/rudi/kernel/linux-2.6.39.1# addr2line -e vmlinux 0xc00b139c /home/rudi/kernel/linux-2.6.39.1/fs/block_dev.c:1275 Doesn´t say me much. :-( Just to make sure I unterstand where things broke. The System boot from my uImage, get to the point to where it should load the root FS and then things broke up, correct? Thx Rudi Am 25.02.2015 um 23:17 schrieb Juergen Borleis: Hi Rudi, Lappies wrote: could someone point me please in thr right direction? My mini2440 was up and running for 3 year no, without any problems. This morning I waked up and my Alarm clock was blinking, so it mean the electricity was gone this night. My mini2440 doesn´t start anymore, so I connected it to my Linuxbox and check with picocom what is going on. It boot up, recognize the SDCARD and then Panic TCP cubic registered s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-rtc s3c2410-rtc: setting system clock to 2015-02-25 21:25:32 UTC (1424899532) Waiting for root device /dev/mmcblk0p3... s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 398kHz (requested: 400kHz). s3c-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz). s3c-sdi s3c2440-sdi: running at 16875kHz (requested: 25000kHz). mmc0: new SDHC card at address 8c3b mmcblk0: mmc0:8c3b SD04G 3.69 GiB (ro) mmcblk0: p1 p2 p3 Unable to handle kernel NULL pointer dereference at virtual address 016c pgd = c0004000 [016c] *pgd= Internal error: Oops: 5 [#1] last sysfs file: Modules linked in: CPU: 0Not tainted (2.6.39.1 #1) pc : [c00b139c]lr : [c00b139c]psr: 6013 sp : c3827e40 ip : c0308f24 fp : 0083 r10: c02f7d68 r9 : c3826000 r8 : c34021c0 r7 : c3402380 r6 : c34021d0 r5 : r4 : ffe2 r3 : r2 : r1 : c34023a4 r0 : c03bf0f8 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: c000717f Table: 30004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc3826270) Stack: (0xc3827e40 to 0xc3828000) 7e40: c3402254 c34023a4 0003 c00b0758 c3827e5c c3407e80 0003 7e60: c3827e78 c34021c0 0083 c02f7d68 8000 0083 7e80: c00b14f4 8000 c02f7d68 c02f7d68 c008c4b0 c0124a2c 7ea0: c3938c00 c38077b8 80d0 000a 000a c009fda0 8000 7ec0: c3806780 c02f7d68 c02f7d68 c3938c00 c00de6a8 c00e00bc 8000 7ee0: c3938c20 c008b55c c02f7d68 8000 8000 c3806780 c3938c20 c00a10b8 7f00: 8000 c3938c20 c3938c00 c02f7d68 c00a1134 8000 8000 7f20: 0020 c3938c20 c00a17e0 000a c00728cc 000a 7f40: c38060a0 c3401780 c3814000 c0286b73 8000 c0286b73 7f60: c00a18c8 0600 0004 c3938c20 c3938c00 7f80: c3811000 c001d214 c3811000 8000 c0008bd4 c02675dc 7fa0: 0080 00200200 16a0 c3811000 c02f4588 0b33 c0286b73 c00237e4 7fc0: c001d224 c001d214 c00237e4 0013 c0008f04 fffe 2013 7fe0: ff9c c03097a0 c0008344 c0008440 c00237e4 0800 Function entered at [c00b139c] from [c00b14f4] Function entered at [c00b14f4] from [c008c4b0] Function entered at [c008c4b0] from [c00de6a8] Function entered at [c00de6a8] from [c008b55c] Function entered at [c008b55c] from [c00a10b8] Function entered at [c00a10b8] from [c00a1134] Function entered at [c00a1134] from [c00a17e0] Function entered at [c00a17e0] from [c00a18c8] Function entered at [c00a18c8] from [c0008bd4] Function entered at [c0008bd4] from [c0008f04] Function entered at [c0008f04] from [c0008440] Function entered at [c0008440] from [c00237e4] Code: e3a01000 e1a7 e5a01024 ebfe68ec (e595216c) ---[ end trace 747c9e3437494824 ]--- Kernel panic - not syncing: Attempted to kill init! Function entered at [c0027024] from [c02669f4] If you have the vmlinux around you can ask the addr2line tool about the real functions refereed here, to get an idea why it fails: $ addr2line -e vmlinux 0xc00b139c This will tell you the source file and the line which corresponds to this address. It will also work if you re-build the kernel with the same compiler and configuration. Regards, Juergen
