thr3ads.net - Xen users - [Xen-users] XEN 4.0 boot error [Apr 2010]

If this information is useful, please help other people find it:
Share via:

Ian Tobin

2010-Apr-07 19:45 UTC

[Xen-users] XEN 4.0 boot error

Hey all,

 

Just downloaded the new Xen 4.0 and ran

 

Make xen

Make tools

Make stubdom

 

Copied the new files from dist/install

 

Im already running pv_ops 2.6.31.6 kernel.

 

When I boot i get

 

(XEN) Panic on CPU 0:

(XEN) IO-APIC +  timer doesn''t work!

 

I have tried booting with noapic boot option but makes no difference.
The system worked fine on 3.4.2

 

CPU is AMD.

 

Any ideas?

 

Thanks

 

Ian

 

 



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

Ian Tobin

2010-Apr-07 19:51 UTC

head link

[Xen-users] XEN 4.0 boot error

Hey all,

 

Just downloaded the new Xen 4.0 and ran

 

Make xen

Make tools

Make stubdom

 

Copied the new files from dist/install

 

Im already running pv_ops 2.6.31.6 kernel.

 

When I boot i get

 

(XEN) Panic on CPU 0:

(XEN) IO-APIC +  timer doesn''t work!

 

I have tried booting with noapic boot option but makes no difference.
The system worked fine on 3.4.2

 

CPU is AMD.

 

Any ideas?

 

Thanks

 

Ian

 

 



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

Pasi Kärkkäinen

2010-Apr-08 14:34 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin
wrote:>    Hey all,
> 
>    Just downloaded the new Xen 4.0 and ran
> 
>    Make xen
>    Make tools
>    Make stubdom
> 
>    Copied the new files from dist/install
>    Im already running pv_ops 2.6.31.6 kernel.
> 
>    When I boot i get
> 
>    (XEN) Panic on CPU 0:
>    (XEN) IO-APIC +  timer doesn''t work!
> 
>    I have tried booting with noapic boot option but makes no difference. 
The
>    system worked fine on 3.4.2
> 
>    CPU is AMD.
> 
>    Any ideas?
> 
Well.. can you post a full serial console log of the boot process?

See here for help: http://wiki.xensource.com/xenwiki/XenParavirtOps

-- Pasi


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

Konto usnetu

2010-Apr-08 18:23 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

2010/4/8 Pasi Kärkkäinen <pasik@iki.fi>
> On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
> >    Hey all,
> >
> >    Just downloaded the new Xen 4.0 and ran
> >
> >    Make xen
> >    Make tools
> >    Make stubdom
> >
> >    Copied the new files from dist/install
> >    Im already running pv_ops 2.6.31.6 kernel.
> >
> >    When I boot i get
> >
> >    (XEN) Panic on CPU 0:
> >    (XEN) IO-APIC +  timer doesn''t work!
> >
> >    I have tried booting with noapic boot option but makes no
difference.
>  The
> >    system worked fine on 3.4.2
> >
> >    CPU is AMD.
> >
> >    Any ideas?
> >
>
> Well.. can you post a full serial console log of the boot process?
>
> See here for help: http://wiki.xensource.com/xenwiki/XenParavirtOps
>
>
I have the same problem to boot xen 4.0 on debian lenny 5.0,  under I paste
a some error:

41.017078]   Magic number: 6:876:244
[   41.061177] md: Waiting for all devices to be available before autodetect
[   41.142579] md: If you don''t use raid, use raid=noautodetect
[   41.211225] md: Autodetecting RAID arrays.
[   41.260417] md: Scanned 0 and added 0 devices.
[   41.313729] md: autorun ...
[   41.347281] md: ... autorun DONE.
[   41.387150] Root-NFS: No NFS server available, giving up.
[   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
[   41.524664] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
[   41.601913] Please append a correct "root=" boot option; here are
the
available partitions:
[   41.702180] 0b00         1048575 sr0 driver: sr
[   41.756691] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
[   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
[   41.921708] Call Trace:
[   41.951139]  [<c15e8386>] ? printk+0xf/0x11
[   42.001366]  [<c15e82ca>] panic+0x39/0xe6
[   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
[   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
[   42.173838]  [<c191eca2>] mount_root+0x66/0x84
[   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
[   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
[   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
[   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10


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

Pasi Kärkkäinen

2010-Apr-08 18:54 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu
wrote:>    2010/4/8 Pasi Kärkkäinen <[1]pasik@iki.fi>
> 
>      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
>      >    Hey all,
>      >
>      >    Just downloaded the new Xen 4.0 and ran
>      >
>      >    Make xen
>      >    Make tools
>      >    Make stubdom
>      >
>      >    Copied the new files from dist/install
>      >    Im already running pv_ops 2.6.31.6 kernel.
>      >
>      >    When I boot i get
>      >
>      >    (XEN) Panic on CPU 0:
>      >    (XEN) IO-APIC +  timer doesn''t work!
>      >
>      >    I have tried booting with noapic boot option but makes no
>      difference.  The
>      >    system worked fine on 3.4.2
>      >
>      >    CPU is AMD.
>      >
>      >    Any ideas?
>      >
> 
>      Well.. can you post a full serial console log of the boot process?
> 
>      See here for help: [2]http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
>    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under I
>    paste a some error:
> 
>    41.017078]   Magic number: 6:876:244
>    [   41.061177] md: Waiting for all devices to be available before
>    autodetect
>    [   41.142579] md: If you don''t use raid, use raid=noautodetect
>    [   41.211225] md: Autodetecting RAID arrays.
>    [   41.260417] md: Scanned 0 and added 0 devices.
>    [   41.313729] md: autorun ...
>    [   41.347281] md: ... autorun DONE.
>    [   41.387150] Root-NFS: No NFS server available, giving up.
>    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
>    [   41.524664] VFS: Cannot open root device "sda1" or
unknown-block(2,0)

So the disk was not detected, or did you pass wrong root= parameter? 

Please post the _full_ log.

-- Pasi
>    [   41.601913] Please append a correct "root=" boot option;
here are the
>    available partitions:
>    [   41.702180] 0b00         1048575 sr0 driver: sr
>    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount root fs
on
>    unknown-block(2,0)
>    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
>    [   41.921708] Call Trace:
>    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
>    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
>    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
>    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
>    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
>    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
>    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
>    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> 

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

For@ll

2010-Apr-08 19:46 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

2010/4/8 Pasi Kärkkäinen <pasik@iki.fi>
> On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
> >    2010/4/8 Pasi Kärkkäinen <[1]pasik@iki.fi>
> >
> >      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
> >      >    Hey all,
> >      >
> >      >    Just downloaded the new Xen 4.0 and ran
> >      >
> >      >    Make xen
> >      >    Make tools
> >      >    Make stubdom
> >      >
> >      >    Copied the new files from dist/install
> >      >    Im already running pv_ops 2.6.31.6 kernel.
> >      >
> >      >    When I boot i get
> >      >
> >      >    (XEN) Panic on CPU 0:
> >      >    (XEN) IO-APIC +  timer doesn''t work!
> >      >
> >      >    I have tried booting with noapic boot option but makes no
> >      difference.  The
> >      >    system worked fine on 3.4.2
> >      >
> >      >    CPU is AMD.
> >      >
> >      >    Any ideas?
> >      >
> >
> >      Well.. can you post a full serial console log of the boot
process?
> >
> >      See here for help: [2]
> http://wiki.xensource.com/xenwiki/XenParavirtOps
> >
> >    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under
I
> >    paste a some error:
> >
> >    41.017078]   Magic number: 6:876:244
> >    [   41.061177] md: Waiting for all devices to be available before
> >    autodetect
> >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
> >    [   41.211225] md: Autodetecting RAID arrays.
> >    [   41.260417] md: Scanned 0 and added 0 devices.
> >    [   41.313729] md: autorun ...
> >    [   41.347281] md: ... autorun DONE.
> >    [   41.387150] Root-NFS: No NFS server available, giving up.
> >    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
> >    [   41.524664] VFS: Cannot open root device "sda1" or
> unknown-block(2,0)
>
>
> So the disk was not detected, or did you pass wrong root= parameter?
>
> Please post the _full_ log.
>
> -- Pasi
>
> >    [   41.601913] Please append a correct "root=" boot
option; here are
> the
> >    available partitions:
> >    [   41.702180] 0b00         1048575 sr0 driver: sr
> >    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount
root
> fs on
> >    unknown-block(2,0)
> >    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
> >    [   41.921708] Call Trace:
> >    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
> >    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
> >    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
> >    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
> >    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
> >    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
> >    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
> >    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
> >    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> >
>
>Hi,

This is a longer version dmesg from console redirection ( ipmitool connect
to iRMC)


[   25.101873] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0 pin
16 triggering 1 polarity 1
[   25.210426] pci 0000:00:1c.7: PCI INT A -> GSI 16 (level, low) -> IRQ
16
[   25.290926] NET: Registered protocol family 2
[   25.343369] IP route cache hash table entries: 32768 (order: 5, 131072
bytes)
[   25.429385] TCP established hash table entries: 131072 (order: 8, 1048576
bytes)
[   25.518783] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   25.598413] TCP: Hash tables configured (established 131072 bind 65536)
[   25.677741] TCP reno registered
[   25.715586] NET: Registered protocol family 1
[   25.767966] kvm: no hardware support
[   25.810908] has_svm: not amd
[   25.845501] kvm: no hardware support
[   25.888606] Simple Boot Flag at 0x50 set to 0x1
[   25.946611] Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>,
Peter Oruba
[   26.040604] Scanning for low memory corruption every 60 seconds
[   26.112527] audit: initializing netlink socket (disabled)
[   26.179722] type=2000 audit(1270763053.504:1): initialized
[   11.184373] highmem bounce pool size: 64 pages
[   11.237701] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[   11.319190] VFS: Disk quotas dquot_6.5.2
[   11.366415] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   11.445284] DLM (built Apr  8 2010 14:55:36) installed
[   11.508815] OCFS2 1.5.0
[   11.538530] ocfs2: Registered cluster interface o2cb
[   11.598381] ocfs2: Registered cluster interface user
[   11.657945] OCFS2 Node Manager 1.5.0
[   11.701011] OCFS2 DLM 1.5.0
[   11.734622] OCFS2 DLMFS 1.5.0
[   11.770430] OCFS2 User DLM kernel interface loaded
[   11.828680] Slow work thread pool: Starting up
[   11.882081] Slow work thread pool: Ready
[   11.929163] GFS2 (built Apr  8 2010 14:56:07) installed
[   11.991853] msgmni has been set to 1248
[   12.039039] alg: No test for stdrng (krng)
[   12.088412] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 252)
[   12.177207] io scheduler noop registered
[   12.224285] io scheduler anticipatory registered
[   12.279686] io scheduler deadline registered
[   12.330936] io scheduler cfq registered (default)
[   12.390106] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   12.457519] ACPI: AC Adapter [PSD] (on-line)
[   12.509066] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[   12.597857] ACPI: Power Button [PWRF]
[   12.641975] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[   12.740153] ACPI: Power Button [PWRB]
[   12.784590] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   12.845935] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   12.907366] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   12.968754] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   13.034662] Event-channel device installed.
[   13.088923] blktap_device_init: blktap device major 253
[   13.151673] blktap_ring_init: blktap ring major: 251
[   13.212676] registering netback
[   13.260648] hpet_acpi_add: no address or irqs in _CRS
[   13.321642] Non-volatile memory driver v1.3
[   13.372539] Linux agpgart interface v0.103
[   13.422152] [drm] Initialized drm 1.1.0 20060810
[   13.477799] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
˙[   13.797361] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   13.872710] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   13.946381] brd: module loaded
[   13.985783] loop: module loaded
[   14.024058] input: Macintosh mouse button emulation as
/devices/virtual/input/input2
[   14.118477] xen_set_ioapic_routing: irq 22 gsi 22 vector 22 ioapic 0 pin
22 triggering 1 polarity 1
[   14.227076] ata_piix 0000:00:1f.2: PCI INT A -> GSI 22 (level, low) ->
IRQ 22
[   14.312643] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[   14.375473] scsi0 : ata_piix
[   14.410844] scsi1 : ata_piix
[   14.445932] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1870 irq
14
[   14.529487] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1878 irq
15
[   14.613055] xen_set_ioapic_routing: irq 23 gsi 23 vector 23 ioapic 0 pin
23 triggering 1 polarity 1
[   14.721616] ata_piix 0000:00:1f.5: PCI INT B -> GSI 23 (level, low) ->
IRQ 23
[   14.807293] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[   14.870023] scsi2 : ata_piix
[   14.905173] scsi3 : ata_piix
[   14.940127] ata3: SATA max UDMA/133 cmd 0x18c8 ctl 0x18bc bmdma 0x1890
irq 23
[   15.025708] ata4: SATA max UDMA/133 cmd 0x18c0 ctl 0x18b8 bmdma 0x1898
irq 23
[   15.112211] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[   15.189453] Copyright (c) 1999-2006 Intel Corporation.
[   30.313754] ata2.00: SATA link down (SStatus 0 SControl 300)
[   30.313848] ata2.01: SATA link down (SStatus 0 SControl 300)
[   30.326241] ata1.00: SATA link down (SStatus 0 SControl 300)
[   30.326268] ata1.01: SATA link down (SStatus 0 SControl 300)
[   30.500741] ata4: SATA link down (SStatus 0 SControl 300)
[   15.587630] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
[   16.373656] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   16.392986] ata3.00: ATAPI: HL-DT-ST DVDRAM GT20N, CW03, max UDMA/133
[   16.414991] ata3.00: configured for UDMA/133
[   30.751248] scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GT20N
CW03 PQ: 0 ANSI: 5
[   30.763236] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2
cdda tray
[   30.763240] Uniform CD-ROM driver Revision: 3.20
[   30.764188] sr 2:0:0:0: Attached scsi generic sg0 type 5
[   16.167491] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[   16.237533] xen_set_ioapic_routing: irq 17 gsi 17 vector 17 ioapic 0 pin
17 triggering 1 polarity 1
[   16.346385] e1000e 0000:00:19.0: PCI INT A -> GSI 17 (level, low) ->
IRQ
17
[   16.429871] e1000e 0000:00:19.0: pci_enable_pcie_error_reporting failed
0xfffffffb
[   16.631590] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1)
00:40:d0:c0:94:ab
[   16.720405] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[   16.798930] 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 313130-032
[   16.873209] xen_set_ioapic_routing: irq 18 gsi 18 vector 18 ioapic 0 pin
18 triggering 1 polarity 1
[   16.981766] e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level, low) ->
IRQ
18
[   17.151067] 0000:06:00.0: eth1: (PCI Express:2.5GB/s:Width x1)
00:40:d0:c0:94:aa
[   17.239785] 0000:06:00.0: eth1: Intel(R) PRO/1000 Network Connection
[   17.316095] 0000:06:00.0: eth1: MAC: 3, PHY: 8, PBA No: 313132-030
[   17.390967] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[   17.464089] e100: Copyright(c) 1999-2006 Intel Corporation
[   17.530921] sky2 driver version 1.23
[   17.575855] console [netcon0] enabled
[   17.619813] netconsole: network logging started
[   17.674531] Fusion MPT base driver 3.04.10
[   17.723728] Copyright (c) 1999-2008 LSI Corporation
[   17.782276] Fusion MPT FC Host driver 3.04.10
[   17.834877] Fusion MPT misc device (ioctl) driver 3.04.10
[   17.900030] mptctl: Registered with Fusion MPT base driver
[   17.965842] mptctl: /dev/mptctl @ (major,minor=10,220)
[   18.028613] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller
(EHCI) Driver
[   18.106968] xen_set_ioapic_routing: irq 21 gsi 21 vector 21 ioapic 0 pin
21 triggering 1 polarity 1
[   18.215560] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 21 (level, low) ->
IRQ 21
[   18.301142] ehci_hcd 0000:00:1a.0: EHCI Host Controller
[   18.364179] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus
number 1
[   18.456986] ehci_hcd 0000:00:1a.0: debug port 2
[   18.511435] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
[   18.589288] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[   18.658307] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   18.739739] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[   18.826521] usb usb1: Product: EHCI Host Controller
[   18.885035] usb usb1: Manufacturer: Linux 2.6.31.13 ehci_hcd
[   18.952915] usb usb1: SerialNumber: 0000:00:1a.0
[   19.008822] usb usb1: configuration #1 chosen from 1 choice
[   19.076102] hub 1-0:1.0: USB hub found
[   19.121247] hub 1-0:1.0: 2 ports detected
[   19.169523] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic 0 pin
20 triggering 1 polarity 1
[   19.278107] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) ->
IRQ 20
[   19.363693] ehci_hcd 0000:00:1d.0: EHCI Host Controller
[   19.426837] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus
number 2
[   19.519665] ehci_hcd 0000:00:1d.0: debug port 2
[   19.574137] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
[   20.413312] usb 1-1: new high speed USB device using ehci_hcd and address
2
[   19.760373] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[   19.829381] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   19.910786] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[   19.997491] usb usb2: Product: EHCI Host Controller
[   20.056022] usb usb2: Manufacturer: Linux 2.6.31.13 ehci_hcd
[   20.123938] usb usb2: SerialNumber: 0000:00:1d.0
[   20.179767] usb usb2: configuration #1 chosen from 1 choice
[   35.261351] usb 1-1: New USB device found, idVendor=8087, idProduct=0020
[   35.261353] usb 1-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[   35.261696] usb 1-1: configuration #1 chosen from 1 choice
[   35.262004] hub 1-1:1.0: USB hub found
[   35.262112] hub 1-1:1.0: 6 ports detected
[   20.571877] hub 2-0:1.0: USB hub found
[   20.616947] hub 2-0:1.0: 2 ports detected
[   20.665554] ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI)
Driver
[   20.740168] uhci_hcd: USB Universal Host Controller Interface driver
[   20.817277] usbcore: registered new interface driver usblp
[   20.883086] Initializing USB Mass Storage driver...
[   20.941974] usbcore: registered new interface driver usb-storage
[   21.014026] USB Mass Storage support registered.
[   36.112936] usb 2-1: new high speed USB device using ehci_hcd and address
2
[   21.153280] usbcore: registered new interface driver libusual
[   36.228304] usb 2-1: New USB device found, idVendor=8087, idProduct=0020
[   36.228307] usb 2-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[   36.228660] usb 2-1: configuration #1 chosen from 1 choice
[   36.228969] hub 2-1:1.0: USB hub found
[   36.229070] hub 2-1:1.0: 8 ports detected
[   36.495535] usb 2-1.4: new low speed USB device using ehci_hcd and
address 3
[   36.592902] usb 2-1.4: New USB device found, idVendor=04d9,
idProduct=1603
[   36.592905] usb 2-1.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[   36.592908] usb 2-1.4: Product: USB Keyboard
[   36.592910] usb 2-1.4: Manufacturer:
[   36.593255] usb 2-1.4: configuration #1 chosen from 1 choice
[   36.657328] usb 2-1.5: new full speed USB device using ehci_hcd and
address 4
[   36.735047] usb 2-1.5: New USB device found, idVendor=0000,
idProduct=0000
[   36.735049] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[   36.735052] usb 2-1.5: Product: iRMC USB Device
[   36.735054] usb 2-1.5: Manufacturer: Fujitsu
[   36.735056] usb 2-1.5: SerialNumber: 600ABC94D3074C
[   36.735417] usb 2-1.5: configuration #1 chosen from 1 choice
[   22.454959] PNP: No PS/2 controller found. Probing ports directly.
[   23.293431] hrtimer: interrupt took 9183132 ns
[   22.842002] serio: i8042 KBD port at 0x60,0x64 irq 1
[   22.902741] mice: PS/2 mouse device common for all mice
[   22.977135] rtc_cmos 00:06: RTC can wake from S4
[   23.032918] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[   23.106105] rtc0: alarms up to one month, y3k, 114 bytes nvram
[   23.176478] xen_allocate_pirq: returning irq 20 for gsi 20
[   23.242289] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic 0 pin
20 triggering 1 polarity 1
[   23.350973] i801_smbus 0000:00:1f.3: PCI INT D -> GSI 20 (level, low)
->
IRQ 20
[   23.440784] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-devel@redhat.com
[   23.542605] cpuidle: using governor ladder
[   23.591833] cpuidle: using governor menu
[   23.642069] usbcore: registered new interface driver hiddev
[   38.781806] input:   USB Keyboard as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
[   38.899189] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID v1.10
Keyboard [  USB Keyboard] on usb-0000:00:1d.0-1.4/input0
[   39.057332] input:   USB Keyboard as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input4
[   39.174832] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID v1.10
Device [  USB Keyboard] on usb-0000:00:1d.0-1.4/input1
[   39.315677] input: Fujitsu iRMC USB Device as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input5
[   39.442738] generic-usb 0003:0000:0000.0003: input,hidraw2: USB HID v1.11
Keyboard [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input0
[   39.594713] input: Fujitsu iRMC USB Device as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input6
[   39.722047] generic-usb 0003:0000:0000.0004: input,hidraw3: USB HID v1.11
Mouse [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input1
[   39.869436] usbcore: registered new interface driver usbhid
[   39.936280] usbhid: v2.6:USB HID core driver
[   39.988359] Advanced Linux Sound Architecture Driver Version 1.0.20.
[   40.066220] ALSA device list:
[   40.101937]   No soundcards found.
[   40.142841] Netfilter messages via NETLINK v0.30.
[   40.199352] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   40.273258] ctnetlink v0.93: registering with nfnetlink.
[   40.338192] ip_tables: (C) 2000-2006 Netfilter Core Team
[   40.402000] TCP cubic registered
[   40.440827] Initializing XFRM netlink socket
[   40.493211] NET: Registered protocol family 10
[   40.549310] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   40.614164] IPv6 over IPv4 tunneling driver
[   40.666254] NET: Registered protocol family 17
[   40.720665] RPC: Registered udp transport module.
[   40.777108] RPC: Registered tcp transport module.
[   40.834214] SCTP: Hash tables configured (established 65536 bind 65536)
[   40.914548] Using IPI No-Shortcut mode
[   40.960325] registered taskstats version 1
[   41.009654]   Magic number: 6:500:752
[   41.053698] tty ttyS3: hash matches
[   41.095785] md: Waiting for all devices to be available before autodetect
[   41.177190] md: If you don''t use raid, use raid=noautodetect
[   41.245761] md: Autodetecting RAID arrays.
[   41.294919] md: Scanned 0 and added 0 devices.
[   41.348234] md: autorun ...
[   41.381789] md: ... autorun DONE.
[   41.421739] Root-NFS: No NFS server available, giving up.
[   41.486540] VFS: Unable to mount root fs via NFS, trying floppy.
[   41.559115] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
[   41.636362] Please append a correct "root=" boot option; here are
the
available partitions:
[   41.736610] 0b00         1048575 sr0 driver: sr
[   41.791146] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
[   41.890337] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
[   41.956135] Call Trace:
[   41.985599]  [<c15e8386>] ? printk+0xf/0x11
[   42.035826]  [<c15e82ca>] panic+0x39/0xe6
[   42.083950]  [<c191ec2d>] mount_block_root+0x163/0x172
[   42.145673]  [<c1002930>] ? hypercall_page+0x930/0x1005
[   42.208414]  [<c191eca2>] mount_root+0x66/0x84
[   42.261803]  [<c191ee05>] prepare_namespace+0x145/0x16c
[   42.324489]  [<c191e34f>] kernel_init+0x16e/0x17d
[   42.380929]  [<c191e1e1>] ? kernel_init+0x0/0x17d
[   42.437369]  [<c1028d37>] kernel_thread_helper+0x7/0x10


For@ll


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

Boris Derzhavets

2010-Apr-08 20:12 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

PV DomU seems to be loaded
Profile seems to reference root=/dev/sda1.
Try root=/dev/xvda1

Boris.



--- On Thu, 4/8/10, For@ll <forall@stalowka.info> wrote:

From: For@ll <forall@stalowka.info>
Subject: Re: [Xen-users] XEN 4.0 boot error
To: xen-users@lists.xensource.com
Date: Thursday, April 8, 2010, 3:46 PM



2010/4/8 Pasi Kärkkäinen <pasik@iki.fi>

On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
>    2010/4/8 Pasi Kärkkäinen <[1]pasik@iki.fi>
>
>      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
>      >    Hey all,
>      >
>      >    Just downloaded the new Xen 4.0 and ran
>      >
>      >    Make xen
>      >    Make tools
>      >    Make stubdom
>      >
>      >    Copied the new files from dist/install
>      >    Im already running pv_ops 2.6.31.6 kernel.
>      >
>      >    When I boot i get
>      >
>      >    (XEN) Panic on CPU 0:
>      >    (XEN) IO-APIC +  timer doesn''t work!
>      >
>      >    I have tried booting with noapic boot option but makes no
>      difference.  The
>      >    system worked fine on 3.4.2
>      >
>      >    CPU is AMD.
>      >
>      >    Any ideas?
>      >
>
>      Well.. can you post a full serial console log of the boot process?
>
>      See here for help: [2]http://wiki.xensource.com/xenwiki/XenParavirtOps
>
>    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under I
>    paste a some error:
>
>    41.017078]   Magic number: 6:876:244
>    [   41.061177] md: Waiting for all devices to be available before
>    autodetect
>    [   41.142579] md: If you don''t use raid, use raid=noautodetect
>    [   41.211225] md: Autodetecting RAID arrays.
>    [   41.260417] md: Scanned 0 and added 0 devices.
>    [   41.313729] md: autorun ...
>    [   41.347281] md: ... autorun DONE.
>    [   41.387150] Root-NFS: No NFS server available, giving up.
>    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
>    [   41.524664] VFS: Cannot open root device "sda1" or
unknown-block(2,0)


So the disk was not detected, or did you pass wrong root= parameter?


Please post the _full_ log.


-- Pasi

>    [   41.601913] Please append a correct "root=" boot option;
here are the
>    available partitions:
>    [   41.702180] 0b00         1048575 sr0 driver: sr
>    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount root fs
on
>    unknown-block(2,0)
>    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
>    [   41.921708] Call Trace:
>    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
>    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
>    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
>    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
>    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
>    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
>    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
>    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
>

Hi,

This is a longer version dmesg from console redirection ( ipmitool connect to
iRMC)


[   25.101873] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0 pin 16
triggering 1 polarity 1

[   25.210426] pci 0000:00:1c.7: PCI INT A -> GSI 16 (level, low) -> IRQ
16
[   25.290926] NET: Registered protocol family 2
[   25.343369] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)

[   25.429385] TCP established hash table entries: 131072 (order: 8, 1048576
bytes)
[   25.518783] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   25.598413] TCP: Hash tables configured (established 131072 bind 65536)

[   25.677741] TCP reno registered
[   25.715586] NET: Registered protocol family 1
[   25.767966] kvm: no hardware support
[   25.810908] has_svm: not amd
[   25.845501] kvm: no hardware support
[   25.888606] Simple Boot Flag at 0x50 set to 0x1

[   25.946611] Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
[   26.040604] Scanning for low memory corruption every 60 seconds
[   26.112527] audit: initializing netlink socket (disabled)

[   26.179722] type=2000 audit(1270763053.504:1): initialized
[   11.184373] highmem bounce pool size: 64 pages
[   11.237701] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[   11.319190] VFS: Disk quotas dquot_6.5.2

[   11.366415] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   11.445284] DLM (built Apr  8 2010 14:55:36) installed
[   11.508815] OCFS2 1.5.0
[   11.538530] ocfs2: Registered cluster interface o2cb

[   11.598381] ocfs2: Registered cluster interface user
[   11.657945] OCFS2 Node Manager 1.5.0
[   11.701011] OCFS2 DLM 1.5.0
[   11.734622] OCFS2 DLMFS 1.5.0
[   11.770430] OCFS2 User DLM kernel interface loaded

[   11.828680] Slow work thread pool: Starting up
[   11.882081] Slow work thread pool: Ready
[   11.929163] GFS2 (built Apr  8 2010 14:56:07) installed
[   11.991853] msgmni has been set to 1248
[   12.039039] alg: No test for stdrng (krng)

[   12.088412] Block layer SCSI generic (bsg) driver version 0.4 loaded (major
252)
[   12.177207] io scheduler noop registered
[   12.224285] io scheduler anticipatory registered
[   12.279686] io scheduler deadline registered

[   12.330936] io scheduler cfq registered (default)
[   12.390106] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   12.457519] ACPI: AC Adapter [PSD] (on-line)
[   12.509066] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0

[   12.597857] ACPI: Power Button [PWRF]
[   12.641975] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[   12.740153] ACPI: Power Button [PWRB]
[   12.784590] ACPI: CPU-1 (power states: C1[C1] C2[C3])

[   12.845935] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   12.907366] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   12.968754] ACPI: CPU-1 (power states: C1[C1] C2[C3])
[   13.034662] Event-channel device installed.

[   13.088923] blktap_device_init: blktap device major 253
[   13.151673] blktap_ring_init: blktap ring major: 251
[   13.212676] registering netback
[   13.260648] hpet_acpi_add: no address or irqs in _CRS
[   13.321642] Non-volatile memory driver v1.3

[   13.372539] Linux agpgart interface v0.103
[   13.422152] [drm] Initialized drm 1.1.0 20060810
[   13.477799] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
˙[   13.797361] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

[   13.872710] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   13.946381] brd: module loaded
[   13.985783] loop: module loaded
[   14.024058] input: Macintosh mouse button emulation as
/devices/virtual/input/input2

[   14.118477] xen_set_ioapic_routing: irq 22 gsi 22 vector 22 ioapic 0 pin 22
triggering 1 polarity 1
[   14.227076] ata_piix 0000:00:1f.2: PCI INT A -> GSI 22 (level, low) ->
IRQ 22
[   14.312643] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]

[   14.375473] scsi0 : ata_piix
[   14.410844] scsi1 : ata_piix
[   14.445932] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1870 irq 14
[   14.529487] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1878 irq 15

[   14.613055] xen_set_ioapic_routing: irq 23 gsi 23 vector 23 ioapic 0 pin 23
triggering 1 polarity 1
[   14.721616] ata_piix 0000:00:1f.5: PCI INT B -> GSI 23 (level, low) ->
IRQ 23
[   14.807293] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]

[   14.870023] scsi2 : ata_piix
[   14.905173] scsi3 : ata_piix
[   14.940127] ata3: SATA max UDMA/133 cmd 0x18c8 ctl 0x18bc bmdma 0x1890 irq 23
[   15.025708] ata4: SATA max UDMA/133 cmd 0x18c0 ctl 0x18b8 bmdma 0x1898 irq 23

[   15.112211] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
[   15.189453] Copyright (c) 1999-2006 Intel Corporation.
[   30.313754] ata2.00: SATA link down (SStatus 0 SControl 300)
[   30.313848] ata2.01: SATA link down (SStatus 0 SControl 300)

[   30.326241] ata1.00: SATA link down (SStatus 0 SControl 300)
[   30.326268] ata1.01: SATA link down (SStatus 0 SControl 300)
[   30.500741] ata4: SATA link down (SStatus 0 SControl 300)
[   15.587630] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2

[   16.373656] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   16.392986] ata3.00: ATAPI: HL-DT-ST DVDRAM GT20N, CW03, max UDMA/133
[   16.414991] ata3.00: configured for UDMA/133
[   30.751248] scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GT20N     CW03
PQ: 0 ANSI: 5

[   30.763236] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda
tray
[   30.763240] Uniform CD-ROM driver Revision: 3.20
[   30.764188] sr 2:0:0:0: Attached scsi generic sg0 type 5
[   16.167491] e1000e: Copyright (c) 1999-2008 Intel Corporation.

[   16.237533] xen_set_ioapic_routing: irq 17 gsi 17 vector 17 ioapic 0 pin 17
triggering 1 polarity 1
[   16.346385] e1000e 0000:00:19.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
[   16.429871] e1000e 0000:00:19.0: pci_enable_pcie_error_reporting failed
0xfffffffb

[   16.631590] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1)
00:40:d0:c0:94:ab
[   16.720405] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[   16.798930] 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 313130-032

[   16.873209] xen_set_ioapic_routing: irq 18 gsi 18 vector 18 ioapic 0 pin 18
triggering 1 polarity 1
[   16.981766] e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level, low) ->
IRQ 18
[   17.151067] 0000:06:00.0: eth1: (PCI Express:2.5GB/s:Width x1)
00:40:d0:c0:94:aa

[   17.239785] 0000:06:00.0: eth1: Intel(R) PRO/1000 Network Connection
[   17.316095] 0000:06:00.0: eth1: MAC: 3, PHY: 8, PBA No: 313132-030
[   17.390967] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[   17.464089] e100: Copyright(c) 1999-2006 Intel Corporation

[   17.530921] sky2 driver version 1.23
[   17.575855] console [netcon0] enabled
[   17.619813] netconsole: network logging started
[   17.674531] Fusion MPT base driver 3.04.10
[   17.723728] Copyright (c) 1999-2008 LSI Corporation

[   17.782276] Fusion MPT FC Host driver 3.04.10
[   17.834877] Fusion MPT misc device (ioctl) driver 3.04.10
[   17.900030] mptctl: Registered with Fusion MPT base driver
[   17.965842] mptctl: /dev/mptctl @ (major,minor=10,220)

[   18.028613] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller
(EHCI) Driver
[   18.106968] xen_set_ioapic_routing: irq 21 gsi 21 vector 21 ioapic 0 pin 21
triggering 1 polarity 1
[   18.215560] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 21 (level, low) ->
IRQ 21

[   18.301142] ehci_hcd 0000:00:1a.0: EHCI Host Controller
[   18.364179] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus
number 1
[   18.456986] ehci_hcd 0000:00:1a.0: debug port 2
[   18.511435] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000

[   18.589288] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[   18.658307] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   18.739739] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1

[   18.826521] usb usb1: Product: EHCI Host Controller
[   18.885035] usb usb1: Manufacturer: Linux 2.6.31.13 ehci_hcd
[   18.952915] usb usb1: SerialNumber: 0000:00:1a.0
[   19.008822] usb usb1: configuration #1 chosen from 1 choice

[   19.076102] hub 1-0:1.0: USB hub found
[   19.121247] hub 1-0:1.0: 2 ports detected
[   19.169523] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic 0 pin 20
triggering 1 polarity 1
[   19.278107] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level, low) ->
IRQ 20

[   19.363693] ehci_hcd 0000:00:1d.0: EHCI Host Controller
[   19.426837] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus
number 2
[   19.519665] ehci_hcd 0000:00:1d.0: debug port 2
[   19.574137] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000

[   20.413312] usb 1-1: new high speed USB device using ehci_hcd and address 2
[   19.760373] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[   19.829381] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

[   19.910786] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[   19.997491] usb usb2: Product: EHCI Host Controller
[   20.056022] usb usb2: Manufacturer: Linux 2.6.31.13 ehci_hcd
[   20.123938] usb usb2: SerialNumber: 0000:00:1d.0

[   20.179767] usb usb2: configuration #1 chosen from 1 choice
[   35.261351] usb 1-1: New USB device found, idVendor=8087, idProduct=0020
[   35.261353] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[   35.261696] usb 1-1: configuration #1 chosen from 1 choice
[   35.262004] hub 1-1:1.0: USB hub found
[   35.262112] hub 1-1:1.0: 6 ports detected
[   20.571877] hub 2-0:1.0: USB hub found
[   20.616947] hub 2-0:1.0: 2 ports detected

[   20.665554] ohci_hcd: USB 1.1 ''Open'' Host Controller (OHCI)
Driver
[   20.740168] uhci_hcd: USB Universal Host Controller Interface driver
[   20.817277] usbcore: registered new interface driver usblp

[   20.883086] Initializing USB Mass Storage driver...
[   20.941974] usbcore: registered new interface driver usb-storage
[   21.014026] USB Mass Storage support registered.
[   36.112936] usb 2-1: new high speed USB device using ehci_hcd and address 2

[   21.153280] usbcore: registered new interface driver libusual
[   36.228304] usb 2-1: New USB device found, idVendor=8087, idProduct=0020
[   36.228307] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[   36.228660] usb 2-1: configuration #1 chosen from 1 choice
[   36.228969] hub 2-1:1.0: USB hub found
[   36.229070] hub 2-1:1.0: 8 ports detected
[   36.495535] usb 2-1.4: new low speed USB device using ehci_hcd and address 3

[   36.592902] usb 2-1.4: New USB device found, idVendor=04d9, idProduct=1603
[   36.592905] usb 2-1.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[   36.592908] usb 2-1.4: Product: USB Keyboard
[   36.592910] usb 2-1.4: Manufacturer:

[   36.593255] usb 2-1.4: configuration #1 chosen from 1 choice
[   36.657328] usb 2-1.5: new full speed USB device using ehci_hcd and address 4
[   36.735047] usb 2-1.5: New USB device found, idVendor=0000, idProduct=0000

[   36.735049] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[   36.735052] usb 2-1.5: Product: iRMC USB Device
[   36.735054] usb 2-1.5: Manufacturer: Fujitsu
[   36.735056] usb 2-1.5: SerialNumber: 600ABC94D3074C

[   36.735417] usb 2-1.5: configuration #1 chosen from 1 choice
[   22.454959] PNP: No PS/2 controller found. Probing ports directly.
[   23.293431] hrtimer: interrupt took 9183132 ns
[   22.842002] serio: i8042 KBD port at 0x60,0x64 irq 1

[   22.902741] mice: PS/2 mouse device common for all mice
[   22.977135] rtc_cmos 00:06: RTC can wake from S4
[   23.032918] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[   23.106105] rtc0: alarms up to one month, y3k, 114 bytes nvram

[   23.176478] xen_allocate_pirq: returning irq 20 for gsi 20
[   23.242289] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic 0 pin 20
triggering 1 polarity 1
[   23.350973] i801_smbus 0000:00:1f.3: PCI INT D -> GSI 20 (level, low)
-> IRQ 20

[   23.440784] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-devel@redhat.com
[   23.542605] cpuidle: using governor ladder
[   23.591833] cpuidle: using governor menu

[   23.642069] usbcore: registered new interface driver hiddev
[   38.781806] input:   USB Keyboard as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
[   38.899189] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID v1.10
Keyboard [  USB Keyboard] on usb-0000:00:1d.0-1.4/input0

[   39.057332] input:   USB Keyboard as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input4
[   39.174832] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID v1.10
Device [  USB Keyboard] on usb-0000:00:1d.0-1.4/input1

[   39.315677] input: Fujitsu iRMC USB Device as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input5
[   39.442738] generic-usb 0003:0000:0000.0003: input,hidraw2: USB HID v1.11
Keyboard [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input0

[   39.594713] input: Fujitsu iRMC USB Device as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input6
[   39.722047] generic-usb 0003:0000:0000.0004: input,hidraw3: USB HID v1.11
Mouse [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input1

[   39.869436] usbcore: registered new interface driver usbhid
[   39.936280] usbhid: v2.6:USB HID core driver
[   39.988359] Advanced Linux Sound Architecture Driver Version 1.0.20.
[   40.066220] ALSA device list:

[   40.101937]   No soundcards found.
[   40.142841] Netfilter messages via NETLINK v0.30.
[   40.199352] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   40.273258] ctnetlink v0.93: registering with nfnetlink.

[   40.338192] ip_tables: (C) 2000-2006 Netfilter Core Team
[   40.402000] TCP cubic registered
[   40.440827] Initializing XFRM netlink socket
[   40.493211] NET: Registered protocol family 10
[   40.549310] ip6_tables: (C) 2000-2006 Netfilter Core Team

[   40.614164] IPv6 over IPv4 tunneling driver
[   40.666254] NET: Registered protocol family 17
[   40.720665] RPC: Registered udp transport module.
[   40.777108] RPC: Registered tcp transport module.
[   40.834214] SCTP: Hash tables configured (established 65536 bind 65536)

[   40.914548] Using IPI No-Shortcut mode
[   40.960325] registered taskstats version 1
[   41.009654]   Magic number: 6:500:752
[   41.053698] tty ttyS3: hash matches
[   41.095785] md: Waiting for all devices to be available before autodetect

[   41.177190] md: If you don''t use raid, use raid=noautodetect
[   41.245761] md: Autodetecting RAID arrays.
[   41.294919] md: Scanned 0 and added 0 devices.
[   41.348234] md: autorun ...
[   41.381789] md: ... autorun DONE.

[   41.421739] Root-NFS: No NFS server available, giving up.
[   41.486540] VFS: Unable to mount root fs via NFS, trying floppy.
[   41.559115] VFS: Cannot open root device "sda1" or
unknown-block(2,0)

[   41.636362] Please append a correct "root=" boot option; here are
the available partitions:
[   41.736610] 0b00         1048575 sr0 driver: sr
[   41.791146] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)

[   41.890337] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
[   41.956135] Call Trace:
[   41.985599]  [<c15e8386>] ? printk+0xf/0x11
[   42.035826]  [<c15e82ca>] panic+0x39/0xe6
[   42.083950]  [<c191ec2d>] mount_block_root+0x163/0x172

[   42.145673]  [<c1002930>] ? hypercall_page+0x930/0x1005
[   42.208414]  [<c191eca2>] mount_root+0x66/0x84
[   42.261803]  [<c191ee05>] prepare_namespace+0x145/0x16c
[   42.324489]  [<c191e34f>] kernel_init+0x16e/0x17d

[   42.380929]  [<c191e1e1>] ? kernel_init+0x0/0x17d
[   42.437369]  [<c1028d37>] kernel_thread_helper+0x7/0x10


For@ll





-----Inline Attachment Follows-----

_______________________________________________
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

Pasi Kärkkäinen

2010-Apr-08 20:43 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

On Thu, Apr 08, 2010 at 09:46:49PM +0200, For@ll wrote:>      >      See here for help:
>      [2][3]http://wiki.xensource.com/xenwiki/XenParavirtOps
>      >
>      >    I have the same problem to boot xen 4.0 on debian lenny 5.0, 
under
>      I
>      >    paste a some error:
>      >
>      >    41.017078]   Magic number: 6:876:244
>      >    [   41.061177] md: Waiting for all devices to be available
before
>      >    autodetect
>      >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
>      >    [   41.211225] md: Autodetecting RAID arrays.
>      >    [   41.260417] md: Scanned 0 and added 0 devices.
>      >    [   41.313729] md: autorun ...
>      >    [   41.347281] md: ... autorun DONE.
>      >    [   41.387150] Root-NFS: No NFS server available, giving up.
>      >    [   41.451921] VFS: Unable to mount root fs via NFS, trying
floppy.
>      >    [   41.524664] VFS: Cannot open root device "sda1"
or
>      unknown-block(2,0)
> 
>      So the disk was not detected, or did you pass wrong root= parameter?
> 
>      Please post the _full_ log.
> 
>      -- Pasi
> 
> 
>    Hi,
> 
>    This is a longer version dmesg from console redirection ( ipmitool
connect
>    to iRMC)
> 
I don''t see any disks detected in the log..

Can you please post a boot log on baremetal (non-xen), 
or tell which disk controller has your root disk? what driver it uses on
baremetal linux?

-- Pasi

>    [   25.101873] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0
>    pin 16 triggering 1 polarity 1
>    [   25.210426] pci 0000:00:1c.7: PCI INT A -> GSI 16 (level, low)
-> IRQ
>    16
>    [   25.290926] NET: Registered protocol family 2
>    [   25.343369] IP route cache hash table entries: 32768 (order: 5,
131072
>    bytes)
>    [   25.429385] TCP established hash table entries: 131072 (order: 8,
>    1048576 bytes)
>    [   25.518783] TCP bind hash table entries: 65536 (order: 7, 524288
bytes)
>    [   25.598413] TCP: Hash tables configured (established 131072 bind
65536)
>    [   25.677741] TCP reno registered
>    [   25.715586] NET: Registered protocol family 1
>    [   25.767966] kvm: no hardware support
>    [   25.810908] has_svm: not amd
>    [   25.845501] kvm: no hardware support
>    [   25.888606] Simple Boot Flag at 0x50 set to 0x1
>    [   25.946611] Microcode Update Driver: v2.00
>    <[4]tigran@aivazian.fsnet.co.uk>, Peter Oruba
>    [   26.040604] Scanning for low memory corruption every 60 seconds
>    [   26.112527] audit: initializing netlink socket (disabled)
>    [   26.179722] type=2000 audit(1270763053.504:1): initialized
>    [   11.184373] highmem bounce pool size: 64 pages
>    [   11.237701] HugeTLB registered 2 MB page size, pre-allocated 0 pages
>    [   11.319190] VFS: Disk quotas dquot_6.5.2
>    [   11.366415] Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
>    [   11.445284] DLM (built Apr  8 2010 14:55:36) installed
>    [   11.508815] OCFS2 1.5.0
>    [   11.538530] ocfs2: Registered cluster interface o2cb
>    [   11.598381] ocfs2: Registered cluster interface user
>    [   11.657945] OCFS2 Node Manager 1.5.0
>    [   11.701011] OCFS2 DLM 1.5.0
>    [   11.734622] OCFS2 DLMFS 1.5.0
>    [   11.770430] OCFS2 User DLM kernel interface loaded
>    [   11.828680] Slow work thread pool: Starting up
>    [   11.882081] Slow work thread pool: Ready
>    [   11.929163] GFS2 (built Apr  8 2010 14:56:07) installed
>    [   11.991853] msgmni has been set to 1248
>    [   12.039039] alg: No test for stdrng (krng)
>    [   12.088412] Block layer SCSI generic (bsg) driver version 0.4 loaded
>    (major 252)
>    [   12.177207] io scheduler noop registered
>    [   12.224285] io scheduler anticipatory registered
>    [   12.279686] io scheduler deadline registered
>    [   12.330936] io scheduler cfq registered (default)
>    [   12.390106] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>    [   12.457519] ACPI: AC Adapter [PSD] (on-line)
>    [   12.509066] input: Power Button as
>    /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
>    [   12.597857] ACPI: Power Button [PWRF]
>    [   12.641975] input: Power Button as
>    /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
>    [   12.740153] ACPI: Power Button [PWRB]
>    [   12.784590] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>    [   12.845935] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>    [   12.907366] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>    [   12.968754] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>    [   13.034662] Event-channel device installed.
>    [   13.088923] blktap_device_init: blktap device major 253
>    [   13.151673] blktap_ring_init: blktap ring major: 251
>    [   13.212676] registering netback
>    [   13.260648] hpet_acpi_add: no address or irqs in _CRS
>    [   13.321642] Non-volatile memory driver v1.3
>    [   13.372539] Linux agpgart interface v0.103
>    [   13.422152] [drm] Initialized drm 1.1.0 20060810
>    [   13.477799] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>    ÿ[   13.797361] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>    [   13.872710] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>    [   13.946381] brd: module loaded
>    [   13.985783] loop: module loaded
>    [   14.024058] input: Macintosh mouse button emulation as
>    /devices/virtual/input/input2
>    [   14.118477] xen_set_ioapic_routing: irq 22 gsi 22 vector 22 ioapic 0
>    pin 22 triggering 1 polarity 1
>    [   14.227076] ata_piix 0000:00:1f.2: PCI INT A -> GSI 22 (level,
low) ->
>    IRQ 22
>    [   14.312643] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
>    [   14.375473] scsi0 : ata_piix
>    [   14.410844] scsi1 : ata_piix
>    [   14.445932] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1870
>    irq 14
>    [   14.529487] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1878
>    irq 15
>    [   14.613055] xen_set_ioapic_routing: irq 23 gsi 23 vector 23 ioapic 0
>    pin 23 triggering 1 polarity 1
>    [   14.721616] ata_piix 0000:00:1f.5: PCI INT B -> GSI 23 (level,
low) ->
>    IRQ 23
>    [   14.807293] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
>    [   14.870023] scsi2 : ata_piix
>    [   14.905173] scsi3 : ata_piix
>    [   14.940127] ata3: SATA max UDMA/133 cmd 0x18c8 ctl 0x18bc bmdma
0x1890
>    irq 23
>    [   15.025708] ata4: SATA max UDMA/133 cmd 0x18c0 ctl 0x18b8 bmdma
0x1898
>    irq 23
>    [   15.112211] Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
>    [   15.189453] Copyright (c) 1999-2006 Intel Corporation.
>    [   30.313754] ata2.00: SATA link down (SStatus 0 SControl 300)
>    [   30.313848] ata2.01: SATA link down (SStatus 0 SControl 300)
>    [   30.326241] ata1.00: SATA link down (SStatus 0 SControl 300)
>    [   30.326268] ata1.01: SATA link down (SStatus 0 SControl 300)
>    [   30.500741] ata4: SATA link down (SStatus 0 SControl 300)
>    [   15.587630] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
>    [   16.373656] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>    [   16.392986] ata3.00: ATAPI: HL-DT-ST DVDRAM GT20N, CW03, max UDMA/133
>    [   16.414991] ata3.00: configured for UDMA/133
>    [   30.751248] scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GT20N
>    CW03 PQ: 0 ANSI: 5
>    [   30.763236] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
xa/form2
>    cdda tray
>    [   30.763240] Uniform CD-ROM driver Revision: 3.20
>    [   30.764188] sr 2:0:0:0: Attached scsi generic sg0 type 5
>    [   16.167491] e1000e: Copyright (c) 1999-2008 Intel Corporation.
>    [   16.237533] xen_set_ioapic_routing: irq 17 gsi 17 vector 17 ioapic 0
>    pin 17 triggering 1 polarity 1
>    [   16.346385] e1000e 0000:00:19.0: PCI INT A -> GSI 17 (level, low)
->
>    IRQ 17
>    [   16.429871] e1000e 0000:00:19.0: pci_enable_pcie_error_reporting
failed
>    0xfffffffb
>    [   16.631590] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1)
>    00:40:d0:c0:94:ab
>    [   16.720405] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
>    [   16.798930] 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 313130-032
>    [   16.873209] xen_set_ioapic_routing: irq 18 gsi 18 vector 18 ioapic 0
>    pin 18 triggering 1 polarity 1
>    [   16.981766] e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level, low)
->
>    IRQ 18
>    [   17.151067] 0000:06:00.0: eth1: (PCI Express:2.5GB/s:Width x1)
>    00:40:d0:c0:94:aa
>    [   17.239785] 0000:06:00.0: eth1: Intel(R) PRO/1000 Network Connection
>    [   17.316095] 0000:06:00.0: eth1: MAC: 3, PHY: 8, PBA No: 313132-030
>    [   17.390967] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
>    [   17.464089] e100: Copyright(c) 1999-2006 Intel Corporation
>    [   17.530921] sky2 driver version 1.23
>    [   17.575855] console [netcon0] enabled
>    [   17.619813] netconsole: network logging started
>    [   17.674531] Fusion MPT base driver 3.04.10
>    [   17.723728] Copyright (c) 1999-2008 LSI Corporation
>    [   17.782276] Fusion MPT FC Host driver 3.04.10
>    [   17.834877] Fusion MPT misc device (ioctl) driver 3.04.10
>    [   17.900030] mptctl: Registered with Fusion MPT base driver
>    [   17.965842] mptctl: /dev/mptctl @ (major,minor=10,220)
>    [   18.028613] ehci_hcd: USB 2.0 ''Enhanced'' Host
Controller (EHCI) Driver
>    [   18.106968] xen_set_ioapic_routing: irq 21 gsi 21 vector 21 ioapic 0
>    pin 21 triggering 1 polarity 1
>    [   18.215560] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 21 (level,
low) ->
>    IRQ 21
>    [   18.301142] ehci_hcd 0000:00:1a.0: EHCI Host Controller
>    [   18.364179] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned
bus
>    number 1
>    [   18.456986] ehci_hcd 0000:00:1a.0: debug port 2
>    [   18.511435] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
>    [   18.589288] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
>    [   18.658307] usb usb1: New USB device found, idVendor=1d6b,
>    idProduct=0002
>    [   18.739739] usb usb1: New USB device strings: Mfr=3, Product=2,
>    SerialNumber=1
>    [   18.826521] usb usb1: Product: EHCI Host Controller
>    [   18.885035] usb usb1: Manufacturer: Linux 2.6.31.13 ehci_hcd
>    [   18.952915] usb usb1: SerialNumber: 0000:00:1a.0
>    [   19.008822] usb usb1: configuration #1 chosen from 1 choice
>    [   19.076102] hub 1-0:1.0: USB hub found
>    [   19.121247] hub 1-0:1.0: 2 ports detected
>    [   19.169523] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic 0
>    pin 20 triggering 1 polarity 1
>    [   19.278107] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level,
low) ->
>    IRQ 20
>    [   19.363693] ehci_hcd 0000:00:1d.0: EHCI Host Controller
>    [   19.426837] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus
>    number 2
>    [   19.519665] ehci_hcd 0000:00:1d.0: debug port 2
>    [   19.574137] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
>    [   20.413312] usb 1-1: new high speed USB device using ehci_hcd and
>    address 2
>    [   19.760373] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
>    [   19.829381] usb usb2: New USB device found, idVendor=1d6b,
>    idProduct=0002
>    [   19.910786] usb usb2: New USB device strings: Mfr=3, Product=2,
>    SerialNumber=1
>    [   19.997491] usb usb2: Product: EHCI Host Controller
>    [   20.056022] usb usb2: Manufacturer: Linux 2.6.31.13 ehci_hcd
>    [   20.123938] usb usb2: SerialNumber: 0000:00:1d.0
>    [   20.179767] usb usb2: configuration #1 chosen from 1 choice
>    [   35.261351] usb 1-1: New USB device found, idVendor=8087,
>    idProduct=0020
>    [   35.261353] usb 1-1: New USB device strings: Mfr=0, Product=0,
>    SerialNumber=0
>    [   35.261696] usb 1-1: configuration #1 chosen from 1 choice
>    [   35.262004] hub 1-1:1.0: USB hub found
>    [   35.262112] hub 1-1:1.0: 6 ports detected
>    [   20.571877] hub 2-0:1.0: USB hub found
>    [   20.616947] hub 2-0:1.0: 2 ports detected
>    [   20.665554] ohci_hcd: USB 1.1 ''Open'' Host
Controller (OHCI) Driver
>    [   20.740168] uhci_hcd: USB Universal Host Controller Interface driver
>    [   20.817277] usbcore: registered new interface driver usblp
>    [   20.883086] Initializing USB Mass Storage driver...
>    [   20.941974] usbcore: registered new interface driver usb-storage
>    [   21.014026] USB Mass Storage support registered.
>    [   36.112936] usb 2-1: new high speed USB device using ehci_hcd and
>    address 2
>    [   21.153280] usbcore: registered new interface driver libusual
>    [   36.228304] usb 2-1: New USB device found, idVendor=8087,
>    idProduct=0020
>    [   36.228307] usb 2-1: New USB device strings: Mfr=0, Product=0,
>    SerialNumber=0
>    [   36.228660] usb 2-1: configuration #1 chosen from 1 choice
>    [   36.228969] hub 2-1:1.0: USB hub found
>    [   36.229070] hub 2-1:1.0: 8 ports detected
>    [   36.495535] usb 2-1.4: new low speed USB device using ehci_hcd and
>    address 3
>    [   36.592902] usb 2-1.4: New USB device found, idVendor=04d9,
>    idProduct=1603
>    [   36.592905] usb 2-1.4: New USB device strings: Mfr=1, Product=2,
>    SerialNumber=0
>    [   36.592908] usb 2-1.4: Product: USB Keyboard
>    [   36.592910] usb 2-1.4: Manufacturer:
>    [   36.593255] usb 2-1.4: configuration #1 chosen from 1 choice
>    [   36.657328] usb 2-1.5: new full speed USB device using ehci_hcd and
>    address 4
>    [   36.735047] usb 2-1.5: New USB device found, idVendor=0000,
>    idProduct=0000
>    [   36.735049] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
>    SerialNumber=3
>    [   36.735052] usb 2-1.5: Product: iRMC USB Device
>    [   36.735054] usb 2-1.5: Manufacturer: Fujitsu
>    [   36.735056] usb 2-1.5: SerialNumber: 600ABC94D3074C
>    [   36.735417] usb 2-1.5: configuration #1 chosen from 1 choice
>    [   22.454959] PNP: No PS/2 controller found. Probing ports directly.
>    [   23.293431] hrtimer: interrupt took 9183132 ns
>    [   22.842002] serio: i8042 KBD port at 0x60,0x64 irq 1
>    [   22.902741] mice: PS/2 mouse device common for all mice
>    [   22.977135] rtc_cmos 00:06: RTC can wake from S4
>    [   23.032918] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
>    [   23.106105] rtc0: alarms up to one month, y3k, 114 bytes nvram
>    [   23.176478] xen_allocate_pirq: returning irq 20 for gsi 20
>    [   23.242289] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic 0
>    pin 20 triggering 1 polarity 1
>    [   23.350973] i801_smbus 0000:00:1f.3: PCI INT D -> GSI 20 (level,
low)
>    -> IRQ 20
>    [   23.440784] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)
>    initialised: [5]dm-devel@redhat.com
>    [   23.542605] cpuidle: using governor ladder
>    [   23.591833] cpuidle: using governor menu
>    [   23.642069] usbcore: registered new interface driver hiddev
>    [   38.781806] input:   USB Keyboard as
>    /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
>    [   38.899189] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID
>    v1.10 Keyboard [  USB Keyboard] on usb-0000:00:1d.0-1.4/input0
>    [   39.057332] input:   USB Keyboard as
>    /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input4
>    [   39.174832] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID
>    v1.10 Device [  USB Keyboard] on usb-0000:00:1d.0-1.4/input1
>    [   39.315677] input: Fujitsu iRMC USB Device as
>    /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input5
>    [   39.442738] generic-usb 0003:0000:0000.0003: input,hidraw2: USB HID
>    v1.11 Keyboard [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input0
>    [   39.594713] input: Fujitsu iRMC USB Device as
>    /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input6
>    [   39.722047] generic-usb 0003:0000:0000.0004: input,hidraw3: USB HID
>    v1.11 Mouse [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input1
>    [   39.869436] usbcore: registered new interface driver usbhid
>    [   39.936280] usbhid: v2.6:USB HID core driver
>    [   39.988359] Advanced Linux Sound Architecture Driver Version 1.0.20.
>    [   40.066220] ALSA device list:
>    [   40.101937]   No soundcards found.
>    [   40.142841] Netfilter messages via NETLINK v0.30.
>    [   40.199352] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
>    [   40.273258] ctnetlink v0.93: registering with nfnetlink.
>    [   40.338192] ip_tables: (C) 2000-2006 Netfilter Core Team
>    [   40.402000] TCP cubic registered
>    [   40.440827] Initializing XFRM netlink socket
>    [   40.493211] NET: Registered protocol family 10
>    [   40.549310] ip6_tables: (C) 2000-2006 Netfilter Core Team
>    [   40.614164] IPv6 over IPv4 tunneling driver
>    [   40.666254] NET: Registered protocol family 17
>    [   40.720665] RPC: Registered udp transport module.
>    [   40.777108] RPC: Registered tcp transport module.
>    [   40.834214] SCTP: Hash tables configured (established 65536 bind
65536)
>    [   40.914548] Using IPI No-Shortcut mode
>    [   40.960325] registered taskstats version 1
>    [   41.009654]   Magic number: 6:500:752
>    [   41.053698] tty ttyS3: hash matches
>    [   41.095785] md: Waiting for all devices to be available before
>    autodetect
>    [   41.177190] md: If you don''t use raid, use raid=noautodetect
>    [   41.245761] md: Autodetecting RAID arrays.
>    [   41.294919] md: Scanned 0 and added 0 devices.
>    [   41.348234] md: autorun ...
>    [   41.381789] md: ... autorun DONE.
>    [   41.421739] Root-NFS: No NFS server available, giving up.
>    [   41.486540] VFS: Unable to mount root fs via NFS, trying floppy.
>    [   41.559115] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
>    [   41.636362] Please append a correct "root=" boot option;
here are the
>    available partitions:
>    [   41.736610] 0b00         1048575 sr0 driver: sr
>    [   41.791146] Kernel panic - not syncing: VFS: Unable to mount root fs
on
>    unknown-block(2,0)
>    [   41.890337] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
>    [   41.956135] Call Trace:
>    [   41.985599]  [<c15e8386>] ? printk+0xf/0x11
>    [   42.035826]  [<c15e82ca>] panic+0x39/0xe6
>    [   42.083950]  [<c191ec2d>] mount_block_root+0x163/0x172
>    [   42.145673]  [<c1002930>] ? hypercall_page+0x930/0x1005
>    [   42.208414]  [<c191eca2>] mount_root+0x66/0x84
>    [   42.261803]  [<c191ee05>] prepare_namespace+0x145/0x16c
>    [   42.324489]  [<c191e34f>] kernel_init+0x16e/0x17d
>    [   42.380929]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>    [   42.437369]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> 
>    For@ll
> 
> References
> 
>    Visible links
>    1. mailto:pasik@iki.fi
>    2. mailto:pasik@iki.fi
>    3. http://wiki.xensource.com/xenwiki/XenParavirtOps
>    4. mailto:tigran@aivazian.fsnet.co.uk
>    5. mailto:dm-devel@redhat.com
> _______________________________________________
> 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

Pasi Kärkkäinen

2010-Apr-08 20:44 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

On Thu, Apr 08, 2010 at 01:12:10PM -0700, Boris Derzhavets
wrote:>    PV DomU seems to be loaded
>    Profile seems to reference root=/dev/sda1.
>    Try root=/dev/xvda1
> 
No, I think he''s trying to boot dom0.

-- Pasi
>    Boris.
> 
>    --- On Thu, 4/8/10, For@ll <forall@stalowka.info> wrote:
> 
>      From: For@ll <forall@stalowka.info>
>      Subject: Re: [Xen-users] XEN 4.0 boot error
>      To: xen-users@lists.xensource.com
>      Date: Thursday, April 8, 2010, 3:46 PM
> 
>      2010/4/8 Pasi KÃ€rkkÃ€inen <[1]pasik@iki.fi>
> 
>        On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
>        >    2010/4/8 Pasi KÃ€rkkÃ€inen <[1][2]pasik@iki.fi>
>        >
>        >      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
>        >      >    Hey all,
>        >      >
>        >      >    Just downloaded the new Xen 4.0 and ran
>        >      >
>        >      >    Make xen
>        >      >    Make tools
>        >      >    Make stubdom
>        >      >
>        >      >    Copied the new files from dist/install
>        >      >    Im already running pv_ops 2.6.31.6 kernel.
>        >      >
>        >      >    When I boot i get
>        >      >
>        >      >    (XEN) Panic on CPU 0:
>        >      >    (XEN) IO-APIC +  timer doesn''t work!
>        >      >
>        >      >    I have tried booting with noapic boot option but
makes no
>        >      difference.  The
>        >      >    system worked fine on 3.4.2
>        >      >
>        >      >    CPU is AMD.
>        >      >
>        >      >    Any ideas?
>        >      >
>        >
>        >      Well.. can you post a full serial console log of the boot
>        process?
>        >
>        >      See here for help:
>        [2][3]http://wiki.xensource.com/xenwiki/XenParavirtOps
>        >
>        >    I have the same problem to boot xen 4.0 on debian lenny 5.0,
>         under I
>        >    paste a some error:
>        >
>        >    41.017078]   Magic number: 6:876:244
>        >    [   41.061177] md: Waiting for all devices to be available
before
>        >    autodetect
>        >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
>        >    [   41.211225] md: Autodetecting RAID arrays.
>        >    [   41.260417] md: Scanned 0 and added 0 devices.
>        >    [   41.313729] md: autorun ...
>        >    [   41.347281] md: ... autorun DONE.
>        >    [   41.387150] Root-NFS: No NFS server available, giving up.
>        >    [   41.451921] VFS: Unable to mount root fs via NFS, trying
>        floppy.
>        >    [   41.524664] VFS: Cannot open root device "sda1"
or
>        unknown-block(2,0)
> 
>        So the disk was not detected, or did you pass wrong root= parameter?
> 
>        Please post the _full_ log.
> 
>        -- Pasi
> 
>        >    [   41.601913] Please append a correct "root="
boot option; here
>        are the
>        >    available partitions:
>        >    [   41.702180] 0b00         1048575 sr0 driver: sr
>        >    [   41.756691] Kernel panic - not syncing: VFS: Unable to
mount
>        root fs on
>        >    unknown-block(2,0)
>        >    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13
#2
>        >    [   41.921708] Call Trace:
>        >    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
>        >    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
>        >    [   42.049483]  [<c191ec2d>]
mount_block_root+0x163/0x172
>        >    [   42.111158]  [<c1002930>] ?
hypercall_page+0x930/0x1005
>        >    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
>        >    [   42.227178]  [<c191ee05>]
prepare_namespace+0x145/0x16c
>        >    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
>        >    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>        >    [   42.402764]  [<c1028d37>]
kernel_thread_helper+0x7/0x10
>        >
> 
>      Hi,
> 
>      This is a longer version dmesg from console redirection ( ipmitool
>      connect to iRMC)
> 
>      [   25.101873] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
0
>      pin 16 triggering 1 polarity 1
>      [   25.210426] pci 0000:00:1c.7: PCI INT A -> GSI 16 (level, low)
-> IRQ
>      16
>      [   25.290926] NET: Registered protocol family 2
>      [   25.343369] IP route cache hash table entries: 32768 (order: 5,
>      131072 bytes)
>      [   25.429385] TCP established hash table entries: 131072 (order: 8,
>      1048576 bytes)
>      [   25.518783] TCP bind hash table entries: 65536 (order: 7, 524288
>      bytes)
>      [   25.598413] TCP: Hash tables configured (established 131072 bind
>      65536)
>      [   25.677741] TCP reno registered
>      [   25.715586] NET: Registered protocol family 1
>      [   25.767966] kvm: no hardware support
>      [   25.810908] has_svm: not amd
>      [   25.845501] kvm: no hardware support
>      [   25.888606] Simple Boot Flag at 0x50 set to 0x1
>      [   25.946611] Microcode Update Driver: v2.00
>      <[4]tigran@aivazian.fsnet.co.uk>, Peter Oruba
>      [   26.040604] Scanning for low memory corruption every 60 seconds
>      [   26.112527] audit: initializing netlink socket (disabled)
>      [   26.179722] type=2000 audit(1270763053.504:1): initialized
>      [   11.184373] highmem bounce pool size: 64 pages
>      [   11.237701] HugeTLB registered 2 MB page size, pre-allocated 0
pages
>      [   11.319190] VFS: Disk quotas dquot_6.5.2
>      [   11.366415] Dquot-cache hash table entries: 1024 (order 0, 4096
>      bytes)
>      [   11.445284] DLM (built Apr  8 2010 14:55:36) installed
>      [   11.508815] OCFS2 1.5.0
>      [   11.538530] ocfs2: Registered cluster interface o2cb
>      [   11.598381] ocfs2: Registered cluster interface user
>      [   11.657945] OCFS2 Node Manager 1.5.0
>      [   11.701011] OCFS2 DLM 1.5.0
>      [   11.734622] OCFS2 DLMFS 1.5.0
>      [   11.770430] OCFS2 User DLM kernel interface loaded
>      [   11.828680] Slow work thread pool: Starting up
>      [   11.882081] Slow work thread pool: Ready
>      [   11.929163] GFS2 (built Apr  8 2010 14:56:07) installed
>      [   11.991853] msgmni has been set to 1248
>      [   12.039039] alg: No test for stdrng (krng)
>      [   12.088412] Block layer SCSI generic (bsg) driver version 0.4
loaded
>      (major 252)
>      [   12.177207] io scheduler noop registered
>      [   12.224285] io scheduler anticipatory registered
>      [   12.279686] io scheduler deadline registered
>      [   12.330936] io scheduler cfq registered (default)
>      [   12.390106] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>      [   12.457519] ACPI: AC Adapter [PSD] (on-line)
>      [   12.509066] input: Power Button as
>      /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
>      [   12.597857] ACPI: Power Button [PWRF]
>      [   12.641975] input: Power Button as
>      /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
>      [   12.740153] ACPI: Power Button [PWRB]
>      [   12.784590] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   12.845935] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   12.907366] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   12.968754] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   13.034662] Event-channel device installed.
>      [   13.088923] blktap_device_init: blktap device major 253
>      [   13.151673] blktap_ring_init: blktap ring major: 251
>      [   13.212676] registering netback
>      [   13.260648] hpet_acpi_add: no address or irqs in _CRS
>      [   13.321642] Non-volatile memory driver v1.3
>      [   13.372539] Linux agpgart interface v0.103
>      [   13.422152] [drm] Initialized drm 1.1.0 20060810
>      [   13.477799] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>      Ë*[   13.797361] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>      [   13.872710] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>      [   13.946381] brd: module loaded
>      [   13.985783] loop: module loaded
>      [   14.024058] input: Macintosh mouse button emulation as
>      /devices/virtual/input/input2
>      [   14.118477] xen_set_ioapic_routing: irq 22 gsi 22 vector 22 ioapic
0
>      pin 22 triggering 1 polarity 1
>      [   14.227076] ata_piix 0000:00:1f.2: PCI INT A -> GSI 22 (level,
low)
>      -> IRQ 22
>      [   14.312643] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
>      [   14.375473] scsi0 : ata_piix
>      [   14.410844] scsi1 : ata_piix
>      [   14.445932] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma
0x1870
>      irq 14
>      [   14.529487] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma
0x1878
>      irq 15
>      [   14.613055] xen_set_ioapic_routing: irq 23 gsi 23 vector 23 ioapic
0
>      pin 23 triggering 1 polarity 1
>      [   14.721616] ata_piix 0000:00:1f.5: PCI INT B -> GSI 23 (level,
low)
>      -> IRQ 23
>      [   14.807293] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
>      [   14.870023] scsi2 : ata_piix
>      [   14.905173] scsi3 : ata_piix
>      [   14.940127] ata3: SATA max UDMA/133 cmd 0x18c8 ctl 0x18bc bmdma
>      0x1890 irq 23
>      [   15.025708] ata4: SATA max UDMA/133 cmd 0x18c0 ctl 0x18b8 bmdma
>      0x1898 irq 23
>      [   15.112211] Intel(R) PRO/1000 Network Driver - version
7.3.21-k3-NAPI
>      [   15.189453] Copyright (c) 1999-2006 Intel Corporation.
>      [   30.313754] ata2.00: SATA link down (SStatus 0 SControl 300)
>      [   30.313848] ata2.01: SATA link down (SStatus 0 SControl 300)
>      [   30.326241] ata1.00: SATA link down (SStatus 0 SControl 300)
>      [   30.326268] ata1.01: SATA link down (SStatus 0 SControl 300)
>      [   30.500741] ata4: SATA link down (SStatus 0 SControl 300)
>      [   15.587630] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
>      [   16.373656] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>      [   16.392986] ata3.00: ATAPI: HL-DT-ST DVDRAM GT20N, CW03, max
UDMA/133
>      [   16.414991] ata3.00: configured for UDMA/133
>      [   30.751248] scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GT20N
>      CW03 PQ: 0 ANSI: 5
>      [   30.763236] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
>      xa/form2 cdda tray
>      [   30.763240] Uniform CD-ROM driver Revision: 3.20
>      [   30.764188] sr 2:0:0:0: Attached scsi generic sg0 type 5
>      [   16.167491] e1000e: Copyright (c) 1999-2008 Intel Corporation.
>      [   16.237533] xen_set_ioapic_routing: irq 17 gsi 17 vector 17 ioapic
0
>      pin 17 triggering 1 polarity 1
>      [   16.346385] e1000e 0000:00:19.0: PCI INT A -> GSI 17 (level,
low) ->
>      IRQ 17
>      [   16.429871] e1000e 0000:00:19.0: pci_enable_pcie_error_reporting
>      failed 0xfffffffb
>      [   16.631590] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1)
>      00:40:d0:c0:94:ab
>      [   16.720405] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network
Connection
>      [   16.798930] 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 313130-032
>      [   16.873209] xen_set_ioapic_routing: irq 18 gsi 18 vector 18 ioapic
0
>      pin 18 triggering 1 polarity 1
>      [   16.981766] e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level,
low) ->
>      IRQ 18
>      [   17.151067] 0000:06:00.0: eth1: (PCI Express:2.5GB/s:Width x1)
>      00:40:d0:c0:94:aa
>      [   17.239785] 0000:06:00.0: eth1: Intel(R) PRO/1000 Network
Connection
>      [   17.316095] 0000:06:00.0: eth1: MAC: 3, PHY: 8, PBA No: 313132-030
>      [   17.390967] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
>      [   17.464089] e100: Copyright(c) 1999-2006 Intel Corporation
>      [   17.530921] sky2 driver version 1.23
>      [   17.575855] console [netcon0] enabled
>      [   17.619813] netconsole: network logging started
>      [   17.674531] Fusion MPT base driver 3.04.10
>      [   17.723728] Copyright (c) 1999-2008 LSI Corporation
>      [   17.782276] Fusion MPT FC Host driver 3.04.10
>      [   17.834877] Fusion MPT misc device (ioctl) driver 3.04.10
>      [   17.900030] mptctl: Registered with Fusion MPT base driver
>      [   17.965842] mptctl: /dev/mptctl @ (major,minor=10,220)
>      [   18.028613] ehci_hcd: USB 2.0 ''Enhanced'' Host
Controller (EHCI)
>      Driver
>      [   18.106968] xen_set_ioapic_routing: irq 21 gsi 21 vector 21 ioapic
0
>      pin 21 triggering 1 polarity 1
>      [   18.215560] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 21 (level,
low)
>      -> IRQ 21
>      [   18.301142] ehci_hcd 0000:00:1a.0: EHCI Host Controller
>      [   18.364179] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned
>      bus number 1
>      [   18.456986] ehci_hcd 0000:00:1a.0: debug port 2
>      [   18.511435] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
>      [   18.589288] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
>      [   18.658307] usb usb1: New USB device found, idVendor=1d6b,
>      idProduct=0002
>      [   18.739739] usb usb1: New USB device strings: Mfr=3, Product=2,
>      SerialNumber=1
>      [   18.826521] usb usb1: Product: EHCI Host Controller
>      [   18.885035] usb usb1: Manufacturer: Linux 2.6.31.13 ehci_hcd
>      [   18.952915] usb usb1: SerialNumber: 0000:00:1a.0
>      [   19.008822] usb usb1: configuration #1 chosen from 1 choice
>      [   19.076102] hub 1-0:1.0: USB hub found
>      [   19.121247] hub 1-0:1.0: 2 ports detected
>      [   19.169523] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic
0
>      pin 20 triggering 1 polarity 1
>      [   19.278107] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level,
low)
>      -> IRQ 20
>      [   19.363693] ehci_hcd 0000:00:1d.0: EHCI Host Controller
>      [   19.426837] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned
>      bus number 2
>      [   19.519665] ehci_hcd 0000:00:1d.0: debug port 2
>      [   19.574137] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
>      [   20.413312] usb 1-1: new high speed USB device using ehci_hcd and
>      address 2
>      [   19.760373] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
>      [   19.829381] usb usb2: New USB device found, idVendor=1d6b,
>      idProduct=0002
>      [   19.910786] usb usb2: New USB device strings: Mfr=3, Product=2,
>      SerialNumber=1
>      [   19.997491] usb usb2: Product: EHCI Host Controller
>      [   20.056022] usb usb2: Manufacturer: Linux 2.6.31.13 ehci_hcd
>      [   20.123938] usb usb2: SerialNumber: 0000:00:1d.0
>      [   20.179767] usb usb2: configuration #1 chosen from 1 choice
>      [   35.261351] usb 1-1: New USB device found, idVendor=8087,
>      idProduct=0020
>      [   35.261353] usb 1-1: New USB device strings: Mfr=0, Product=0,
>      SerialNumber=0
>      [   35.261696] usb 1-1: configuration #1 chosen from 1 choice
>      [   35.262004] hub 1-1:1.0: USB hub found
>      [   35.262112] hub 1-1:1.0: 6 ports detected
>      [   20.571877] hub 2-0:1.0: USB hub found
>      [   20.616947] hub 2-0:1.0: 2 ports detected
>      [   20.665554] ohci_hcd: USB 1.1 ''Open'' Host
Controller (OHCI) Driver
>      [   20.740168] uhci_hcd: USB Universal Host Controller Interface
driver
>      [   20.817277] usbcore: registered new interface driver usblp
>      [   20.883086] Initializing USB Mass Storage driver...
>      [   20.941974] usbcore: registered new interface driver usb-storage
>      [   21.014026] USB Mass Storage support registered.
>      [   36.112936] usb 2-1: new high speed USB device using ehci_hcd and
>      address 2
>      [   21.153280] usbcore: registered new interface driver libusual
>      [   36.228304] usb 2-1: New USB device found, idVendor=8087,
>      idProduct=0020
>      [   36.228307] usb 2-1: New USB device strings: Mfr=0, Product=0,
>      SerialNumber=0
>      [   36.228660] usb 2-1: configuration #1 chosen from 1 choice
>      [   36.228969] hub 2-1:1.0: USB hub found
>      [   36.229070] hub 2-1:1.0: 8 ports detected
>      [   36.495535] usb 2-1.4: new low speed USB device using ehci_hcd and
>      address 3
>      [   36.592902] usb 2-1.4: New USB device found, idVendor=04d9,
>      idProduct=1603
>      [   36.592905] usb 2-1.4: New USB device strings: Mfr=1, Product=2,
>      SerialNumber=0
>      [   36.592908] usb 2-1.4: Product: USB Keyboard
>      [   36.592910] usb 2-1.4: Manufacturer:
>      [   36.593255] usb 2-1.4: configuration #1 chosen from 1 choice
>      [   36.657328] usb 2-1.5: new full speed USB device using ehci_hcd and
>      address 4
>      [   36.735047] usb 2-1.5: New USB device found, idVendor=0000,
>      idProduct=0000
>      [   36.735049] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
>      SerialNumber=3
>      [   36.735052] usb 2-1.5: Product: iRMC USB Device
>      [   36.735054] usb 2-1.5: Manufacturer: Fujitsu
>      [   36.735056] usb 2-1.5: SerialNumber: 600ABC94D3074C
>      [   36.735417] usb 2-1.5: configuration #1 chosen from 1 choice
>      [   22.454959] PNP: No PS/2 controller found. Probing ports directly.
>      [   23.293431] hrtimer: interrupt took 9183132 ns
>      [   22.842002] serio: i8042 KBD port at 0x60,0x64 irq 1
>      [   22.902741] mice: PS/2 mouse device common for all mice
>      [   22.977135] rtc_cmos 00:06: RTC can wake from S4
>      [   23.032918] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
>      [   23.106105] rtc0: alarms up to one month, y3k, 114 bytes nvram
>      [   23.176478] xen_allocate_pirq: returning irq 20 for gsi 20
>      [   23.242289] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic
0
>      pin 20 triggering 1 polarity 1
>      [   23.350973] i801_smbus 0000:00:1f.3: PCI INT D -> GSI 20 (level,
low)
>      -> IRQ 20
>      [   23.440784] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)
>      initialised: [5]dm-devel@redhat.com
>      [   23.542605] cpuidle: using governor ladder
>      [   23.591833] cpuidle: using governor menu
>      [   23.642069] usbcore: registered new interface driver hiddev
>      [   38.781806] input:   USB Keyboard as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
>      [   38.899189] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID
>      v1.10 Keyboard [  USB Keyboard] on usb-0000:00:1d.0-1.4/input0
>      [   39.057332] input:   USB Keyboard as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input4
>      [   39.174832] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID
>      v1.10 Device [  USB Keyboard] on usb-0000:00:1d.0-1.4/input1
>      [   39.315677] input: Fujitsu iRMC USB Device as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input5
>      [   39.442738] generic-usb 0003:0000:0000.0003: input,hidraw2: USB HID
>      v1.11 Keyboard [Fujitsu iRMC USB Device] on
usb-0000:00:1d.0-1.5/input0
>      [   39.594713] input: Fujitsu iRMC USB Device as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input6
>      [   39.722047] generic-usb 0003:0000:0000.0004: input,hidraw3: USB HID
>      v1.11 Mouse [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input1
>      [   39.869436] usbcore: registered new interface driver usbhid
>      [   39.936280] usbhid: v2.6:USB HID core driver
>      [   39.988359] Advanced Linux Sound Architecture Driver Version
1.0.20.
>      [   40.066220] ALSA device list:
>      [   40.101937]   No soundcards found.
>      [   40.142841] Netfilter messages via NETLINK v0.30.
>      [   40.199352] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
>      [   40.273258] ctnetlink v0.93: registering with nfnetlink.
>      [   40.338192] ip_tables: (C) 2000-2006 Netfilter Core Team
>      [   40.402000] TCP cubic registered
>      [   40.440827] Initializing XFRM netlink socket
>      [   40.493211] NET: Registered protocol family 10
>      [   40.549310] ip6_tables: (C) 2000-2006 Netfilter Core Team
>      [   40.614164] IPv6 over IPv4 tunneling driver
>      [   40.666254] NET: Registered protocol family 17
>      [   40.720665] RPC: Registered udp transport module.
>      [   40.777108] RPC: Registered tcp transport module.
>      [   40.834214] SCTP: Hash tables configured (established 65536 bind
>      65536)
>      [   40.914548] Using IPI No-Shortcut mode
>      [   40.960325] registered taskstats version 1
>      [   41.009654]   Magic number: 6:500:752
>      [   41.053698] tty ttyS3: hash matches
>      [   41.095785] md: Waiting for all devices to be available before
>      autodetect
>      [   41.177190] md: If you don''t use raid, use
raid=noautodetect
>      [   41.245761] md: Autodetecting RAID arrays.
>      [   41.294919] md: Scanned 0 and added 0 devices.
>      [   41.348234] md: autorun ...
>      [   41.381789] md: ... autorun DONE.
>      [   41.421739] Root-NFS: No NFS server available, giving up.
>      [   41.486540] VFS: Unable to mount root fs via NFS, trying floppy.
>      [   41.559115] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
>      [   41.636362] Please append a correct "root=" boot option;
here are the
>      available partitions:
>      [   41.736610] 0b00         1048575 sr0 driver: sr
>      [   41.791146] Kernel panic - not syncing: VFS: Unable to mount root
fs
>      on unknown-block(2,0)
>      [   41.890337] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
>      [   41.956135] Call Trace:
>      [   41.985599]  [<c15e8386>] ? printk+0xf/0x11
>      [   42.035826]  [<c15e82ca>] panic+0x39/0xe6
>      [   42.083950]  [<c191ec2d>] mount_block_root+0x163/0x172
>      [   42.145673]  [<c1002930>] ? hypercall_page+0x930/0x1005
>      [   42.208414]  [<c191eca2>] mount_root+0x66/0x84
>      [   42.261803]  [<c191ee05>] prepare_namespace+0x145/0x16c
>      [   42.324489]  [<c191e34f>] kernel_init+0x16e/0x17d
>      [   42.380929]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>      [   42.437369]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> 
>      For@ll
> 
>      -----Inline Attachment Follows-----
> 
>      _______________________________________________
>      Xen-users mailing list
>      [6]Xen-users@lists.xensource.com
>      [7]http://lists.xensource.com/xen-users
> 
> References
> 
>    Visible links
>    1. file:///mc/compose?to=pasik@iki.fi
>    2. file:///mc/compose?to=pasik@iki.fi
>    3. http://wiki.xensource.com/xenwiki/XenParavirtOps
>    4. file:///mc/compose?to=tigran@aivazian.fsnet.co.uk
>    5. file:///mc/compose?to=dm-devel@redhat.com
>    6. file:///mc/compose?to=Xen-users@lists.xensource.com
>    7. http://lists.xensource.com/xen-users
> _______________________________________________
> 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

Boris Derzhavets

2010-Apr-08 21:16 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

Sorry, you are right.

Boris.

--- On Thu, 4/8/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-users] XEN 4.0 boot error
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "For@ll" <forall@stalowka.info>,
xen-users@lists.xensource.com
Date: Thursday, April 8, 2010, 4:44 PM

On Thu, Apr 08, 2010 at 01:12:10PM -0700, Boris Derzhavets
wrote:>    PV DomU seems to be loaded
>    Profile seems to reference root=/dev/sda1.
>    Try root=/dev/xvda1
> 
No, I think he''s trying to boot dom0.

-- Pasi
>    Boris.
> 
>    --- On Thu, 4/8/10, For@ll <forall@stalowka.info> wrote:
> 
>      From: For@ll <forall@stalowka.info>
>      Subject: Re: [Xen-users] XEN 4.0 boot error
>      To: xen-users@lists.xensource.com
>      Date: Thursday, April 8, 2010, 3:46 PM
> 
>      2010/4/8 Pasi KÃ€rkkÃ€inen <[1]pasik@iki.fi>
> 
>        On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
>        >    2010/4/8 Pasi KÃ€rkkÃ€inen <[1][2]pasik@iki.fi>
>        >
>        >      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
>        >      >    Hey all,
>        >      >
>        >      >    Just downloaded the new Xen 4.0 and ran
>        >      >
>        >      >    Make xen
>        >      >    Make tools
>        >      >    Make stubdom
>        >      >
>        >      >    Copied the new files from dist/install
>        >      >    Im already running pv_ops 2.6.31.6 kernel.
>        >      >
>        >      >    When I boot i get
>        >      >
>        >      >    (XEN) Panic on CPU 0:
>        >      >    (XEN) IO-APIC +  timer doesn''t work!
>        >      >
>        >      >    I have tried booting with noapic boot option but
makes no
>        >      difference.  The
>        >      >    system worked fine on 3.4.2
>        >      >
>        >      >    CPU is AMD.
>        >      >
>        >      >    Any ideas?
>        >      >
>        >
>        >      Well.. can you post a full serial console log of the boot
>        process?
>        >
>        >      See here for help:
>        [2][3]http://wiki.xensource.com/xenwiki/XenParavirtOps
>        >
>        >    I have the same problem to boot xen 4.0 on debian lenny 5.0,
>         under I
>        >    paste a some error:
>        >
>        >    41.017078]   Magic number: 6:876:244
>        >    [   41.061177] md: Waiting for all devices to be available
before
>        >    autodetect
>        >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
>        >    [   41.211225] md: Autodetecting RAID arrays.
>        >    [   41.260417] md: Scanned 0 and added 0 devices.
>        >    [   41.313729] md: autorun ...
>        >    [   41.347281] md: ... autorun DONE.
>        >    [   41.387150] Root-NFS: No NFS server available, giving up.
>        >    [   41.451921] VFS: Unable to mount root fs via NFS, trying
>        floppy.
>        >    [   41.524664] VFS: Cannot open root device "sda1"
or
>        unknown-block(2,0)
> 
>        So the disk was not detected, or did you pass wrong root= parameter?
> 
>        Please post the _full_ log.
> 
>        -- Pasi
> 
>        >    [   41.601913] Please append a correct "root="
boot option; here
>        are the
>        >    available partitions:
>        >    [   41.702180] 0b00         1048575 sr0 driver: sr
>        >    [   41.756691] Kernel panic - not syncing: VFS: Unable to
mount
>        root fs on
>        >    unknown-block(2,0)
>        >    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13
#2
>        >    [   41.921708] Call Trace:
>        >    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
>        >    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
>        >    [   42.049483]  [<c191ec2d>]
mount_block_root+0x163/0x172
>        >    [   42.111158]  [<c1002930>] ?
hypercall_page+0x930/0x1005
>        >    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
>        >    [   42.227178]  [<c191ee05>]
prepare_namespace+0x145/0x16c
>        >    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
>        >    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>        >    [   42.402764]  [<c1028d37>]
kernel_thread_helper+0x7/0x10
>        >
> 
>      Hi,
> 
>      This is a longer version dmesg from console redirection ( ipmitool
>      connect to iRMC)
> 
>      [   25.101873] xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic
0
>      pin 16 triggering 1 polarity 1
>      [   25.210426] pci 0000:00:1c.7: PCI INT A -> GSI 16 (level, low)
-> IRQ
>      16
>      [   25.290926] NET: Registered protocol family 2
>      [   25.343369] IP route cache hash table entries: 32768 (order: 5,
>      131072 bytes)
>      [   25.429385] TCP established hash table entries: 131072 (order: 8,
>      1048576 bytes)
>      [   25.518783] TCP bind hash table entries: 65536 (order: 7, 524288
>      bytes)
>      [   25.598413] TCP: Hash tables configured (established 131072 bind
>      65536)
>      [   25.677741] TCP reno registered
>      [   25.715586] NET: Registered protocol family 1
>      [   25.767966] kvm: no hardware support
>      [   25.810908] has_svm: not amd
>      [   25.845501] kvm: no hardware support
>      [   25.888606] Simple Boot Flag at 0x50 set to 0x1
>      [   25.946611] Microcode Update Driver: v2.00
>      <[4]tigran@aivazian.fsnet.co.uk>, Peter Oruba
>      [   26.040604] Scanning for low memory corruption every 60 seconds
>      [   26.112527] audit: initializing netlink socket (disabled)
>      [   26.179722] type=2000 audit(1270763053.504:1): initialized
>      [   11.184373] highmem bounce pool size: 64 pages
>      [   11.237701] HugeTLB registered 2 MB page size, pre-allocated 0
pages
>      [   11.319190] VFS: Disk quotas dquot_6.5.2
>      [   11.366415] Dquot-cache hash table entries: 1024 (order 0, 4096
>      bytes)
>      [   11.445284] DLM (built Apr  8 2010 14:55:36) installed
>      [   11.508815] OCFS2 1.5.0
>      [   11.538530] ocfs2: Registered cluster interface o2cb
>      [   11.598381] ocfs2: Registered cluster interface user
>      [   11.657945] OCFS2 Node Manager 1.5.0
>      [   11.701011] OCFS2 DLM 1.5.0
>      [   11.734622] OCFS2 DLMFS 1.5.0
>      [   11.770430] OCFS2 User DLM kernel interface loaded
>      [   11.828680] Slow work thread pool: Starting up
>      [   11.882081] Slow work thread pool: Ready
>      [   11.929163] GFS2 (built Apr  8 2010 14:56:07) installed
>      [   11.991853] msgmni has been set to 1248
>      [   12.039039] alg: No test for stdrng (krng)
>      [   12.088412] Block layer SCSI generic (bsg) driver version 0.4
loaded
>      (major 252)
>      [   12.177207] io scheduler noop registered
>      [   12.224285] io scheduler anticipatory registered
>      [   12.279686] io scheduler deadline registered
>      [   12.330936] io scheduler cfq registered (default)
>      [   12.390106] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>      [   12.457519] ACPI: AC Adapter [PSD] (on-line)
>      [   12.509066] input: Power Button as
>      /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
>      [   12.597857] ACPI: Power Button [PWRF]
>      [   12.641975] input: Power Button as
>      /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
>      [   12.740153] ACPI: Power Button [PWRB]
>      [   12.784590] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   12.845935] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   12.907366] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   12.968754] ACPI: CPU-1 (power states: C1[C1] C2[C3])
>      [   13.034662] Event-channel device installed.
>      [   13.088923] blktap_device_init: blktap device major 253
>      [   13.151673] blktap_ring_init: blktap ring major: 251
>      [   13.212676] registering netback
>      [   13.260648] hpet_acpi_add: no address or irqs in _CRS
>      [   13.321642] Non-volatile memory driver v1.3
>      [   13.372539] Linux agpgart interface v0.103
>      [   13.422152] [drm] Initialized drm 1.1.0 20060810
>      [   13.477799] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>      Ë*[   13.797361] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>      [   13.872710] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>      [   13.946381] brd: module loaded
>      [   13.985783] loop: module loaded
>      [   14.024058] input: Macintosh mouse button emulation as
>      /devices/virtual/input/input2
>      [   14.118477] xen_set_ioapic_routing: irq 22 gsi 22 vector 22 ioapic
0
>      pin 22 triggering 1 polarity 1
>      [   14.227076] ata_piix 0000:00:1f.2: PCI INT A -> GSI 22 (level,
low)
>      -> IRQ 22
>      [   14.312643] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
>      [   14.375473] scsi0 : ata_piix
>      [   14.410844] scsi1 : ata_piix
>      [   14.445932] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma
0x1870
>      irq 14
>      [   14.529487] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma
0x1878
>      irq 15
>      [   14.613055] xen_set_ioapic_routing: irq 23 gsi 23 vector 23 ioapic
0
>      pin 23 triggering 1 polarity 1
>      [   14.721616] ata_piix 0000:00:1f.5: PCI INT B -> GSI 23 (level,
low)
>      -> IRQ 23
>      [   14.807293] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
>      [   14.870023] scsi2 : ata_piix
>      [   14.905173] scsi3 : ata_piix
>      [   14.940127] ata3: SATA max UDMA/133 cmd 0x18c8 ctl 0x18bc bmdma
>      0x1890 irq 23
>      [   15.025708] ata4: SATA max UDMA/133 cmd 0x18c0 ctl 0x18b8 bmdma
>      0x1898 irq 23
>      [   15.112211] Intel(R) PRO/1000 Network Driver - version
7.3.21-k3-NAPI
>      [   15.189453] Copyright (c) 1999-2006 Intel Corporation.
>      [   30.313754] ata2.00: SATA link down (SStatus 0 SControl 300)
>      [   30.313848] ata2.01: SATA link down (SStatus 0 SControl 300)
>      [   30.326241] ata1.00: SATA link down (SStatus 0 SControl 300)
>      [   30.326268] ata1.01: SATA link down (SStatus 0 SControl 300)
>      [   30.500741] ata4: SATA link down (SStatus 0 SControl 300)
>      [   15.587630] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
>      [   16.373656] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>      [   16.392986] ata3.00: ATAPI: HL-DT-ST DVDRAM GT20N, CW03, max
UDMA/133
>      [   16.414991] ata3.00: configured for UDMA/133
>      [   30.751248] scsi 2:0:0:0: CD-ROM            HL-DT-ST DVDRAM GT20N
>      CW03 PQ: 0 ANSI: 5
>      [   30.763236] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
>      xa/form2 cdda tray
>      [   30.763240] Uniform CD-ROM driver Revision: 3.20
>      [   30.764188] sr 2:0:0:0: Attached scsi generic sg0 type 5
>      [   16.167491] e1000e: Copyright (c) 1999-2008 Intel Corporation.
>      [   16.237533] xen_set_ioapic_routing: irq 17 gsi 17 vector 17 ioapic
0
>      pin 17 triggering 1 polarity 1
>      [   16.346385] e1000e 0000:00:19.0: PCI INT A -> GSI 17 (level,
low) ->
>      IRQ 17
>      [   16.429871] e1000e 0000:00:19.0: pci_enable_pcie_error_reporting
>      failed 0xfffffffb
>      [   16.631590] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1)
>      00:40:d0:c0:94:ab
>      [   16.720405] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network
Connection
>      [   16.798930] 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 313130-032
>      [   16.873209] xen_set_ioapic_routing: irq 18 gsi 18 vector 18 ioapic
0
>      pin 18 triggering 1 polarity 1
>      [   16.981766] e1000e 0000:06:00.0: PCI INT A -> GSI 18 (level,
low) ->
>      IRQ 18
>      [   17.151067] 0000:06:00.0: eth1: (PCI Express:2.5GB/s:Width x1)
>      00:40:d0:c0:94:aa
>      [   17.239785] 0000:06:00.0: eth1: Intel(R) PRO/1000 Network
Connection
>      [   17.316095] 0000:06:00.0: eth1: MAC: 3, PHY: 8, PBA No: 313132-030
>      [   17.390967] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
>      [   17.464089] e100: Copyright(c) 1999-2006 Intel Corporation
>      [   17.530921] sky2 driver version 1.23
>      [   17.575855] console [netcon0] enabled
>      [   17.619813] netconsole: network logging started
>      [   17.674531] Fusion MPT base driver 3.04.10
>      [   17.723728] Copyright (c) 1999-2008 LSI Corporation
>      [   17.782276] Fusion MPT FC Host driver 3.04.10
>      [   17.834877] Fusion MPT misc device (ioctl) driver 3.04.10
>      [   17.900030] mptctl: Registered with Fusion MPT base driver
>      [   17.965842] mptctl: /dev/mptctl @ (major,minor=10,220)
>      [   18.028613] ehci_hcd: USB 2.0 ''Enhanced'' Host
Controller (EHCI)
>      Driver
>      [   18.106968] xen_set_ioapic_routing: irq 21 gsi 21 vector 21 ioapic
0
>      pin 21 triggering 1 polarity 1
>      [   18.215560] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 21 (level,
low)
>      -> IRQ 21
>      [   18.301142] ehci_hcd 0000:00:1a.0: EHCI Host Controller
>      [   18.364179] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned
>      bus number 1
>      [   18.456986] ehci_hcd 0000:00:1a.0: debug port 2
>      [   18.511435] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
>      [   18.589288] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
>      [   18.658307] usb usb1: New USB device found, idVendor=1d6b,
>      idProduct=0002
>      [   18.739739] usb usb1: New USB device strings: Mfr=3, Product=2,
>      SerialNumber=1
>      [   18.826521] usb usb1: Product: EHCI Host Controller
>      [   18.885035] usb usb1: Manufacturer: Linux 2.6.31.13 ehci_hcd
>      [   18.952915] usb usb1: SerialNumber: 0000:00:1a.0
>      [   19.008822] usb usb1: configuration #1 chosen from 1 choice
>      [   19.076102] hub 1-0:1.0: USB hub found
>      [   19.121247] hub 1-0:1.0: 2 ports detected
>      [   19.169523] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic
0
>      pin 20 triggering 1 polarity 1
>      [   19.278107] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 20 (level,
low)
>      -> IRQ 20
>      [   19.363693] ehci_hcd 0000:00:1d.0: EHCI Host Controller
>      [   19.426837] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned
>      bus number 2
>      [   19.519665] ehci_hcd 0000:00:1d.0: debug port 2
>      [   19.574137] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
>      [   20.413312] usb 1-1: new high speed USB device using ehci_hcd and
>      address 2
>      [   19.760373] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
>      [   19.829381] usb usb2: New USB device found, idVendor=1d6b,
>      idProduct=0002
>      [   19.910786] usb usb2: New USB device strings: Mfr=3, Product=2,
>      SerialNumber=1
>      [   19.997491] usb usb2: Product: EHCI Host Controller
>      [   20.056022] usb usb2: Manufacturer: Linux 2.6.31.13 ehci_hcd
>      [   20.123938] usb usb2: SerialNumber: 0000:00:1d.0
>      [   20.179767] usb usb2: configuration #1 chosen from 1 choice
>      [   35.261351] usb 1-1: New USB device found, idVendor=8087,
>      idProduct=0020
>      [   35.261353] usb 1-1: New USB device strings: Mfr=0, Product=0,
>      SerialNumber=0
>      [   35.261696] usb 1-1: configuration #1 chosen from 1 choice
>      [   35.262004] hub 1-1:1.0: USB hub found
>      [   35.262112] hub 1-1:1.0: 6 ports detected
>      [   20.571877] hub 2-0:1.0: USB hub found
>      [   20.616947] hub 2-0:1.0: 2 ports detected
>      [   20.665554] ohci_hcd: USB 1.1 ''Open'' Host
Controller (OHCI) Driver
>      [   20.740168] uhci_hcd: USB Universal Host Controller Interface
driver
>      [   20.817277] usbcore: registered new interface driver usblp
>      [   20.883086] Initializing USB Mass Storage driver...
>      [   20.941974] usbcore: registered new interface driver usb-storage
>      [   21.014026] USB Mass Storage support registered.
>      [   36.112936] usb 2-1: new high speed USB device using ehci_hcd and
>      address 2
>      [   21.153280] usbcore: registered new interface driver libusual
>      [   36.228304] usb 2-1: New USB device found, idVendor=8087,
>      idProduct=0020
>      [   36.228307] usb 2-1: New USB device strings: Mfr=0, Product=0,
>      SerialNumber=0
>      [   36.228660] usb 2-1: configuration #1 chosen from 1 choice
>      [   36.228969] hub 2-1:1.0: USB hub found
>      [   36.229070] hub 2-1:1.0: 8 ports detected
>      [   36.495535] usb 2-1.4: new low speed USB device using ehci_hcd and
>      address 3
>      [   36.592902] usb 2-1.4: New USB device found, idVendor=04d9,
>      idProduct=1603
>      [   36.592905] usb 2-1.4: New USB device strings: Mfr=1, Product=2,
>      SerialNumber=0
>      [   36.592908] usb 2-1.4: Product: USB Keyboard
>      [   36.592910] usb 2-1.4: Manufacturer:
>      [   36.593255] usb 2-1.4: configuration #1 chosen from 1 choice
>      [   36.657328] usb 2-1.5: new full speed USB device using ehci_hcd and
>      address 4
>      [   36.735047] usb 2-1.5: New USB device found, idVendor=0000,
>      idProduct=0000
>      [   36.735049] usb 2-1.5: New USB device strings: Mfr=1, Product=2,
>      SerialNumber=3
>      [   36.735052] usb 2-1.5: Product: iRMC USB Device
>      [   36.735054] usb 2-1.5: Manufacturer: Fujitsu
>      [   36.735056] usb 2-1.5: SerialNumber: 600ABC94D3074C
>      [   36.735417] usb 2-1.5: configuration #1 chosen from 1 choice
>      [   22.454959] PNP: No PS/2 controller found. Probing ports directly.
>      [   23.293431] hrtimer: interrupt took 9183132 ns
>      [   22.842002] serio: i8042 KBD port at 0x60,0x64 irq 1
>      [   22.902741] mice: PS/2 mouse device common for all mice
>      [   22.977135] rtc_cmos 00:06: RTC can wake from S4
>      [   23.032918] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
>      [   23.106105] rtc0: alarms up to one month, y3k, 114 bytes nvram
>      [   23.176478] xen_allocate_pirq: returning irq 20 for gsi 20
>      [   23.242289] xen_set_ioapic_routing: irq 20 gsi 20 vector 20 ioapic
0
>      pin 20 triggering 1 polarity 1
>      [   23.350973] i801_smbus 0000:00:1f.3: PCI INT D -> GSI 20 (level,
low)
>      -> IRQ 20
>      [   23.440784] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01)
>      initialised: [5]dm-devel@redhat.com
>      [   23.542605] cpuidle: using governor ladder
>      [   23.591833] cpuidle: using governor menu
>      [   23.642069] usbcore: registered new interface driver hiddev
>      [   38.781806] input:   USB Keyboard as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input3
>      [   38.899189] generic-usb 0003:04D9:1603.0001: input,hidraw0: USB HID
>      v1.10 Keyboard [  USB Keyboard] on usb-0000:00:1d.0-1.4/input0
>      [   39.057332] input:   USB Keyboard as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input4
>      [   39.174832] generic-usb 0003:04D9:1603.0002: input,hidraw1: USB HID
>      v1.10 Device [  USB Keyboard] on usb-0000:00:1d.0-1.4/input1
>      [   39.315677] input: Fujitsu iRMC USB Device as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input5
>      [   39.442738] generic-usb 0003:0000:0000.0003: input,hidraw2: USB HID
>      v1.11 Keyboard [Fujitsu iRMC USB Device] on
usb-0000:00:1d.0-1.5/input0
>      [   39.594713] input: Fujitsu iRMC USB Device as
>      /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.1/input/input6
>      [   39.722047] generic-usb 0003:0000:0000.0004: input,hidraw3: USB HID
>      v1.11 Mouse [Fujitsu iRMC USB Device] on usb-0000:00:1d.0-1.5/input1
>      [   39.869436] usbcore: registered new interface driver usbhid
>      [   39.936280] usbhid: v2.6:USB HID core driver
>      [   39.988359] Advanced Linux Sound Architecture Driver Version
1.0.20.
>      [   40.066220] ALSA device list:
>      [   40.101937]   No soundcards found.
>      [   40.142841] Netfilter messages via NETLINK v0.30.
>      [   40.199352] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
>      [   40.273258] ctnetlink v0.93: registering with nfnetlink.
>      [   40.338192] ip_tables: (C) 2000-2006 Netfilter Core Team
>      [   40.402000] TCP cubic registered
>      [   40.440827] Initializing XFRM netlink socket
>      [   40.493211] NET: Registered protocol family 10
>      [   40.549310] ip6_tables: (C) 2000-2006 Netfilter Core Team
>      [   40.614164] IPv6 over IPv4 tunneling driver
>      [   40.666254] NET: Registered protocol family 17
>      [   40.720665] RPC: Registered udp transport module.
>      [   40.777108] RPC: Registered tcp transport module.
>      [   40.834214] SCTP: Hash tables configured (established 65536 bind
>      65536)
>      [   40.914548] Using IPI No-Shortcut mode
>      [   40.960325] registered taskstats version 1
>      [   41.009654]   Magic number: 6:500:752
>      [   41.053698] tty ttyS3: hash matches
>      [   41.095785] md: Waiting for all devices to be available before
>      autodetect
>      [   41.177190] md: If you don''t use raid, use
raid=noautodetect
>      [   41.245761] md: Autodetecting RAID arrays.
>      [   41.294919] md: Scanned 0 and added 0 devices.
>      [   41.348234] md: autorun ...
>      [   41.381789] md: ... autorun DONE.
>      [   41.421739] Root-NFS: No NFS server available, giving up.
>      [   41.486540] VFS: Unable to mount root fs via NFS, trying floppy.
>      [   41.559115] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
>      [   41.636362] Please append a correct "root=" boot option;
here are the
>      available partitions:
>      [   41.736610] 0b00         1048575 sr0 driver: sr
>      [   41.791146] Kernel panic - not syncing: VFS: Unable to mount root
fs
>      on unknown-block(2,0)
>      [   41.890337] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
>      [   41.956135] Call Trace:
>      [   41.985599]  [<c15e8386>] ? printk+0xf/0x11
>      [   42.035826]  [<c15e82ca>] panic+0x39/0xe6
>      [   42.083950]  [<c191ec2d>] mount_block_root+0x163/0x172
>      [   42.145673]  [<c1002930>] ? hypercall_page+0x930/0x1005
>      [   42.208414]  [<c191eca2>] mount_root+0x66/0x84
>      [   42.261803]  [<c191ee05>] prepare_namespace+0x145/0x16c
>      [   42.324489]  [<c191e34f>] kernel_init+0x16e/0x17d
>      [   42.380929]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>      [   42.437369]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> 
>      For@ll
> 
>      -----Inline Attachment Follows-----
> 
>      _______________________________________________
>      Xen-users mailing list
>      [6]Xen-users@lists.xensource.com
>      [7]http://lists.xensource.com/xen-users
> 
> References
> 
>    Visible links
>    1. file:///mc/compose?to=pasik@iki.fi
>    2. file:///mc/compose?to=pasik@iki.fi
>    3. http://wiki.xensource.com/xenwiki/XenParavirtOps
>    4. file:///mc/compose?to=tigran@aivazian.fsnet.co.uk
>    5. file:///mc/compose?to=dm-devel@redhat.com
>    6. file:///mc/compose?to=Xen-users@lists.xensource.com
>    7. http://lists.xensource.com/xen-users
> _______________________________________________
> 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



      

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

Ian Tobin

2010-Apr-08 21:43 UTC

head link

RE: [Xen-users] XEN 4.0 boot error

Hey guys,

Sorry for the delay, been manic today.

I actually resolved this issue by messing around in the bios and enabling ACPI
HPET Table

Im not sure what that does but it booted straight away after that.

Maybe someone could shed some light on what it does.

Cheers

Ian


-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Pasi Kärkkäinen
Sent: 08 April 2010 19:54
To: Konto usnetu
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] XEN 4.0 boot error

On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu
wrote:>    2010/4/8 Pasi Kärkkäinen <[1]pasik@iki.fi>
> 
>      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
>      >    Hey all,
>      >
>      >    Just downloaded the new Xen 4.0 and ran
>      >
>      >    Make xen
>      >    Make tools
>      >    Make stubdom
>      >
>      >    Copied the new files from dist/install
>      >    Im already running pv_ops 2.6.31.6 kernel.
>      >
>      >    When I boot i get
>      >
>      >    (XEN) Panic on CPU 0:
>      >    (XEN) IO-APIC +  timer doesn''t work!
>      >
>      >    I have tried booting with noapic boot option but makes no
>      difference.  The
>      >    system worked fine on 3.4.2
>      >
>      >    CPU is AMD.
>      >
>      >    Any ideas?
>      >
> 
>      Well.. can you post a full serial console log of the boot process?
> 
>      See here for help: [2]http://wiki.xensource.com/xenwiki/XenParavirtOps
> 
>    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under I
>    paste a some error:
> 
>    41.017078]   Magic number: 6:876:244
>    [   41.061177] md: Waiting for all devices to be available before
>    autodetect
>    [   41.142579] md: If you don''t use raid, use raid=noautodetect
>    [   41.211225] md: Autodetecting RAID arrays.
>    [   41.260417] md: Scanned 0 and added 0 devices.
>    [   41.313729] md: autorun ...
>    [   41.347281] md: ... autorun DONE.
>    [   41.387150] Root-NFS: No NFS server available, giving up.
>    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
>    [   41.524664] VFS: Cannot open root device "sda1" or
unknown-block(2,0)

So the disk was not detected, or did you pass wrong root= parameter? 

Please post the _full_ log.

-- Pasi
>    [   41.601913] Please append a correct "root=" boot option;
here are the
>    available partitions:
>    [   41.702180] 0b00         1048575 sr0 driver: sr
>    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount root fs
on
>    unknown-block(2,0)
>    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
>    [   41.921708] Call Trace:
>    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
>    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
>    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
>    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
>    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
>    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
>    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
>    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
>    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> 

_______________________________________________
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

Pasi Kärkkäinen

2010-Apr-08 21:51 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

On Thu, Apr 08, 2010 at 10:43:57PM +0100, Ian Tobin
wrote:> Hey guys,
> 
> Sorry for the delay, been manic today.
> 
> I actually resolved this issue by messing around in the bios and enabling
ACPI HPET Table
> 
> Im not sure what that does but it booted straight away after that.
> 
> Maybe someone could shed some light on what it does.
>
HPET is High Precision Event Timer, afaik.
That shouldn''t affect kernel finding root disk/device..

Maybe the setting affected some ACPI IRQ routing stuff aswell.. 

-- Pasi
> Cheers
> 
> Ian
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Pasi Kärkkäinen
> Sent: 08 April 2010 19:54
> To: Konto usnetu
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] XEN 4.0 boot error
> 
> On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
> >    2010/4/8 Pasi Kärkkäinen <[1]pasik@iki.fi>
> > 
> >      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
> >      >    Hey all,
> >      >
> >      >    Just downloaded the new Xen 4.0 and ran
> >      >
> >      >    Make xen
> >      >    Make tools
> >      >    Make stubdom
> >      >
> >      >    Copied the new files from dist/install
> >      >    Im already running pv_ops 2.6.31.6 kernel.
> >      >
> >      >    When I boot i get
> >      >
> >      >    (XEN) Panic on CPU 0:
> >      >    (XEN) IO-APIC +  timer doesn''t work!
> >      >
> >      >    I have tried booting with noapic boot option but makes no
> >      difference.  The
> >      >    system worked fine on 3.4.2
> >      >
> >      >    CPU is AMD.
> >      >
> >      >    Any ideas?
> >      >
> > 
> >      Well.. can you post a full serial console log of the boot
process?
> > 
> >      See here for help:
[2]http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> >    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under
I
> >    paste a some error:
> > 
> >    41.017078]   Magic number: 6:876:244
> >    [   41.061177] md: Waiting for all devices to be available before
> >    autodetect
> >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
> >    [   41.211225] md: Autodetecting RAID arrays.
> >    [   41.260417] md: Scanned 0 and added 0 devices.
> >    [   41.313729] md: autorun ...
> >    [   41.347281] md: ... autorun DONE.
> >    [   41.387150] Root-NFS: No NFS server available, giving up.
> >    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
> >    [   41.524664] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
> 
> 
> So the disk was not detected, or did you pass wrong root= parameter? 
> 
> Please post the _full_ log.
> 
> -- Pasi
> 
> >    [   41.601913] Please append a correct "root=" boot
option; here are the
> >    available partitions:
> >    [   41.702180] 0b00         1048575 sr0 driver: sr
> >    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount
root fs on
> >    unknown-block(2,0)
> >    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
> >    [   41.921708] Call Trace:
> >    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
> >    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
> >    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
> >    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
> >    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
> >    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
> >    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
> >    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
> >    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> > 
> 
> 
> _______________________________________________
> 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

Ian Tobin

2010-Apr-08 21:54 UTC

head link

RE: [Xen-users] XEN 4.0 boot error

Agreed, it shouldn''t affect disk finding but going back to my original
issue it sorted my problem :)

Ian



-----Original Message-----
From: Pasi Kärkkäinen [mailto:pasik@iki.fi] 
Sent: 08 April 2010 22:52
To: Ian Tobin
Cc: Konto usnetu; xen-users@lists.xensource.com
Subject: Re: [Xen-users] XEN 4.0 boot error

On Thu, Apr 08, 2010 at 10:43:57PM +0100, Ian Tobin
wrote:> Hey guys,
> 
> Sorry for the delay, been manic today.
> 
> I actually resolved this issue by messing around in the bios and enabling
ACPI HPET Table
> 
> Im not sure what that does but it booted straight away after that.
> 
> Maybe someone could shed some light on what it does.
>
HPET is High Precision Event Timer, afaik.
That shouldn''t affect kernel finding root disk/device..

Maybe the setting affected some ACPI IRQ routing stuff aswell.. 

-- Pasi
> Cheers
> 
> Ian
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Pasi Kärkkäinen
> Sent: 08 April 2010 19:54
> To: Konto usnetu
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] XEN 4.0 boot error
> 
> On Thu, Apr 08, 2010 at 08:23:45PM +0200, Konto usnetu wrote:
> >    2010/4/8 Pasi Kärkkäinen <[1]pasik@iki.fi>
> > 
> >      On Wed, Apr 07, 2010 at 08:51:39PM +0100, Ian Tobin wrote:
> >      >    Hey all,
> >      >
> >      >    Just downloaded the new Xen 4.0 and ran
> >      >
> >      >    Make xen
> >      >    Make tools
> >      >    Make stubdom
> >      >
> >      >    Copied the new files from dist/install
> >      >    Im already running pv_ops 2.6.31.6 kernel.
> >      >
> >      >    When I boot i get
> >      >
> >      >    (XEN) Panic on CPU 0:
> >      >    (XEN) IO-APIC +  timer doesn''t work!
> >      >
> >      >    I have tried booting with noapic boot option but makes no
> >      difference.  The
> >      >    system worked fine on 3.4.2
> >      >
> >      >    CPU is AMD.
> >      >
> >      >    Any ideas?
> >      >
> > 
> >      Well.. can you post a full serial console log of the boot
process?
> > 
> >      See here for help:
[2]http://wiki.xensource.com/xenwiki/XenParavirtOps
> > 
> >    I have the same problem to boot xen 4.0 on debian lenny 5.0,  under
I
> >    paste a some error:
> > 
> >    41.017078]   Magic number: 6:876:244
> >    [   41.061177] md: Waiting for all devices to be available before
> >    autodetect
> >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
> >    [   41.211225] md: Autodetecting RAID arrays.
> >    [   41.260417] md: Scanned 0 and added 0 devices.
> >    [   41.313729] md: autorun ...
> >    [   41.347281] md: ... autorun DONE.
> >    [   41.387150] Root-NFS: No NFS server available, giving up.
> >    [   41.451921] VFS: Unable to mount root fs via NFS, trying floppy.
> >    [   41.524664] VFS: Cannot open root device "sda1" or
unknown-block(2,0)
> 
> 
> So the disk was not detected, or did you pass wrong root= parameter? 
> 
> Please post the _full_ log.
> 
> -- Pasi
> 
> >    [   41.601913] Please append a correct "root=" boot
option; here are the
> >    available partitions:
> >    [   41.702180] 0b00         1048575 sr0 driver: sr
> >    [   41.756691] Kernel panic - not syncing: VFS: Unable to mount
root fs on
> >    unknown-block(2,0)
> >    [   41.855912] Pid: 1, comm: swapper Not tainted 2.6.31.13 #2
> >    [   41.921708] Call Trace:
> >    [   41.951139]  [<c15e8386>] ? printk+0xf/0x11
> >    [   42.001366]  [<c15e82ca>] panic+0x39/0xe6
> >    [   42.049483]  [<c191ec2d>] mount_block_root+0x163/0x172
> >    [   42.111158]  [<c1002930>] ? hypercall_page+0x930/0x1005
> >    [   42.173838]  [<c191eca2>] mount_root+0x66/0x84
> >    [   42.227178]  [<c191ee05>] prepare_namespace+0x145/0x16c
> >    [   42.289857]  [<c191e34f>] kernel_init+0x16e/0x17d
> >    [   42.346326]  [<c191e1e1>] ? kernel_init+0x0/0x17d
> >    [   42.402764]  [<c1028d37>] kernel_thread_helper+0x7/0x10
> > 
> 
> 
> _______________________________________________
> 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

For@ll

2010-Apr-09 05:18 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

W dniu 08.04.2010 22:43, Pasi Kärkkäinen pisze:> On Thu, Apr 08, 2010 at 09:46:49PM +0200, For@ll wrote:
>   
>>      >      See here for help:
>>      [2][3]http://wiki.xensource.com/xenwiki/XenParavirtOps
>>      >
>>      >    I have the same problem to boot xen 4.0 on debian lenny
5.0,  under
>>      I
>>      >    paste a some error:
>>      >
>>      >    41.017078]   Magic number: 6:876:244
>>      >    [   41.061177] md: Waiting for all devices to be available
before
>>      >    autodetect
>>      >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
>>      >    [   41.211225] md: Autodetecting RAID arrays.
>>      >    [   41.260417] md: Scanned 0 and added 0 devices.
>>      >    [   41.313729] md: autorun ...
>>      >    [   41.347281] md: ... autorun DONE.
>>      >    [   41.387150] Root-NFS: No NFS server available, giving
up.
>>      >    [   41.451921] VFS: Unable to mount root fs via NFS,
trying floppy.
>>      >    [   41.524664] VFS: Cannot open root device
"sda1" or
>>      unknown-block(2,0)
>>
>>      So the disk was not detected, or did you pass wrong root=
parameter?
>>
>>      Please post the _full_ log.
>>
>>      -- Pasi
>>
>>
>>    Hi,
>>
>>    This is a longer version dmesg from console redirection ( ipmitool
connect
>>    to iRMC)
>>
>>     
> I don''t see any disks detected in the log..
>
> Can you please post a boot log on baremetal (non-xen), 
> or tell which disk controller has your root disk? what driver it uses on
baremetal linux?
>
> -- Pasi
>
>   
Hi,

My disk controler:

00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4
port SATA IDE Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
Controller (rev 05)
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2
port SATA IDE Controller (rev 05)
05:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET
PCI-Express Fusion-MPT SAS (rev 08)

  15.990184] Fusion MPT SAS Host driver 3.04.06
[   16.043300] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level,
low) -> IRQ 16
[   16.131780] mptbase: ioc0: Initiating bringup
[   16.186195] ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 21 (level,
low) -> IRQ 21
[   16.271581] ehci_hcd 0000:00:1a.0: EHCI Host Controller
[   16.335331] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned
bus number 1
[   16.428149] ehci_hcd 0000:00:1a.0: debug port 2
[   16.482831] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
[   16.569265] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[   16.657988] usb usb1: configuration #1 chosen from 1 choice
[   16.758032] hub 1-0:1.0: USB hub found
[   16.802529] hub 1-0:1.0: 2 ports detected
[   16.953604] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   17.034700] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[   17.293039] usb usb1: Product: EHCI Host Controller
[   17.432093] usb usb1: Manufacturer: Linux 2.6.26-2-686-bigmem ehci_hcd
[   17.510449] usb usb1: SerialNumber: 0000:00:1a.0
[   17.691888] usb 1-1: new high speed USB device using ehci_hcd and
address 2
[   17.902387] usb 1-1: configuration #1 chosen from 1 choice
[   17.970725] hub 1-1:1.0: USB hub found
[   18.017157] hub 1-1:1.0: 6 ports detected
[   18.094031] ioc0: LSISAS1064E B3: Capabilities={Initiator}
[   18.094031] mptbase: ioc0: PCI-MSI enabled
[   18.171795] usb 1-1: New USB device found, idVendor=8087, idProduct=0020
[   18.171797] usb 1-1: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[   27.514134] scsi0 : ioc0: LSISAS1064E B3, FwRev=011b0000h, Ports=1,
MaxQ=277, IRQ=215
[   27.628920] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2502ABYS-5
3B04 PQ: 0 ANSI: 5
[   27.744107] scsi 0:0:1:0: Direct-Access     ATA      WDC WD2502ABYS-5
3B04 PQ: 0 ANSI: 5
[   27.846823] scsi 0:1:0:0: Direct-Access     LSILOGIC Logical Volume  
3000 PQ: 0 ANSI: 2
[   27.943701] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level,
low) -> IRQ 20
[   28.231483] ehci_hcd 0000:00:1d.0: EHCI Host Controller
[   28.295499] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned
bus number 2
[   28.387771] ehci_hcd 0000:00:1d.0: debug port 2
[   28.441880] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
[   28.513935] Driver ''sd'' needs updating - please use
bus_type methods
[   28.591370] sd 0:1:0:0: [sda] 486326272 512-byte hardware sectors
(248999 MB)
[   28.668013] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00, driver
10 Dec 2004
[   28.668013] usb usb2: configuration #1 chosen from 1 choice
[   28.668013] hub 2-0:1.0: USB hub found
[   28.668013] hub 2-0:1.0: 2 ports detected
[   28.989376] sd 0:1:0:0: [sda] Write Protect is off
[   29.253072] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   29.253072] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[   29.253072] usb usb2: Product: EHCI Host Controller
[   29.253072] usb usb2: Manufacturer: Linux 2.6.26-2-686-bigmem ehci_hcd
[   29.253072] usb usb2: SerialNumber: 0000:00:1d.0
[   29.471527] usb 2-1: new high speed USB device using ehci_hcd and
address 2
[   29.727995] sd 0:1:0:0: [sda] Write cache: disabled, read cache:
enabled, doesn''t support DPO or FUA
[   29.868274] No dock devices found.
[   29.873610] sd 0:1:0:0: [sda] 486326272 512-byte hardware sectors
(248999 MB)
[   29.873867] sd 0:1:0:0: [sda] Write Protect is off
[   29.874327] sd 0:1:0:0: [sda] Write cache: disabled, read cache:
enabled, doesn''t support DPO or FUA
[   29.874327]  sda: sda1 sda2 sda3
[   30.204818] sd 0:1:0:0: [sda] Attached SCSI disk


Debian Lenny with kernel 2.6.26-2-bigmem

For@ll






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

For@ll

2010-Apr-09 05:47 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

W dniu 09.04.2010 07:18, For@ll pisze:> W dniu 08.04.2010 22:43, Pasi Kärkkäinen pisze:
>   
>> On Thu, Apr 08, 2010 at 09:46:49PM +0200, For@ll wrote:
>>   
>>     
>>>      >      See here for help:
>>>      [2][3]http://wiki.xensource.com/xenwiki/XenParavirtOps
>>>      >
>>>      >    I have the same problem to boot xen 4.0 on debian
lenny 5.0,  under
>>>      I
>>>      >    paste a some error:
>>>      >
>>>      >    41.017078]   Magic number: 6:876:244
>>>      >    [   41.061177] md: Waiting for all devices to be
available before
>>>      >    autodetect
>>>      >    [   41.142579] md: If you don''t use raid, use
raid=noautodetect
>>>      >    [   41.211225] md: Autodetecting RAID arrays.
>>>      >    [   41.260417] md: Scanned 0 and added 0 devices.
>>>      >    [   41.313729] md: autorun ...
>>>      >    [   41.347281] md: ... autorun DONE.
>>>      >    [   41.387150] Root-NFS: No NFS server available,
giving up.
>>>      >    [   41.451921] VFS: Unable to mount root fs via NFS,
trying floppy.
>>>      >    [   41.524664] VFS: Cannot open root device
"sda1" or
>>>      unknown-block(2,0)
>>>
>>>      So the disk was not detected, or did you pass wrong root=
parameter?
>>>
>>>      Please post the _full_ log.
>>>
>>>      -- Pasi
>>>
>>>
>>>    Hi,
>>>
>>>    This is a longer version dmesg from console redirection (
ipmitool connect
>>>    to iRMC)
>>>
>>>     
>>>       
>> I don''t see any disks detected in the log..
>>
>> Can you please post a boot log on baremetal (non-xen), 
>> or tell which disk controller has your root disk? what driver it uses
on baremetal linux?
>>
>> -- Pasi
>>
>>   
>>     
> Hi,
>
> My disk controler:
>
> 00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4
> port SATA IDE Controller (rev 05)
> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
> Controller (rev 05)
> 00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2
> port SATA IDE Controller (rev 05)
> 05:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET
> PCI-Express Fusion-MPT SAS (rev 08)
>
>   15.990184] Fusion MPT SAS Host driver 3.04.06
> [   16.043300] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level,
> low) -> IRQ 16
> [   16.131780] mptbase: ioc0: Initiating bringup
> [   16.186195] ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 21 (level,
> low) -> IRQ 21
> [   16.271581] ehci_hcd 0000:00:1a.0: EHCI Host Controller
> [   16.335331] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned
> bus number 1
> [   16.428149] ehci_hcd 0000:00:1a.0: debug port 2
> [   16.482831] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
> [   16.569265] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00, driver
> 10 Dec 2004
> [   16.657988] usb usb1: configuration #1 chosen from 1 choice
> [   16.758032] hub 1-0:1.0: USB hub found
> [   16.802529] hub 1-0:1.0: 2 ports detected
> [   16.953604] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
> [   17.034700] usb usb1: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [   17.293039] usb usb1: Product: EHCI Host Controller
> [   17.432093] usb usb1: Manufacturer: Linux 2.6.26-2-686-bigmem ehci_hcd
> [   17.510449] usb usb1: SerialNumber: 0000:00:1a.0
> [   17.691888] usb 1-1: new high speed USB device using ehci_hcd and
> address 2
> [   17.902387] usb 1-1: configuration #1 chosen from 1 choice
> [   17.970725] hub 1-1:1.0: USB hub found
> [   18.017157] hub 1-1:1.0: 6 ports detected
> [   18.094031] ioc0: LSISAS1064E B3: Capabilities={Initiator}
> [   18.094031] mptbase: ioc0: PCI-MSI enabled
> [   18.171795] usb 1-1: New USB device found, idVendor=8087, idProduct=0020
> [   18.171797] usb 1-1: New USB device strings: Mfr=0, Product=0,
> SerialNumber=0
> [   27.514134] scsi0 : ioc0: LSISAS1064E B3, FwRev=011b0000h, Ports=1,
> MaxQ=277, IRQ=215
> [   27.628920] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2502ABYS-5
> 3B04 PQ: 0 ANSI: 5
> [   27.744107] scsi 0:0:1:0: Direct-Access     ATA      WDC WD2502ABYS-5
> 3B04 PQ: 0 ANSI: 5
> [   27.846823] scsi 0:1:0:0: Direct-Access     LSILOGIC Logical Volume  
> 3000 PQ: 0 ANSI: 2
> [   27.943701] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level,
> low) -> IRQ 20
> [   28.231483] ehci_hcd 0000:00:1d.0: EHCI Host Controller
> [   28.295499] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned
> bus number 2
> [   28.387771] ehci_hcd 0000:00:1d.0: debug port 2
> [   28.441880] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
> [   28.513935] Driver ''sd'' needs updating - please use
bus_type methods
> [   28.591370] sd 0:1:0:0: [sda] 486326272 512-byte hardware sectors
> (248999 MB)
> [   28.668013] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00, driver
> 10 Dec 2004
> [   28.668013] usb usb2: configuration #1 chosen from 1 choice
> [   28.668013] hub 2-0:1.0: USB hub found
> [   28.668013] hub 2-0:1.0: 2 ports detected
> [   28.989376] sd 0:1:0:0: [sda] Write Protect is off
> [   29.253072] usb usb2: New USB device found, idVendor=1d6b,
idProduct=0002
> [   29.253072] usb usb2: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [   29.253072] usb usb2: Product: EHCI Host Controller
> [   29.253072] usb usb2: Manufacturer: Linux 2.6.26-2-686-bigmem ehci_hcd
> [   29.253072] usb usb2: SerialNumber: 0000:00:1d.0
> [   29.471527] usb 2-1: new high speed USB device using ehci_hcd and
> address 2
> [   29.727995] sd 0:1:0:0: [sda] Write cache: disabled, read cache:
> enabled, doesn''t support DPO or FUA
> [   29.868274] No dock devices found.
> [   29.873610] sd 0:1:0:0: [sda] 486326272 512-byte hardware sectors
> (248999 MB)
> [   29.873867] sd 0:1:0:0: [sda] Write Protect is off
> [   29.874327] sd 0:1:0:0: [sda] Write cache: disabled, read cache:
> enabled, doesn''t support DPO or FUA
> [   29.874327]  sda: sda1 sda2 sda3
> [   30.204818] sd 0:1:0:0: [sda] Attached SCSI disk
>
>
> Debian Lenny with kernel 2.6.26-2-bigmem
>
> For@ll
>
>
>
>
>
>   Hi,

It''s works:) I''m missing add controler in my config kernel.

Thx for help.



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

Pasi Kärkkäinen

2010-Apr-09 07:30 UTC

head link

Re: [Xen-users] XEN 4.0 boot error

On Fri, Apr 09, 2010 at 07:18:32AM +0200, For@ll wrote:> W dniu 08.04.2010 22:43, Pasi Kärkkäinen pisze:
> > On Thu, Apr 08, 2010 at 09:46:49PM +0200, For@ll wrote:
> >   
> >>      >      See here for help:
> >>      [2][3]http://wiki.xensource.com/xenwiki/XenParavirtOps
> >>      >
> >>      >    I have the same problem to boot xen 4.0 on debian
lenny 5.0,  under
> >>      I
> >>      >    paste a some error:
> >>      >
> >>      >    41.017078]   Magic number: 6:876:244
> >>      >    [   41.061177] md: Waiting for all devices to be
available before
> >>      >    autodetect
> >>      >    [   41.142579] md: If you don''t use raid,
use raid=noautodetect
> >>      >    [   41.211225] md: Autodetecting RAID arrays.
> >>      >    [   41.260417] md: Scanned 0 and added 0 devices.
> >>      >    [   41.313729] md: autorun ...
> >>      >    [   41.347281] md: ... autorun DONE.
> >>      >    [   41.387150] Root-NFS: No NFS server available,
giving up.
> >>      >    [   41.451921] VFS: Unable to mount root fs via NFS,
trying floppy.
> >>      >    [   41.524664] VFS: Cannot open root device
"sda1" or
> >>      unknown-block(2,0)
> >>
> >>      So the disk was not detected, or did you pass wrong root=
parameter?
> >>
> >>      Please post the _full_ log.
> >>
> >>      -- Pasi
> >>
> >>
> >>    Hi,
> >>
> >>    This is a longer version dmesg from console redirection (
ipmitool connect
> >>    to iRMC)
> >>
> >>     
> > I don''t see any disks detected in the log..
> >
> > Can you please post a boot log on baremetal (non-xen), 
> > or tell which disk controller has your root disk? what driver it uses
on baremetal linux?
> >
> > -- Pasi
> >
> >   
> 
> Hi,
> 
> My disk controler:
> 
> 00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4
> port SATA IDE Controller (rev 05)
> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus
> Controller (rev 05)
> 00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2
> port SATA IDE Controller (rev 05)
> 05:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064ET
> PCI-Express Fusion-MPT SAS (rev 08)
> 
>   15.990184] Fusion MPT SAS Host driver 3.04.06
> [   16.043300] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level,
> low) -> IRQ 16
> [   16.131780] mptbase: ioc0: Initiating bringup
> [   16.186195] ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 21 (level,
> low) -> IRQ 21
> [   16.271581] ehci_hcd 0000:00:1a.0: EHCI Host Controller
> [   16.335331] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned
> bus number 1
> [   16.428149] ehci_hcd 0000:00:1a.0: debug port 2
> [   16.482831] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xce003000
> [   16.569265] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00, driver
> 10 Dec 2004
> [   16.657988] usb usb1: configuration #1 chosen from 1 choice
> [   16.758032] hub 1-0:1.0: USB hub found
> [   16.802529] hub 1-0:1.0: 2 ports detected
> [   16.953604] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
> [   17.034700] usb usb1: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [   17.293039] usb usb1: Product: EHCI Host Controller
> [   17.432093] usb usb1: Manufacturer: Linux 2.6.26-2-686-bigmem ehci_hcd
> [   17.510449] usb usb1: SerialNumber: 0000:00:1a.0
> [   17.691888] usb 1-1: new high speed USB device using ehci_hcd and
> address 2
> [   17.902387] usb 1-1: configuration #1 chosen from 1 choice
> [   17.970725] hub 1-1:1.0: USB hub found
> [   18.017157] hub 1-1:1.0: 6 ports detected
> [   18.094031] ioc0: LSISAS1064E B3: Capabilities={Initiator}
> [   18.094031] mptbase: ioc0: PCI-MSI enabled
> [   18.171795] usb 1-1: New USB device found, idVendor=8087, idProduct=0020
> [   18.171797] usb 1-1: New USB device strings: Mfr=0, Product=0,
> SerialNumber=0
> [   27.514134] scsi0 : ioc0: LSISAS1064E B3, FwRev=011b0000h, Ports=1,
> MaxQ=277, IRQ=215
> [   27.628920] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2502ABYS-5
> 3B04 PQ: 0 ANSI: 5
> [   27.744107] scsi 0:0:1:0: Direct-Access     ATA      WDC WD2502ABYS-5
> 3B04 PQ: 0 ANSI: 5
> [   27.846823] scsi 0:1:0:0: Direct-Access     LSILOGIC Logical Volume  
> 3000 PQ: 0 ANSI: 2
> [   27.943701] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level,
> low) -> IRQ 20
> [   28.231483] ehci_hcd 0000:00:1d.0: EHCI Host Controller
> [   28.295499] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned
> bus number 2
> [   28.387771] ehci_hcd 0000:00:1d.0: debug port 2
> [   28.441880] ehci_hcd 0000:00:1d.0: irq 20, io mem 0xce004000
> [   28.513935] Driver ''sd'' needs updating - please use
bus_type methods
> [   28.591370] sd 0:1:0:0: [sda] 486326272 512-byte hardware sectors
> (248999 MB)
> [   28.668013] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00, driver
> 10 Dec 2004
> [   28.668013] usb usb2: configuration #1 chosen from 1 choice
> [   28.668013] hub 2-0:1.0: USB hub found
> [   28.668013] hub 2-0:1.0: 2 ports detected
> [   28.989376] sd 0:1:0:0: [sda] Write Protect is off
> [   29.253072] usb usb2: New USB device found, idVendor=1d6b,
idProduct=0002
> [   29.253072] usb usb2: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [   29.253072] usb usb2: Product: EHCI Host Controller
> [   29.253072] usb usb2: Manufacturer: Linux 2.6.26-2-686-bigmem ehci_hcd
> [   29.253072] usb usb2: SerialNumber: 0000:00:1d.0
> [   29.471527] usb 2-1: new high speed USB device using ehci_hcd and
> address 2
> [   29.727995] sd 0:1:0:0: [sda] Write cache: disabled, read cache:
> enabled, doesn''t support DPO or FUA
> [   29.868274] No dock devices found.
> [   29.873610] sd 0:1:0:0: [sda] 486326272 512-byte hardware sectors
> (248999 MB)
> [   29.873867] sd 0:1:0:0: [sda] Write Protect is off
> [   29.874327] sd 0:1:0:0: [sda] Write cache: disabled, read cache:
> enabled, doesn''t support DPO or FUA
> [   29.874327]  sda: sda1 sda2 sda3
> [   30.204818] sd 0:1:0:0: [sda] Attached SCSI disk
> 
> 
> Debian Lenny with kernel 2.6.26-2-bigmem
> 
Hmm.. and did you use the Lenny 2.6.26-2-xen kernel with Xen 4.0.0 ? 
or pvops dom0 kernel? which version?

-- Pasi


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

Apparently Analagous Threads

Search for more reasonably related threads

Xen users - Apr 2010 - XEN 4.0 boot error

[Xen-users] XEN 4.0 boot error

[Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

RE: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

RE: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Re: [Xen-users] XEN 4.0 boot error

Apparently Analagous Threads