public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Claas Langbehn <claas@rootdir.de>
To: Artur Kedzierski <artur@kedzierski.org>
Cc: linux-kernel@vger.kernel.org, haveaniceday@cv-sv.de
Subject: Re: This kernel requires the following features not present on the CPU... (on a VIA C7 CPU)
Date: Tue, 22 May 2007 08:55:54 +0200	[thread overview]
Message-ID: <465293FA.1040909@rootdir.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0705191820100.11197@merry.kedzierski.org>

Hello Artur,
>     I purchased C7 VIA Esther and I experience similar problem with
> random crashes. There is also a thread on Via Arena about "J7F4K - 
> Hard Lockups" where people describe the same issue:
> http://forums.viaarena.com/messageview.aspx?catid=28&threadid=77032
>     I've tried the following kernels:
> 2.6.21.1 - crashes pretty quick
> 2.6.21.1 with disabled CPU scaling - better mileage but still crashes
> 2.6.22-rc1 - hangs on boot
> 2.6.22-rc1-mm1 - doesn't compile
> 2.6.22-rc2 - hangs on boot
here, too: crashes over crashes...
>     I've ran memtest86 and no memory problems were found.
>     Any ideas or suggestions?
>     Thank You.
The same here.


I applied the patch mentioned by Christian Volkmann in the thread "Re: 
2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 II"  on May 
19th 2007. Since then I did not have a crash any more. Touch wood!

Could anyone explain to me what CMPXCHG64 / cx8 is and what happens if 
the kernel has been compiled to use it but the CPU does not have it? 
Especially if the CPU like the C7 supports it, but it's disabled? Would 
random crashes be a plausible effect?


Regards,
claas

  reply	other threads:[~2007-05-22  6:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20  1:30 This kernel requires the following features not present on the CPU... (on a VIA C7 CPU) Artur Kedzierski
2007-05-22  6:55 ` Claas Langbehn [this message]
2007-05-22 15:53   ` Christian Volkmann
  -- strict thread matches above, loose matches on Subject: below --
2007-05-17 12:27 Claas Langbehn
2007-05-17 15:24 ` Alan Cox
2007-05-17 15:41   ` Claas Langbehn
2007-05-17 18:33 ` H. Peter Anvin
2007-05-18 11:17   ` Claas Langbehn
2007-05-17 20:12 ` Simon Arlott
2007-05-17 20:15   ` H. Peter Anvin
2007-05-17 22:16     ` Simon Arlott
2007-05-17 22:19       ` H. Peter Anvin
2007-05-18  6:24   ` Jan Engelhardt
2007-05-17 20:13 ` Simon Arlott

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=465293FA.1040909@rootdir.de \
    --to=claas@rootdir.de \
    --cc=artur@kedzierski.org \
    --cc=haveaniceday@cv-sv.de \
    --cc=linux-kernel@vger.kernel.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