Vallo Kallaste wrote: > You got me wrong. I'm user and do not know and don't want to know > about any CPU architecture and bugs. But I've got problems and > simply trying to provide any data possible to gather by myself. > Either CPU hardware or software bug, fine. You're claiming to know > the bug and possible fix, but don't want to publish it, fine.
I do not object to publication of code that embodies a workaroun to the poblem, so long as that workaround doesn;t specifically disclose the root cause problem itself. > I don't want to think about it because with my knowledge this is going > to nowhere and only wasting my time. Things you see above are my > results using consistent testing environment, take it or leave it. > I'll stick with DISABLE_PSE enabled and DISABLE_PG_G disabled for > the time being. I'll make the same offer of a fixed kernel binary, for testing purposes, if you are willing to test two: one to be sure that there is no serendipity involved, and one with the patch. We can skip the first one if you can give me a CVS date or tag to checkout to get code identical to code you have locally, which has the problem. E.g. if you have a local copy of the CVS tree, and you check out with a date tag of, say, last Wednesday, and the kernel you build from that coe ha he problem, then I can check out identical code, patch it, and give you a binary to try. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
