On May 9, 2:14pm, ragge%ludd.ltu.se@localhost (Anders Magnusson) wrote:
-- Subject: Re: VAX 4000/200 panic with 6.1.5
| Christos Zoulas skrev den 2015-05-08 23:59:
| > In article <554CE0C3.3020904%gmail.com@localhost>,
| > Felix Deichmann <m4j0rd0m0%gmail.com@localhost> wrote:
| >> Am 07.05.2015 um 20:21 schrieb Felix Deichmann:
| >>> However, my attempt to netboot a 6.1.5 GENERIC kernel on the machine had
| >>> little success (panic).
| >>> [...]
| >>> vsbus0 at mainbus0
| >> ^^^^^^
| >> OK, finding the problem was easier than expected. The machine wants
| >> ibus, no vsbus...
| >> Fix for ka660.c is included in PR port-vax/49884. Please pull-up to 6 and 7.
| > But still it should not jump to NULL...
| >
| Debatable. It has been told that it has a bus that it can never have,
| hence it references registers that do not exist. It's a coding problem,
| not a configuration error.
I would accept that if it would just misbehave because it was reading
bogus locations, but in this case it seems that it tries to call a function
through a NULL pointer; certainly that can be prevented (or KASSERTed).