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-next>] [day] [month] [year] [list]
Message-ID: <web-606798161@zbackend1.aha.ru>
Date:	Wed, 14 Sep 2011 22:42:03 -0400
From:	"werner" <w.landgraf@...ru>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: 3.1-rc6 boot problem reason searching

With M586 it also boots.

Enclosed is the dmesg , if of any importance   (ignore 
that the kernel is named -i486, this is only because I 
don't want to rename everything, hoping that soon M486 
returns to work).

Below is also the diff which config's are changed 
implicitely on changing from M486 to M586 .




Thus, the problem is between M486 and M586 ,  compiled 
with 486 it don't boot, but compiled for 586 it boots.

Alias, M686 runs the whole day without any other problems.

You can suggest me now a next config to try out for better 
find the reason for the problem.


wl







=============================================================
bash-4.1# cd /boot
bash-4.1# diff .config config
3c3
< # Linux/i386 3.1.0-rc5 Kernel Configuration
---
> # Linux/i386 3.1.0-rc6 Kernel Configuration
303,304c303,304
< CONFIG_M486=y
< # CONFIG_M586 is not set
---
> # CONFIG_M486 is not set
> CONFIG_M586=y
336d335
< CONFIG_X86_INVD_BUG=y
383a383
> # CONFIG_HIGHMEM64G is not set
bash-4.1#


=============================================================
On Wed, 14 Sep 2011 08:35:44 -0700
  Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Wed, Sep 14, 2011 at 5:56 AM, werner 
><w.landgraf@...ru> wrote:
>> Now, for find out what exactly is the reason why it dont 
>>boot with 486, you
>> can give me suggestions which CONFIG excatly perhaps to 
>>disable, instead of
>> 486.
> 
> Try M586 next ("586/K5/5x86/6x86/6x86MX"). If that 
>works, that narrows
> it down to M486->M586.
> 
> And if that *doesn't* work, try M586TSC 
>("Pentium-Classic") and then
> M586MMX ("Pentium-MMX") to see exactly where it breaks..
> 
>                        Linus
> 
> 

"werner" <w.landgraf@...ru>
---
Professional hosting for everyone - http://www.host.ru

Download attachment "dmesg.txt.bz2" of type "application/octet-stream" (25856 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ