garbage string as cpu identifier

Bin Ren br260 at cam.ac.uk
Tue Mar 9 17:18:31 PST 2004


The patch is not to 'fix' your problem by replacing garbage
string with a sane one, but rather to make sure on your
Athlon CPU, 'cpuid' does return garbage string expectedly.
This could mean a very tricky software initialization bug
or even a hardware bug. After confirming fault 'cpuid',
I'll try to find the very reason and fix it.

-- Bin

On 10 Mar 2004, at 00:29, Doom Neine wrote:

> thanks a lot, forgot to cc this to the list
> so yes, seems simple enough and i've already done what
> you asked, but i haven't replaced the current one with
> the one i just modified of course, i'll try to rebuild
> with the new changes after about 24 hours if no one
> else has a better suggestion or gives me a reason not
> to do so by then
>
> thanks
>
> Nathanael
> --- Bin Ren <br260 at cam.ac.uk> wrote:
>> Hi,
>>
>> I'm using 5.2-current. Maybe the file has
>> been updated. The patch is very very simple:
>> replace two lines with 6 lines. Is it possible
>> for you to apply the patch manually? Line
>> number is in the patch file. Thanks.
>>
>> You must be 'root' to have write permission.
>>
>> -- Bin
>>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
>



More information about the freebsd-current mailing list