NetBSD Problem Report #31152

From www@netbsd.org  Mon Sep  5 02:47:02 2005
Return-Path: <www@netbsd.org>
Received: by narn.netbsd.org (Postfix, from userid 31301)
	id 8C87D63B84E; Mon,  5 Sep 2005 02:47:02 +0000 (UTC)
Message-Id: <20050905024702.8C87D63B84E@narn.netbsd.org>
Date: Mon,  5 Sep 2005 02:47:02 +0000 (UTC)
From: konis@stats.ox.ac.uk
Reply-To: konis@stats.ox.ac.uk
To: gnats-bugs@netbsd.org
Subject: multiprocessor kernel (2.0.2 & -current) panics on PowerMac 9500 w/ 2 x ppc604 @ 200 mhz
X-Send-Pr-Version: www-1.0

>Number:         31152
>Category:       port-macppc
>Synopsis:       multiprocessor kernel (2.0.2 & -current) panics on PowerMac 9500 w/ 2 x ppc604 @ 200 mhz
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    port-macppc-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 05 02:50:00 +0000 2005
>Closed-Date:    Tue Jun 19 16:32:00 +0000 2018
>Last-Modified:  Tue Jun 19 16:32:00 +0000 2018
>Originator:     Kjell Konis
>Release:        2.0.2
>Organization:
>Environment:
NetBSD PM9500 2.0.2 NetBSD 2.0.2 (GENERIC) #0: Tue Mar 22 16:19:08 UTC 2005  jmc@faith.netbsd.org:/home/builds/ab/netbsd-2-0-2-RELEASE/macppc/200503220140Z-obj/home/builds/ab/netbsd-2-0-2-RELEASE/src/sys/arch/macppc/compile/GENERIC macppc

(obviously not from the panicing kernel)
>Description:
I built a kernel with multiprocessor support using the adjustkernel utility to generate the configuration.  When booted, the kernel panics either just before or just after the login prompt.  Here is a trace from my most recent panic:

...
<startup text>
...

NetBSD/macppc (PM9500) (ttyE0)

login: kjell
Password:
mp_save_fpu_proc{1} pid = 317.1, fpcpu->ci_cpuid = 0
panic: mp_save_fpu_proc
Stopped in pid 317.1 (login) at netbsd:cpu_Debugger+0x10:      lwz   r0, r1 0
x14
bd(1)> trace
0xd5167e00: at panic+x19c
0xd5167e90: at mp_save_fpu_lwp+0xec
0xd5167eb0: at save_fpu_lwp+0x70
0xd5167ec0: at trap+0x94c
0xd5167f40: user FPU trap by 0xefca4530: srr1=0xd032
            r1=0xffffd0e0 cr=0x24004048 xer=0 ctr=xefca1fe8

The panic occurs on kernels built with the sources included with the 2.0.2 release as well as sources from the -current branch (the branch obtained using 'cvs update -A -dP').

The panic only occurs when the openfirmware output-device is set to the pci video card, which in my particular machine is /bandit@F2000000/ATY,XCLAIM@D.  If the output-device is set to ttya then the kernel seems to run just fine (I actually built the kernel 4 times trying to induce the panic).

My machine is a powermac 9500 with a daughter card with 2 604 ppc cpus running at 200 MHz, 144 mMB of RAM, a 350 MB hard drive (ID 0) with MacOS 9 and a 4.3 GB hard drive (ID 4) with NetBSD.
>How-To-Repeat:
In openfirmware set the output-device to /bandit@F2000000/ATY,XCLAIM@D then boot the multiprocessor kernel and wait for the panic.

0 > setenv output-device /bandit@F2000000/ATY,XCLAIM@D  ok
0 > boot scsi-int/sd@4:0 netbsd.mp


>Fix:
No fix other than to set the output-device to ttya and connect remotely.

>Release-Note:

>Audit-Trail:
From: Kjell Konis <konis@stats.ox.ac.uk>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-macppc/31152
Date: Mon, 2 Jan 2006 12:52:52 -0800

 Hello,

 I'm the one that originally reported this bug.  The problem appears  
 to be fixed in the current development branch.  I have been running  
 this kernel

    NetBSD 3.99.15 (MYKERNEL) #0: Sat Dec 31 20:54:20 PST 2005

 for a couple of days now and have had no problems.  The config was  
 GENERIC + no altivec, multiprocessor and vga buffer hack for XFree86  
 r128 driver.  That is

 -bash-3.00$ diff MYKERNEL GENERIC
 29c29
 < #options      ALTIVEC         # Include AltiVec support
 ---
  > options       ALTIVEC         # Include AltiVec support
 555,559d554
 <
 < options       OFB_FAKE_VGA_FB
 < options       MULTIPROCESSOR

 Thanks and keep up the good work.

 Kjell

State-Changed-From-To: open->closed
State-Changed-By: maya@NetBSD.org
State-Changed-When: Tue, 19 Jun 2018 16:32:00 +0000
State-Changed-Why:
Reported as fixed by the author long ago. Thanks for the report and update!


>Unformatted:

Home	PR Database Search