From: "werner" <w.landgraf@ru.ru>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: 3.1-rc6 boot problem reason searching
Date: Wed, 14 Sep 2011 22:42:03 -0400 [thread overview]
Message-ID: <web-606798161@zbackend1.aha.ru> (raw)
In-Reply-To: <CA+55aFwyC7s=YK10Wkpr+GzdukXp-JUtf_=MgWcrhBOtTg4eTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
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@linux-foundation.org> wrote:
> On Wed, Sep 14, 2011 at 5:56 AM, werner
><w.landgraf@ru.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.ru>
---
Professional hosting for everyone - http://www.host.ru
[-- Attachment #2: dmesg.txt.bz2 --]
[-- Type: application/octet-stream, Size: 25856 bytes --]
next parent reply other threads:[~2011-09-15 2:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <web-606439650@zbackend1.aha.ru>
[not found] ` <CA+55aFwyC7s=YK10Wkpr+GzdukXp-JUtf_=MgWcrhBOtTg4eTg@mail.gmail.com>
2011-09-15 2:42 ` werner [this message]
2011-09-15 3:11 ` 3.1-rc6 boot problem reason searching Linus Torvalds
2011-09-15 4:11 ` werner
2011-09-15 14:41 ` Andrew Lutomirski
2011-09-15 15:21 ` Andrew Lutomirski
2011-09-15 15:47 ` Linus Torvalds
[not found] ` <web-607296211@zbackend1.aha.ru>
[not found] ` <CAObL_7HAxg0j3ywpTy1-5Y5vBBQLSTiF7AZ0bctRsPOLKA8ZNA@mail.gmail.com>
[not found] ` <CA+55aFwEKNEN8QPpBhAkDQ4UGFtSDtpdwFRSkTvnhaYRTmrsOA@mail.gmail.com>
[not found] ` <CAObL_7Gjk91MFSwbaMnfdxwrM0mDGxWtDBaKMoimg2FSUqjAUg@mail.gmail.com>
[not found] ` <CA+55aFxmW7rFEpanD-ngB-Egx5j1q8b_u31Keo3+s-TJ13UZGA@mail.gmail.com>
2011-09-15 18:23 ` Linus Torvalds
2011-09-15 18:56 ` Andrew Lutomirski
2011-09-16 1:10 ` werner
2011-09-16 1:20 ` Linus Torvalds
2011-09-16 1:27 ` Andrew Lutomirski
2011-09-16 1:33 ` Wanlong Gao
2011-09-16 1:34 ` Linus Torvalds
2011-09-15 4:28 werner
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=web-606798161@zbackend1.aha.ru \
--to=w.landgraf@ru.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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