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


[Xen-bugs] [Bug 89] nVidea onboard SATA Controller causes booting Proble

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 89] nVidea onboard SATA Controller causes booting Problems on dom0
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 20 Oct 2005 15:18:24 +0000
Delivery-date: Thu, 20 Oct 2005 15:18:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From ultra@xxxxxxxxxxx  2005-10-20 15:18 -------
I get a different error with sata-nv, using LVM and initrd

 __  __            _____  ___         _                _
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ '_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (root@xxxxxxxxxxxxxxx) (gcc version 4.0.0 20050519 (Red
Hat 4.0.0-8)) Thu Oct 20 10:47:58 EDT 2005
 Latest ChangeSet: Wed Oct 19 06:53:00 2005 +0100 7426:7c951e3eb5ab

(XEN) Console output is synchronous.
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009f800 (usable)
(XEN)  000000000009f800 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000003fff0000 (usable)
(XEN)  000000003fff0000 - 000000003fff3000 (ACPI NVS)
(XEN)  000000003fff3000 - 0000000040000000 (ACPI data)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fef00000 (reserved)
(XEN)  00000000fefffc00 - 00000000ff000000 (reserved)
(XEN)  00000000ffff0000 - 0000000100000000 (reserved)
(XEN) System RAM: 1023MB (1048124kB)
(XEN) Xen heap: 14MB (14680kB)
(XEN) found SMP MP-table at 000f3850
(XEN) DMI 2.2 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 Nvidia                                ) @ 
(XEN) ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
(XEN) ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
(XEN) ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @
(XEN) ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:12 APIC version 16
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) ACPI: IRQ14 used by override.
(XEN) ACPI: IRQ15 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 2009.192 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU0: AMD Flush Filter enabled
(XEN) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
(XEN) CPU: L2 Cache: 512K (64 bytes/line)
(XEN) CPU0: AMD Athlon(tm) 64 Processor 3000+ stepping 00
(XEN) Total of 1 processors activated.
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ...  failed.
(XEN) ...trying to set up timer as Virtual Wire IRQ... failed.
(XEN) ...trying to set up timer as ExtINT IRQ...spurious 8259A interrupt: IRQ7.
(XEN)  works.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 1 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) Xen-ELF header found:
(XEN)  Dom0 alloc.:   0000000003000000->0000000004000000 (126976 pages to be
(XEN)  Loaded kernel: ffffffff80100000->ffffffff8064d086
(XEN)  Init. ramdisk: ffffffff8064e000->ffffffff809d1400
(XEN)  Phys-Mach map: ffffffff809d2000->ffffffff80ad2000
(XEN)  Start info:    ffffffff80ad2000->ffffffff80ad3000
(XEN)  Page tables:   ffffffff80ad3000->ffffffff80adc000
(XEN)  Boot stack:    ffffffff80adc000->ffffffff80add000
(XEN)  TOTAL:         ffffffff80000000->ffffffff80c00000
(XEN)  ENTRY ADDRESS: ffffffff80100000
(XEN) Initrd len 0x383400, start at 0xffffffff8064e000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
(XEN) (file=irq.c, line=224) Cannot bind IRQ 4 to guest. In use by 'ns16550'.
(XEN) (file=irq.c, line=224) Cannot bind IRQ 2 to guest. In use by 'cascade'.
(XEN) (file=irq.c, line=224) Cannot bind IRQ 4 to guest. In use by 'ns16550'.
(XEN) (file=irq.c, line=224) Cannot bind IRQ 2 to guest. In use by 'cascade'.
Red Hat nash version 4.2.15 starting
  Reading all physical volumes.  This may take a while...
  No volume groups found
  Unable to find volume group "athlon64"
ERROR: /bin/lvm exited abnormally with value 5 ! (pid 876)
mount: error 6 mounting ext3
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list