Debian Bug report logs - #515982
linux-image-2.6-486: Cannot boot on i486

Full log

Message #10 received at [email protected] (full text, mbox, reply):

Received: (at 515982) by bugs.debian.org; 18 Feb 2009 17:01:02 +0000
From [email protected] Wed Feb 18 17:01:02 2009
X-Spam-Checker-Version: SpamAssassin 3.2.3-bugs.debian.org_2005_01_02
	(2007-08-08) on rietz.debian.org
X-Spam-Level: 
X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 151; neutral, 92; spammy,
	0. spammytokens: hammytokens:0.000-+--Severity, 0.000-+--2.6.26,
	0.000-+--UD:wiki.debian.org, 0.000-+--wikidebianorg, 0.000-+--wiki.debian.org
X-Spam-Status: No, score=-5.2 required=4.0 tests=AWL,BAYES_00,HAS_BUG_NUMBER,
	IMPRONONCABLE_2,SUBENDNUM autolearn=ham
	version=3.2.3-bugs.debian.org_2005_01_02
Return-path: <[email protected]>
Received: from baikonur.stro.at ([213.239.196.228])
	by rietz.debian.org with esmtp (Exim 4.63)
	(envelope-from <[email protected]>)
	id 1LZpnB-0008S2-Lb
	for [email protected]; Wed, 18 Feb 2009 17:01:02 +0000
Received: by baikonur.stro.at (Postfix, from userid 1001)
	id C88505C00B; Wed, 18 Feb 2009 17:58:13 +0100 (CET)
Date: Wed, 18 Feb 2009 17:58:13 +0100
From: maximilian attems <[email protected]>
To: Bas Wijnen <[email protected]>, [email protected]
Subject: Re: Bug#515982: linux-image-2.6-486: Cannot boot on i486
Message-ID: <[email protected]>
References: <[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by Amavis (ClamAV) at stro.at

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

Send a report that this bug log contains spam.