Subject: Re: bad kernel news
To: Matt Thomas <matt@3am-software.com>
From: Dave Huang <khym@azeotrope.org>
List: port-macppc
Date: 12/07/2004 18:16:02
On Tue, Dec 07, 2004 at 02:02:14PM -0800, Matt Thomas wrote:
> At 01:06 PM 12/7/2004, Tim Kelly wrote:
> >At 12:58 AM -0600 12/4/04, Dave Huang wrote:
> >>On Fri, Dec 03, 2004 at 10:45:37PM -0600, Dave Huang wrote:
> >>> I haven't tried it, but it sounds promising to me... note
> >>
> >>OK, I just tried it (NetBSD 2.0 source, but with rev 1.26 of
> >>locore_subr.S), and I don't get the "panic: mp_save_fpu_proc"
> >>anymore--I get a different panic though. While doing a "build.sh -j3
> >>distribution", I got:
> >>
> >>panic: pmap_pvo_enter: called recursively!
> >>Stopped in pid 10893.1 (nbmake) at netbsd:cpu_Debugger+0x10:  lwz r0, 
> >r1, 0x14
> >>
> >>The keyboard's locked up, so I can't do anything except press the
> >>reset button.
> >>
> >>Is this a valid test, or do I need to update all of my sources to 
> >-current?
> >
> >He's got a dual G4 MP.
> 
> This has been fixed in current but the fix was too late for 2.0 but will
> be in 2.1.  (apply the diff in 1.26 to the 2.0 version or just use the
> -current version)

Which problem are we talking about? With a 2.0 kernel+rev 1.26 of
locore_subr.S, I no longer get "panic: mp_save_fpu_proc", but I do get
"panic: pmap_pvo_enter: called recursively!"
-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 29 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++