From: Michael H. <mho...@gr...> - 2005-06-24 18:49:29
|
The crash is being caused in the pixel packing routines. There is nothing obvious at the moment, so I'm going to backtrack through revisions until I can track down the change list. -Mike Michael Houston wrote: > Hrmm. With top of tree, Quake is segfaulting, at least on my config > (RHEL4 an ATI 9800s with 8.14.13 drivers) running even through > crdemo.conf. It runs fine alone. Good fun, this might take awhile to > track down. > > -Mike > > Nathan Jeffery wrote: > >> Hi mike >> >> thanks for the response, i've tested all the bucket modes, but had no >> difference in effect. I havent tried disabling DLM yet, but will try >> that later today and report on the effect. >> >> Thankyou also for taking the timeout to investigate next week, will >> hopefully be able to provide more details before then >> >> BTW what are you still doing awake :-), I didn't expect a response >> until tomorrow >> >> Best regards >> >> Nathan >> >> >> On Fri, 24 Jun 2005, Mike Houston wrote: >> >>> I haven't tested quake in awhile, but I remember I had issues if >>> Quake ran full screen, but no issues if I ran it in an X window. I >>> don't remember if I was having texturing issues or just performance >>> problems. I'll try to find some time next week to take a look. >>> Although, this might be a new phenomenon as we've seen scattered >>> reports of various apps not displaying texture when running through >>> chromium. Maybe a DLM bug has crept in? What happens if you >>> disable DLM in the tilesort SPU? What about different bucket modes >>> like broadcast? >>> >>> -Mike >>> >>> Nathan Jeffery wrote: >>> >>>> >>>> Hi >>>> >>>> i have another slight application niggle, and knowing alot of >>>> people have fully "tested" quake within chromium I'm certain that >>>> someone on this list will have the answer, Mike? :-) . >>>> >>>> When running quake3 on a linux box, with the output going to a 6 >>>> channel render setup, the application runs fully though there >>>> appears to be a distinct lack of textures being drawn. When running >>>> quake3 on a windows setup the scene is fully drawn. >>>> >>>> I've had the same problem with wildcat cards in the machines, and >>>> now fx3000g's. >>>> >>>> Is there a simple explanation as to why this might be the case >>>> under linux? >>>> >>>> thankyou in advance >>>> >>>> nathan >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >>>> from IBM. Find simple to follow Roadmaps, straightforward articles, >>>> informative Webcasts and more! Get everything you need to get up to >>>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >>>> _______________________________________________ >>>> Chromium-users mailing list >>>> Chr...@li... >>>> https://lists.sourceforge.net/lists/listinfo/chromium-users >>> >>> >>> >>> >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Chromium-users mailing list >> Chr...@li... >> https://lists.sourceforge.net/lists/listinfo/chromium-users > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Chromium-users mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-users |
From: Brian P. <bri...@tu...> - 2005-06-24 20:08:06
|
Michael Houston wrote: > The crash is being caused in the pixel packing routines. There is > nothing obvious at the moment, so I'm going to backtrack through > revisions until I can track down the change list. I made some changes in some pixel packing code a few weeks ago. If you can tell me how to reproduce the problem with a small test case, I can look into it (but perhaps not until next week). -Brian |
From: Michael H. <mho...@gr...> - 2005-06-24 20:58:58
|
CR-1.7 works just fine. -Mike Brian Paul wrote: > Michael Houston wrote: > >> The crash is being caused in the pixel packing routines. There is >> nothing obvious at the moment, so I'm going to backtrack through >> revisions until I can track down the change list. > > > I made some changes in some pixel packing code a few weeks ago. If > you can tell me how to reproduce the problem with a small test case, I > can look into it (but perhaps not until next week). > > -Brian > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Chromium-dev mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-dev |
From: Michael H. <mho...@gr...> - 2005-06-25 01:00:29
|
1.8 is okay as well... The textures seem to be working there for me. I'm running quake3 in a window and not full screen. Full screen seems to have display issues. Not sure what's going on there, but I remember I always had problems with the full screen mode running through Chromium (WireGL as well). The segfaults I'm seeing crept in somewhere between 1.8 and top of tree. It segfaults almost immediately when loading the splash screen (texture). -Mike Michael Houston wrote: > CR-1.7 works just fine. > > -Mike > > Brian Paul wrote: > >> Michael Houston wrote: >> >>> The crash is being caused in the pixel packing routines. There is >>> nothing obvious at the moment, so I'm going to backtrack through >>> revisions until I can track down the change list. >> >> >> >> I made some changes in some pixel packing code a few weeks ago. If >> you can tell me how to reproduce the problem with a small test case, >> I can look into it (but perhaps not until next week). >> >> -Brian >> >> >> ------------------------------------------------------- >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >> from IBM. Find simple to follow Roadmaps, straightforward articles, >> informative Webcasts and more! Get everything you need to get up to >> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click >> _______________________________________________ >> Chromium-dev mailing list >> Chr...@li... >> https://lists.sourceforge.net/lists/listinfo/chromium-dev > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Chromium-dev mailing list > Chr...@li... > https://lists.sourceforge.net/lists/listinfo/chromium-dev |