Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Mar 2006 00:40:02 +0200
From:      Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>
To:        freebsd-ppc@freebsd.org
Subject:   'portinstall -R a2ps-a4' causes kernel trap
Message-ID:  <20060328004002.0ace89ff.torfinn.ingolfsen@broadpark.no>

next in thread | raw e-mail | index | archive | help
Hi,
I try to install the ports I need on my G4, running:
root@kg-g4# uname -a
FreeBSD kg-g4.kg4.no 7.0-20051105-SNAP FreeBSD 7.0-20051105-SNAP #0: Sat
Nov  5 04:33:52 UTC 2005    
root@macmini.ptree32.com.au:/usr/obj/usr/src/sys/GENERIC  powerpc

Note: I have already installed 65 ports in total, including a few large
ports like perl-5.8.8, ruby-1.8.4_4.1, and the xorg-6.9.0 metaport; so
far no problems.

But when I try to install the a2ps-a4 port, I get a kernel panic. First
it installed as a dependcy to the xfce-4 meta port (ok, one of its
subports, probably xfprint4), but I have also tried it with 'portinstall
-R a2ps-a4', it fails in the same spot.

Here are the last few lines before the kenel panic (from an xterm on
another machine, thru ssh):

Making all in sheets
Making all in encoding
Making all in afm
. ../tests/defs ; touch fonts.map ;  if /bin/sh ./make_fonts_map.sh > /dev/null; then  cp fonts.map.new fonts.map ; else  echo "Failed to build a fonts.map file.";  echo "Reverting to default file.";  cp ./fontsmap fonts.map;  fi
Looking for the afm files read by /usr/ports/print/a2ps-a4/work/a2ps-4.13/src/a2ps...

The kernel trap looks like this (transcribed from the console screen - beware of errors!):
fatal kernel trap:

   exception         = 0x3 (data storage interrupt)
   virtual address = 0x7fffd634
   srr0                  = 0x3cc438
   srr1                  = 0x9032
   curthread         = 0x129aa980
              pid = 10275, comm = a2ps

[thread pid 10275  tid 100086]
stopped at    0x3cc438: lwz   r11,r30, 0x4
db>

(at this point I can issue a 'reboot'  command, but nothing happens, I must press the rest button on the G4 to restart it)
When the machine comes back up again (manual fsck and all), there is no crash dump.


Is this a known issue, or should i file a PR?
Does anyone wnat me to do more testing?
What should I test then?
-- 
Regards,
Torfinn Ingolfsen,
Norway




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060328004002.0ace89ff.torfinn.ingolfsen>