Subject: Re: RVEC Internal Error 700 on G4/500 with 2.4.18-pre7/mol 0.9.60
From: Rob Pfile (rob.pfile@riverstonenet.com)
Date: Mon Feb 04 2002 - 10:15:25 MST
thanks for the reply.
i have CONFIG_TAU=y but CONFIG_TAU_INT is not set... also i have
altivec disabled in /etc/molrc. i guess i will keep diffing my 2.4.8
.config against my 2.4.18 config, or maybe recompile without
TAU/Altivec to see what happens.
rob
benh@kernel.crashing.org writes:
> >I looked back thru the archives and only found one mention of the
> >"RVEC Internal Error 700" message, which isnt applicable to my
> >situation.
> >
> >in short, mol 0.9.60 was working fine for me on 2.4.8-pre7 (benh) but
> >after i upgraded to 2.4.18-pre7 (also benh), mol dies with the
> >abovementioned error.
> >
> >at first i thought this was because i had to recompile the modules,
> >but after doing that i still have the same problem.
> >
> >anybody have any ideas? maybe its the kernel misreporting the cpu type
> >or something?
>
> Not sure about this one, but sounds like a problem with altivec. I
> know I had to hack my MOL to get altivec working. Also make sure
> you don't enable TAU interrupt support in the kernel, it tends to
> trigger some bad CPU bugs.
>
> Ben.
>
>
>
This archive was generated by hypermail 2a24 : Mon Feb 04 2002 - 10:31:29 MST