|
WARNING: at kernel/irq/handle.c - after changing rootfs, but why?
Hi everyone,
today I changed from an image with initramfs to an image with separate kernel and rootfs. Theses images are used for an Embedded System (ARM9 SAM9G25), that is runnging with an Linux 2.6.39. During boot I got the following warning, that didn't show up with the initramfs: WARNING: at kernel/irq/handle.c:130 handle_irq_event_percpu+0x70/0x198() irq 12 handler atmci_interrupt+0x0/0x6b0 enabled interrupts Modules linked in: Backtrace: [<c0024918>] (dump_backtrace+0x0/0x10c) from [<c01f5664>] (dump_stack+0x18/0x1c) r6:c005d558 r5:00000009 r4:c028fea8 r3:c02956bc [<c01f564c>] (dump_stack+0x0/0x1c) from [<c0030f74>] (warn_slowpath_common+0x54/0x6c) [<c0030f20>] (warn_slowpath_common+0x0/0x6c) from [<c0031030>] (warn_slowpath_fmt+0x38/0x40) r8:00000000 r7:00000000 r6:0000000c r5:00000001 r4:c7969f60 r3:00000009 [<c0030ff8>] (warn_slowpath_fmt+0x0/0x40) from [<c005d558>] (handle_irq_event_percpu+0x70/0x198) r3:0000000c r2:c025b447 [<c005d4e8>] (handle_irq_event_percpu+0x0/0x198) from [<c005d6b0>] (handle_irq_event+0x30/0x40) [<c005d680>] (handle_irq_event+0x0/0x40) from [<c005f274>] (handle_level_irq+0xbc/0xe4) r4:c02976a8 r3:00020000 [<c005f1b8>] (handle_level_irq+0x0/0xe4) from [<c0021078>] (asm_do_IRQ+0x78/0xa8) r4:0000000c r3:c005f1b8 [<c0021000>] (asm_do_IRQ+0x0/0xa8) from [<c0021a74>] (__irq_svc+0x34/0x60) Exception stack(0xc028ff48 to 0xc028ff90) ff40: 00000000 0005317f 0005217f 60000013 c028e000 c02ab1a4 ff60: c03b9480 c0291f0c 20000000 41069265 2001c2a8 c028ff9c 600000d3 c028ff90 ff80: c0022748 c0022754 60000013 ffffffff r5:fefff000 r4:ffffffff [<c0022714>] (default_idle+0x0/0x44) from [<c0022908>] (cpu_idle+0x70/0xc8) [<c0022898>] (cpu_idle+0x0/0xc8) from [<c01f37f4>] (rest_init+0x60/0x78) r5:c001d5c4 r4:c0290094 [<c01f3794>] (rest_init+0x0/0x78) from [<c00088c0> (start_kernel+0x23c/0x284) [<c0008684>] (start_kernel+0x0/0x284) from [<20008038>] (0x20008038) ---[ end trace 45f8d0076fc9ced3 ]--- I have to say, the system doesn't crash here and boots on as the usual way and is usable in the end (I end up in Busybox - the distro). What I did: I created an SD card with 2 FAT32 partitions of ~1 GB each. On the first there are the bootloaders and the kernel and on the second I extracted the rootfs.tar, that was generated with the help of Buildroot 2013.11. The Linux command line looks like this: console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait rw (I'm not sure if this belongs to here, but first i couldn't even boot the rootfs at all, since he wasn't able to initialize the mmcblk. Now with the rootwait it works just fine). My question is: does anyone know where this error comes from? I couldn't find any useful threads anywhere about this. I'd like to remove this error, because I guess it's wasting a bit of time during boot and that's my actual aim: keeping the boot time at the lowest time it could get. |
I found out: when using the *nix dd command the problem is solved. With that the rootfs is properly installed on a specific partition. If interested, have a look at: http://en.wikipedia.org/wiki/Dd_%28Unix%29, where if(input file) is the path to the rootfs file (e.g. rootfs.squashfs) and of(output file) is the path to the partition where it should be installed (e.g.: sdbx - for en external sd card).
|
| All times are GMT -5. The time now is 11:47 AM. |