[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel


  • To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Matej Zary <zary@xxxxxxxxx>
  • Date: Thu, 22 Apr 2010 14:30:58 +0200
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Thu, 22 Apr 2010 05:32:38 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcriF6k4TQei7heRQOu8O79a3yUChQ==
  • Thread-topic: Re: [Xen-users] Serial console - Xen 4.0 - debugging pv_ops 2.6.31 dom0 kernel

On Tue, 2010-04-20 at 20:36 +0300, Pasi KÃrkkÃinen wrote:
> On Mon, Apr 19, 2010 at 04:56:48PM +0200, Matej Zary wrote:
> > Hello all,
> > 
> > I compiled from source Xen 4.0 with the default 2.6.31.13 pv_ops dom0 
> > kernel on barebone Debian Lenny installation. Problem is, this dom0 kernel 
> > won't boot. First complaining about ioapic, so I tried with noioapci, still 
> > no luck (the screen blackens during boot and computer reboots). :( So here 
> > comes serial console. This PC is older shady Asrock nForce 430 board with 
> > AMD Athlon X2 1,9 Ghz CPU => no onboard serial port. Therefore I added PCI 
> > card with i/o ports. 
> > 
> > dmesg | grep tty
> > [    0.004000] console [tty0] enabled
> > [    0.923873] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > [    0.924008] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > [    7.887891] 0000:01:0a.0: ttyS1 at I/O 0xec00 (irq = 18) is a 16550A
> > [    7.887891] 0000:01:0a.0: ttyS2 at I/O 0xe480 (irq = 18) is a 16550A
> > 
> > 
> > According to http://wiki.xensource.com/xenwiki/XenSerialConsole I used 
> > usb->com cable on my laptop and tried the link test with minicom on both 
> > sides - chatting worked flawlessly (using /dev/ttyS1 on "server" side). 
> > 
> > Problem is, I'm not able configure boot options for Xen to work with this 
> > serial port. My grub menu.lst (one from many experiments):
> > 
> > title        Xen 4.0, Linux kernel 2.6.31.13 with serial console
> > root         (hd0,0)
> > kernel       /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all 
> > com2=115200, 8n1, 0xec00, 18 console=com2
> 
> 
> Try this instead:
> kernel       /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all 
> com1=115200,8n1,0xec00,18 console=com1
> 
> You can't have spaces between the parameters.
> dom0 kernel line looks OK.
> 
> If that doesn't work then try specifying 0 as the IRQ (instead of 18).
> Also.. hmm.. I wonder if the irq should be in hex or in decimal.. 


Yes, only the spaces were the problem. :)


So to summarize (might be another example on
http://wiki.xensource.com/xenwiki/XenSerialConsole - at this time
there's no cfg example for additional cheap I/O ports PCI card yet):

dmesg | grep tty
[    0.004000] console [tty0] enabled
[    1.444943] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    1.445716] 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    8.433667] 0000:01:0a.0: ttyS1 at I/O 0xec00 (irq = 18) is a 16550A
[    8.433667] 0000:01:0a.0: ttyS2 at I/O 0xe480 (irq = 18) is a 16550A


lspci -vvv

01:0a.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O
Controller (rev 01) (prog-if 02)
        Subsystem: LSI Logic / Symbios Logic 1P2S
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
        Interrupt: pin A routed to IRQ 18
        Region 0: I/O ports at ec00 [size=8]
        Region 1: I/O ports at e480 [size=8]
        Region 2: I/O ports at e400 [size=8]
        Region 3: I/O ports at e080 [size=8]
        Region 4: I/O ports at e000 [size=8]
        Region 5: I/O ports at dc00 [size=16]
        Kernel driver in use: parport_serial
        Kernel modules: parport_serial



/boot/grub/menu.lst

title        Xen 4.0, Linux kernel 2.6.31.13 with serial console
root         (hd0,0)
kernel       /boot/xen-4.0.gz dom0_mem=512M loglvl=all guest_loglvl=all
com1=38400,8n1,0xec00,18 console=com1
module       /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro console=hvc0
earlyprintk=xen nomodeset
module       /boot/initrd.img-2.6.31.13


Confusing parameters are com1=38400 and console=com1 (because the used
port is actually Com2 - ttyS1). It doesn't matter whether is there com1
or com2=38400 and console=com2, it works the same..


So again, many thanks all who tried to help.

Regards 

Matej 



> 
> -- Pasi
> 
> > module       /boot/vmlinuz-2.6.31.13 root=/dev/sda1 ro console=hvc0 
> > earlyprintk=xen nomodeset
> > module       /boot/initrd.img-2.6.31.13
> > 
> > Tried many  variations, but still no luck getting the xen boot process on 
> > my serial connected console.
> > 
> > Any hints?
> > 
> > 
> > Many thanks.
> > 
> > Matej

<<attachment: winmail.dat>>

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.