| View previous topic :: View next topic |
| Author |
Message |
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
 Posted: Sun Nov 06, 2005 1:29 pm Post subject: fglrx driver spams dmesg |
 |
|
For some reason fglrx spam my dmesg like this:
| Code: | ...
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xd37623a0 still mapped
[fglrx:firegl_rmmap] *ERROR* map 0xf2cc82b0 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer qeue 0xf2cc82a0 still mapped
... |
And many, many more of those lines.
I don't even know when it actually happens, seems almost random. Sometimes after some time it's in it, sometimes after the same amount of time and similar things I've done it isn't. I tried remergin and recompiling kernel, removing and reinstalling ati-drivers, changing some settings in xorg.conf (happens with both UseInternalAGPGART on "on" and "off").
Any suggestions? |
|
| Back to top |
|
 |
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Thu Nov 10, 2005 2:45 pm Post subject: |
|
|
Does anyone have any suggestions?  |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Fri Nov 18, 2005 4:53 pm Post subject: |
|
|
Someone must know SOMETHING about this??
Perhaps useful, probably not. The number (0xf2cc82b0 in above example) is the same during subsequent spamming, but it's not always the same. Probably different between reboots or maybe X restarts.
If anyone even has a random suggestion, please tell me!
It's not like I have big problems, but it's quite annoying when I need useful dmesg output and /var/log/messages is getting quite big and filled with useless data... |
|
| Back to top |
|
|
Raistlin
l33t
Joined: 17 May 2004
Posts: 691
Location: Boston, MA
|
| Posted: Fri Nov 18, 2005 5:17 pm Post subject: |
|
|
Hi,
what kernel/ati-drivers version do you have?
_________________
Zwei Was Eins Initially
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1726
|
| Posted: Fri Nov 18, 2005 5:19 pm Post subject: |
|
|
| Well, I really have no idea what the problem is, but since no one else seems to be taking a crack at it let me ask if this is a new problem or has this been around for a while? I basically want to boil down to see if this could be tied to an upgraded kernel (I hear that 2.6.14 has had some issues with the ATI drivers (although I haven't had any problems yet that I haven't already had)) or if a simple re-compile of the drivers (which I believe need to be done after a kernel compile) would fix the problem. |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Fri Nov 18, 2005 6:07 pm Post subject: |
|
|
| My kernel is 2.6.14-gentoo-r2 and ati-drivers 8.19.10. I also had the problems with the 2.6.13-gentoo-r5 kernel and 8.18.something ati-drivers. |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1726
|
| Posted: Fri Nov 18, 2005 6:47 pm Post subject: |
|
|
| Have you re-compiled the drivers since updating the kernel. I had to, but I think that the problem I had was much different than the one you are experiencing. Also, is the fglrx module loading properly (this was the problem that I had - the new kernel broke the old drivers so I just had to do a quick re-compile and it fixed the issue) |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Fri Nov 18, 2005 6:53 pm Post subject: |
|
|
| When I had the old versions I recompiled the kernel, drivers, rebooted. When I installed the new kernel I recompiled the drivers and rebooted. With the new drivers I only recompiled those and rebooted. In all cases the same errors. The fglrx kernel module loads just fine without any errors. |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1726
|
| Posted: Fri Nov 18, 2005 8:05 pm Post subject: |
|
|
Since your module is loading fine you aren't having the issue I was.
Ok, I did a bit of searching and no one seems to have the exact problem that you are having, but I did find that for your error:
| Quote: | | [fglrx:firegl_rmmap] *ERROR* map 0xd37623b0 still in use (map_count=1) |
The following post: https://forums.gentoo.org/viewtopic-t-315616-highlight-fireglrmmap.html) suggested the following:
| Quote: |
dustfinger wrote:
[fglrx:firegl_rmmap] *ERROR* map 0xdcc7bf10 still in use (map_count=1)
[fglrx:firegl_rmmap] *ERROR* map 0xdcc7bed0 still in use (map_count=1)
[fglrx:firegl_rmmap] *ERROR* map 0xdf2da210 still in use (map_count=1)
[fglrx:firegl_rmmap] *ERROR* map 0xdf2da290 still in use (map_count=1)
[fglrx:firegl_rmmap] *ERROR* map 0xdf2da2d0 still in use (map_count=1)
I got rid of these errors by setting "UseInternalAGPGART" to "no".
|
These aren't the exact same errors, but I think it would be worth checking into.
Also check: https://forums.gentoo.org/viewtopic-t-358063-highlight-fireglrmmap.html
Their problems seems to be more complex than what you are having, but it is another place to look. |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Sat Nov 19, 2005 8:01 am Post subject: |
|
|
alienjon, thanks for your help, but I already found that thread. I've already tried with both UseInternalAGP to on and off but it makes no difference, like I also said in the startpost.
|
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1726
|
| Posted: Sat Nov 19, 2005 9:47 pm Post subject: |
|
|
| Oops. Must have missed that. |
|
| Back to top |
|
|
Kelvie
Tux's lil' helper
Joined: 13 Aug 2004
Posts: 88
Location: Richmond, BC
|
| Posted: Mon Nov 28, 2005 4:45 pm Post subject: |
|
|
| I have the exact same problem. It is extremely annoying because it essentially makes the syslog useless. Also , what video card are you using? I have a radeon mobility 9600 (M9 or M10, forget) |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Mon Nov 28, 2005 5:31 pm Post subject: |
|
|
I have a Sapphire ATI Radeon 9600XT.
... and still the same problem.
My system log is now 700MB+ lol. |
|
| Back to top |
|
|
Kelvie
Tux's lil' helper
Joined: 13 Aug 2004
Posts: 88
Location: Richmond, BC
|
| Posted: Mon Nov 28, 2005 7:00 pm Post subject: |
|
|
Hmm.. I think I've found out what causes mine (pending further testing).
I have xine set to opengl for video out -- fglrx doesn't like that. mplayer doesn't seem to have this problem when using -vo gl.
I set xine to xv for video output, and I am not getting those messages thusfar -- I wonder if any other apps try to access the video out the same way though. |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Mon Nov 28, 2005 8:53 pm Post subject: |
|
|
| Well I guess if you have direct rendering enabled that X itself uses opengl for rendering... |
|
| Back to top |
|
|
arabis
Apprentice
Joined: 11 Apr 2005
Posts: 195
Location: Québec, Canada
|
| Posted: Sat Jan 28, 2006 12:49 pm Post subject: |
|
|
I have these errors too.
These errors occurs when I play a video using opengl with mplayer or xine or when I play with Doom3demo.
But with kde opengl screensaver, no errors.
Is there someone who found a good solution for this problem (beside not using dri or not using opengl for video  ).
_________________
Acer Ferrari 4002 WLMI fr
AMD64, Turion ML-30
ATI Mobility X700
DVDR double couche |
|
| Back to top |
|
|
krazykit
Tux's lil' helper
Joined: 28 Aug 2004
Posts: 91
|
| Posted: Sat Jan 28, 2006 6:37 pm Post subject: |
|
|
| Quote: | | My system log is now 700MB+ lol. |
I checked my system log after you mentioned this... mine was 4 gigs... seems I misconfigured logging... and most of it WAS ATI spam. |
|
| Back to top |
|
|
beatryder
Veteran
Joined: 08 Apr 2005
Posts: 1138
|
| Posted: Sat Jan 28, 2006 7:10 pm Post subject: |
|
|
I have this same problem, it happens for me only when I play a garbled video, or play more than one video at a time
_________________
Dont make it idiot proof, make it work.
Neucode.org
<suppressed key> |
|
| Back to top |
|
|
arabis
Apprentice
Joined: 11 Apr 2005
Posts: 195
Location: Québec, Canada
|
| Posted: Sat Jan 28, 2006 10:11 pm Post subject: |
|
|
Are you using logrotate, otherwise:
This will give you a chance. 
| Quote: | | it happens for me only when I play a garbled video |
What do you mean "garbled"?
_________________
Acer Ferrari 4002 WLMI fr
AMD64, Turion ML-30
ATI Mobility X700
DVDR double couche |
|
| Back to top |
|
|
beatryder
Veteran
Joined: 08 Apr 2005
Posts: 1138
|
| Posted: Sun Jan 29, 2006 12:38 am Post subject: |
|
|
| Quote: | | What do you mean "garbled"? |
I mean corrupted, or the codec is wrong.
_________________
Dont make it idiot proof, make it work.
Neucode.org
<suppressed key> |
|
| Back to top |
|
|
arabis
Apprentice
Joined: 11 Apr 2005
Posts: 195
Location: Québec, Canada
|
| Posted: Tue Jan 31, 2006 3:30 pm Post subject: |
|
|
About this garbled thing: I check many videos and some doesn't give me errors messages and some does.
So, I guess the culprit is not ati-drivers but the videos themselves. Is there a way to fix these videos.
_________________
Acer Ferrari 4002 WLMI fr
AMD64, Turion ML-30
ATI Mobility X700
DVDR double couche |
|
| Back to top |
|
|
ahs
n00b
Joined: 28 Dec 2005
Posts: 3
|
| Posted: Sun Feb 05, 2006 9:54 am Post subject: |
|
|
I'm having the same problems here. My /var/log/message's growth is somewhere near 1 MB / minute
The error messages are different though. This is really getting annoying, since as the previous poster
mentioned, it makes syslog useless.
| Code: | Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] context 1 - use_count up to 1
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] got lock
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] switch context to 1...
Feb 5 10:52:25 manwe [fglrx:_r6x_switch_context] 0 => 1
Feb 5 10:52:25 manwe [fglrx:_r6x_switch_context] no context switch neccessary (b)
Feb 5 10:52:25 manwe [fglrx:_r6x_WaitNotBusy]
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] context 1 - use_count down to 0
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] context 1 has lock
Feb 5 10:52:25 manwe [fglrx:firegl_lock] 0x00000001 got lock -> set lock.priv = 0xf75305c0
Feb 5 10:52:25 manwe [fglrx:firegl_ioctl] ioctl finished, retcode = 0
|
|
|
| Back to top |
|
|
rickvernam
Guru
Joined: 09 Jul 2004
Posts: 313
|
| Posted: Tue Feb 07, 2006 4:04 pm Post subject: |
|
|
| ahs wrote: | I'm having the same problems here. My /var/log/message's growth is somewhere near 1 MB / minute
The error messages are different though. This is really getting annoying, since as the previous poster
mentioned, it makes syslog useless.
| Code: | Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] context 1 - use_count up to 1
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] got lock
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] switch context to 1...
Feb 5 10:52:25 manwe [fglrx:_r6x_switch_context] 0 => 1
Feb 5 10:52:25 manwe [fglrx:_r6x_switch_context] no context switch neccessary (b)
Feb 5 10:52:25 manwe [fglrx:_r6x_WaitNotBusy]
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] context 1 - use_count down to 0
Feb 5 10:52:25 manwe [fglrx:firegl_lock_device] context 1 has lock
Feb 5 10:52:25 manwe [fglrx:firegl_lock] 0x00000001 got lock -> set lock.priv = 0xf75305c0
Feb 5 10:52:25 manwe [fglrx:firegl_ioctl] ioctl finished, retcode = 0
|
|
Having the EXACT same chunk of messages here (not my system - a co-workers). what versions of xorg, kernel, ati-drivers, ati card & do you have UseInternalAGPGART set to yes or no? |
|
| Back to top |
|
|
thomasvk
Guru
Joined: 19 Mar 2005
Posts: 597
|
| Posted: Sun Jul 09, 2006 11:02 am Post subject: |
|
|
Hi there!
By now my old videocard (9600XT) has broken and I lived with an NVidia 6600LE for a while. Now I'm back with an ATI card, the X800Pro, again. Until now I used the 'radeon' driver but I thought I'd give the binary drivers a go... and what do you know!? The same fooking errors spamming my system log again. I cannot believe there's no-one who has a solution for this or AT LEAST know WHERE it's coming from, what the CAUSE is. It's very frustrating. |
|
| Back to top |
|
|
rickvernam
Guru
Joined: 09 Jul 2004
Posts: 313
|
| Posted: Sun Jul 09, 2006 2:21 pm Post subject: |
|
|
I can't be sure what was causing the problem, nor what made it go away.
The solution I had to come up with was to turn of syslog b/c /var/log/messages was needing to be emptied every day to keep the hd from filling.
At some point later, I had to do something to the system that required me to view the log, so I tunred syslog back on. at that point, fglrx was not spamming the log.
I, unfortunately, do not know what changes were made to the system during that period of time. |
|
| Back to top |
|
|
|
Kernel & Hardware
