Console problem

Console problem

[Andre.Messerschmidt]

Hi.

I wrote my own console driver based on the ARC console driver (to keep it
simple). When I am booting my modified 2.4.3 kernel, I get an "unable to
open initial console" error (code: No such device). I have tracked it down
to the point where the kernel searches for a valid TTY device with major and
minor ID 4:64. 
All devices that are present at this time are: 3:0-3:256 2:0-2:256 5:0 5:1.
Obviously there is no 4:64 device.

I mount root via NFS and my devices are as follows:.
crw-------    1 root     tty        5,   1 Mär  4 17:49 console
crw-------    1 root     tty        4,   0 Mär  4 17:49 tty0
crw-rw-rw-    1 root     tty        4,   1 Mär  4 17:49 tty1
...
crw-r--r--    1 root     root       4,  64 Mär  5 08:26 ttyS0
crw-r--r--    1 root     root       4,  65 Mär  5 08:26 ttyS1

I also add a "console=ttyS0,9600" to the kernel command line. 
Am I missing anything? Why is there no device 4:64? (My console driver
identifies itself as 4,64)   
Any help would be appreciated.


best regards
--
Andre Messerschmidt

Application Engineer
Infineon Technologies AG

Re: Console problem

[James Simmons]

> I wrote my own console driver based on the ARC console driver (to keep it
> simple). When I am booting my modified 2.4.3 kernel, I get an "unable to
> open initial console" error (code: No such device). I have tracked it down
> to the point where the kernel searches for a valid TTY device with major and
> minor ID 4:64. 
> All devices that are present at this time are: 3:0-3:256 2:0-2:256 5:0 5:1.
> Obviously there is no 4:64 device.

Did you call register_console ?

Re: console problem

[Mark Chambers]

Hi Arun,

I've got a question about your situation:  If you have no terminal attached
to your system, how do you know what Linux is doing?  Or to put it
conversely, how do you know that it's failing?  Are you sure the problem is
really related to removing the cable or do you change something else to run
without a terminal?

I have seen my code hang in the very same place - but it did it whether a
cable was attached or not, because the UART was not set up correctly.

Mark Chambers


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: console problem

[Arun Dharankar]

Hi Mark,

When I use the BDI2000 to find out what the board is doing, I can
see the place where the PPCBoot and Linux will hang.  As for debugging
the problem, I mentioned my conclusion in reply to another post.

Thanks for your followup!

Best regards,
-Arun.

On Tuesday 23 July 2002 03:13 pm, Mark Chambers wrote:
> Hi Arun,
>
> I've got a question about your situation:  If you have no terminal attached
> to your system, how do you know what Linux is doing?  Or to put it
> conversely, how do you know that it's failing?  Are you sure the problem is
> really related to removing the cable or do you change something else to run
> without a terminal?
>
> I have seen my code hang in the very same place - but it did it whether a
> cable was attached or not, because the UART was not set up correctly.
>
> Mark Chambers


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Console problem

[Monica Correa]

[-- Attachment #1: Type: text/plain, Size: 14685 bytes --]

  Hi, 
 
   I'm having some problems to boot the Linux kernel 2.6.11.11 on a HP 
Superdome with 16 Itanium 2 processors and EFI version 1.1.  After the 
"Uncompressing Linux ... done" message appears, there is no more output 
for the console. The boot doesn't stop (I'm sending part of the 
/var/log/messages file attached to this email), but no more messages are 
printed in the console and the "login" prompt is not shown. It seems to 
be a console problem, but I'm not sure about how to fix it... When I 
boot kernel  2.4 without the "console=" option, I have a similar 
problem, no kernel output, but the "login" prompt is shown. For kernel 
2.4 the problem is solved when I specify the "console=ttyS0" argument in 
the boot process. However, the same doesn't happen for kernel 2.6. Even 
if I specify "console=ttyS0", I have no kernel output and no "login" 
prompt. I also tried "console=hcdp" but it also doesn't work. Has anyone 
experienced a similar problem which could help me solving it? 
 
  Any suggestion is welcome! 
 
  Thanks in advance, 
  Monica

Jun 10 11:47:56 localhost syslogd 1.4.1#17: restart.
Jun 10 11:47:56 localhost kernel: klogd 1.4.1#17, log source = 
/proc/kmsg started.
Jun 10 11:47:56 localhost kernel: Cannot find map file.
Jun 10 11:47:56 localhost kernel: No module symbols loaded - kernel 
modules not enabled.
Jun 10 11:47:56 localhost kernel: Linux version 2.6.11.11 
(root@brpoaolympiaa1) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #13 SMP 
Fri Jun 10 11:44:06 BRT 2005
Jun 10 11:47:56 localhost kernel: EFI v1.10 by HP: 
SALsystab=0x720ff7d4408 ACPI 2.0=0x720ffba0000 HCDP=0x720ffbc8508 
SMBIOS=0x7fffe000
Jun 10 11:47:56 localhost kernel: booting generic kernel on platform hpzx1
Jun 10 11:47:56 localhost kernel: PCDP: v3 at 0x720ffbc8508
Jun 10 11:47:56 localhost kernel: Number of logical nodes in system = 4
Jun 10 11:47:56 localhost kernel: Number of memory chunks in system = 5
Jun 10 11:47:56 localhost kernel: efi.trim_top: ignoring 12288KB of 
memory at 0x72000000000 due to granule hole at 0x720fe000000
Jun 10 11:47:56 localhost kernel: warning: skipping physical page 0
Jun 10 11:47:56 localhost last message repeated 2 times
Jun 10 11:47:56 localhost kernel: SAL 3.2: HP Orca/IPF version 3.54
Jun 10 11:47:56 localhost kernel: SAL Platform features: None
Jun 10 11:47:56 localhost kernel: SAL: AP wakeup using external 
interrupt vector 0xff
Jun 10 11:47:56 localhost kernel: ACPI: Local APIC address c0000000fee00000
Jun 10 11:47:56 localhost kernel: GSI 16 (level, low) -> CPU 0 (0x0001) 
vector 48
Jun 10 11:47:56 localhost kernel: 10 CPUs available, 12 CPUs total
Jun 10 11:47:56 localhost kernel: MCA related initialization done
Jun 10 11:47:56 localhost kernel: warning: skipping physical page 0
Jun 10 11:47:56 localhost kernel: Virtual mem_map starts at 
0xa0007ff98b20c000
Jun 10 11:47:56 localhost kernel: Built 4 zonelists
Jun 10 11:47:56 localhost kernel: Kernel command line: 
BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz2.6.11.11.gz root=/dev/sda2 ro 
console=hcdp
Jun 10 11:47:56 localhost kernel: PID hash table entries: 4096 (order: 
12, 131072 bytes)
Jun 10 11:47:56 localhost kernel: Console: colour dummy device 80x25
Jun 10 11:47:56 localhost kernel: Memory: 12458688k/12507760k available 
(4961k code, 56480k reserved, 2482k data, 352k init)
Jun 10 11:47:56 localhost kernel: McKinley Errata 9 workaround not 
needed; disabling it
Jun 10 11:47:56 localhost kernel: Dentry cache hash table entries: 
2097152 (order: 10, 16777216 bytes)
Jun 10 11:47:56 localhost kernel: Inode-cache hash table entries: 
1048576 (order: 9, 8388608 bytes)
Jun 10 11:47:56 localhost kernel: Mount-cache hash table entries: 1024 
(order: 0, 16384 bytes)
Jun 10 11:47:56 localhost kernel: Boot processor id 0x0/0x1
Jun 10 11:47:56 localhost kernel: task migration cache decay timeout: 10 
msecs.
Jun 10 11:47:56 localhost kernel: CPU 1: synchronized ITC with CPU 0 
(last diff 6 cycles, maxerr 442 cycles)
Jun 10 11:47:56 localhost kernel: CPU 2: synchronized ITC with CPU 0 
(last diff -2 cycles, maxerr 2281 cycles)
Jun 10 11:47:56 localhost kernel: CPU 3: synchronized ITC with CPU 0 
(last diff -2 cycles, maxerr 2276 cycles)
Jun 10 11:47:56 localhost kernel: CPU 4: synchronized ITC with CPU 0 
(last diff 3 cycles, maxerr 1776 cycles)
Jun 10 11:47:56 localhost kernel: CPU 5: synchronized ITC with CPU 0 
(last diff -2 cycles, maxerr 1776 cycles)
Jun 10 11:47:56 localhost kernel: CPU 6: synchronized ITC with CPU 0 
(last diff -2 cycles, maxerr 2276 cycles)
Jun 10 11:47:56 localhost kernel: CPU 7: synchronized ITC with CPU 0 
(last diff 2 cycles, maxerr 2274 cycles)
Jun 10 11:47:56 localhost kernel: CPU 8: synchronized ITC with CPU 0 
(last diff 0 cycles, maxerr 2271 cycles)
Jun 10 11:47:56 localhost kernel: CPU 9: synchronized ITC with CPU 0 
(last diff 0 cycles, maxerr 2281 cycles)
Jun 10 11:47:56 localhost kernel: Brought up 10 CPUs
Jun 10 11:47:56 localhost kernel: Total of 10 processors activated 
(13467.04 BogoMIPS).
Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 16
Jun 10 11:47:56 localhost kernel: ACPI: Subsystem revision 20050211
Jun 10 11:47:56 localhost kernel: ACPI: Interpreter enabled
Jun 10 11:47:56 localhost kernel: ACPI: Using IOSAPIC for interrupt routing
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L000] (00:00)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L001] (00:1c)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L002] (00:38)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L004] (00:54)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L006] (00:70)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L008] (00:8c)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L010] (00:a9)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L012] (00:c6)
Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L014] (00:e3)
Jun 10 11:47:56 localhost kernel: SCSI subsystem initialized
Jun 10 11:47:56 localhost kernel: PCI: Using ACPI for IRQ routing
Jun 10 11:47:56 localhost kernel: ** PCI interrupts are no longer routed 
automatically.  If this
Jun 10 11:47:56 localhost kernel: ** causes a device to stop working, it 
is probably because the
Jun 10 11:47:56 localhost kernel: ** driver failed to call 
pci_enable_device().  As a temporary
Jun 10 11:47:56 localhost kernel: ** workaround, the "pci=routeirq" 
argument restores the old
Jun 10 11:47:56 localhost kernel: ** behavior.  If this argument makes 
the device work again,
Jun 10 11:47:56 localhost kernel: ** please email the output of "lspci" 
to bjorn.helgaas@hp.com
Jun 10 11:47:56 localhost kernel: ** so I can fix the driver.
Jun 10 11:47:56 localhost kernel: IOC: sx1000 0.1 HPA 0xf8120002000 IOVA 
space 1024Mb at 0x80000000
Jun 10 11:47:56 localhost kernel: IOC: sx1000 0.1 HPA 0xf8120003000 IOVA 
space 1024Mb at 0x80000000
Jun 10 11:47:56 localhost kernel: perfmon: version 2.0 IRQ 238
Jun 10 11:47:56 localhost kernel: perfmon: Itanium 2 PMU detected, 16 
PMCs, 18 PMDs, 4 counters (47 bits)
Jun 10 11:47:56 localhost kernel: PAL Information Facility v0.5
Jun 10 11:47:56 localhost kernel: perfmon: added sampling format 
default_format
Jun 10 11:47:56 localhost kernel: perfmon_default_smpl: default_format 
v2.0 registered
Jun 10 11:47:56 localhost kernel: Total HugeTLB memory allocated, 0
Jun 10 11:47:56 localhost kernel: VFS: Disk quotas dquot_6.5.1
Jun 10 11:47:56 localhost kernel: Dquot-cache hash table entries: 2048 
(order 0, 16384 bytes)
Jun 10 11:47:56 localhost kernel: devfs: 2004-01-31 Richard Gooch 
(rgooch@atnf.csiro.au)
Jun 10 11:47:56 localhost kernel: devfs: boot_options: 0x0
Jun 10 11:47:56 localhost kernel: Installing knfsd (copyright (C) 1996 
okir@monad.swb.de).
Jun 10 11:47:56 localhost kernel: Initializing Cryptographic API
Jun 10 11:47:56 localhost kernel: EFI Time Services Driver v0.4
Jun 10 11:47:56 localhost kernel: io scheduler noop registered
Jun 10 11:47:56 localhost kernel: io scheduler anticipatory registered
Jun 10 11:47:56 localhost kernel: io scheduler deadline registered
Jun 10 11:47:56 localhost kernel: io scheduler cfq registered
Jun 10 11:47:56 localhost kernel: RAMDISK driver initialized: 16 RAM 
disks of 16384K size 1024 blocksize
Jun 10 11:47:56 localhost kernel: GSI 24 (level, low) -> CPU 1 (0x0401) 
vector 49
Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 0000:00:02.0[A] -> 
GSI 24 (level, low) -> IRQ 49
Jun 10 11:47:56 localhost kernel: sym0: <1010-66> rev 0x1 at pci 
0000:00:02.0 irq 49
Jun 10 11:47:56 localhost kernel: sym0: Symbios NVRAM, ID 7, Fast-80, 
SE, parity checking
Jun 10 11:47:56 localhost kernel: sym0: open drain IRQ line driver, 
using on-chip SRAM
Jun 10 11:47:56 localhost kernel: sym0: using LOAD/STORE-based firmware.
Jun 10 11:47:56 localhost kernel: sym0: handling phase mismatch from 
SCRIPTS.
Jun 10 11:47:56 localhost kernel: sym0: SCSI BUS has been reset.
Jun 10 11:47:56 localhost kernel: scsi0 : sym-2.1.18n
Jun 10 11:47:56 localhost kernel:   Vendor: HP 36.4G  Model: 
MAS3367NC         Rev: HPC3
Jun 10 11:47:56 localhost kernel:   Type:   
Direct-Access                      ANSI SCSI revision: 03
Jun 10 11:47:56 localhost kernel: sym0:6:0: tagged command queuing 
enabled, command queue depth 16.
Jun 10 11:47:56 localhost kernel:  target0:0:6: Beginning Domain Validation
Jun 10 11:47:56 localhost kernel: sym0:6: wide asynchronous.
Jun 10 11:47:56 localhost kernel: sym0:6: FAST-20 WIDE SCSI 40.0 MB/s ST 
(50.0 ns, offset 31)
Jun 10 11:47:56 localhost kernel:  target0:0:6: Ending Domain Validation
Jun 10 11:47:56 localhost kernel: GSI 25 (level, low) -> CPU 2 (0x0801) 
vector 50
Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 0000:00:02.1[B] -> 
GSI 25 (level, low) -> IRQ 50
Jun 10 11:47:56 localhost kernel: sym1: <1010-66> rev 0x1 at pci 
0000:00:02.1 irq 50
Jun 10 11:47:56 localhost kernel: sym1: Symbios NVRAM, ID 7, Fast-80, 
SE, parity checking
Jun 10 11:47:56 localhost kernel: sym1: open drain IRQ line driver, 
using on-chip SRAM
Jun 10 11:47:56 localhost kernel: sym1: using LOAD/STORE-based firmware.
Jun 10 11:47:56 localhost kernel: sym1: handling phase mismatch from 
SCRIPTS.
Jun 10 11:47:56 localhost kernel: sym1: SCSI BUS has been reset.
Jun 10 11:47:56 localhost kernel: scsi1 : sym-2.1.18n
Jun 10 11:47:56 localhost kernel:   Vendor: HP        Model: DVD-ROM 
305       Rev: 1.01
Jun 10 11:47:56 localhost kernel:   Type:   
CD-ROM                             ANSI SCSI revision: 02
Jun 10 11:47:56 localhost kernel:  target1:0:2: Beginning Domain Validation
Jun 10 11:47:56 localhost kernel:  target1:0:2: Domain Validation 
skipping write tests
Jun 10 11:47:56 localhost kernel: sym1:2: FAST-20 SCSI 20.0 MB/s ST 
(50.0 ns, offset 16)
Jun 10 11:47:56 localhost kernel:  target1:0:2: Ending Domain Validation
Jun 10 11:47:56 localhost kernel: GSI 26 (level, low) -> CPU 3 (0x0c01) 
vector 51
Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 0000:00:03.0[A] -> 
GSI 26 (level, low) -> IRQ 51
Jun 10 11:47:56 localhost kernel: sym2: <1010-66> rev 0x1 at pci 
0000:00:03.0 irq 51
Jun 10 11:47:56 localhost kernel: sym2: Symbios NVRAM, ID 7, Fast-80, 
SE, parity checking
Jun 10 11:47:56 localhost kernel: sym2: open drain IRQ line driver, 
using on-chip SRAM
Jun 10 11:47:56 localhost kernel: sym2: using LOAD/STORE-based firmware.
Jun 10 11:47:56 localhost kernel: sym2: handling phase mismatch from 
SCRIPTS.
Jun 10 11:47:56 localhost kernel: sym2: SCSI BUS has been reset.
Jun 10 11:47:56 localhost kernel: scsi2 : sym-2.1.18n
Jun 10 11:47:56 localhost kernel: GSI 27 (level, low) -> CPU 0 (0x0001) 
vector 52
Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 0000:00:03.1[B] -> 
GSI 27 (level, low) -> IRQ 52
Jun 10 11:47:56 localhost kernel: sym3: <1010-66> rev 0x1 at pci 
0000:00:03.1 irq 52
Jun 10 11:47:56 localhost kernel: sym3: Symbios NVRAM, ID 7, Fast-80, 
LVD, parity checking
Jun 10 11:47:56 localhost kernel: sym3: open drain IRQ line driver, 
using on-chip SRAM
Jun 10 11:47:56 localhost kernel: sym3: using LOAD/STORE-based firmware.
Jun 10 11:47:56 localhost kernel: sym3: handling phase mismatch from 
SCRIPTS.
Jun 10 11:47:56 localhost kernel: sym3: SCSI BUS has been reset.
Jun 10 11:47:56 localhost kernel: scsi3 : sym-2.1.18n
Jun 10 11:47:56 localhost kernel: SCSI device sda: 71132960 512-byte 
hdwr sectors (36420 MB)
Jun 10 11:47:56 localhost kernel: SCSI device sda: drive cache: write 
through
Jun 10 11:47:56 localhost kernel: SCSI device sda: 71132960 512-byte 
hdwr sectors (36420 MB)
Jun 10 11:47:56 localhost kernel: SCSI device sda: drive cache: write 
through
Jun 10 11:47:56 localhost kernel:  /dev/scsi/host0/bus0/target6/lun0: p1 
p2 p3
Jun 10 11:47:56 localhost kernel: Attached scsi disk sda at scsi0, 
channel 0, id 6, lun 0
Jun 10 11:47:56 localhost kernel: mice: PS/2 mouse device common for all 
mice
Jun 10 11:47:56 localhost kernel: md: raid5 personality registered as nr 4
Jun 10 11:47:56 localhost kernel: raid5: measuring checksumming speed
Jun 10 11:47:56 localhost kernel:    ia64      :  2064.384 MB/sec
Jun 10 11:47:56 localhost kernel: raid5: using function: ia64 (2064.384 
MB/sec)
Jun 10 11:47:56 localhost kernel: md: md driver 0.90.1 MAX_MD_DEVS=256, 
MD_SB_DISKS=27
Jun 10 11:47:56 localhost kernel: EFI Variables Facility v0.08 2004-May-17
Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 2
Jun 10 11:47:56 localhost kernel: IP: routing cache hash table of 262144 
buckets, 4096Kbytes
Jun 10 11:47:56 localhost kernel: TCP established hash table entries: 
8388608 (order: 13, 134217728 bytes)
Jun 10 11:47:56 localhost kernel: TCP bind hash table entries: 65536 
(order: 6, 1048576 bytes)
Jun 10 11:47:56 localhost kernel: TCP: Hash tables configured 
(established 8388608 bind 65536)
Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 1
Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 17
Jun 10 11:47:56 localhost kernel: devfs_mk_dev: could not append to 
parent for md/0
Jun 10 11:47:56 localhost kernel: md: Autodetecting RAID arrays.
Jun 10 11:47:56 localhost kernel: md: autorun ...
Jun 10 11:47:56 localhost kernel: md: ... autorun DONE.
Jun 10 11:47:56 localhost kernel: EXT2-fs warning (device sda2): 
ext2_fill_super: mounting ext3 filesystem as ext2
Jun 10 11:47:56 localhost kernel:
Jun 10 11:47:56 localhost kernel: VFS: Mounted root (ext2 filesystem) 
readonly.
Jun 10 11:47:56 localhost kernel: Freeing unused kernel memory: 352kB freed
Jun 10 11:47:56 localhost kernel: Warning: unable to open an initial 
console.
Jun 10 11:47:56 localhost kernel: Adding 1473632k swap on /dev/sda3.  
Priority:-1 extents:1
Jun 10 11:47:58 localhost lpd[3239]: restarted


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3182 bytes --]

RE: Console problem

[Magenheimer, Dan (HP Labs Fort Collins)]

Take a look at linux/Documentation/ia64/serial.txt (in
linux-2.6.10 or greater) for a detailed explanation.
(Thanks to Bjorn for good documentation... I just
ran into a similar problem myself and he pointed me
to this.)

Dan

> -----Original Message-----
> From: linux-ia64-owner@vger.kernel.org 
> [mailto:linux-ia64-owner@vger.kernel.org] On Behalf Of Monica Correa
> Sent: Friday, June 10, 2005 4:06 PM
> To: gelato-technical@gelato.unsw.edu.au; linux-ia64@vger.kernel.org
> Subject: Console problem
> 
>   Hi, 
>  
>    I'm having some problems to boot the Linux kernel 
> 2.6.11.11 on a HP 
> Superdome with 16 Itanium 2 processors and EFI version 1.1.  
> After the 
> "Uncompressing Linux ... done" message appears, there is no 
> more output 
> for the console. The boot doesn't stop (I'm sending part of the 
> /var/log/messages file attached to this email), but no more 
> messages are 
> printed in the console and the "login" prompt is not shown. 
> It seems to 
> be a console problem, but I'm not sure about how to fix it... When I 
> boot kernel  2.4 without the "console=" option, I have a similar 
> problem, no kernel output, but the "login" prompt is shown. 
> For kernel 
> 2.4 the problem is solved when I specify the "console=ttyS0" 
> argument in 
> the boot process. However, the same doesn't happen for kernel 
> 2.6. Even 
> if I specify "console=ttyS0", I have no kernel output and no "login" 
> prompt. I also tried "console=hcdp" but it also doesn't work. 
> Has anyone 
> experienced a similar problem which could help me solving it? 
>  
>   Any suggestion is welcome! 
>  
>   Thanks in advance, 
>   Monica
> 
> Jun 10 11:47:56 localhost syslogd 1.4.1#17: restart.
> Jun 10 11:47:56 localhost kernel: klogd 1.4.1#17, log source = 
> /proc/kmsg started.
> Jun 10 11:47:56 localhost kernel: Cannot find map file.
> Jun 10 11:47:56 localhost kernel: No module symbols loaded - kernel 
> modules not enabled.
> Jun 10 11:47:56 localhost kernel: Linux version 2.6.11.11 
> (root@brpoaolympiaa1) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #13 SMP 
> Fri Jun 10 11:44:06 BRT 2005
> Jun 10 11:47:56 localhost kernel: EFI v1.10 by HP: 
> SALsystab=0x720ff7d4408 ACPI 2.0=0x720ffba0000 HCDP=0x720ffbc8508 
> SMBIOS=0x7fffe000
> Jun 10 11:47:56 localhost kernel: booting generic kernel on 
> platform hpzx1
> Jun 10 11:47:56 localhost kernel: PCDP: v3 at 0x720ffbc8508
> Jun 10 11:47:56 localhost kernel: Number of logical nodes in 
> system = 4
> Jun 10 11:47:56 localhost kernel: Number of memory chunks in 
> system = 5
> Jun 10 11:47:56 localhost kernel: efi.trim_top: ignoring 12288KB of 
> memory at 0x72000000000 due to granule hole at 0x720fe000000
> Jun 10 11:47:56 localhost kernel: warning: skipping physical page 0
> Jun 10 11:47:56 localhost last message repeated 2 times
> Jun 10 11:47:56 localhost kernel: SAL 3.2: HP Orca/IPF version 3.54
> Jun 10 11:47:56 localhost kernel: SAL Platform features: None
> Jun 10 11:47:56 localhost kernel: SAL: AP wakeup using external 
> interrupt vector 0xff
> Jun 10 11:47:56 localhost kernel: ACPI: Local APIC address 
> c0000000fee00000
> Jun 10 11:47:56 localhost kernel: GSI 16 (level, low) -> CPU 
> 0 (0x0001) 
> vector 48
> Jun 10 11:47:56 localhost kernel: 10 CPUs available, 12 CPUs total
> Jun 10 11:47:56 localhost kernel: MCA related initialization done
> Jun 10 11:47:56 localhost kernel: warning: skipping physical page 0
> Jun 10 11:47:56 localhost kernel: Virtual mem_map starts at 
> 0xa0007ff98b20c000
> Jun 10 11:47:56 localhost kernel: Built 4 zonelists
> Jun 10 11:47:56 localhost kernel: Kernel command line: 
> BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz2.6.11.11.gz 
> root=/dev/sda2 ro 
> console=hcdp
> Jun 10 11:47:56 localhost kernel: PID hash table entries: 
> 4096 (order: 
> 12, 131072 bytes)
> Jun 10 11:47:56 localhost kernel: Console: colour dummy device 80x25
> Jun 10 11:47:56 localhost kernel: Memory: 12458688k/12507760k 
> available 
> (4961k code, 56480k reserved, 2482k data, 352k init)
> Jun 10 11:47:56 localhost kernel: McKinley Errata 9 workaround not 
> needed; disabling it
> Jun 10 11:47:56 localhost kernel: Dentry cache hash table entries: 
> 2097152 (order: 10, 16777216 bytes)
> Jun 10 11:47:56 localhost kernel: Inode-cache hash table entries: 
> 1048576 (order: 9, 8388608 bytes)
> Jun 10 11:47:56 localhost kernel: Mount-cache hash table 
> entries: 1024 
> (order: 0, 16384 bytes)
> Jun 10 11:47:56 localhost kernel: Boot processor id 0x0/0x1
> Jun 10 11:47:56 localhost kernel: task migration cache decay 
> timeout: 10 
> msecs.
> Jun 10 11:47:56 localhost kernel: CPU 1: synchronized ITC with CPU 0 
> (last diff 6 cycles, maxerr 442 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 2: synchronized ITC with CPU 0 
> (last diff -2 cycles, maxerr 2281 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 3: synchronized ITC with CPU 0 
> (last diff -2 cycles, maxerr 2276 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 4: synchronized ITC with CPU 0 
> (last diff 3 cycles, maxerr 1776 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 5: synchronized ITC with CPU 0 
> (last diff -2 cycles, maxerr 1776 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 6: synchronized ITC with CPU 0 
> (last diff -2 cycles, maxerr 2276 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 7: synchronized ITC with CPU 0 
> (last diff 2 cycles, maxerr 2274 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 8: synchronized ITC with CPU 0 
> (last diff 0 cycles, maxerr 2271 cycles)
> Jun 10 11:47:56 localhost kernel: CPU 9: synchronized ITC with CPU 0 
> (last diff 0 cycles, maxerr 2281 cycles)
> Jun 10 11:47:56 localhost kernel: Brought up 10 CPUs
> Jun 10 11:47:56 localhost kernel: Total of 10 processors activated 
> (13467.04 BogoMIPS).
> Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 16
> Jun 10 11:47:56 localhost kernel: ACPI: Subsystem revision 20050211
> Jun 10 11:47:56 localhost kernel: ACPI: Interpreter enabled
> Jun 10 11:47:56 localhost kernel: ACPI: Using IOSAPIC for 
> interrupt routing
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L000] (00:00)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L001] (00:1c)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L002] (00:38)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L004] (00:54)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L006] (00:70)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L008] (00:8c)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L010] (00:a9)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L012] (00:c6)
> Jun 10 11:47:56 localhost kernel: ACPI: PCI Root Bridge [L014] (00:e3)
> Jun 10 11:47:56 localhost kernel: SCSI subsystem initialized
> Jun 10 11:47:56 localhost kernel: PCI: Using ACPI for IRQ routing
> Jun 10 11:47:56 localhost kernel: ** PCI interrupts are no 
> longer routed 
> automatically.  If this
> Jun 10 11:47:56 localhost kernel: ** causes a device to stop 
> working, it 
> is probably because the
> Jun 10 11:47:56 localhost kernel: ** driver failed to call 
> pci_enable_device().  As a temporary
> Jun 10 11:47:56 localhost kernel: ** workaround, the "pci=routeirq" 
> argument restores the old
> Jun 10 11:47:56 localhost kernel: ** behavior.  If this 
> argument makes 
> the device work again,
> Jun 10 11:47:56 localhost kernel: ** please email the output 
> of "lspci" 
> to bjorn.helgaas@hp.com
> Jun 10 11:47:56 localhost kernel: ** so I can fix the driver.
> Jun 10 11:47:56 localhost kernel: IOC: sx1000 0.1 HPA 
> 0xf8120002000 IOVA 
> space 1024Mb at 0x80000000
> Jun 10 11:47:56 localhost kernel: IOC: sx1000 0.1 HPA 
> 0xf8120003000 IOVA 
> space 1024Mb at 0x80000000
> Jun 10 11:47:56 localhost kernel: perfmon: version 2.0 IRQ 238
> Jun 10 11:47:56 localhost kernel: perfmon: Itanium 2 PMU detected, 16 
> PMCs, 18 PMDs, 4 counters (47 bits)
> Jun 10 11:47:56 localhost kernel: PAL Information Facility v0.5
> Jun 10 11:47:56 localhost kernel: perfmon: added sampling format 
> default_format
> Jun 10 11:47:56 localhost kernel: perfmon_default_smpl: 
> default_format 
> v2.0 registered
> Jun 10 11:47:56 localhost kernel: Total HugeTLB memory allocated, 0
> Jun 10 11:47:56 localhost kernel: VFS: Disk quotas dquot_6.5.1
> Jun 10 11:47:56 localhost kernel: Dquot-cache hash table 
> entries: 2048 
> (order 0, 16384 bytes)
> Jun 10 11:47:56 localhost kernel: devfs: 2004-01-31 Richard Gooch 
> (rgooch@atnf.csiro.au)
> Jun 10 11:47:56 localhost kernel: devfs: boot_options: 0x0
> Jun 10 11:47:56 localhost kernel: Installing knfsd (copyright 
> (C) 1996 
> okir@monad.swb.de).
> Jun 10 11:47:56 localhost kernel: Initializing Cryptographic API
> Jun 10 11:47:56 localhost kernel: EFI Time Services Driver v0.4
> Jun 10 11:47:56 localhost kernel: io scheduler noop registered
> Jun 10 11:47:56 localhost kernel: io scheduler anticipatory registered
> Jun 10 11:47:56 localhost kernel: io scheduler deadline registered
> Jun 10 11:47:56 localhost kernel: io scheduler cfq registered
> Jun 10 11:47:56 localhost kernel: RAMDISK driver initialized: 16 RAM 
> disks of 16384K size 1024 blocksize
> Jun 10 11:47:56 localhost kernel: GSI 24 (level, low) -> CPU 
> 1 (0x0401) 
> vector 49
> Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 
> 0000:00:02.0[A] -> 
> GSI 24 (level, low) -> IRQ 49
> Jun 10 11:47:56 localhost kernel: sym0: <1010-66> rev 0x1 at pci 
> 0000:00:02.0 irq 49
> Jun 10 11:47:56 localhost kernel: sym0: Symbios NVRAM, ID 7, Fast-80, 
> SE, parity checking
> Jun 10 11:47:56 localhost kernel: sym0: open drain IRQ line driver, 
> using on-chip SRAM
> Jun 10 11:47:56 localhost kernel: sym0: using 
> LOAD/STORE-based firmware.
> Jun 10 11:47:56 localhost kernel: sym0: handling phase mismatch from 
> SCRIPTS.
> Jun 10 11:47:56 localhost kernel: sym0: SCSI BUS has been reset.
> Jun 10 11:47:56 localhost kernel: scsi0 : sym-2.1.18n
> Jun 10 11:47:56 localhost kernel:   Vendor: HP 36.4G  Model: 
> MAS3367NC         Rev: HPC3
> Jun 10 11:47:56 localhost kernel:   Type:   
> Direct-Access                      ANSI SCSI revision: 03
> Jun 10 11:47:56 localhost kernel: sym0:6:0: tagged command queuing 
> enabled, command queue depth 16.
> Jun 10 11:47:56 localhost kernel:  target0:0:6: Beginning 
> Domain Validation
> Jun 10 11:47:56 localhost kernel: sym0:6: wide asynchronous.
> Jun 10 11:47:56 localhost kernel: sym0:6: FAST-20 WIDE SCSI 
> 40.0 MB/s ST 
> (50.0 ns, offset 31)
> Jun 10 11:47:56 localhost kernel:  target0:0:6: Ending Domain 
> Validation
> Jun 10 11:47:56 localhost kernel: GSI 25 (level, low) -> CPU 
> 2 (0x0801) 
> vector 50
> Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 
> 0000:00:02.1[B] -> 
> GSI 25 (level, low) -> IRQ 50
> Jun 10 11:47:56 localhost kernel: sym1: <1010-66> rev 0x1 at pci 
> 0000:00:02.1 irq 50
> Jun 10 11:47:56 localhost kernel: sym1: Symbios NVRAM, ID 7, Fast-80, 
> SE, parity checking
> Jun 10 11:47:56 localhost kernel: sym1: open drain IRQ line driver, 
> using on-chip SRAM
> Jun 10 11:47:56 localhost kernel: sym1: using 
> LOAD/STORE-based firmware.
> Jun 10 11:47:56 localhost kernel: sym1: handling phase mismatch from 
> SCRIPTS.
> Jun 10 11:47:56 localhost kernel: sym1: SCSI BUS has been reset.
> Jun 10 11:47:56 localhost kernel: scsi1 : sym-2.1.18n
> Jun 10 11:47:56 localhost kernel:   Vendor: HP        Model: DVD-ROM 
> 305       Rev: 1.01
> Jun 10 11:47:56 localhost kernel:   Type:   
> CD-ROM                             ANSI SCSI revision: 02
> Jun 10 11:47:56 localhost kernel:  target1:0:2: Beginning 
> Domain Validation
> Jun 10 11:47:56 localhost kernel:  target1:0:2: Domain Validation 
> skipping write tests
> Jun 10 11:47:56 localhost kernel: sym1:2: FAST-20 SCSI 20.0 MB/s ST 
> (50.0 ns, offset 16)
> Jun 10 11:47:56 localhost kernel:  target1:0:2: Ending Domain 
> Validation
> Jun 10 11:47:56 localhost kernel: GSI 26 (level, low) -> CPU 
> 3 (0x0c01) 
> vector 51
> Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 
> 0000:00:03.0[A] -> 
> GSI 26 (level, low) -> IRQ 51
> Jun 10 11:47:56 localhost kernel: sym2: <1010-66> rev 0x1 at pci 
> 0000:00:03.0 irq 51
> Jun 10 11:47:56 localhost kernel: sym2: Symbios NVRAM, ID 7, Fast-80, 
> SE, parity checking
> Jun 10 11:47:56 localhost kernel: sym2: open drain IRQ line driver, 
> using on-chip SRAM
> Jun 10 11:47:56 localhost kernel: sym2: using 
> LOAD/STORE-based firmware.
> Jun 10 11:47:56 localhost kernel: sym2: handling phase mismatch from 
> SCRIPTS.
> Jun 10 11:47:56 localhost kernel: sym2: SCSI BUS has been reset.
> Jun 10 11:47:56 localhost kernel: scsi2 : sym-2.1.18n
> Jun 10 11:47:56 localhost kernel: GSI 27 (level, low) -> CPU 
> 0 (0x0001) 
> vector 52
> Jun 10 11:47:56 localhost kernel: ACPI: PCI interrupt 
> 0000:00:03.1[B] -> 
> GSI 27 (level, low) -> IRQ 52
> Jun 10 11:47:56 localhost kernel: sym3: <1010-66> rev 0x1 at pci 
> 0000:00:03.1 irq 52
> Jun 10 11:47:56 localhost kernel: sym3: Symbios NVRAM, ID 7, Fast-80, 
> LVD, parity checking
> Jun 10 11:47:56 localhost kernel: sym3: open drain IRQ line driver, 
> using on-chip SRAM
> Jun 10 11:47:56 localhost kernel: sym3: using 
> LOAD/STORE-based firmware.
> Jun 10 11:47:56 localhost kernel: sym3: handling phase mismatch from 
> SCRIPTS.
> Jun 10 11:47:56 localhost kernel: sym3: SCSI BUS has been reset.
> Jun 10 11:47:56 localhost kernel: scsi3 : sym-2.1.18n
> Jun 10 11:47:56 localhost kernel: SCSI device sda: 71132960 512-byte 
> hdwr sectors (36420 MB)
> Jun 10 11:47:56 localhost kernel: SCSI device sda: drive cache: write 
> through
> Jun 10 11:47:56 localhost kernel: SCSI device sda: 71132960 512-byte 
> hdwr sectors (36420 MB)
> Jun 10 11:47:56 localhost kernel: SCSI device sda: drive cache: write 
> through
> Jun 10 11:47:56 localhost kernel:  
> /dev/scsi/host0/bus0/target6/lun0: p1 
> p2 p3
> Jun 10 11:47:56 localhost kernel: Attached scsi disk sda at scsi0, 
> channel 0, id 6, lun 0
> Jun 10 11:47:56 localhost kernel: mice: PS/2 mouse device 
> common for all 
> mice
> Jun 10 11:47:56 localhost kernel: md: raid5 personality 
> registered as nr 4
> Jun 10 11:47:56 localhost kernel: raid5: measuring checksumming speed
> Jun 10 11:47:56 localhost kernel:    ia64      :  2064.384 MB/sec
> Jun 10 11:47:56 localhost kernel: raid5: using function: ia64 
> (2064.384 
> MB/sec)
> Jun 10 11:47:56 localhost kernel: md: md driver 0.90.1 
> MAX_MD_DEVS%6, 
> MD_SB_DISKS'
> Jun 10 11:47:56 localhost kernel: EFI Variables Facility 
> v0.08 2004-May-17
> Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 2
> Jun 10 11:47:56 localhost kernel: IP: routing cache hash 
> table of 262144 
> buckets, 4096Kbytes
> Jun 10 11:47:56 localhost kernel: TCP established hash table entries: 
> 8388608 (order: 13, 134217728 bytes)
> Jun 10 11:47:56 localhost kernel: TCP bind hash table entries: 65536 
> (order: 6, 1048576 bytes)
> Jun 10 11:47:56 localhost kernel: TCP: Hash tables configured 
> (established 8388608 bind 65536)
> Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 1
> Jun 10 11:47:56 localhost kernel: NET: Registered protocol family 17
> Jun 10 11:47:56 localhost kernel: devfs_mk_dev: could not append to 
> parent for md/0
> Jun 10 11:47:56 localhost kernel: md: Autodetecting RAID arrays.
> Jun 10 11:47:56 localhost kernel: md: autorun ...
> Jun 10 11:47:56 localhost kernel: md: ... autorun DONE.
> Jun 10 11:47:56 localhost kernel: EXT2-fs warning (device sda2): 
> ext2_fill_super: mounting ext3 filesystem as ext2
> Jun 10 11:47:56 localhost kernel:
> Jun 10 11:47:56 localhost kernel: VFS: Mounted root (ext2 filesystem) 
> readonly.
> Jun 10 11:47:56 localhost kernel: Freeing unused kernel 
> memory: 352kB freed
> Jun 10 11:47:56 localhost kernel: Warning: unable to open an initial 
> console.
> Jun 10 11:47:56 localhost kernel: Adding 1473632k swap on /dev/sda3.  
> Priority:-1 extents:1
> Jun 10 11:47:58 localhost lpd[3239]: restarted
> 
> 

console problem

[Stefan Berger]

I am experiencing a problem with the console as follows:

xm create userdomain-0 -c
Using config file "/etc/xen/userdomain-0".
Started domain UserDomain0
xc_console: Could not open tty `/dev/pts/3': No such file or directory

xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
Domain-0           0      385    -      4   r----     22.7
UserDomain0        1       31    3      1   -b---      0.9

ls -l /dev/pts/
total 0
crw--w----  1 root tty 136, 0 Aug  4 22:15 0
crw--w----  1 root tty 136, 1 Aug  4 22:21 1
crw--w----  1 root tty 136, 2 Aug  4 22:18 2

The source tree is up-to-date as of now.

  Stefan

Re: console problem

[Anthony Liguori]

Stefan Berger wrote:

>I am experiencing a problem with the console as follows:
>  
>
This could be a timing issue.  I assume that xm console works as 
expected correct?

Now that the store supports watches on non-existent nodes, I can handle 
this properly.  I'll submit a patch tomorrow.

Regards,

Anthony Liguori

>xm create userdomain-0 -c
>Using config file "/etc/xen/userdomain-0".
>Started domain UserDomain0
>xc_console: Could not open tty `/dev/pts/3': No such file or directory
>
>xm list
>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>Domain-0           0      385    -      4   r----     22.7
>UserDomain0        1       31    3      1   -b---      0.9
>
>ls -l /dev/pts/
>total 0
>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>
>The source tree is up-to-date as of now.
>
>  Stefan
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

Re: console problem

[Stefan Berger]

aliguori@us.ltcfwd.linux.ibm.com wrote on 08/04/2005 10:30:37 PM:

> Stefan Berger wrote:
> 
> >I am experiencing a problem with the console as follows:
> > 
> >
> This could be a timing issue.  I assume that xm console works as 
> expected correct?

No, i.e., 'xm console 1' does not work, either.

> 
> Now that the store supports watches on non-existent nodes, I can handle 
> this properly.  I'll submit a patch tomorrow.

Ok.

  Stefan
> 
> Regards,
> 
> Anthony Liguori
> 
> >xm create userdomain-0 -c
> >Using config file "/etc/xen/userdomain-0".
> >Started domain UserDomain0
> >xc_console: Could not open tty `/dev/pts/3': No such file or directory
> >
> >xm list
> >Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
> >Domain-0           0      385    -      4   r----     22.7
> >UserDomain0        1       31    3      1   -b---      0.9
> >
> >ls -l /dev/pts/
> >total 0
> >crw--w----  1 root tty 136, 0 Aug  4 22:15 0
> >crw--w----  1 root tty 136, 1 Aug  4 22:21 1
> >crw--w----  1 root tty 136, 2 Aug  4 22:18 2
> >
> >The source tree is up-to-date as of now.
> >
> >  Stefan
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com
> >http://lists.xensource.com/xen-devel
> >
> > 
> >
> 

RE: console problem

[Li, Xin B]

I'm also blocked by this issue when debugging x86_64 xenU smp.
-xin

>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com 
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>Anthony Liguori
>Sent: 2005年8月5日 10:31
>To: Stefan Berger
>Cc: xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] console problem
>
>Stefan Berger wrote:
>
>>I am experiencing a problem with the console as follows:
>>  
>>
>This could be a timing issue.  I assume that xm console works as 
>expected correct?
>
>Now that the store supports watches on non-existent nodes, I 
>can handle 
>this properly.  I'll submit a patch tomorrow.
>
>Regards,
>
>Anthony Liguori
>
>>xm create userdomain-0 -c
>>Using config file "/etc/xen/userdomain-0".
>>Started domain UserDomain0
>>xc_console: Could not open tty `/dev/pts/3': No such file or directory
>>
>>xm list
>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>Domain-0           0      385    -      4   r----     22.7
>>UserDomain0        1       31    3      1   -b---      0.9
>>
>>ls -l /dev/pts/
>>total 0
>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>
>>The source tree is up-to-date as of now.
>>
>>  Stefan
>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
>>  
>>
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>

Re: console problem

[Anthony Liguori]

Make sure your trees are fresh. Some folks have been experience problems
because hg pull -u doesn't seem to handle deletes all that well.

Also try restarting consoled.

Regards,

Anthony Liguori

Li, Xin B wrote:

>I'm also blocked by this issue when debugging x86_64 xenU smp.
>-xin
>
>  
>
>>-----Original Message-----
>>From: xen-devel-bounces@lists.xensource.com 
>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>>Anthony Liguori
>>Sent: 2005年8月5日 10:31
>>To: Stefan Berger
>>Cc: xen-devel@lists.xensource.com
>>Subject: Re: [Xen-devel] console problem
>>
>>Stefan Berger wrote:
>>
>>    
>>
>>>I am experiencing a problem with the console as follows:
>>> 
>>>
>>>      
>>>
>>This could be a timing issue.  I assume that xm console works as 
>>expected correct?
>>
>>Now that the store supports watches on non-existent nodes, I 
>>can handle 
>>this properly.  I'll submit a patch tomorrow.
>>
>>Regards,
>>
>>Anthony Liguori
>>
>>    
>>
>>>xm create userdomain-0 -c
>>>Using config file "/etc/xen/userdomain-0".
>>>Started domain UserDomain0
>>>xc_console: Could not open tty `/dev/pts/3': No such file or directory
>>>
>>>xm list
>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>>Domain-0           0      385    -      4   r----     22.7
>>>UserDomain0        1       31    3      1   -b---      0.9
>>>
>>>ls -l /dev/pts/
>>>total 0
>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>>
>>>The source tree is up-to-date as of now.
>>>
>>> Stefan
>>>
>>>_______________________________________________
>>>Xen-devel mailing list
>>>Xen-devel@lists.xensource.com
>>>http://lists.xensource.com/xen-devel
>>>
>>> 
>>>
>>>      
>>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
>>    
>>
>
>  
>

RE: console problem

[Li, Xin B]

Don't help even I check out a completely new copy!
-Xin 

>-----Original Message-----
>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
>Sent: 2005年8月5日 11:53
>To: Li, Xin B
>Cc: Stefan Berger; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] console problem
>
>Make sure your trees are fresh. Some folks have been 
>experience problems
>because hg pull -u doesn't seem to handle deletes all that well.
>
>Also try restarting consoled.
>
>Regards,
>
>Anthony Liguori
>
>Li, Xin B wrote:
>
>>I'm also blocked by this issue when debugging x86_64 xenU smp.
>>-xin
>>
>>  
>>
>>>-----Original Message-----
>>>From: xen-devel-bounces@lists.xensource.com 
>>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>>>Anthony Liguori
>>>Sent: 2005年8月5日 10:31
>>>To: Stefan Berger
>>>Cc: xen-devel@lists.xensource.com
>>>Subject: Re: [Xen-devel] console problem
>>>
>>>Stefan Berger wrote:
>>>
>>>    
>>>
>>>>I am experiencing a problem with the console as follows:
>>>> 
>>>>
>>>>      
>>>>
>>>This could be a timing issue.  I assume that xm console works as 
>>>expected correct?
>>>
>>>Now that the store supports watches on non-existent nodes, I 
>>>can handle 
>>>this properly.  I'll submit a patch tomorrow.
>>>
>>>Regards,
>>>
>>>Anthony Liguori
>>>
>>>    
>>>
>>>>xm create userdomain-0 -c
>>>>Using config file "/etc/xen/userdomain-0".
>>>>Started domain UserDomain0
>>>>xc_console: Could not open tty `/dev/pts/3': No such file 
>or directory
>>>>
>>>>xm list
>>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>>>Domain-0           0      385    -      4   r----     22.7
>>>>UserDomain0        1       31    3      1   -b---      0.9
>>>>
>>>>ls -l /dev/pts/
>>>>total 0
>>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>>>
>>>>The source tree is up-to-date as of now.
>>>>
>>>> Stefan
>>>>
>>>>_______________________________________________
>>>>Xen-devel mailing list
>>>>Xen-devel@lists.xensource.com
>>>>http://lists.xensource.com/xen-devel
>>>>
>>>> 
>>>>
>>>>      
>>>>
>>>_______________________________________________
>>>Xen-devel mailing list
>>>Xen-devel@lists.xensource.com
>>>http://lists.xensource.com/xen-devel
>>>
>>>    
>>>
>>
>>  
>>
>
>

Re: console problem

[Anthony Liguori]

Li, Xin B wrote:

>Don't help even I check out a completely new copy!
>  
>
Did you try killing consoled and restarting it (just invoke consoled on
the command line).

Please open a bug in bugzilla and provide as much information about your
system as possible so I can attempt to reproduce.

Thanks,

Anthony Liguori

>-Xin 
>
>  
>
>>-----Original Message-----
>>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
>>Sent: 2005年8月5日 11:53
>>To: Li, Xin B
>>Cc: Stefan Berger; xen-devel@lists.xensource.com
>>Subject: Re: [Xen-devel] console problem
>>
>>Make sure your trees are fresh. Some folks have been 
>>experience problems
>>because hg pull -u doesn't seem to handle deletes all that well.
>>
>>Also try restarting consoled.
>>
>>Regards,
>>
>>Anthony Liguori
>>
>>Li, Xin B wrote:
>>
>>    
>>
>>>I'm also blocked by this issue when debugging x86_64 xenU smp.
>>>-xin
>>>
>>> 
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: xen-devel-bounces@lists.xensource.com 
>>>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>>>>Anthony Liguori
>>>>Sent: 2005年8月5日 10:31
>>>>To: Stefan Berger
>>>>Cc: xen-devel@lists.xensource.com
>>>>Subject: Re: [Xen-devel] console problem
>>>>
>>>>Stefan Berger wrote:
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>I am experiencing a problem with the console as follows:
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>This could be a timing issue.  I assume that xm console works as 
>>>>expected correct?
>>>>
>>>>Now that the store supports watches on non-existent nodes, I 
>>>>can handle 
>>>>this properly.  I'll submit a patch tomorrow.
>>>>
>>>>Regards,
>>>>
>>>>Anthony Liguori
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>xm create userdomain-0 -c
>>>>>Using config file "/etc/xen/userdomain-0".
>>>>>Started domain UserDomain0
>>>>>xc_console: Could not open tty `/dev/pts/3': No such file 
>>>>>          
>>>>>
>>or directory
>>    
>>
>>>>>xm list
>>>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>>>>Domain-0           0      385    -      4   r----     22.7
>>>>>UserDomain0        1       31    3      1   -b---      0.9
>>>>>
>>>>>ls -l /dev/pts/
>>>>>total 0
>>>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>>>>
>>>>>The source tree is up-to-date as of now.
>>>>>
>>>>>Stefan
>>>>>
>>>>>_______________________________________________
>>>>>Xen-devel mailing list
>>>>>Xen-devel@lists.xensource.com
>>>>>http://lists.xensource.com/xen-devel
>>>>>
>>>>>
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>_______________________________________________
>>>>Xen-devel mailing list
>>>>Xen-devel@lists.xensource.com
>>>>http://lists.xensource.com/xen-devel
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>> 
>>>
>>>      
>>>
>>    
>>
>
>  
>

RE: console problem

[Li, Xin B]

>-----Original Message-----
>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
>Sent: 2005年8月5日 13:41
>To: Li, Xin B
>Cc: Stefan Berger; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] console problem
>
>Li, Xin B wrote:
>
>>Don't help even I check out a completely new copy!
>>  
>>
>Did you try killing consoled and restarting it (just invoke consoled on
>the command line).
>
>Please open a bug in bugzilla and provide as much information 
>about your
>system as possible so I can attempt to reproduce.

Thanks, I will create a bug!
-Xin

>
>Thanks,
>
>Anthony Liguori
>
>>-Xin 
>>
>>  
>>
>>>-----Original Message-----
>>>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
>>>Sent: 2005年8月5日 11:53
>>>To: Li, Xin B
>>>Cc: Stefan Berger; xen-devel@lists.xensource.com
>>>Subject: Re: [Xen-devel] console problem
>>>
>>>Make sure your trees are fresh. Some folks have been 
>>>experience problems
>>>because hg pull -u doesn't seem to handle deletes all that well.
>>>
>>>Also try restarting consoled.
>>>
>>>Regards,
>>>
>>>Anthony Liguori
>>>
>>>Li, Xin B wrote:
>>>
>>>    
>>>
>>>>I'm also blocked by this issue when debugging x86_64 xenU smp.
>>>>-xin
>>>>
>>>> 
>>>>
>>>>      
>>>>
>>>>>-----Original Message-----
>>>>>From: xen-devel-bounces@lists.xensource.com 
>>>>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>>>>>Anthony Liguori
>>>>>Sent: 2005年8月5日 10:31
>>>>>To: Stefan Berger
>>>>>Cc: xen-devel@lists.xensource.com
>>>>>Subject: Re: [Xen-devel] console problem
>>>>>
>>>>>Stefan Berger wrote:
>>>>>
>>>>>   
>>>>>
>>>>>        
>>>>>
>>>>>>I am experiencing a problem with the console as follows:
>>>>>>
>>>>>>
>>>>>>     
>>>>>>
>>>>>>          
>>>>>>
>>>>>This could be a timing issue.  I assume that xm console works as 
>>>>>expected correct?
>>>>>
>>>>>Now that the store supports watches on non-existent nodes, I 
>>>>>can handle 
>>>>>this properly.  I'll submit a patch tomorrow.
>>>>>
>>>>>Regards,
>>>>>
>>>>>Anthony Liguori
>>>>>
>>>>>   
>>>>>
>>>>>        
>>>>>
>>>>>>xm create userdomain-0 -c
>>>>>>Using config file "/etc/xen/userdomain-0".
>>>>>>Started domain UserDomain0
>>>>>>xc_console: Could not open tty `/dev/pts/3': No such file 
>>>>>>          
>>>>>>
>>>or directory
>>>    
>>>
>>>>>>xm list
>>>>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>>>>>Domain-0           0      385    -      4   r----     22.7
>>>>>>UserDomain0        1       31    3      1   -b---      0.9
>>>>>>
>>>>>>ls -l /dev/pts/
>>>>>>total 0
>>>>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>>>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>>>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>>>>>
>>>>>>The source tree is up-to-date as of now.
>>>>>>
>>>>>>Stefan
>>>>>>
>>>>>>_______________________________________________
>>>>>>Xen-devel mailing list
>>>>>>Xen-devel@lists.xensource.com
>>>>>>http://lists.xensource.com/xen-devel
>>>>>>
>>>>>>
>>>>>>
>>>>>>     
>>>>>>
>>>>>>          
>>>>>>
>>>>>_______________________________________________
>>>>>Xen-devel mailing list
>>>>>Xen-devel@lists.xensource.com
>>>>>http://lists.xensource.com/xen-devel
>>>>>
>>>>>   
>>>>>
>>>>>        
>>>>>
>>>> 
>>>>
>>>>      
>>>>
>>>    
>>>
>>
>>  
>>
>
>

RE: console problem

[Li Ge]

[-- Attachment #1.1.1: Type: text/plain, Size: 4789 bytes --]






I opened a bug(#141) for this yesterday. I am still seeing the problem with
the latest tree (changeset: 6025).


Thanks,
Li


                                                                       
             "Li, Xin B"                                               
             <xin.b.li@intel.c                                         
             om>                                                        To
             Sent by:                  aliguori@us.ltcfwd.linux.ibm.com
             xen-devel-bounces                                          cc
             @lists.xensource.         xen-devel@lists.xensource.com,  
             com                       Stefan Berger/Watson/IBM@IBMUS  
                                                                   Subject
                                       RE: [Xen-devel] console problem 
             08/05/2005 12:43                                          
             AM                                                        
                                                                       
                                                                       
                                                                       
                                                                       




>-----Original Message-----
>From: Anthony Liguori [mailto:aliguori@us.ibm.com]
>Sent: 2005年8月5日 13:41
>To: Li, Xin B
>Cc: Stefan Berger; xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] console problem
>
>Li, Xin B wrote:
>
>>Don't help even I check out a completely new copy!
>>
>>
>Did you try killing consoled and restarting it (just invoke consoled on
>the command line).
>
>Please open a bug in bugzilla and provide as much information
>about your
>system as possible so I can attempt to reproduce.

Thanks, I will create a bug!
-Xin

>
>Thanks,
>
>Anthony Liguori
>
>>-Xin
>>
>>
>>
>>>-----Original Message-----
>>>From: Anthony Liguori [mailto:aliguori@us.ibm.com]
>>>Sent: 2005年8月5日 11:53
>>>To: Li, Xin B
>>>Cc: Stefan Berger; xen-devel@lists.xensource.com
>>>Subject: Re: [Xen-devel] console problem
>>>
>>>Make sure your trees are fresh. Some folks have been
>>>experience problems
>>>because hg pull -u doesn't seem to handle deletes all that well.
>>>
>>>Also try restarting consoled.
>>>
>>>Regards,
>>>
>>>Anthony Liguori
>>>
>>>Li, Xin B wrote:
>>>
>>>
>>>
>>>>I'm also blocked by this issue when debugging x86_64 xenU smp.
>>>>-xin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: xen-devel-bounces@lists.xensource.com
>>>>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
>>>>>Anthony Liguori
>>>>>Sent: 2005年8月5日 10:31
>>>>>To: Stefan Berger
>>>>>Cc: xen-devel@lists.xensource.com
>>>>>Subject: Re: [Xen-devel] console problem
>>>>>
>>>>>Stefan Berger wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I am experiencing a problem with the console as follows:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>This could be a timing issue.  I assume that xm console works as
>>>>>expected correct?
>>>>>
>>>>>Now that the store supports watches on non-existent nodes, I
>>>>>can handle
>>>>>this properly.  I'll submit a patch tomorrow.
>>>>>
>>>>>Regards,
>>>>>
>>>>>Anthony Liguori
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>xm create userdomain-0 -c
>>>>>>Using config file "/etc/xen/userdomain-0".
>>>>>>Started domain UserDomain0
>>>>>>xc_console: Could not open tty `/dev/pts/3': No such file
>>>>>>
>>>>>>
>>>or directory
>>>
>>>
>>>>>>xm list
>>>>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>>>>>Domain-0           0      385    -      4   r----     22.7
>>>>>>UserDomain0        1       31    3      1   -b---      0.9
>>>>>>
>>>>>>ls -l /dev/pts/
>>>>>>total 0
>>>>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>>>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>>>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>>>>>
>>>>>>The source tree is up-to-date as of now.
>>>>>>
>>>>>>Stefan
>>>>>>
>>>>>>_______________________________________________
>>>>>>Xen-devel mailing list
>>>>>>Xen-devel@lists.xensource.com
>>>>>>http://lists.xensource.com/xen-devel
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>_______________________________________________
>>>>>Xen-devel mailing list
>>>>>Xen-devel@lists.xensource.com
>>>>>http://lists.xensource.com/xen-devel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>

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

[-- Attachment #1.1.2: Type: text/html, Size: 9400 bytes --]

[-- Attachment #1.2: graycol.gif --]
[-- Type: image/gif, Size: 105 bytes --]

[-- Attachment #1.3: pic24500.gif --]
[-- Type: image/gif, Size: 1255 bytes --]

[-- Attachment #1.4: ecblank.gif --]
[-- Type: image/gif, Size: 45 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: console problem

[Keir Fraser]

On 5 Aug 2005, at 16:34, Li Ge wrote:

> I opened a bug(#141) for this yesterday. I am still seeing the problem 
> with the latest tree (changeset: 6025).
>
>
>  Thanks,
>  Li

I have to start consoled manually 'consoled start', which I do 
immediately after starting xend. then everything works for me.

  -- Keir

RE: console problem

[David F Barrera]

On Fri, 2005-08-05 at 10:34 -0500, Li Ge wrote:
> I opened a bug(#141) for this yesterday. I am still seeing the problem
> with the latest tree (changeset: 6025). 

I, too, am seeing this problem on both an FC3 and a SLES 9 SP2 builds.

[root@dbarrera xen]# xm create -c vm1.cfg
Using config file "vm1.cfg".
Started domain vm1
xc_console: Could not read tty from store: No such file or directory

The latest changeset on both builds is:
changeset:   6027:69b7c9c3a9fdf22d840132f274f3fa64101a0ed0
tag:         tip
user:        kaf24@firebug.cl.cam.ac.uk
date:        Fri Aug  5 10:11:46 2005
summary:     Fix mach2phys table allocation for 32-bit PAE Xen.

> 
> 
> Thanks,
> Li
> Inactive hide details for Li,"Li, Xin B" <xin.b.li@intel.com>
> 
> 
>                                 "Li, Xin B" <xin.b.li@intel.com> 
>                                 Sent by: xen-devel-bounces@lists.xensource.com 
>                                 
>                                 08/05/2005 12:43 AM
>                                 
> 
>                To
> 
> aliguori@us.ltcfwd.linux.ibm.com
> 
>                cc
> 
> xen-
> devel@lists.xensource.com, Stefan Berger/Watson/IBM@IBMUS
> 
>           Subject
> 
> RE: [Xen-devel]
> console problem
> 
> 
> 
> >-----Original Message-----
> >From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
> >Sent: 2005年8月5日 13:41
> >To: Li, Xin B
> >Cc: Stefan Berger; xen-devel@lists.xensource.com
> >Subject: Re: [Xen-devel] console problem
> >
> >Li, Xin B wrote:
> >
> >>Don't help even I check out a completely new copy!
> >>  
> >>
> >Did you try killing consoled and restarting it (just invoke consoled
> on
> >the command line).
> >
> >Please open a bug in bugzilla and provide as much information 
> >about your
> >system as possible so I can attempt to reproduce.
> 
> Thanks, I will create a bug!
> -Xin
> 
> >
> >Thanks,
> >
> >Anthony Liguori
> >
> >>-Xin 
> >>
> >>  
> >>
> >>>-----Original Message-----
> >>>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
> >>>Sent: 2005年8月5日 11:53
> >>>To: Li, Xin B
> >>>Cc: Stefan Berger; xen-devel@lists.xensource.com
> >>>Subject: Re: [Xen-devel] console problem
> >>>
> >>>Make sure your trees are fresh. Some folks have been 
> >>>experience problems
> >>>because hg pull -u doesn't seem to handle deletes all that well.
> >>>
> >>>Also try restarting consoled.
> >>>
> >>>Regards,
> >>>
> >>>Anthony Liguori
> >>>
> >>>Li, Xin B wrote:
> >>>
> >>>    
> >>>
> >>>>I'm also blocked by this issue when debugging x86_64 xenU smp.
> >>>>-xin
> >>>>
> >>>> 
> >>>>
> >>>>      
> >>>>
> >>>>>-----Original Message-----
> >>>>>From: xen-devel-bounces@lists.xensource.com 
> >>>>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> >>>>>Anthony Liguori
> >>>>>Sent: 2005年8月5日 10:31
> >>>>>To: Stefan Berger
> >>>>>Cc: xen-devel@lists.xensource.com
> >>>>>Subject: Re: [Xen-devel] console problem
> >>>>>
> >>>>>Stefan Berger wrote:
> >>>>>
> >>>>>   
> >>>>>
> >>>>>        
> >>>>>
> >>>>>>I am experiencing a problem with the console as follows:
> >>>>>>
> >>>>>>
> >>>>>>     
> >>>>>>
> >>>>>>          
> >>>>>>
> >>>>>This could be a timing issue.  I assume that xm console works as 
> >>>>>expected correct?
> >>>>>
> >>>>>Now that the store supports watches on non-existent nodes, I 
> >>>>>can handle 
> >>>>>this properly.  I'll submit a patch tomorrow.
> >>>>>
> >>>>>Regards,
> >>>>>
> >>>>>Anthony Liguori
> >>>>>
> >>>>>   
> >>>>>
> >>>>>        
> >>>>>
> >>>>>>xm create userdomain-0 -c
> >>>>>>Using config file "/etc/xen/userdomain-0".
> >>>>>>Started domain UserDomain0
> >>>>>>xc_console: Could not open tty `/dev/pts/3': No such file 
> >>>>>>          
> >>>>>>
> >>>or directory
> >>>    
> >>>
> >>>>>>xm list
> >>>>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
> >>>>>>Domain-0           0      385    -      4   r----     22.7
> >>>>>>UserDomain0        1       31    3      1   -b---      0.9
> >>>>>>
> >>>>>>ls -l /dev/pts/
> >>>>>>total 0
> >>>>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
> >>>>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
> >>>>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
> >>>>>>
> >>>>>>The source tree is up-to-date as of now.
> >>>>>>
> >>>>>>Stefan
> >>>>>>
> >>>>>>_______________________________________________
> >>>>>>Xen-devel mailing list
> >>>>>>Xen-devel@lists.xensource.com
> >>>>>>http://lists.xensource.com/xen-devel
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>     
> >>>>>>
> >>>>>>          
> >>>>>>
> >>>>>_______________________________________________
> >>>>>Xen-devel mailing list
> >>>>>Xen-devel@lists.xensource.com
> >>>>>http://lists.xensource.com/xen-devel
> >>>>>
> >>>>>   
> >>>>>
> >>>>>        
> >>>>>
> >>>> 
> >>>>
> >>>>      
> >>>>
> >>>    
> >>>
> >>
> >>  
> >>
> >
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides

Re: console problem

[Anthony Liguori]

Yes, I'm aware of this.  The problem is that we've never had a good 
dependency system for the daemons we started.  The extra daemon has made 
the problem much worse and now we're seeing timing issues.

You can work around the problem by manually starting consoled (you may 
have to restart xenstored too).  Under the right circumstances, xend 
restart will loop because xenstored gets itself hosed.

I'm reworking a lot of this code right now to make it more robust and 
solve the problem completely.  Just hang in there a bit :-)

Regards,

Anthony Liguori

David F Barrera wrote:

>On Fri, 2005-08-05 at 10:34 -0500, Li Ge wrote:
>  
>
>>I opened a bug(#141) for this yesterday. I am still seeing the problem
>>with the latest tree (changeset: 6025). 
>>    
>>
>
>I, too, am seeing this problem on both an FC3 and a SLES 9 SP2 builds.
>
>[root@dbarrera xen]# xm create -c vm1.cfg
>Using config file "vm1.cfg".
>Started domain vm1
>xc_console: Could not read tty from store: No such file or directory
>
>The latest changeset on both builds is:
>changeset:   6027:69b7c9c3a9fdf22d840132f274f3fa64101a0ed0
>tag:         tip
>user:        kaf24@firebug.cl.cam.ac.uk
>date:        Fri Aug  5 10:11:46 2005
>summary:     Fix mach2phys table allocation for 32-bit PAE Xen.
>
>  
>
>>Thanks,
>>Li
>>Inactive hide details for Li,"Li, Xin B" <xin.b.li@intel.com>
>>
>>
>>                                "Li, Xin B" <xin.b.li@intel.com> 
>>                                Sent by: xen-devel-bounces@lists.xensource.com 
>>                                
>>                                08/05/2005 12:43 AM
>>                                
>>
>>               To
>>
>>aliguori@us.ltcfwd.linux.ibm.com
>>
>>               cc
>>
>>xen-
>>devel@lists.xensource.com, Stefan Berger/Watson/IBM@IBMUS
>>
>>          Subject
>>
>>RE: [Xen-devel]
>>console problem
>>
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
>>>Sent: 2005年8月5日 13:41
>>>To: Li, Xin B
>>>Cc: Stefan Berger; xen-devel@lists.xensource.com
>>>Subject: Re: [Xen-devel] console problem
>>>
>>>Li, Xin B wrote:
>>>
>>>      
>>>
>>>>Don't help even I check out a completely new copy!
>>>> 
>>>>
>>>>        
>>>>
>>>Did you try killing consoled and restarting it (just invoke consoled
>>>      
>>>
>>on
>>    
>>
>>>the command line).
>>>
>>>Please open a bug in bugzilla and provide as much information 
>>>about your
>>>system as possible so I can attempt to reproduce.
>>>      
>>>
>>Thanks, I will create a bug!
>>-Xin
>>
>>    
>>
>>>Thanks,
>>>
>>>Anthony Liguori
>>>
>>>      
>>>
>>>>-Xin 
>>>>
>>>> 
>>>>
>>>>        
>>>>
>>>>>-----Original Message-----
>>>>>From: Anthony Liguori [mailto:aliguori@us.ibm.com] 
>>>>>Sent: 2005年8月5日 11:53
>>>>>To: Li, Xin B
>>>>>Cc: Stefan Berger; xen-devel@lists.xensource.com
>>>>>Subject: Re: [Xen-devel] console problem
>>>>>
>>>>>Make sure your trees are fresh. Some folks have been 
>>>>>experience problems
>>>>>because hg pull -u doesn't seem to handle deletes all that well.
>>>>>
>>>>>Also try restarting consoled.
>>>>>
>>>>>Regards,
>>>>>
>>>>>Anthony Liguori
>>>>>
>>>>>Li, Xin B wrote:
>>>>>
>>>>>   
>>>>>
>>>>>          
>>>>>
>>>>>>I'm also blocked by this issue when debugging x86_64 xenU smp.
>>>>>>-xin
>>>>>>
>>>>>>
>>>>>>
>>>>>>     
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>-----Original Message-----
>>>>>>>From: xen-devel-bounces@lists.xensource.com 
>>>>>>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>>>>>>>Anthony Liguori
>>>>>>>Sent: 2005年8月5日 10:31
>>>>>>>To: Stefan Berger
>>>>>>>Cc: xen-devel@lists.xensource.com
>>>>>>>Subject: Re: [Xen-devel] console problem
>>>>>>>
>>>>>>>Stefan Berger wrote:
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>       
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>I am experiencing a problem with the console as follows:
>>>>>>>>
>>>>>>>>
>>>>>>>>    
>>>>>>>>
>>>>>>>>         
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>This could be a timing issue.  I assume that xm console works as 
>>>>>>>expected correct?
>>>>>>>
>>>>>>>Now that the store supports watches on non-existent nodes, I 
>>>>>>>can handle 
>>>>>>>this properly.  I'll submit a patch tomorrow.
>>>>>>>
>>>>>>>Regards,
>>>>>>>
>>>>>>>Anthony Liguori
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>       
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>xm create userdomain-0 -c
>>>>>>>>Using config file "/etc/xen/userdomain-0".
>>>>>>>>Started domain UserDomain0
>>>>>>>>xc_console: Could not open tty `/dev/pts/3': No such file 
>>>>>>>>         
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>or directory
>>>>>   
>>>>>
>>>>>          
>>>>>
>>>>>>>>xm list
>>>>>>>>Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
>>>>>>>>Domain-0           0      385    -      4   r----     22.7
>>>>>>>>UserDomain0        1       31    3      1   -b---      0.9
>>>>>>>>
>>>>>>>>ls -l /dev/pts/
>>>>>>>>total 0
>>>>>>>>crw--w----  1 root tty 136, 0 Aug  4 22:15 0
>>>>>>>>crw--w----  1 root tty 136, 1 Aug  4 22:21 1
>>>>>>>>crw--w----  1 root tty 136, 2 Aug  4 22:18 2
>>>>>>>>
>>>>>>>>The source tree is up-to-date as of now.
>>>>>>>>
>>>>>>>>Stefan
>>>>>>>>
>>>>>>>>_______________________________________________
>>>>>>>>Xen-devel mailing list
>>>>>>>>Xen-devel@lists.xensource.com
>>>>>>>>http://lists.xensource.com/xen-devel
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>    
>>>>>>>>
>>>>>>>>         
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>_______________________________________________
>>>>>>>Xen-devel mailing list
>>>>>>>Xen-devel@lists.xensource.com
>>>>>>>http://lists.xensource.com/xen-devel
>>>>>>>
>>>>>>>  
>>>>>>>
>>>>>>>       
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>     
>>>>>>
>>>>>>            
>>>>>>
>>>>>   
>>>>>
>>>>>          
>>>>>
>>>> 
>>>>
>>>>        
>>>>
>>>      
>>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
>>
>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>    
>>

Re: console problem

[aq]

On 8/6/05, Anthony Liguori <aliguori@us.ibm.com> wrote:
> Yes, I'm aware of this.  The problem is that we've never had a good
> dependency system for the daemons we started.  The extra daemon has made
> the problem much worse and now we're seeing timing issues.
> 
> You can work around the problem by manually starting consoled (you may
> have to restart xenstored too).  Under the right circumstances, xend
> restart will loop because xenstored gets itself hosed.
> 
> I'm reworking a lot of this code right now to make it more robust and
> solve the problem completely.  Just hang in there a bit :-)

as you are rewriting consoled, how about renaming it (for ex, to xenconsoled) ? 

now we have xenblkd, xend, xenstored, so if all the xen-related
processes have xen as prefix (which is a good thing), we can see what
is running by just one command "ps|grep xen" :-)


regards,
aq

RE: console problem

[Li, Xin B]

 
>as you are rewriting consoled, how about renaming it (for ex, 
>to xenconsoled) ? 
>
>now we have xenblkd, xend, xenstored, so if all the xen-related
>processes have xen as prefix (which is a good thing), we can see what
>is running by just one command "ps|grep xen" :-)
>
>

Good suggesion!

>regards,
>aq
>

Re: console problem

[Keir Fraser]

On 6 Aug 2005, at 06:45, Li, Xin B wrote:

>> as you are rewriting consoled, how about renaming it (for ex,
>> to xenconsoled) ?
>>
>> now we have xenblkd, xend, xenstored, so if all the xen-related
>> processes have xen as prefix (which is a good thing), we can see what
>> is running by just one command "ps|grep xen" :-)

I'm considerign renaming to xenconsd and xencons (instead of consoled 
and xc_console). The rename is probably best done directly on our 
repository, rather than waiting for a trivial but noisy patch.

Any dissent? :-)

  -- Keir

Re: console problem

[Anthony Liguori]

Keir Fraser wrote:

>
> On 6 Aug 2005, at 06:45, Li, Xin B wrote:
>
>>> as you are rewriting consoled, how about renaming it (for ex,
>>> to xenconsoled) ?
>>>
>>> now we have xenblkd, xend, xenstored, so if all the xen-related
>>> processes have xen as prefix (which is a good thing), we can see what
>>> is running by just one command "ps|grep xen" :-)
>>
>
> I'm considerign renaming to xenconsd and xencons (instead of consoled 
> and xc_console). The rename is probably best done directly on our 
> repository, rather than waiting for a trivial but noisy patch.

Would be nice to make it xenconsoled and xenconsole.  It's just three 
extra letters and it makes what they are significantly more obvious.

Regards,

Anthony Liguori

> Any dissent? :-)
>
>  -- Keir
>
>

console problem

[UNIREA Sannicolau Mare]

Hi!
I have a dos program builted in FoxPro
- when I run in it console mode ($dosemu), it looks horrible
- when I runt it in GUI mode ($xdosemu), it looks perfect

Problem is that I want it run in console mode!
What can be the problem?

Re: console problem

[Justin Zygmont]

On Wed, 31 Aug 2005, UNIREA Sannicolau Mare wrote:

> Hi!
> I have a dos program builted in FoxPro
> - when I run in it console mode ($dosemu), it looks horrible
> - when I runt it in GUI mode ($xdosemu), it looks perfect
>
> Problem is that I want it run in console mode!
> What can be the problem?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Did you set the $term_char variable in your dosemu.conf?  also could you 
be using a UTF locale?

Re: console problem

[UNIREA Sannicolau Mare]

>
> > Hi!
> > I have a dos program builted in FoxPro
> > - when I run in it console mode ($dosemu), it looks horrible
> > - when I runt it in GUI mode ($xdosemu), it looks perfect
> >
> > Problem is that I want it run in console mode!
> > What can be the problem?

>
> Did you set the $term_char variable in your dosemu.conf?  also could you
> be using a UTF locale?
>
>

Didn't found $term_char variable in your dosemu.conf... I have the latest
version of dosemu rpm (1.2.2-1), running on a Fedora Core2

Re: console problem

[Justin Zygmont]

On Thu, 1 Sep 2005, UNIREA Sannicolau Mare wrote:

>>
>>> Hi!
>>> I have a dos program builted in FoxPro
>>> - when I run in it console mode ($dosemu), it looks horrible
>>> - when I runt it in GUI mode ($xdosemu), it looks perfect
>>>
>>> Problem is that I want it run in console mode!
>>> What can be the problem?
>
>>
>> Did you set the $term_char variable in your dosemu.conf?  also could you
>> be using a UTF locale?
>>
>>
>
> Didn't found $term_char variable in your dosemu.conf... I have the latest
> version of dosemu rpm (1.2.2-1), running on a Fedora Core2

I can't always remember the exact name, you should have been able to see 
it.

Re: console problem

[Andrzej Kaczmarczyk]

> Hi!
> I have a dos program builted in FoxPro
> - when I run in it console mode ($dosemu), it looks horrible
> - when I runt it in GUI mode ($xdosemu), it looks perfect
>
> Problem is that I want it run in console mode!
1. what do you mean by 'horrible' the font, layout, colors, controls, mode?
2. from other mail you said you have latest 1.2 version this is NOT the 
latest, fetch the cvs version, it has a number of improvements and bugfixes. 
(don't expect 1.2 or any other to be stable, it is an emulation soft anyway)

CUIN Kaczy

Re: console problem

[Alain]

>> Didn't found $term_char variable in your dosemu.conf... I have the latest
>> version of dosemu rpm (1.2.2-1), running on a Fedora Core2

Why do you use all old stuff? Many console problems where fixed in later
versions.

Alain

Re: console problem

[UNIREA Sannicolau Mare]

> > Didn't found $term_char variable in your dosemu.conf... I have the
latest
> > version of dosemu rpm (1.2.2-1), running on a Fedora Core2
>
> I can't always remember the exact name, you should have been able to see
> it.

Ok! I found it: is called $_term_char_set! What value should I give?

Re: console problem

[Justin Zygmont]

On Mon, 5 Sep 2005, UNIREA Sannicolau Mare wrote:

>>> Didn't found $term_char variable in your dosemu.conf... I have the
> latest
>>> version of dosemu rpm (1.2.2-1), running on a Fedora Core2
>>
>> I can't always remember the exact name, you should have been able to see
>> it.
>
> Ok! I found it: is called $_term_char_set! What value should I give?

well that was step #1 , now if you can just change it to ibm

Re: console problem

[UNIREA Sannicolau Mare]

> I have a dos program builted in FoxPro
> - when I run in it console mode ($dosemu), it looks horrible
> - when I runt it in GUI mode ($xdosemu), it looks perfect

>Did you set the $term_char variable in your dosemu.conf?  also could you
>be using a UTF locale?

> > Ok! I found it: is called $_term_char_set! What value should I give?
> well that was step #1 , now if you can just change it to ibm

Ok! I have changed it to ibm, but it looks the same. Shall I do enithing
else?

Re: console problem

[Stas Sergeev]

Hello.

UNIREA Sannicolau Mare wrote:
> Ok! I have changed it to ibm, but it looks the same. Shall I do 
> enithing else?
Yes, set the $_internal_char_set and the
$_external_char_set options properly, remove
the $_term_char_set from your dosemu.conf.
If that still fails, upgrade from CVS.

Re: console problem

[UNIREA Sannicolau Mare]

> Hello.
> 
> UNIREA Sannicolau Mare wrote:
> > Ok! I have changed it to ibm, but it looks the same. Shall I do 
> > enithing else?
> Yes, set the $_internal_char_set and the
> $_external_char_set options properly, remove
> the $_term_char_set from your dosemu.conf.
I'll try that

> If that still fails, upgrade from CVS.
What do you mean by that? What is CVS?

Re: console problem

[Clarence Dang]

On Thursday 15 September 2005 16:39, UNIREA Sannicolau Mare wrote:
> > If that still fails, upgrade from CVS.
>
> What do you mean by that? What is CVS?

Stas is known to not reply to such questions :P

Since, no one has answered, here is my canned response:

CVS is a way of keeping track of all past and present versions 
of source code.  With DOSEMU, it is the only way of getting a 
reasonable version since the packages on the DOSEMU site are 
outdated. 
 
The commands you want are: 
 
1. cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dosemu login 
(enter blank password) 
 
2. cvs -z6 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dosemu co -P 
dosemu 
 
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html