Bug#532562: linux-image-2.6.26-2-versatile: Kernel panics randomly while using apt-get
On Wed, Jun 10, 2009 at 01:55:21PM -0300, Axel Allende Lira wrote:
>
>
> Aurelien Jarno escreveu:
>> On Wed, Jun 10, 2009 at 02:52:14PM +0200, Martin Michlmayr wrote:
>>> Aurelien, can you take a look at this bug report?
>>>
>>> * Axel Allende Lira <axellira@gmail.com> [2009-06-10 04:14]:
>>>> bootstrap inside loop mounted hd image, and then booting it with a
>>>> third party
>>>> kernel. I installed linux-image-2.6.26-2-versatile after the
>>>> bootstrapping was
>>>> complete so I could have the cdrom and mouse drivers. The problem
>>>> is:
>>
>> Does it means that version 2.6.26-1-versatile works correctly?
>
> I didn't try 2.6.26-1-versatile. Revision 2 was already out when I started.
Ok, so then I guess you use another kernel before? Was it working
correctly?
>>>> when ins-
>>>> talling anything using apt-get, the kernel will panic after
>>>> downloading the fi-
>>>> les, at configuration time. This caused corruption of many files in
>>>> /var/lib/
>>>> dpkg, making dpkg unusable. I solved this issue by rebuilding the
>>>> system on an
>>>> ext3 partition. Even though, the problem is still there. The last
>>>> lines of the
>>>> panic output are as follow (sorry, couldn`t get anything prior to
>>>> that, since I
>>>> can't scroll up and all...):
>>
>> The trace is to incomplete to be useful.
>>
>> You should try to boot the system on the serial port to catch more
>> messages. You should add console=ttyAMA0 to the kernel arguments, and
>> add -nographic to the QEMU arguments.
>>
>>>> [ 0.000000] [<bf000480>] (scsi_finish_command+0x0/0xcc
>>>> [scsi_mod]) from [<bf0
>>>> 07808>] (scsi_softirq_done+0x10c/0x128 [scsi_mod])
>>>> [ 0.000000] r6:cec694c0 r5:00000005 r4:00000bb8
>>>> [ 0.000000] [<bf0076fc>] (scsi_softirq_done+0x0/0x128 [scsi_mod])
>>>> from [<c010
>>>> bafc>] (blk_done_softirq+0x78/0x9c)
>>>> [ 0.000000] [<c010ba84>] (blk_done_softirq+0x0/0xd4) from
>>>> [<c0047680>] (__do_
>>>> softirq+0x60/0xd4)
>>>> [ 0.000000] [<c0047284>] (__do_softirq+0x0/0xd4) from
>>>> [<c0047680>] (irq_exit+
>>>> 0x44/0x4c)
>>>> [ 0.000000] r6:00000000 r5:c0289f78 r4:0000001b
>>>> [ 0.000000] [<c004763c>] (irq_exit+0x0/0x4c) from [<c002404c>]
>>>> (__exception_t
>>>> ext_start+0x4c/0x64)
>>>> [ 0.000000] [<c0024000>] (__exception_text_start+0x0/0x64) from
>>>> [<c00248a4>]
>>>> (__irq_usr+0x44/0xa0)
>>>> [ 0.000000] Exception stack(0xcf561fb0 to 0xcf561ff8)
>>>> [ 0.000000] 1fa0 00000000
>>>> 00000008 00000
>>>> 02e 00000035
>>>> [ 0.000000] 1fc0: beeb3362 0005781d 00000001 00000016 00059f70
>>>> beeb336d 00059
>>>> a40 0005aa18
>>>> [ 0.000000] ife0: 0006ffd6 beeb27d0 00023890 00024968 60000010 ffffffff
>>>>
>>>> [ 0.000000] r6:0000001 r5:f1140000 r4:ffffffff
>>>> [ 0.000000] Code: e1a01000 e5932000 e59f06fc ea00002f (e5963358)
>>>> [ 0.000000] Kernel panic - not syncing: Fatal exception in interrupt
>>>>
>>>> In order to get this, I ran the system with:
>>>> qemu-system-arm -M versatilepb -kernel vmlinuz-2.6.26-2-versatile -initrd
>>>> initrd.img-2.6.26-2-versatile [1] -hda hda.img -hdb swap.img [2] -cdrom
>>>> debian-501-armel-DVD-1.iso [3] -m 256M -append "root=/dev/sda rw mem=256M"
>>>>
>>
>> Installing the system directly on the emulated hard-drive without any
>> partitions looks strange. I doubt it will make any change, but it may
>> worth trying an installation using partitions.
>
> I DO use a partition. As I said, the system is on an ext3 partition, and
> there's a complementar swap image. I made them using mke2fs -j on
> hda.img, and mkswap on swap.img.
If you are using partitions, then you should specify a different root
to the kernel, probably root=/dev/sda1.
>> What worries me more is the mem=256M argument. Why have you adding it
>> here? Could you try without it?
>
> I'm using this emulated hardware as a test bed for making a rootfs for
> my pda. I'm testing graphical applications, so I thought it would be
> useful to have more memory. I tried without it, and got the same result.
Yes, you should pass the value to qemu with the -m argument. The kernel
should autodetect the right value, which might be a few kB/MB smaller
than the one you specifiy. There is no need to force a memory size with
a mem= argument.
>> Also which version of QEMU are you using?
>
> 0.10.3, compiled from source.
>
Which file format are you using for the images? You should clearly not
use qcow2 with this version of QEMU. And it is strongly recommended to
upgrade to 0.10.5 even if you are not using the qcow2 format.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: