Summary: SunOS 4.1 crashes - Data fault

From: Claude Scarpelli (claude@genethon.genethon.fr)
Date: Thu Feb 07 1991 - 12:10:58 CST


Many thanks to Sun-managers !

About 10 persons give me the answers. There is a bug in SunOS 4.1
(bugid 1029939). See the readme file from the patch some of you sent me
at the end of this message. One of you say that the PMEG patch
solve the problem too, but it don't apply the two patches, because
they involve a common file. Here are the relevant crash(8) informations :

genethon# crash -d vmcore.2 -n vmunix.2
dumpfile = vmcore.2, namelist = vmunix.2, outfile = stdout
> t
      FP PC SYM+ OFF ARGS
f8460998 f804fa80 _panic+ 6c f815ed13 f8460ac4 f815ebb8 80 7c231 f848ae98
f84609f8 f80dcec4 _trap+ 1cc 9 f8460ac4 f842afb4 80 1 50
(?)
f8460a68 f8006a78 _flush_windows+ 60 b f8460ea4 f8460eb8 80 11900fe1 f8460ea4
f8460b10 f80c654c _resume+ ec f8238d68 18 f814fb48 f814fb60 f8461000 f814fb60
(?)
f848ae98 f80c643c _swtch+ 80 f8238d68 f848b000 1 f815dc00 f7ffe1f0 5ee8
f848aef8 f80de8e0 _sys_rttchk+ 38 f8238d68 f848af58 f848af58 175 f848b000 f8488000
>

See the _flush_windows .

Thank's to
stern@East.Sun.COM (Hal Stern - Consultant)
Dave Baines <dwb@lfcs.edinburgh.ac.uk>
ang@theory.lcs.mit.edu (William Ang)
kevin@Corp.Sun.COM (Kevin Sheehan {Consulting Poster Child})
Pilotti@Jupiter.SAIC.COM (Keith Pilotti)
fsg!karl!reynolds@uunet.UU.NET (Brian Reynolds)
"John Palkovic" <palkovic@linac.fnal.gov>

--------------README file from the patch-------------
Keywords: 4.1, 4/110, flush_wind, trap, fault, data
Synopsis: data fault trap in flush_windows on 4/110 running 4.1
Date: August 13, 1990
SunOS release: 4.1

Unbundled Product:

Unbundled Release:

Topic:

BugId's fixed with this patch: 1029939

Architectures for which this patch is available: sun4 sun4c

Obsoleted by: 4.1.1

Problem Description:

On a fork, the child gets a copy of the parent's
process control block, which for the child will be invalid.
If it enters the kernel because of a register window overflow
or underflow, the code will fault in a user stack page.
When the process is eventually resumed, the bad pcb causes
the panic.



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:10 CDT