Bug#234556: Possible Transmeta CMS bug
Just in order to collect a bit more data on this case, I would like
everybody that encounter this bug to give me their version of the CMS
(Code Morphing Software) that they are using on their hardware.
You can find this information at boot time (whatever OS you are using).
Mine is the following:
CPU: After generic identify, caps: 0080893f 0081813f 00000000 00000000
CPU: After vendor identify, caps: 0080893f 0081813f 0000004e 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 512K (128 bytes/line)
CPU: Processor revision 184.108.40.206, 933 MHz
CPU: Code Morphing Software revision 4.3.2-9-343
CPU: 20020426 17:54 official release 4.3.2#2
CPU: After all inits, caps: 0080893f 0081813f 0000004e 00000000
CPU: Transmeta(tm) Crusoe(tm) Processor TM5800 stepping 03
So, I'm sure that the revision 4.3.2-9-343 has the bug.
I know also that the revision 4.3.2-9-548 has also the bug
I would like to have a list of people that encounter this bug and have
an idea of what CMS revision can be blamed for this in order to show
Transmeta people that it could be good for them to investigate this
a bit further.
Of course, if you know people with Transmeta Crusoe which are
encountering such problems, I would encourage you to tell them about
this and to send their CMS version to me.
Thanks in advance.
Computer Science Department, | Office: B1-201
Aalborg University, | Phone: +45 96 35 72 23
Fredriks Bajersvej 7E, | Fax: +45 98 15 98 89
9220 Aalborg East, Denmark | Email: firstname.lastname@example.org