From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
	cinap_lenrek@felloff.net
In-reply-to: <816678B6DFD200970DC81CAC122F1AE5@felloff.net>
References: <816678B6DFD200970DC81CAC122F1AE5@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <19865.1555560178.1@orthanc.ca>
Date: Wed, 17 Apr 2019 21:02:58 -0700
Message-Id: <fd2fd1eb6ed91100@orthanc.ca>
Subject: Re: [9fans] SMC SYS-5018A-FTN4 lapic weirdness (9front)
Topicbox-Message-UUID: fac49802-ead9-11e9-9d60-3106f5b1d025

cinap_lenrek@felloff.net writes:
> bit 7 is "illegal register access". try to print the pc from the ureg
> passed to the first argument in lapicerror() in /sys/src/9/pc/apic.c.

A quick printf hack says ureg->pc = 0xffffffff801103b3 mostly
(>99.9%), but a few other oddballs are:

  cpu0  0x2400c8
  cpu0  0x226df6
  cpu0  0xffffffff80208b1c
  cpu0  0xffffffff802083f9

etc.  During boot I see complaints from cpu1, but once the machine is
fully booted only cpu0 spits messages.

This is from a generic Dick Tracy amd64 kernel, with a U->pc printf
added to lapicerror().

--lyndon