mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24 still doesn't boot on i486..
Date: Fri, 4 Apr 2008 09:01:33 -0400	[thread overview]
Message-ID: <20080404130133.GF24239@csclub.uwaterloo.ca> (raw)
In-Reply-To: <47F5EE6A.6080705@msgid.tls.msk.ru>

On Fri, Apr 04, 2008 at 01:01:30PM +0400, Michael Tokarev wrote:
> Just a follow-up on my earlier bugreport, when
> 2.6.23 first come out....
> 
> 2.6.24 seems to not boot on i486-class hardware.
> The machine reboots right after "Booting linux"
> message.  2.6.22 was the last worked kernel.
> 
> The relevant config entries are:
> 
> CONFIG_TICK_ONESHOT=y
> CONFIG_NO_HZ=y
> CONFIG_HIGH_RES_TIMERS=y
> CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
> CONFIG_X86_PC=y
> CONFIG_M486=y
> CONFIG_X86_GENERIC=y
> CONFIG_X86_CMPXCHG=y          <-- is it right?
> CONFIG_X86_L1_CACHE_SHIFT=7
> CONFIG_X86_XADD=y
> CONFIG_X86_PPRO_FENCE=y
> CONFIG_X86_F00F_BUG=y
> CONFIG_X86_WP_WORKS_OK=y
> CONFIG_X86_INVLPG=y
> CONFIG_X86_BSWAP=y
> CONFIG_X86_POPAD_OK=y
> CONFIG_X86_ALIGNMENT_16=y
> CONFIG_X86_INTEL_USERCOPY=y
> CONFIG_X86_MINIMUM_CPU_FAMILY=4
> CONFIG_X86_UP_APIC=y
> CONFIG_X86_UP_IOAPIC=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_X86_IO_APIC=y
> CONFIG_X86_MCE=y
> CONFIG_X86_MCE_NONFATAL=y
> CONFIG_X86_MCE_P4THERMAL=y
> CONFIG_NOHIGHMEM=y
> CONFIG_VMSPLIT_3G=y
> 
> Compiled with gcc (GCC) 4.2.3 (Debian 4.2.3-2).
> 
> This email is also a JFYI-style email.  Yesterday
> I tried to debug this issue but discovered that the
> power unit of that machine failed.  Well, it still
> works and the machine boots, but at the same time
> it smells like frosted/fried plastic ;)  So I don't
> have i486 hardware anymore to test things on...
> 
> And now I wonder if I'm the only person in this world
> with i486 machine... ;)

I have one that works flawlessly. :)  15 years of mostly 24/7 operation
and still going.  The last 9 years has been as a
firewall/router/fileserver.

-- 
Len Sorensen

      parent reply	other threads:[~2008-04-04 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  9:01 Michael Tokarev
2008-04-04 12:40 ` Mikael Pettersson
2008-04-04 12:57   ` Ingo Molnar
2008-04-04 13:06   ` Lennart Sorensen
2008-04-04 13:01 ` Lennart Sorensen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080404130133.GF24239@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®