Bug#515982: linux-image-2.6-486: Cannot boot on i486
Package: linux-image-2.6-486 Version: 2.6.26+17 Severity: Grave Justification: Makes package unusable Installing lenny on a 486 is not possible, because the installer kernel cannot boot. Upgrading from Etch will work, but only if the old kernel continues to be used. When trying to boot the kernel, it seems to panic immediately (I can't really check, because my hercules monitor doesn't allow scrollback). I copied the crash message (by hand, so it may contain some typos, and I left some numbers out; please ask if they are important, it's easy to reproduce, if you have the hardware). Below is the text that's on screen after trying to boot. I also included the output of /proc/cpuinfo (when using Etch's 2.6.18 kernel). The cache is switched off to make sure that wasn't the problem; the result is identical if I do switch it on. Thanks, Bas Call Trace: native_init_IRQ+0x46/0x79 apply_paravirt+0x81/0x91 do_IRQ+0x50/0x60 common_interrupt+0x23/0x30 vprintk+0x269/0x275 ktime_get+0xd/0x21 tick_nohz_stop_sched_tick+0x24f/0x259 do_IRQ+0x50/0x60 common_interrupt+0x23/0x30 alternative_instructions+0x23/0x3c check_bugs+0xd2/0xd4 start_kernel+0x271/0x27e = Code: 00 89 c2 fa 90 8d b4 26 00 00 00 00 90 89 c8 89 ef c1 e8 02 89 c1 f3 a5 89 d9 83 e1 03 74 02 f3 a4 89 d0 50 9d 90 8d b4 26 00 00 00 00 b8 01 00 00 00 0f a2 5a 89 e8 5b 5e 5f 5d c3 55 31 c9 57 EIP: [c010797d] text_poke_early+0x41/0x52 SS:ESP 0068:c0363eb0 ---[ end trace 4eaa2a86a8e2da22 ]--- Kernel panic - not syncing: Attempted to kill the idle task! processor : 0 vendor_id : GenuineIntel cpu family : 4 model : 8 model name : 486 DX/4 stepping: 0 cache size : 0 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme bogomips: 49.40 -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://a82-93-13-222.adsl.xs4all.nl/e-mail.html signature.asc Description: Digital signature
Bug#515982: linux-image-2.6-486: Cannot boot on i486
On Wed, Feb 18, 2009 at 05:51:15PM +0100, Bas Wijnen wrote: Package: linux-image-2.6-486 Version: 2.6.26+17 Severity: Grave Justification: Makes package unusable Installing lenny on a 486 is not possible, because the installer kernel cannot boot. Upgrading from Etch will work, but only if the old kernel continues to be used. When trying to boot the kernel, it seems to panic immediately (I can't really check, because my hercules monitor doesn't allow scrollback). I copied the crash message (by hand, so it may contain some typos, and I left some numbers out; please ask if they are important, it's easy to reproduce, if you have the hardware). Below is the text that's on screen after trying to boot. I also included the output of /proc/cpuinfo (when using Etch's 2.6.18 kernel). The cache is switched off to make sure that wasn't the problem; the result is identical if I do switch it on. Thanks, Bas Call Trace: native_init_IRQ+0x46/0x79 apply_paravirt+0x81/0x91 do_IRQ+0x50/0x60 common_interrupt+0x23/0x30 vprintk+0x269/0x275 ktime_get+0xd/0x21 tick_nohz_stop_sched_tick+0x24f/0x259 do_IRQ+0x50/0x60 common_interrupt+0x23/0x30 alternative_instructions+0x23/0x3c check_bugs+0xd2/0xd4 start_kernel+0x271/0x27e = Code: 00 89 c2 fa 90 8d b4 26 00 00 00 00 90 89 c8 89 ef c1 e8 02 89 c1 f3 a5 89 d9 83 e1 03 74 02 f3 a4 89 d0 50 9d 90 8d b4 26 00 00 00 00 b8 01 00 00 00 0f a2 5a 89 e8 5b 5e 5f 5d c3 55 31 c9 57 EIP: [c010797d] text_poke_early+0x41/0x52 SS:ESP 0068:c0363eb0 ---[ end trace 4eaa2a86a8e2da22 ]--- Kernel panic - not syncing: Attempted to kill the idle task! can you check if 2.6.28 trunk buildserver images are fine inbetween? see apt lines http://wiki.debian.org/DebianKernel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515982: linux-image-2.6-486: Cannot boot on i486
On Wed, Feb 18, 2009 at 05:58:13PM +0100, maximilian attems wrote: Code: 00 89 c2 fa 90 8d b4 26 00 00 00 00 90 89 c8 89 ef c1 e8 02 89 c1 f3 a5 89 d9 83 e1 03 74 02 f3 a4 89 d0 50 9d 90 8d b4 26 00 00 00 00 b8 01 00 00 00 0f a2 5a 89 e8 5b 5e 5f 5d c3 55 31 c9 57 EIP: [c010797d] text_poke_early+0x41/0x52 SS:ESP 0068:c0363eb0 ---[ end trace 4eaa2a86a8e2da22 ]--- Kernel panic - not syncing: Attempted to kill the idle task! can you check if 2.6.28 trunk buildserver images are fine inbetween? They give the same panic, with almost the same output (now it's at text_poke_early+0x3e/0x4e, but the Code is the same). For the record, that's with http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/linux-image-2.6.28-1-486_2.6.28-1~experimental.1~snapshot.12825_i386.deb Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://a82-93-13-222.adsl.xs4all.nl/e-mail.html signature.asc Description: Digital signature
Bug#515982: linux-image-2.6-486: Cannot boot on i486
On Wed, Feb 18, 2009 at 08:06:05PM +0100, Bas Wijnen wrote: On Wed, Feb 18, 2009 at 05:58:13PM +0100, maximilian attems wrote: Code: 00 89 c2 fa 90 8d b4 26 00 00 00 00 90 89 c8 89 ef c1 e8 02 89 c1 f3 a5 89 d9 83 e1 03 74 02 f3 a4 89 d0 50 9d 90 8d b4 26 00 00 00 00 b8 01 00 00 00 0f a2 5a 89 e8 5b 5e 5f 5d c3 55 31 c9 57 EIP: [c010797d] text_poke_early+0x41/0x52 SS:ESP 0068:c0363eb0 ---[ end trace 4eaa2a86a8e2da22 ]--- Kernel panic - not syncing: Attempted to kill the idle task! can you check if 2.6.28 trunk buildserver images are fine inbetween? They give the same panic, with almost the same output (now it's at text_poke_early+0x3e/0x4e, but the Code is the same). text_poke_early() is patching code sequences that need to be changed dynamically. The problem seems to be that it itself contains such a code sequence! The bytes 8d b4 26 00 00 00 00 match GENERIC_NOP7 and the instruction pointer in this crash points into the middle of those, which suggests that they've just been changed. I think this is something to do with the tracing added by CONFIG_TRACE_IRQFLAGS_SUPPORT. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
