WARNING - OLD ARCHIVES

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

xen-bugs

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-bugs] [Bug 428] New: Diagnostic output produced spontaneously on xm

from [bugzilla-daemon] [Permanent Link][Original]
To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 428] New: Diagnostic output produced spontaneously on xm dmesg
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 01 Dec 2005 17:55:08 +0000
Delivery-date: Thu, 01 Dec 2005 17:55:12 +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 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=428

           Summary: Diagnostic output produced spontaneously on xm dmesg
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: trivial
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dbarrera@xxxxxxxxxx
                CC: hohnbaum@xxxxxxxxxx,pl@xxxxxxxxxx


Diagnostic output is being displayed on 'xm dmesg' even though there has been no
intervention on the serial console to trigger it. I've seen it several times on
IBM HS20 Blades 8843s, x86_64. 

> >
> > The interesting thing is that no one is doing anything to the serial 
> > input! This is happening 'spontaneously' in my setup.  Sounds like a 
> > bug?
> 
> Yes, if that really is the case. It looks impossible though. That 
> diagnostic output is only triggered from handle_keypress(), which is 
> only called from serial_rx(), which is only called from the low-level 
> serial driver.
> 
Well, it is the case. There hasn't been anything done on the serial
console to cause it; it is happening 'spontaneously'.

[root@leaf10 ~]# xm dmesg
 __  __            _____  ___         _                _
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ '_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (root@) (gcc version 3.4.4 20050721 (Red Hat
3.4.4-2)) Thu Dec  1 09:52:50 CST 2005
 Latest ChangeSet: Thu Dec  1 08:22:22 2005 +0100 8151:f5b119533cc8

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 000000000009d400 (usable)
(XEN)  000000000009d400 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000d7fbe640 (usable)
(XEN)  00000000d7fbe640 - 00000000d7fd0000 (ACPI data)
(XEN)  00000000d7fd0000 - 00000000d8000000 (reserved)
(XEN)  00000000fec00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000228000000 (usable)
(XEN) System RAM: 8191MB (8387948kB)
(XEN) Xen heap: 10MB (10360kB)
(XEN) PAE enabled, limit: 16 GB
(XEN) found SMP MP-table at 0009d540
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 IBM                                   ) @
0x000fdfc0
(XEN) ACPI: RSDT (v001 IBM    SERBLADE 0x00001000 IBM  0x45444f43) @
0xd7fcff80
(XEN) ACPI: FADT (v002 IBM    SERBLADE 0x00001000 IBM  0x45444f43) @
0xd7fcfec0
(XEN) ACPI: MADT (v001 IBM    SERBLADE 0x00001000 IBM  0x45444f43) @
0xd7fcfe00
(XEN) ACPI: MCFG (v001 IBM    SERBLADE 0x00001000 IBM  0x45444f43) @
0xd7fcfdc0
(XEN) ACPI: DSDT (v001 IBM    SERBLADE 0x00001000 INTL 0x02002025) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled)
(XEN) Processor #6 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
(XEN) Processor #7 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x0d] address[0xfec10000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 13, version 32, address 0xfec10000, GSI 24-47
(XEN) ACPI: IOAPIC (id[0x0c] address[0xfec81000] gsi_base[48])
(XEN) IOAPIC[2]: apic_id 12, version 32, address 0xfec81000, GSI 48-71
(XEN) ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72])
(XEN) IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI 72-95
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ11 used by override.
(XEN) Enabling APIC mode:  Flat.  Using 4 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 3200.228 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 01
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 0
(XEN) CPU1: Intel(R) Xeon(TM) CPU 3.20GHz stepping 01
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU2: Intel(R) Xeon(TM) CPU 3.20GHz stepping 01
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 1024K
(XEN) CPU: Physical Processor ID: 3
(XEN) CPU3: Intel(R) Xeon(TM) CPU 3.20GHz stepping 01
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 4 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 4 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=yes,LOADER=generic'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000005000000->0000000006000000 (251904 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c05f5184
(XEN)  Init. ramdisk: c05f6000->c083da00
(XEN)  Phys-Mach map: c083e000->c0938000
(XEN)  Start info:    c0938000->c0939000
(XEN)  Page tables:   c0939000->c0944000
(XEN)  Boot stack:    c0944000->c0945000
(XEN)  TOTAL:         c0000000->c0c00000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Initrd len 0x247a00, start at 0xc05f6000
(XEN) Scrubbing Free RAM: .Scheduler: Simple EDF Scheduler (sedf)
(XEN) NOW=0x00000000022093BB
(XEN) CPU[00] now=35695933
(XEN) RUNQ rq ff1e5c00   n: ff1e5c00, p: ff1e5c00
(XEN)
(XEN) WAITQ rq ff1e5c08   n: ff1e5c08, p: ff1e5c08
(XEN)
(XEN) EXTRAQ (penalty) rq ff1e5c10   n: ff1e5c10, p: ff1e5c10
(XEN)
(XEN) EXTRAQ (utilization) rq ff1e5c18   n: ff1e5c18, p: ff1e5c18
(XEN)
(XEN) not on Q
(XEN)   0: 0.0 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[01] now=35741039
(XEN) RUNQ rq ff1e4980   n: ff1e4980, p: ff1e4980
(XEN)
(XEN) WAITQ rq ff1e4988   n: ff1e4988, p: ff1e4988
(XEN)
(XEN) EXTRAQ (penalty) rq ff1e4990   n: ff1e4990, p: ff1e4990
(XEN)
(XEN) EXTRAQ (utilization) rq ff1e4998   n: ff1e4998, p: ff1e4998
(XEN)
(XEN) not on Q
(XEN)   0: 0.1 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[02] now=35783361
(XEN) RUNQ rq ffbfa980   n: ffbfa980, p: ffbfa980
(XEN)
(XEN) WAITQ rq ffbfa988   n: ffbfa988, p: ffbfa988
(XEN)
(XEN) EXTRAQ (penalty) rq ffbfa990   n: ffbfa990, p: ffbfa990
(XEN)
(XEN) EXTRAQ (utilization) rq ffbfa998   n: ffbfa998, p: ffbfa998
(XEN)
(XEN) not on Q
(XEN)   0: 0.2 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[03] now=35825616
(XEN) RUNQ rq ff1ee980   n: ff1ee980, p: ff1ee980
(XEN)
(XEN) WAITQ rq ff1ee988   n: ff1ee988, p: ff1ee988
(XEN)
(XEN) EXTRAQ (penalty) rq ff1ee990   n: ff1ee990, p: ff1ee990
(XEN)
(XEN) EXTRAQ (utilization) rq ff1ee998   n: ff1ee998, p: ff1ee998
(XEN)
(XEN) not on Q
(XEN)   0: 0.3 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) Scheduler: Simple EDF Scheduler (sedf)
(XEN) NOW=0x000000000335A280
(XEN) CPU[00] now=53860610
(XEN) RUNQ rq ff1e5c00   n: ff1e5c00, p: ff1e5c00
(XEN)
(XEN) WAITQ rq ff1e5c08   n: ff1e5c08, p: ff1e5c08
(XEN)
(XEN) EXTRAQ (penalty) rq ff1e5c10   n: ff1e5c10, p: ff1e5c10
(XEN)
(XEN) EXTRAQ (utilization) rq ff1e5c18   n: ff1e5c18, p: ff1e5c18
(XEN)
(XEN) not on Q
(XEN)   0: 0.0 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[01] now=53908530
(XEN) RUNQ rq ff1e4980   n: ff1e4980, p: ff1e4980
(XEN)
(XEN) WAITQ rq ff1e4988   n: ff1e4988, p: ff1e4988
(XEN)
(XEN) EXTRAQ (penalty) rq ff1e4990   n: ff1e4990, p: ff1e4990
(XEN)
(XEN) EXTRAQ (utilization) rq ff1e4998   n: ff1e4998, p: ff1e4998
(XEN)
(XEN) not on Q
(XEN)   0: 0.1 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[02] now=53951275
(XEN) RUNQ rq ffbfa980   n: ffbfa980, p: ffbfa980
(XEN)
(XEN) WAITQ rq ffbfa988   n: ffbfa988, p: ffbfa988
(XEN)
(XEN) EXTRAQ (penalty) rq ffbfa990   n: ffbfa990, p: ffbfa990
(XEN)
(XEN) EXTRAQ (utilization) rq ffbfa998   n: ffbfa998, p: ffbfa998
(XEN)
(XEN) not on Q
(XEN)   0: 0.2 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[03] now=53993685
(XEN) RUNQ rq ff1ee980   n: ff1ee980, p: ff1ee980
(XEN)
(XEN) WAITQ rq ff1ee988   n: ff1ee988, p: ff1ee988
(XEN)
(XEN) EXTRAQ (penalty) rq ff1ee990   n: ff1ee990, p: ff1ee990
(XEN)
(XEN) EXTRAQ (utilization) rq ff1ee998   n: ff1ee998, p: ff1ee998
(XEN)
(XEN) not on Q
(XEN)   0: 0.3 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) .Scheduler: Simple EDF Scheduler (sedf)
(XEN) NOW=0x000000000492C724
(XEN) CPU[00] now=76735407
(XEN) RUNQ rq ff1e5c00   n: ff1e5c00, p: ff1e5c00
(XEN)
(XEN) WAITQ rq ff1e5c08   n: ff1e5c08, p: ff1e5c08
(XEN)
(XEN) EXTRAQ (penalty) rq ff1e5c10   n: ff1e5c10, p: ff1e5c10
(XEN)
(XEN) EXTRAQ (utilization) rq ff1e5c18   n: ff1e5c18, p: ff1e5c18
(XEN)
(XEN) not on Q
(XEN)   0: 0.0 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[01] now=76778635
(XEN) RUNQ rq ff1e4980   n: ff1e4980, p: ff1e4980
(XEN)
(XEN) WAITQ rq ff1e4988   n: ff1e4988, p: ff1e4988
(XEN)
(XEN) EXTRAQ (penalty) rq ff1e4990   n: ff1e4990, p: ff1e4990
(XEN)
(XEN) EXTRAQ (utilization) rq ff1e4998   n: ff1e4998, p: ff1e4998
(XEN)
(XEN) not on Q
(XEN)   0: 0.1 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[02] now=76820737
(XEN) RUNQ rq ffbfa980   n: ffbfa980, p: ffbfa980
(XEN)
(XEN) WAITQ rq ffbfa988   n: ffbfa988, p: ffbfa988
(XEN)
(XEN) EXTRAQ (penalty) rq ffbfa990   n: ffbfa990, p: ffbfa990
(XEN)
(XEN) EXTRAQ (utilization) rq ffbfa998   n: ffbfa998, p: ffbfa998
(XEN)
(XEN) not on Q
(XEN)   0: 0.2 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN) CPU[03] now=76862654
(XEN) RUNQ rq ff1ee980   n: ff1ee980, p: ff1ee980
(XEN)
(XEN) WAITQ rq ff1ee988   n: ff1ee988, p: ff1ee988
(XEN)
(XEN) EXTRAQ (penalty) rq ff1ee990   n: ff1ee990, p: ff1ee990
(XEN)
(XEN) EXTRAQ (utilization) rq ff1ee998   n: ff1ee998, p: ff1ee998
(XEN)
(XEN) not on Q
(XEN)   0: 0.3 has=F p=20000000 sl=15000000 ddl=0 w=0 c=0 sc=0 xtr
(yes)=0 ew=0
(XEN)
.......................................................................................done.
(XEN) Xen trace buffers: disabled
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
(XEN) microcode: CPU0 not 'upgrading' to earlier revision 0x9
(current=0x12)
(XEN) microcode: CPU1 not 'upgrading' to earlier revision 0x9
(current=0x12)
(XEN) microcode: CPU2 not 'upgrading' to earlier revision 0x9
(current=0x12)
(XEN) microcode: CPU3 not 'upgrading' to earlier revision 0x9
(current=0x12)
(XEN) microcode: No suitable data for CPU2
(XEN) microcode: No suitable data for CPU1
(XEN) microcode: No suitable data for CPU3
(XEN) microcode: No suitable data for CPU0

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 428] New: Diagnostic output produced spontaneously on xm dmesg, bugzilla-daemon <=
Previous by Date:  [Xen-bugs] [Bug 85] xenU fail to create with shadow mode enabling, bugzilla-daemon
Next by Date:  [Xen-bugs] [Bug 399] xm-test reboots machine, bugzilla-daemon
Previous by Thread:  [Xen-bugs] [Bug 85] xenU fail to create with shadow mode enabling, bugzilla-daemon
Next by Thread:  [Xen-bugs] [Bug 399] xm-test reboots machine, bugzilla-daemon
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy