Hi, I have a tyan mainboard with an AMD-8131 PCI-X Bridge. With xen3-testing all PCI-X devices behind that bridge (and the bridge itself) are invisible to the xen0 kernel (in lspci). With xen2-testing it works. I greped the sources for ''AMD-8131'' and ''8131'' and found that xen3 does not contain something, but xen2 seem to have something in it, so that it detects that PCI-X Bridge. From the xen2 sources: "drivers/pci/quirks.c: printk(KERN_INFO "Fixing up AMD8131 IOAPIC mode\n");" Can''t I use my tyan mainboard with xen3 ? Why this stuff in /xen/drivers/pci/* making the PCI-X-Bridge work has been removed in xen3 ? Anyway I can''t even use xen2, because the sava_nv driver hungs at initialisation (with xen3 it sata_nv works, but the tigon3 onboard network-chip in unavailable cause its behind that bridge). I also tried with noapic, but no luck. Anyone has a hint for me ? Thank you very much in advance ! Regards Sebastian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 30 January 2006 14:57, Sebastian Böhm wrote:> I have a tyan mainboard with an AMD-8131 PCI-X Bridge. > > With xen3-testing all PCI-X devices behind that bridge (and the bridge > itself) are invisible to the xen0 kernel (in lspci). > With xen2-testing it works. > > > I greped the sources for ''AMD-8131'' and ''8131'' and found that xen3 does > not contain something, but xen2 seem to have something in it, so that it > detects that PCI-X Bridge.Upsie, We were planning on buying one of those thingies, too (for use with xen), with quad dual-core opterons, tons of RAM, and PCI-X Adaptecs to connect the external RAIDs... Looks like we better wait a bit, then. For the 2.0->3.0 changes you mentioned: I think thats because xen3 now doesn''t do much hardware initialization itself, instead relies on dom0 to do so. Did you check the dom0 kernel config if it contains the neccessary functions? If you create a non-xen kernel with the same config (copy the .config into a vanilla kernel dir, run make oldconfig), does that one work with PCI-X? Would be great if you could keep me updated if you make any progress with your board. Good luck /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ernst Bachmann schrieb:> On Monday 30 January 2006 14:57, Sebastian Böhm wrote: > >> I have a tyan mainboard with an AMD-8131 PCI-X Bridge. >> >> With xen3-testing all PCI-X devices behind that bridge (and the bridge >> itself) are invisible to the xen0 kernel (in lspci). >> With xen2-testing it works. >> >> >> I greped the sources for ''AMD-8131'' and ''8131'' and found that xen3 does >> not contain something, but xen2 seem to have something in it, so that it >> detects that PCI-X Bridge. >> > > Upsie, We were planning on buying one of those thingies, too (for use with > xen), with quad dual-core opterons, tons of RAM, and PCI-X Adaptecs to > connect the external RAIDs... > > Looks like we better wait a bit, then. > > For the 2.0->3.0 changes you mentioned: I think thats because xen3 now doesn''t > do much hardware initialization itself, instead relies on dom0 to do so. > > Did you check the dom0 kernel config if it contains the neccessary functions? > If you create a non-xen kernel with the same config (copy the .config into a > vanilla kernel dir, run make oldconfig), does that one work with PCI-X? >This was the first thing I tried. And yes: without xen it does work (i use the same kernel-config for xen2, and there pcix works also).> Would be great if you could keep me updated if you make any progress with your > board. > > Good luck > /Ernst >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Did you check the dom0 kernel config if it contains the neccessary > > functions? If you create a non-xen kernel with the same config (copy the > > .config into a vanilla kernel dir, run make oldconfig), does that one > > work with PCI-X? > > This was the first thing I tried. And yes: without xen it does work (i > use the same kernel-config for xen2, and there pcix works also).Unfortunately you can''t just copy the config from the Xen2 kernel to the Xen3 kernel: the PCI functionality that you saw in Xen 2 hasn''t been *removed*, it''s just been *moved* into Linux itself and out of Xen. The Linux/Xen2 kernel config won''t have the PCI quirk handling code because PCI quirks were handled by Xen itself. In Xen 3, Linux needs to have this enabled because Xen will not help it anymore. Can you verify that any config options for your board that are enabled in your native Linux build are also enabled under the Xen 3-patched Linux kernel? Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Mark Williamson > Sent: 30 January 2006 14:24 > To: xen-users@lists.xensource.com > Cc: Ernst Bachmann; Sebastian Böhm > Subject: Re: [Xen-users] AMD-8131 > > > > Did you check the dom0 kernel config if it contains the > neccessary > > > functions? If you create a non-xen kernel with the same > config (copy > > > the .config into a vanilla kernel dir, run make oldconfig), does > > > that one work with PCI-X? > > > > This was the first thing I tried. And yes: without xen it > does work (i > > use the same kernel-config for xen2, and there pcix works also). > > Unfortunately you can''t just copy the config from the Xen2 > kernel to the Xen3 > kernel: the PCI functionality that you saw in Xen 2 hasn''t > been *removed*, it''s just been *moved* into Linux itself and > out of Xen. > > The Linux/Xen2 kernel config won''t have the PCI quirk > handling code because PCI quirks were handled by Xen itself. > In Xen 3, Linux needs to have this enabled because Xen will > not help it anymore. > > Can you verify that any config options for your board that > are enabled in your native Linux build are also enabled under > the Xen 3-patched Linux kernel? > > Cheers, > Mark >The fix in quirks.c isn''t something that will make the devices behind the PCI-X bridge disappear or appear - it sets a signle bit in a configuration register, which I think deals with Message Signaled Interrupts [based on the printout comments]. If the devices behind 8131 don''t appear, then there''s something wrong with the PCI enumeration, which not directly related to the quirks.c code. -- Mats _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson schrieb:>>> Did you check the dom0 kernel config if it contains the neccessary >>> functions? If you create a non-xen kernel with the same config (copy the >>> .config into a vanilla kernel dir, run make oldconfig), does that one >>> work with PCI-X? >>> >> This was the first thing I tried. And yes: without xen it does work (i >> use the same kernel-config for xen2, and there pcix works also). >> > > Unfortunately you can''t just copy the config from the Xen2 kernel to the Xen3 > kernel: the PCI functionality that you saw in Xen 2 hasn''t been *removed*, > it''s just been *moved* into Linux itself and out of Xen. > > The Linux/Xen2 kernel config won''t have the PCI quirk handling code because > PCI quirks were handled by Xen itself. In Xen 3, Linux needs to have this > enabled because Xen will not help it anymore. > > Can you verify that any config options for your board that are enabled in your > native Linux build are also enabled under the Xen 3-patched Linux kernel? >100% sure. I tested also with the http://xenbits.xensource.com/linux-2.6-xen.hg kernel. I made one with "Xen-Compatible" and one with "PC-Compatible", so all device options are 100% the same. The direct-booted "PC-Compatible" Kernel detected the PCI-Bus behind that amd-8131 bridge, the "Xen-Compatible" kernel booted with xen3-unstable did not detect the PCI-X Bridge and all devices behind it. So there must be a problem with xen, I presume. /sebastian> Cheers, > Mark > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, could it be that the bridge not gets detected cause I boot with the "noapic" option ? I boot the native kernel also with "noapic" and there it gets detected, but maybe under xen this behaves differend. I need "noapic", because otherwise sata_nv would crash. /sebastian Sebastian Böhm schrieb:>> >> Can you verify that any config options for your board that are enabled in your >> native Linux build are also enabled under the Xen 3-patched Linux kernel? >> > 100% sure. > > I tested also with the http://xenbits.xensource.com/linux-2.6-xen.hg > kernel. > > I made one with "Xen-Compatible" and one with "PC-Compatible", so all > device options are 100% the same. > > The direct-booted "PC-Compatible" Kernel detected the PCI-Bus behind > that amd-8131 bridge, the "Xen-Compatible" kernel booted with > xen3-unstable did not detect the PCI-X Bridge and all devices behind it. > > So there must be a problem with xen, I presume. > > /sebastian >> Cheers, >> Mark >> >> > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users