fglrx: Unknown symbol __call_bad_lock_func

[Ryan Salomon]

When booting a generic kernel (2.6.28.11.15) X comes up fine, with 3D accel, compiz, etc.

When booting a realtime kernel (2.6.28-3-rt), the fglrx module appears to be loaded fine thru DKMS, but I get a corrupted screen when GDM loads. I can switch to a VT once, which just gets me a different corrupted screen, and I can't do anything from there, even flying blind.

Here's the output snippet from the gdm log, looked at after rebooting to the generic kernel:

FATAL: Error inserting fglrx (/lib/modules/2.6.28-3-rt/updates/dkms/fglrx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
(EE) fglrx(0): [FB] Can not get FB MC address range.
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(EE) fglrx(0): XMM failed to open CMMQS connection.
[glesx] __glESXExtensionInit: No GL ES2.0 capable screen found!

Here's the kernel message I got from dmesg:

fglrx: Unknown symbol __call_bad_lock_func

From stack trace during compile:

WARNING: "__call_bad_lock_func" [/var/lib/dkms/fglrx/8.602/build/2.6.x/fglrx.ko] undefined!
call is in linux-headers-2.6.28-3-rt

Possible packages installed, related to problem:
  linux-image-2.6.28-3-rt
  linux-rt-headers-2.6.28-3
  linux-headers-2.6.28-3-rt
  fglrx-kernel-source version 2:8.600-0ubuntu

Release: Ubuntu 9.04 AMD64
Video Card: ATI Radeon 3650 PCIExpress

[Scott Howard (showard314)]

Thanks for the report and helping make Ubuntu better!

Could you include:
Xorg.0.log
~/.xsession-errors

and the output from the command "lspci -vvnn"

You've probably tried these, but just in case, here are some other debugging tasks you can do to determine how complete X failure is:
+ Does ctrl+alt+f1 take you to a console?
+ Does ctrl+alt+backspace restart X?
+ Does mouse pointer still move?
+ Does the keyboard LED come on when hitting the CAPSLOCK key?
+ Can you ssh into the system from another computer?

[Shal (shal)]

Hello,

This bug remains.

When I try to compile fglrx by dkms for a 2.6.28-3-rt , dkms reporta successfull compil but with a warning (in verbose mode).
But when i try to load the module fglrx.ko , it's fail. The warning is in fact an error.

The warning (or error) is that "__call_bad_lock_func" is undefined (see trace).

I have look up this function: not used in ati driver but only declare on 2.6.28-3-rt header (as extern).

Warning: I used the ati driver 8.602 and not the 8.600

Ubuntu 9.04 and Radeon HD3450

[Scott Howard (showard314)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

WARNING: "__call_bad_lock_func" [/var/lib/dkms/fglrx/8.602/build/2.6.x/fglrx.ko] undefined!

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[specialk (geigerkr)]

I can confirm I still have this bug in the runtime kernel:

uname -a
Linux specialk 2.6.28-3-rt #12-Ubuntu SMP PREEMPT RT Fri Apr 17 10:09:12 UTC 2009 x86_64 GNU/Linux

sudo dpkg -l | grep fglrx
ii fglrx-amdcccle 2:8.650-0ubuntu1 Catalyst Control Center for the ATI graphics
ii fglrx-kernel-source 2:8.650-0ubuntu1 Kernel module source for the ATI graphics ac
ii fglrx-modaliases 2:8.650-0ubuntu1 Identifiers supported by the ATI graphics dr
ii xorg-driver-fglrx 2:8.650-0ubuntu1 Video driver for the ATI graphics accelerato

fglrxinfo
X Error of failed request: BadRequest (invalid request code or no such operation)
  Major opcode of failed request: 156 (GLX)
  Minor opcode of failed request: 19 (X_GLXQueryServerString)
  Serial number of failed request: 14
  Current serial number in output stream: 14

/var/log/syslog:
Sep 24 01:01:56 specialk kernel: [ 8445.427870] fglrx: Unknown symbol __call_bad_lock_func

[Alessio Igor Bogani (abogani)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that could be fixed in the Beta release of Karmic Koala. It would help us greatly if you could test with it! Thanks again and we appreciate your help.

[Ryan Salomon (chyldofthebeat)]

Well, I'm running Karmic Beta, and I dl/ed the 2.6.31-7-rt version of the kernel.
I installed version 8.660 of fglrx.
I booted X, and X booted, but started in Metacity, w/compiz unable to start.
It seems like dkms didn't (or couldn't) compile an fglrx module for the rt kernel, as I see none running.

If I run 'sudo dkms build -m fglrx -v 8.660', here's what I get:

Kernel preparation unnecessary for this kernel. Skipping...
applying patch fglrx-rt-compat.patch...patching file firegl_public.c
Hunk #1 FAILED at 1352.
Hunk #2 FAILED at 1377.
2 out of 2 hunks FAILED -- saving rejects to file firegl_public.c.rej
(bad exit status: 1)

Error! Application of patch fglrx-rt-compat.patch failed.
Check /var/lib/dkms/fglrx/8.660/build/ for more information.

I've attached the reject file. Let me know what else I should include, or if I'm completely barking up the wrong tree

[Alessio Igor Bogani (abogani)]

Ryan,

Very good catch!

Thanks!