Messages in this thread |  | | From | Zarmfab Software Development <> | Subject | mlockall() still causes 100 % oops in 2.0.27 | Date | Sun, 1 Dec 1996 23:41:31 +0100 (MET) |
| |
has anybody else noticed that mlockall() causes a 100 % reproduceable oops at alpha-systems running 2.0.27 ?? The same happened with 2.0.26, at i386 the call seems to work. The oops happens in line 129 of mlock.c : char c=get_user((char *)start); i'd really like to work on a fix, but don't even understand the __asm__ directive some lines down, sorry.
|  |