WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen 3.0 testing ACPI problems / no PCI functionality

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] xen 3.0 testing ACPI problems / no PCI functionality
From: Ralph Passgang <ralph@xxxxxxxxxxxxx>
Date: Mon, 9 Jan 2006 21:38:59 +0100
Delivery-date: Mon, 09 Jan 2006 20:44:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43C2ACB1.3090701@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D40A066@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <43C2ACB1.3090701@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.3
If you want another "rubbish" oppinion, then I think it is either your kernel 
config or your chipset that is causing the trouble.

you said you have an sis chipset. In the past (about 1 to maybe 2 years maybe) 
sis chipset were known to be not really working well with linux.

For example I had trouble with two pc's having a sis chipset (diffrent ones!). 
on the first pc std. ethernet nics like 3com, intel, etc. was not working 
(even not listed in lcpci when acpi was on, without acpi there were listed 
but not working). On the other we had a lot of trouble to get a t1/e1 telco 
pri card running, which needs 1000 interrupts/sec, which was obvously to much 
for the sis chipset wih an 1Ghz CPU (at least with linux)... on a bulk 333mhz 
system with an intel chipset there was no interrupt problems at all.

but that are only my 50 cents :)

btw. before getting unpolite, what about sending your kernel config to the 
list, so that someone has a chance to reproduce that... until now nobody get 
enough information from you to really help. and don't say ian hasn't tried to 
help.

and why don't you simply try a std. xen kernel config and maybe "acpi=off"?

If this works with your pc, then it's time to see why your own config is not 
working or what else the problem could be.

if it also doesn't work, then it's probably something else, but at least it is 
sure that there were no stupid mistakes in the kernel config.

You want something, do something...

--Ralph

Am Montag, 9. Januar 2006 19:34 schrieb Patrick:
> thats rubbish .. if you cant tell me what should be up with my config,
> then better dont say anything at all. You even did not listen that I
> compiled a vanilla kernel with the kernel config that does NOT work with
> xen, but with the vanilal kernel PCI works goddamn fine.
> Secondly, if you read my posts before more carefully then you'd know
> that my bios supports ACPI and that the xen kernel (although without
> PCI) boots but then it's rebooting and saying that I didnt not allocated
> enough memory for the memory reservation of dom0 (while without apci
> enabled it doesnt do this and boots fine, just without PCI).
> Thus its neither a fault of my config nor of anything else that is
> related to my person, but only to xen and its faultiness.
>
> Patrick
>
> Ian Pratt wrote:
> >>FFS .. I do not care about ACPI .. now I ask you the _second
> >>time_ to refer to my PCI problem as without PCI nothing works at all.
> >
> >If you use one of our kernels PCI will likely work fine. If you've got a
> >broken bios that doesn't do acpi then disable it with acpi=off on the
> >xen command line. I'd much rather help you get something working with a
> >known good kernel than trying to second guess all the possible ways you
> >could have botched your own config...
> >
> >Ian
> >
> >>Patrick
> >>
> >>Ian Pratt wrote:
> >>>>First of all .. as I said ACPI was the reason why my mashine was
> >>>>constantly rebooting as - if ACPI enabled - xen does did not detect
> >>>>the amount of RAM properly and thus is always claiming it wasnt
> >>>>enough.
> >>>>Sencondly, the xen kernel config is not that much different
> >>
> >>to mine ..
> >>
> >>>>my kernel is just more lightweight tho.
> >>>>...
> >>>>ACPI isnt the main problem, could you please also refer to
> >>
> >>the second
> >>
> >>>>problem, which is of much more importance to me?
> >>>
> >>>Can you not just put 'acpi=off' on the *xen* command line (not the
> >>>linux one)?
> >>>
> >>>Please try this with the -xen kernel.
> >>>
> >>>Ian
> >>>
> >>>>best regards,
> >>>>Patrick
> >>>>
> >>>>Ian Pratt wrote:
> >>>>>>I just encountered that the xen 3.0 testing (from the mercurial
> >>>>>>repository) will not work if I have ACPI compiled into the kernel.
> >>>>>>Although the kernel will build properly, I cant boot it,
> >>
> >>as xen is
> >>
> >>>>>>constantly moaning about the amount of memory reservated
> >>>>
> >>>>for dom0 and
> >>>>
> >>>>>>thus is rebooting again and again (the appropiate settings
> >>>>
> >>>>are given
> >>>>
> >>>>>>and correct).
> >>>>>
> >>>>>Any reason not to be using our -xen kernel config? It has
> >>>>
> >>>>ACPI and sems
> >>>>
> >>>>>to work fine for the almost everyone.
> >>>>>
> >>>>>Ian
> >>>>>
> >>>>>>I confirmed this by NOT compiling ACPI into my kernel at
> >>>>
> >>>>all .. then
> >>>>
> >>>>>>xen boots up fine... BUT then I do not have PCI
> >>>>
> >>>>functionality at all
> >>>>
> >>>>>>(which means lspci is empty and all my PCI devices do not
> >>>>
> >>>>work, even
> >>>>
> >>>>>>not if I try to load the appropiate driver manually). Again the
> >>>>>>settings (config) are compiled in and correctly set (which simply
> >>>>>>means I wasnt a jerk and forgot compiling PCI support in tho).
> >>>>>>I am using sis5513 as mainboard chipset and another
> >>>>
> >>>>confirmation on my
> >>>>
> >>>>>>side, as far as the problerm above's concerned, is that I tried
> >>>>>>exactly the same kernel config (without the xen config symbols of
> >>>>>>course) and compiled a vanilla 2.6.12.6 kernel manually ..
> >>>>
> >>>>it boots up
> >>>>
> >>>>>>fine and PCI support is also given, while doing the same with a
> >>>>>>xen-patched kernel will not work at all and results in pci
> >>>>>>non-functionality.
> >>>>>>
> >>>>>>Any further confirmation about the two problems I mentioned above
> >>>>>>would be appreciated.
> >>>>>>
> >>>>>>
> >>>>>>best regards,
> >>>>>>Patrick
> >>>>>>
> >>>>>>
> >>>>>>_______________________________________________
> >>>>>>Xen-users mailing list
> >>>>>>Xen-users@xxxxxxxxxxxxxxxxxxx
> >>>>>>http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users