lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AC0D651.7030009@msgid.tls.msk.ru>
Date:	Mon, 28 Sep 2009 19:29:21 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.31: booting on a PIII Celeron?

Michael Tokarev wrote:
> Hello.
> I've a problem here with 2.6.31.  kernel is
> compiled for PIII:
> 
>  CONFIG_MPENTIUMIII=y
>  CONFIG_X86_GENERIC=y
> 
> This kernel works on real PIII machine - like this:
> 
> vendor_id    : GenuineIntel
> cpu family    : 6
> model        : 8
> model name    : Pentium III (Coppermine)
> stepping    : 10
> cpu MHz        : 997.580
> 
> But it fails on a Celeron:
> 
> vendor_id    : GenuineIntel
> cpu family    : 6
> model        : 8
> model name    : Celeron (Coppermine)
> stepping    : 6
> cpu MHz        : 797.481
> 

There's one more difference between the two:

PIII, working:
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 mmx fxsr sse up
Celeron, !working:
flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pse36 mmx fxsr sse up

So the celeron machine lacks "apic" flag.  And in my
kernel config, apic is enabled:
  CONFIG_X86_LOCAL_APIC=y
  CONFIG_X86_IO_APIC=y
(but not on the command line like apic=force)

> it fails on early boot, after a bootloader printed
> "Loading kernel... initrd..." -- after that, on the
> Celeron machine, it reboots instantly.
> 
> It's the same kernel binary, I tried it on several
> machines, and the result is pretty consistent - if
> it's a PIII-Celeron it reboots, if it's a PIII -
> kernel boots and works ok.
> 
> All previous kernels with the same config worked on
> these machines, at least as far as this issue is
> concerned.
> 
> Is it a known issue?  Is there anything else I can
> try to debug it?
> 
> Thanks!
> 
> /mjt

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ