mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael S. Zick" <lkml@morethan.org>
To: linux-kernel@vger.kernel.org
Cc: Harald Welte <HaraldWelte@viatech.com>
Subject: [VIA Support]  Instruction timing and cache coherency issues
Date: Sat, 25 Jul 2009 08:27:39 -0500	[thread overview]
Message-ID: <200907250827.43400.lkml@morethan.org> (raw)

Started back in mid-May - long time and a lot of hours later...

As suggested very early in this examination by others -
It is a timing issue.  My inserting "lock" for config_mviac7
was just poking at the edges of the sore spot.  ;)

The "break through" came yesterday while running (or trying to run)
FreeBSD-8.0-beta2 on the various machines at hand. . .

Depending on the cpu model variation and the integrated chipset
used with that cpu - -
*) FB-8.0 will run
*) FB-8.0 will only run in "safe mode"
*) FB-8.0 panics

And that pattern is similar to the 2.6.30 cpu model / chipset pattern.
Scratches head, asking: "now how can that be" with two very different OS designs.

Diddling with the things I have found that either "fix" or "work around"
the various timing / cache coherency issues - - -
Aw, so - found how to affect the timing issues sufficiently so that Linux
would panic dump rather than deadlock on the troublesum combination - -
*Functionally the same* panic backtrace that FreeBSD is showing.

NOW I have a lead into making a "minimum invasive" change so that the 
kernel is happy - even on the flaky VIA combinations.  Patch RSN, just any month.
The FreeBSD project can fix their problems themselves.  ;)

@H.W.  Download the FreeBSD-8.0-beta2 and try running it on your Cloudbook and HP-2133,
you can see what is happening.  Then you might have a word or two with the silicon growers.

Mike

             reply	other threads:[~2009-07-25 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 13:27 Michael S. Zick [this message]
2009-07-30  9:08 ` Pavel Machek
2009-08-02 19:08   ` Harald Welte
2009-08-02 22:08     ` Pavel Machek

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=200907250827.43400.lkml@morethan.org \
    --to=lkml@morethan.org \
    --cc=HaraldWelte@viatech.com \
    --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

all inboxes | Powered by JetHome®