Kernel compile fails with multiple definitions of do_drive_get_GTF

Bug #72014 reported by Davor Cubranic
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.15

I get the following error when compiling linux-source-2.6.15:
  LD drivers/built-in.o
ddrivers/scsi/built-in.o: In function `do_drive_get_GTF': multiple definition of `do_drive_get_GTF'
drivers/ide/built-in.o: first defined here
ld: Warning: size of symbol `do_drive_get_GTF' changed from 496 in drivers/ide/built-in.o to 1162 in drivers/scsi/built-in.o
make[2]: *** [drivers/built-in.o] Error 1
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/src/linux-source-2.6.15'
make: *** [stamp-build] Error 2

Revision history for this message
Davor Cubranic (cubranic) wrote :
Revision history for this message
Torbjörn Svensson (azoff) wrote :

Hello!

I can confirm this, but I have a temporary workaround. If you include the support for you IDE chipset (in my case nForce 550) and have the SATA as an module (in my case, also nForce 550). That would get around the bug, but this is the *only* module I have so it's kinda irritating to have it (I like to have a non-modular system on my servers).

Also, maybe off topic, but I am unable to make libata work without having ACPI with Suspend support and Hotplug compiled. I do not like to have suspend on a server (quite strange to have suspend on a server or? ;-)) nor do my server have Hotplugable hardware, so... Why do I need those to make the libata not have unresolved symbols?

From dmesg of broken modules attached.

Revision history for this message
Carlos Diener / emonkey (emonkey) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in linux-source-2.6.15:
status: New → Incomplete
Revision history for this message
Davor Cubranic (cubranic) wrote :

I'm running Hardy now, but haven't needed to compile the kernel recently, so I can't confirm the bug is still present, sorry.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Markus Korn (thekorn) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,
Markus

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.