pathalias on AT&T 3B1

[John B. Milton]

In article <1391 at sw1e.UUCP> uisdrb at sw1e.UUCP (1826]) writes:
[ config ]
[ started a month ago ]

>NMI (parity error) at 0x1A46CA (*hpte: 0xE1FB) Wed Mar  8 21:34:35 1989
>NMI (parity error) at 0x606CA (*hpte: 0x41FB) Wed Mar  8 22:18:18 1989

>NMI (parity error) at 0x1576CA (*hpte: 0xC1FB) Wed Mar  8 22:18:34 1989
>NMI (parity error) at 0x976CA (*hpte: 0x41FB) Wed Mar  8 22:47:00 1989

>NMI (parity error) at 0x15C6CA (*hpte: 0xC1FB) Tue Mar 14 21:20:58 1989
>NMI (parity error) at 0x1566CA (*hpte: 0xE1FB) Tue Mar 14 21:38:46 1989

>NMI (parity error) at 0x606CA (*hpte: 0x41FB) Tue Mar 14 22:07:15 1989
>NMI (parity error) at 0x1566CA (*hpte: 0xC1FB) Tue Mar 14 22:07:30 1989

>NMI (parity error) at 0x606CA (*hpte: 0x41FB) Wed Mar 15 06:36:37 1989
>NMI (parity error) at 0x1566CA (*hpte: 0xC1FB) Wed Mar 15 06:36:52 1989

>	I should probably mention that I have used both
>the malloc that came with the pathalias package and the one
>that came with the system as indicated in the config.h file.
ok

>	I will appreciate any help or suggestions that might
>help resolve this matter.

I'm not sure just how to map the addresses it's giving back to which physical
RAM is causing it, but bud, you've got bad memory somewhere. This is a
hardware problem, not software (read $$$). Shutdown IMMEDIATELY and run the
diagnostics disk to try to figure out what memory is bad.




John
-- 
John Bly Milton IV, jbm at uncle.UUCP, n8emr!uncle!jbm at osu-cis.cis.ohio-state.edu
(614) h:294-4823, w:764-2933; AMPR: 44.70.0.52;  Don't FLAME, inform!
Newsgroups: unix-pc.general,att.general,comp.mail.uucp
Subject: Re: pathalias on AT&T 3B1
Summary: 
Expires: 
References: <1391 at sw1e.UUCP>
Sender: 
Reply-To: jbm at uncle.UUCP (John B. Milton)
Followup-To: 
Distribution: usa
Organization: U.N.C.L.E.
Keywords: Pathalias, 3B1, UNIXPC

In article <1391 at sw1e.UUCP> uisdrb at sw1e.UUCP (1826]) writes:
[ config ]
[ started a month ago ]

>NMI (parity error) at 0x1A46CA (*hpte: 0xE1FB) Wed Mar  8 21:34:35 1989
>NMI (parity error) at 0x606CA (*hpte: 0x41FB) Wed Mar  8 22:18:18 1989

>NMI (parity error) at 0x1576CA (*hpte: 0xC1FB) Wed Mar  8 22:18:34 1989
>NMI (parity error) at 0x976CA (*hpte: 0x41FB) Wed Mar  8 22:47:00 1989

>NMI (parity error) at 0x15C6CA (*hpte: 0xC1FB) Tue Mar 14 21:20:58 1989
>NMI (parity error) at 0x1566CA (*hpte: 0xE1FB) Tue Mar 14 21:38:46 1989

>NMI (parity error) at 0x606CA (*hpte: 0x41FB) Tue Mar 14 22:07:15 1989
>NMI (parity error) at 0x1566CA (*hpte: 0xC1FB) Tue Mar 14 22:07:30 1989

>NMI (parity error) at 0x606CA (*hpte: 0x41FB) Wed Mar 15 06:36:37 1989
>NMI (parity error) at 0x1566CA (*hpte: 0xC1FB) Wed Mar 15 06:36:52 1989

>	I should probably mention that I have used both
>the malloc that came with the pathalias package and the one
>that came with the system as indicated in the config.h file.
ok

>	I will appreciate any help or suggestions that might
>help resolve this matter.

I'm not sure just how to map the addresses it's giving back to which physical
RAM is causing it, but bud, you've got bad memory somewhere. This is a
hardware problem, not software (read $$$). Shutdown IMMEDIATELY and run the
diagnostics disk to try to figure out what memory is bad.




John
-- 
John Bly Milton IV, jbm at uncle.UUCP, n8emr!uncle!jbm at osu-cis.cis.ohio-state.edu
(614) h:294-4823, w:764-2933; AMPR: 44.70.0.52;  Don't FLAME, inform!