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]
Date:	Sat, 25 Jul 2009 08:27:39 -0500
From:	"Michael S. Zick" <lkml@...ethan.org>
To:	linux-kernel@...r.kernel.org
Cc:	Harald Welte <HaraldWelte@...tech.com>
Subject: [VIA Support]  Instruction timing and cache coherency issues

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
--
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