Re: 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86_64

["Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>]

On Fri, Jun 29, 2007 at 12:23:43PM -0400, Muli Ben-Yehuda wrote:
> On Fri, Jun 29, 2007 at 08:28:58AM -0700, Keshavamurthy, Anil S wrote:
> 
> > +++ linux-2.6.22-rc4-mm2/drivers/pci/dmar.c	2007-06-29 07:46:25.000000000 -0700
> > @@ -260,6 +260,8 @@
> >  	int ret = 0;
> >  
> >  	dmar = (struct acpi_table_dmar *)dmar_tbl;
> > +	if (!dmar)
> > +		return -ENODEV;
> >  
> >  	if (!dmar->width) {
> >  		printk (KERN_WARNING PREFIX "Zero: Invalid DMAR haw\n");
> > @@ -301,7 +303,7 @@
> >  
> >  	parse_dmar_table();
> >  	if (list_empty(&dmar_drhd_units)) {
> > -		printk(KERN_ERR PREFIX "No DMAR devices found\n");
> > +		printk(KERN_INFO PREFIX "No DMAR devices found\n");
> >  		return -ENODEV;
> >  	}
> >  	return 0;
> 
> The convention is to print a KERN_DEBUG message if hardware is not
> found when probing it, otherwise the boot messages become cluttered
> with lots of "$FOO not found".

Since this is IOMMU is built into the kernel and it is
good idea to report that the device is not present. The 
above is printed only once and is consistent with other
IOMMU implementation. Atleast it is useful when people 
report bugs we can makeout whether IOMMU is being detected
or not.

Here is what I see on my box.
[..]
"PCI-GART: No AMD northbridge found."
[..]
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[..]

As you can see I don;t have either GART or Calgary on my box.

-Thanks,
Anil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/