Re: checking the release-critical bugs
> >
> > Now I wish I could find a solution for this PCI problem I'm getting
> > with this matrox milenium I put in my udb.. sigh.. anyone know what
> > the entInt() call does in the kernel? I did track my error down to
> > that.
>
> Well, this appears to be the main entry point for the kernel from user
> space, IIRIR. Where is the entInt being used that has to do with the
> Matrox? Is this a boot-up problem?
Okay I'll start at the begining.. I was tired of the TGA in my alpha..
and since I've heard that the matrox mileniums worked well in UDBs I
picked up one recently.. but I had problems unrelated to the normal
quirks of switching video setup.. I got this error from milo and
normal usage from shells (grabbed from my syslog):
Nov 22 07:40:48 localhost kernel: lca: machine check (la=0xfffffc00002084d0,pc=0xfffffc0000420d78)
Nov 22 07:40:48 localhost kernel: Reason: access to non-existent memory (long frame):
Nov 22 07:40:48 localhost kernel: reason: fffffc02017a7140 exc_addr: fffffc0000420d78 dc_stat: 7
Nov 22 07:40:48 localhost kernel: car: 40441141
Nov 22 07:40:48 localhost kernel: CPU initiated PCI Memory Read cycle to address bd388 failed due to target abort.
Nov 22 07:40:48 localhost kernel: + 0 0000000000000198 0000019800000110
Nov 22 07:40:48 localhost kernel: + 10 0000000100000084 fffffc02017a7140
Nov 22 07:40:48 localhost kernel: + 20 000006f800000000 00000000000bd38a
Nov 22 07:40:48 localhost kernel: + 30 0000000000000000 000000001ffff300
Nov 22 07:40:48 localhost kernel: + 40 0000000000000000 00000155557cd70c
Nov 22 07:40:48 localhost kernel: + 50 0000000000000008 0000000000000000
Nov 22 07:40:48 localhost kernel: + 60 fffffc00003111c0 0000000000010000
Nov 22 07:40:48 localhost kernel: + 70 fffffc00003112d0 fffffc0000311258
Nov 22 07:40:48 localhost kernel: + 80 fffffc0000311608 fffffc0000311818
Nov 22 07:40:48 localhost kernel: + 90 fffffc0000311348 fffffc0000208000
Nov 22 07:40:48 localhost kernel: + a0 000000011ffff700 fffffc000537bcc8
Nov 22 07:40:48 localhost kernel: + b0 fffffc000046c508 000000000000000a
Nov 22 07:40:48 localhost kernel: + c0 0032323a3a3e3e3e 00000155557cd70c
Nov 22 07:40:48 localhost kernel: + d0 0000000000000000 0000000000000001
Nov 22 07:40:48 localhost kernel: + e0 0000000000000000 0000000000000000
Nov 22 07:40:48 localhost kernel: + f0 0000000005330000 fffffffe00000000
Nov 22 07:40:48 localhost kernel: + 100 0000000000200000 00000000005e2b80
Nov 22 07:40:48 localhost kernel: + 110 fffffc0000420d78 0000000000000000
Nov 22 07:40:48 localhost kernel: + 120 0000000000000000 0000000000000000
Nov 22 07:40:48 localhost kernel: + 130 0000000000200000 0000000000001c70
Nov 22 07:40:48 localhost kernel: + 140 0000000000000022 0000000000005010
Nov 22 07:40:48 localhost kernel: + 150 0000000000000007 00000007ffffffff
Nov 22 07:40:48 localhost kernel: + 160 0000000000000428 67b0d8e800000000
Nov 22 07:40:48 localhost kernel: + 170 ffffffff80000070 0000000040441141
Nov 22 07:40:48 localhost kernel: + 180 000bc316000bc316 000bd388000bd388
Nov 22 07:40:48 localhost kernel: + 190 0000000000000000 0000000000000000
Okay I know its long.. but anyways.. Since it happened in milo I switched my
milo verion to one of Nikita's milos (had to grab it from Loics boot disk since
the the net didnt want me going to genie.ucd.ie for me) still got the above
errors. I eventually got to genie and DL'd the source and grep'd that for the
framework of the above errors.. nothing.. I checked the kernel source and found
it (made sense after I rememberd milo uses the kernel source) I backtraced..
lca_machine_check()
machine_check()
entInt()
If I remember everything correctly.. (not @ my machine right now)
So thats how I got to the original complaint(whine :P)
if you have any insight.. please enlighten me.
Phil.
Reply to: