On Sun, 28 Apr 2002, Leif Delgass wrote: > On Sun, 28 Apr 2002, Peter Andersson wrote: > > > Leif Delgass wrote: > > > > >On Sun, 28 Apr 2002, Peter Andersson wrote: > > > > > >>>Well, it looks like the _dispatch_clear completes without a > > >>>problem. Could you run ksymoops on the syslog? That will decode the back > > >>>trace from the oops (it's best to run it right after the oops before you > > >>>reboot, so you use the symbol table from the modules installed at the time > > >>>of the error). > > >>> > > >>It is included in this email. > > >> > > > > > >I didn't get an attachment, could you send it again? > > > > > > > > > > Sorry, wrong attatchment. I don´t know whats wrong with me, didn´t get > > much sleep last night. Here is the right attatchment. > > I know the feeling. ;) > > Well, it looks like you're probably getting the oops at the same point > that I am when I run without agpgart. Next time you get an oops, try to > run ksymoops before rebooting, you'll get fewer warnings and a more > accurate trace. Anyway, I think this is enough info for now. I'll try to > track down and fix the oops I'm seeing on x86 and then we'll see if that > fixes your problem. From your other email, it looks like the bus master > test is working, so that's good news.
OK, I found out what was causing the oops, but I'm not sure why yet. It was in mach64_dma_vertex: buf_priv->prim = vertex.prim; buf_priv->discard = vertex.discard; I've disabled these lines until I can figure out what's wrong. Peter can you update cvs and try it again? -- Leif Delgass http://www.retinalburn.net _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
