Re: port-m68k/27099 (If one runs crashme on a 2.0 m68k machine, the system panics.)

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR port-m68k/27099; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
Cc: dholland-bugs%NetBSD.org@localhost, gnats-bugs%NetBSD.org@localhost,
        port-m68k-maintainer%NetBSD.org@localhost, 
gnats-admin%NetBSD.org@localhost,
        netbsd-bugs%NetBSD.org@localhost, jklos%NetBSD.org@localhost
Subject: Re: port-m68k/27099 (If one runs crashme on a 2.0 m68k machine, the 
system panics.)
Date: Sun, 13 Apr 2008 00:40:57 +0000

 On Fri, Apr 11, 2008 at 12:38:27AM +0900, Izumi Tsutsui wrote:
  > > If so, that's most of the work, and someone just needs to load
  > > trap.c up with printfs to figure out what's happening...
  > 
  > IIRC printf debug didn't help because kernel completely seemed
  > to hang on trap. The instruction cache also looked affected
  > (adding m68k_sync_icache(2) around the bomb() changed some behavor),
  > but I gave up at that point.
 
 That just makes it more fun... :-)  first order of business I guess
 would be to figure out if it makes it into the kernel at all, by
 adding something in locore. (Dunno what; on i386 one tends to do this
 by scribbling on the screen.)
 
 Well, maybe the first order of business is to dig around for known
 processor errata.
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost