Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, Aug 19, 2005 at 09:22:09AM -0700, Peter Buckingham wrote: > >The machine is working quite a bit better with pci=noacpi in leu of > >disabling ACPI in the BIOS, but there are still those nasty errors in > >reference to the ACPI tables being broken: > >ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, > >AE_NOT_FOUND > >search_node 8101428572c0 start_node 8101428572c0 return_node > > > > since it doesn't look like you'll get a bios fix for this you may want > to look at building a custom dsdt. the kernel can load a custom dsdt > from an initrd/initramfs. have a look at the acpi site (acpi.sf.net?). > they talk about what's needed to do this. basically you can get your > dsdt from /proc/acpi/dsdt and disassemble it using the iasl tools, fix > it and then load it with an initrd. note that this is not really a > trivial task :-( Also, please file a bug report against the ACPI component at http://bugzilla.kernel.org . Ultimately the Linux ACPI component must deal with these sorts of errors, or convince the BIOS authors not to make them! -- Joseph Fannin [EMAIL PROTECTED] "That's all I have to say about that." -- Forrest Gump. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, Aug 19, 2005 at 09:22:09AM -0700, Peter Buckingham wrote: The machine is working quite a bit better with pci=noacpi in leu of disabling ACPI in the BIOS, but there are still those nasty errors in reference to the ACPI tables being broken: ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND search_node 8101428572c0 start_node 8101428572c0 return_node since it doesn't look like you'll get a bios fix for this you may want to look at building a custom dsdt. the kernel can load a custom dsdt from an initrd/initramfs. have a look at the acpi site (acpi.sf.net?). they talk about what's needed to do this. basically you can get your dsdt from /proc/acpi/dsdt and disassemble it using the iasl tools, fix it and then load it with an initrd. note that this is not really a trivial task :-( Also, please file a bug report against the ACPI component at http://bugzilla.kernel.org . Ultimately the Linux ACPI component must deal with these sorts of errors, or convince the BIOS authors not to make them! -- Joseph Fannin [EMAIL PROTECTED] That's all I have to say about that. -- Forrest Gump. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Sean Bruno wrote: Well, there doesn't appear to be any reference to a setting in my BIOS for this size(IOMMU). So I don't think that I can change it! :( well, it doesn't really matter since the kernel enables the IOMMU anyway. if you want to change the size you can pass that as a parameter on the command line. The machine is working quite a bit better with pci=noacpi in leu of disabling ACPI in the BIOS, but there are still those nasty errors in reference to the ACPI tables being broken: ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND search_node 8101428572c0 start_node 8101428572c0 return_node since it doesn't look like you'll get a bios fix for this you may want to look at building a custom dsdt. the kernel can load a custom dsdt from an initrd/initramfs. have a look at the acpi site (acpi.sf.net?). they talk about what's needed to do this. basically you can get your dsdt from /proc/acpi/dsdt and disassemble it using the iasl tools, fix it and then load it with an initrd. note that this is not really a trivial task :-( And this one about the 8254 timer: ..MP-BIOS bug: 8254 timer not connected to IO-APIC i've seen this before.. i think this may be related to the timer override not being done for your system (again strangely a bios bug...). why don't you try passing acpi_skip_timer_override on the command line. And finally, I think that something else kind of wierd is happening with the on-board sensors. lm_sensors is having trouble detecting the fan speeds and temperatures of the main board, but I will take that up with their developers. i think this may well be related to the ACPI issues you are having, since this is how the information is normally gathered. peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, 2005-08-19 at 08:59 -0700, Peter Buckingham wrote: > Andi Kleen wrote: > > On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: > > > >>Andi Kleen wrote: > >> > >>>At least his original error message can only happen when CONFIG_GART_IOMMU > >>>is disabled. > >>> > >>>PCI-DMA: More that 4GB of RAM and no IOMMU > >>>PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU > >> > >>Yeah, I agree. In the later dmesgs, though, it seems to be enabled. > > > > > > Those don't show any failure. > > no they don't. basically it just says your bios hasn't configured enough > IOMMU space, so the kernel is going to do it anyway. it's really just a > warning or an fyi rather than an error. i may have chosen the word > poorly ;-) > > in short Sean, this isn't a big deal. you only really need to change > this if you want to remove a warning from your dmesg output. > > peter Well, there doesn't appear to be any reference to a setting in my BIOS for this size(IOMMU). So I don't think that I can change it! :( The machine is working quite a bit better with pci=noacpi in leu of disabling ACPI in the BIOS, but there are still those nasty errors in reference to the ACPI tables being broken: ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND search_node 8101428572c0 start_node 8101428572c0 return_node And this one about the 8254 timer: ..MP-BIOS bug: 8254 timer not connected to IO-APIC And finally, I think that something else kind of wierd is happening with the on-board sensors. lm_sensors is having trouble detecting the fan speeds and temperatures of the main board, but I will take that up with their developers. Sean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Andi Kleen wrote: On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: Andi Kleen wrote: At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU Yeah, I agree. In the later dmesgs, though, it seems to be enabled. Those don't show any failure. no they don't. basically it just says your bios hasn't configured enough IOMMU space, so the kernel is going to do it anyway. it's really just a warning or an fyi rather than an error. i may have chosen the word poorly ;-) in short Sean, this isn't a big deal. you only really need to change this if you want to remove a warning from your dmesg output. peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: > Andi Kleen wrote: > >At least his original error message can only happen when CONFIG_GART_IOMMU > >is disabled. > > > >PCI-DMA: More that 4GB of RAM and no IOMMU > >PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU > > Yeah, I agree. In the later dmesgs, though, it seems to be enabled. Those don't show any failure. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Andi Kleen wrote: At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU Yeah, I agree. In the later dmesgs, though, it seems to be enabled. peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, Aug 19, 2005 at 08:38:25AM -0700, Peter Buckingham wrote: > Hi Sean, > > Sean Bruno wrote: > >Well, I do have IOMMU enabled in my kernel .config. I have attached it > >to this message as well. I would appreciate any guidance as I pretty > >much have no idea what 99% of the items in here are for. This is > >the .config that I used to build the kernel from the dmesg output that > >is attached to this email. > > the error that you see is because you haven't set a big enough size in > the BIOS for the IOMMU. The error message is just saying that the kernel > is enabling the IOMMU anyway. It used to be that it would enable 64MB, > it looks like it's defaulting now to 256MB. When you enable a big enough > size in the bios this error will go away (assuming that your bios fills > in the registers correctly). At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Hi Sean, Sean Bruno wrote: Well, I do have IOMMU enabled in my kernel .config. I have attached it to this message as well. I would appreciate any guidance as I pretty much have no idea what 99% of the items in here are for. This is the .config that I used to build the kernel from the dmesg output that is attached to this email. the error that you see is because you haven't set a big enough size in the BIOS for the IOMMU. The error message is just saying that the kernel is enabling the IOMMU anyway. It used to be that it would enable 64MB, it looks like it's defaulting now to 256MB. When you enable a big enough size in the bios this error will go away (assuming that your bios fills in the registers correctly). peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Hi Sean, Sean Bruno wrote: Well, I do have IOMMU enabled in my kernel .config. I have attached it to this message as well. I would appreciate any guidance as I pretty much have no idea what 99% of the items in here are for. This is the .config that I used to build the kernel from the dmesg output that is attached to this email. the error that you see is because you haven't set a big enough size in the BIOS for the IOMMU. The error message is just saying that the kernel is enabling the IOMMU anyway. It used to be that it would enable 64MB, it looks like it's defaulting now to 256MB. When you enable a big enough size in the bios this error will go away (assuming that your bios fills in the registers correctly). peter - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, Aug 19, 2005 at 08:38:25AM -0700, Peter Buckingham wrote: Hi Sean, Sean Bruno wrote: Well, I do have IOMMU enabled in my kernel .config. I have attached it to this message as well. I would appreciate any guidance as I pretty much have no idea what 99% of the items in here are for. This is the .config that I used to build the kernel from the dmesg output that is attached to this email. the error that you see is because you haven't set a big enough size in the BIOS for the IOMMU. The error message is just saying that the kernel is enabling the IOMMU anyway. It used to be that it would enable 64MB, it looks like it's defaulting now to 256MB. When you enable a big enough size in the bios this error will go away (assuming that your bios fills in the registers correctly). At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.6PCI-DMA: Disabling IOMMU -Andi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Andi Kleen wrote: At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.6PCI-DMA: Disabling IOMMU Yeah, I agree. In the later dmesgs, though, it seems to be enabled. peter - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: Andi Kleen wrote: At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.6PCI-DMA: Disabling IOMMU Yeah, I agree. In the later dmesgs, though, it seems to be enabled. Those don't show any failure. -Andi - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Andi Kleen wrote: On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: Andi Kleen wrote: At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.6PCI-DMA: Disabling IOMMU Yeah, I agree. In the later dmesgs, though, it seems to be enabled. Those don't show any failure. no they don't. basically it just says your bios hasn't configured enough IOMMU space, so the kernel is going to do it anyway. it's really just a warning or an fyi rather than an error. i may have chosen the word poorly ;-) in short Sean, this isn't a big deal. you only really need to change this if you want to remove a warning from your dmesg output. peter - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
On Fri, 2005-08-19 at 08:59 -0700, Peter Buckingham wrote: Andi Kleen wrote: On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote: Andi Kleen wrote: At least his original error message can only happen when CONFIG_GART_IOMMU is disabled. PCI-DMA: More that 4GB of RAM and no IOMMU PCI-DMA: 32bit PCI IO may malfunction.6PCI-DMA: Disabling IOMMU Yeah, I agree. In the later dmesgs, though, it seems to be enabled. Those don't show any failure. no they don't. basically it just says your bios hasn't configured enough IOMMU space, so the kernel is going to do it anyway. it's really just a warning or an fyi rather than an error. i may have chosen the word poorly ;-) in short Sean, this isn't a big deal. you only really need to change this if you want to remove a warning from your dmesg output. peter Well, there doesn't appear to be any reference to a setting in my BIOS for this size(IOMMU). So I don't think that I can change it! :( The machine is working quite a bit better with pci=noacpi in leu of disabling ACPI in the BIOS, but there are still those nasty errors in reference to the ACPI tables being broken: ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND search_node 8101428572c0 start_node 8101428572c0 return_node And this one about the 8254 timer: ..MP-BIOS bug: 8254 timer not connected to IO-APIC And finally, I think that something else kind of wierd is happening with the on-board sensors. lm_sensors is having trouble detecting the fan speeds and temperatures of the main board, but I will take that up with their developers. Sean - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Sean Bruno wrote: Well, there doesn't appear to be any reference to a setting in my BIOS for this size(IOMMU). So I don't think that I can change it! :( well, it doesn't really matter since the kernel enables the IOMMU anyway. if you want to change the size you can pass that as a parameter on the command line. The machine is working quite a bit better with pci=noacpi in leu of disabling ACPI in the BIOS, but there are still those nasty errors in reference to the ACPI tables being broken: ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND search_node 8101428572c0 start_node 8101428572c0 return_node since it doesn't look like you'll get a bios fix for this you may want to look at building a custom dsdt. the kernel can load a custom dsdt from an initrd/initramfs. have a look at the acpi site (acpi.sf.net?). they talk about what's needed to do this. basically you can get your dsdt from /proc/acpi/dsdt and disassemble it using the iasl tools, fix it and then load it with an initrd. note that this is not really a trivial task :-( And this one about the 8254 timer: ..MP-BIOS bug: 8254 timer not connected to IO-APIC i've seen this before.. i think this may be related to the timer override not being done for your system (again strangely a bios bug...). why don't you try passing acpi_skip_timer_override on the command line. And finally, I think that something else kind of wierd is happening with the on-board sensors. lm_sensors is having trouble detecting the fan speeds and temperatures of the main board, but I will take that up with their developers. i think this may well be related to the ACPI issues you are having, since this is how the information is normally gathered. peter - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
