Константин Алексеев
2011-Aug-16 08:27 UTC
[Xen-devel] with kernel''s option ''nosmp'', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
Xen 4.1.1, Kernel 3.0, Debian Weezy. LSI Logic / Symbios Logic SAS1064ET does not initialized, if boot dom0 with kernel''s option ''nosmp''. Under native it does not happen. With Squeezy i have the same bug. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637308 (XEN) Xen version 4.1.1 (Debian 4.1.1-2) (waldi@debian.org) (gcc) ... [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (ben@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-4) ) #1 SMP Sun Jul 24 02:24:44 UTC 2011 [ 0.000000] Command line: placeholder root=/dev/mapper/mpath-system-part1 ro console=tty0 console=hvc0 nosmp ... [ 0.131396] PCI: Probing PCI hardware [ 0.140008] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.140008] pci 0000:00:02.0: PCI bridge to [bus 01-06] [ 0.143634] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.145017] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.148008] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.148008] pci 0000:01:00.0: PCI bridge to [bus 02-05] [ 0.148008] pci 0000:02:00.0: PCI bridge to [bus 03-03] [ 0.152008] pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.152008] pci 0000:02:01.0: PCI bridge to [bus 04-04] [ 0.161156] pci 0000:05:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.161477] pci 0000:02:02.0: PCI bridge to [bus 05-05] [ 0.164009] pci 0000:01:00.3: PCI bridge to [bus 06-06] [ 0.164009] pci 0000:00:03.0: PCI bridge to [bus 07-07] [ 0.164408] pci 0000:08:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with ''pcie_aspm=force'' [ 0.164428] pci 0000:00:04.0: PCI bridge to [bus 08-08] [ 0.164505] pci 0000:00:05.0: PCI bridge to [bus 09-09] [ 0.164581] pci 0000:00:06.0: PCI bridge to [bus 0a-0a] [ 0.164657] pci 0000:00:07.0: PCI bridge to [bus 0b-0b] [ 0.164948] pci 0000:00:1e.0: PCI bridge to [bus 0c-0c] (subtractive decode) [ 0.166126] vgaarb: device added: PCI:0000:0c:0c.0,decodes=io+mem,owns=io+mem,locks=none [ 0.168009] pci 0000:00:1f.0: PIIX/ICH IRQ router [8086:2670] [ 0.168015] pci 0000:00:00.0: found PCI INT A -> IRQ 10 [ 0.168026] pci 0000:00:00.0: sharing IRQ 10 with 0000:00:02.0 [ 0.168033] pci 0000:00:00.0: sharing IRQ 10 with 0000:00:03.0 [ 0.168041] pci 0000:00:00.0: sharing IRQ 10 with 0000:00:04.0 [ 0.168050] pci 0000:00:00.0: sharing IRQ 10 with 0000:00:05.0 [ 0.168058] pci 0000:00:00.0: sharing IRQ 10 with 0000:00:06.0 [ 0.168067] pci 0000:00:00.0: sharing IRQ 10 with 0000:00:07.0 [ 0.168457] pci 0000:00:00.0: sharing IRQ 10 with 0000:08:00.0 [ 0.169859] Switching to clocksource xen [ 0.171492] pnp: PnP ACPI: disabled [ 0.171492] Switched to NOHz mode on CPU #0 [ 0.175024] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 0.175044] pci 0000:04:00.0: no compatible bridge window for [mem 0xffe00000-0xffffffff pref] [ 0.175052] pci 0000:08:00.0: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref] [ 0.175059] pci 0000:08:00.1: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref] [ 0.176054] pci 0000:00:02.0: BAR 15: assigned [mem 0xb8e00000-0xb8ffffff pref] [ 0.176054] pci 0000:00:04.0: BAR 15: assigned [mem 0xb9000000-0xb90fffff pref] [ 0.176054] pci 0000:01:00.0: BAR 15: assigned [mem 0xb8e00000-0xb8ffffff pref] [ 0.176054] pci 0000:02:01.0: BAR 15: assigned [mem 0xb8e00000-0xb8ffffff pref] [ 0.176054] pci 0000:02:00.0: BAR 14: can''t assign mem (size 0x200000) [ 0.176054] pci 0000:02:00.0: BAR 15: can''t assign mem pref (size 0x200000) [ 0.176054] pci 0000:02:00.0: BAR 13: can''t assign io (size 0x1000) [ 0.176054] pci 0000:02:00.0: PCI bridge to [bus 03-03] [ 0.176054] pci 0000:02:00.0: bridge window [io disabled] [ 0.176054] pci 0000:02:00.0: bridge window [mem disabled] [ 0.176054] pci 0000:02:00.0: bridge window [mem pref disabled] [ 0.176054] pci 0000:04:00.0: BAR 6: assigned [mem 0xb8e00000-0xb8ffffff pref] [ 0.176054] pci 0000:02:01.0: PCI bridge to [bus 04-04] [ 0.176054] pci 0000:02:01.0: bridge window [io 0x4000-0x4fff] [ 0.176054] pci 0000:02:01.0: bridge window [mem 0xb8900000-0xb89fffff] [ 0.176054] pci 0000:02:01.0: bridge window [mem 0xb8e00000-0xb8ffffff pref] [ 0.176054] pci 0000:02:02.0: PCI bridge to [bus 05-05] [ 0.176054] pci 0000done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/mpath-system-part1 does not exist. Dropping to a shell! (initramfs) ls /dev/mapper/ control (initramfs) ls /dev/sd* ls: /dev/sd*: No such file or directory (initramfs) -- Konstantin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Aug-17 02:14 UTC
Re: [Xen-devel] with kernel''s option ''nosmp'', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
On Tue, Aug 16, 2011 at 12:27:44PM +0400, Константин Алексеев wrote:> Xen 4.1.1, Kernel 3.0, Debian Weezy. > LSI Logic / Symbios Logic SAS1064ET does not initialized, if boot dom0 > with kernel''s option ''nosmp''.But it does initialize if you don''t use nosmp? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Константин Алексеев
2011-Aug-17 05:28 UTC
Re: [Xen-devel] with kernel''s option ''nosmp'', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
2011/8/17 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:> On Tue, Aug 16, 2011 at 12:27:44PM +0400, Константин Алексеев wrote: >> Xen 4.1.1, Kernel 3.0, Debian Weezy. >> LSI Logic / Symbios Logic SAS1064ET does not initialized, if boot dom0 >> with kernel''s option ''nosmp''. > > But it does initialize if you don''t use nosmp? >Yes, if don''t use nosmp with dom0 it does initialize. -- Konstantin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Aug-17 05:29 UTC
Re: [Xen-devel] with kernel''s option ''nosmp'', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
On Wed, Aug 17, 2011 at 09:13:01AM +0400, Константин Алексеев wrote:> 2011/8/17 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>: > > On Tue, Aug 16, 2011 at 12:27:44PM +0400, Константин Алексеев wrote: > >> Xen 4.1.1, Kernel 3.0, Debian Weezy. > >> LSI Logic / Symbios Logic SAS1064ET does not initialized, if boot dom0 > >> with kernel''s option ''nosmp''. > > > > But it does initialize if you don''t use nosmp? > > > > Yes, if don''t use nosmp with dom0 it does initialize.Please do ever remove the xen-devel from the email exchange. Did you follow also the suggestions in the bugzilla from Ian (about dom0_..) ? Did that fix the issue? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Константин Алексеев
2011-Aug-17 06:16 UTC
Re: [Xen-devel] with kernel''s option ''nosmp'', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
2011/8/17 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:> Did you follow also the suggestions in the bugzilla from Ian (about dom0_..) ? > Did that fix the issue?If you mean suggestions from Ian in debian bug report, then yes, I use dom0_max_vcpus=1 and everything works well. Ian asked to test this bug with the latest kernel and report it. That''s what I''m doing -- Konstantin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2011-Aug-17 06:53 UTC
Re: [Xen-devel] with kernel''s option ''nosmp'', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
On 17/08/2011 07:16, "Константин Алексеев" <kv.alekseev@gmail.com> wrote:> 2011/8/17 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>: >> Did you follow also the suggestions in the bugzilla from Ian (about dom0_..) >> ? >> Did that fix the issue? > > If you mean suggestions from Ian in debian bug report, then yes, > I use dom0_max_vcpus=1 and everything works well. > Ian asked to test this bug with the latest kernel and report it. > That''s what I''m doingIt''s really an unsupported configuration. If you want to limit dom0 vcpus then dom0_max_vcpus= on Xen command line is the correct way. Specifying nosmp causes the machine to boot up in a legacy configuration which we do not test, and is likely to cause mismatches in expectations between dom0 and Xen. There''s no good reason to specify it for general use. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel