Calgary should not be enabled in Intrepid's stock desktop kernel

Bug #252354 reported by Andrew Farmer on 2008-07-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Andy Whitcroft
Nominated for Intrepid by Andrew Farmer

Bug Description

Calgary is enabled in Intrepid desktop kernels, right now I am using 2.6.26-4 of course, I am trying to test a new DSDT table from Foxconn to fix many other errors their BIOS has, and possibly Linux bug(s) too.

I've been kicking e-mails back and forth between Matthew Garrett, I won't pretend to know exactly what Calgary is, but I don't believe it should be in stock kernel, just the SERVER kernel, unless I am missing something?

It sounds like all this does to the desktop kernel is sit there and spit out errors over hardware no desktop would have.

On Sun, Jul 27, 2008 at 04:23:26AM -0400 I wrote:

> Jul 26 08:46:50 ryan-desktop klogd: [ 0.004000] Calgary: detecting Calgary
> via BIOS EBDA area
> Jul 26 08:46:50 ryan-desktop klogd: [ 0.004000] Calgary: Unable to locate
> Rio Grande table in EBDA - bailing!

You've built a kernel that has CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT
set, and as a result it's attempting to probe for hardware you don't
have. This has nothing whatsoever to do with your ACPI tables. Calgary
is a piece of enterprise-level hardware that IBM ship on high-end
servers. If you've turned on that configuration options then you'll get
those messages whatever your ACPI tables say.
Matthew Garrett | <email address hidden>

description: updated
Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged

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.


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 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.

Ralph Janke (txwikinger) wrote :

The Intrepid Ibex 8.10 Beta release was most recently announced - . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

Changed in linux:
status: Triaged → Incomplete
Andy Whitcroft (apw) wrote :

The Clagary IOMMU is a feature of most of the x-series blades and motherboards, which would likely include some used on the desktop. I believe that the messages as reported above indicate that we did not find a suitable IOMMU and that support has been disabled.

@Andrew Farmer

Other than the error message emitted in the boot are you seeing any issues attributable to this error?

Andy Whitcroft (apw) on 2008-11-17
Changed in linux:
assignee: ubuntu-kernel-team → apw
Andy Whitcroft (apw) wrote :

This being enabled is benign on systems without the device, and them being in some released smaller X-series systems it seems safest for this to remain enabled.

Changed in linux:
status: Incomplete → Won't Fix
Kevin Cole (kjcole) wrote :

Perhaps just removing the "bailing!" (or even just the "!") from the message would be a good idea. "!" usually indicates important, and in a message like that, important bad thing happening.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers