Bug 18938 - nfs file locking broken on Athlon cpu's
Summary: nfs file locking broken on Athlon cpu's
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils
Version: 7.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-12 08:56 UTC by Gerald Teschl
Modified: 2007-04-18 16:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-19 18:33:58 UTC
Embargoed:


Attachments (Terms of Use)

Description Gerald Teschl 2000-10-12 08:56:01 UTC
NFS locking does not work on Athlon K7 cpu's.
I have several Worksations running RH7.0 (plus all updates) and on all
machines with
Athlon K7 cpu's NFS locking is broken: E.g. using elm "Cannot flock folder
"/var/spool/mail/gerald"! [No locks available]". Pentium, Pentium II,
Pentium III
systems with identical setup work fine. I testet this with both a server
running 6.2 and 7.0.
I also tried to use the i386 kernel.

Here is /proc/cpuinfo which don't work:
[gerald@ws11 gerald]$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 700.051
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr 6 mce cx8 sep mtrr pge 14 cmov
fcmov 17 psn 22 mmx 24 30 3dnow
bogomips        : 1395.92 

On some other AThlon cpu's there are no problems
[gerald@bounder gerald]$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 2
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 700.056
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr 6 mce cx8 sep mtrr pge 14 cmov
fcmov 17 22 mmx 24 30 3dnow
bogomips        :
1395.92

Comment 1 Gerald Teschl 2000-12-19 18:33:54 UTC
The problem is caused by the host's IP not showing up in /etc/hosts.


Note You need to log in before you can comment on or make changes to this bug.