On Mon, Apr 12, 2010 at 11:28:11AM -0400, Mike Viau wrote:
> >Mon, 12 Apr 2010 09:24:53 +0300 <pasik@xxxxxx> wrote:
> >
> > > On Sat, Apr 10, 2010 at 10:03:51AM -0400, Mike Viau wrote:
> > > Hello,
> > >
> > > I am trying to setup a Xen serial console for easily debugging the
> full
> > > kernel boot messages even if it crashes with the help from the
> following
> > > wiki pages:
> > >
> > > [1]http://wiki.xensource.com/xenwiki/XenSerialConsole
> > > [2]http://wiki.xensource.com/xenwiki/XenParavirtOps
> > >
> > > I noticed the wiki was written for use with grub legacy.
> > >
> >
> > I wouldn't call grub1 legacy since it's still used by most of the
> distros :)
> >
> > > Therefore I am
> > > not certain if the serial console issue is with the way the grub2
> package
> > > implemented serial consoles.
> > >
> > > My problem is the machine locks up on boot after printing the
> messages:
> > >
> > > (XEN) Xen trace buffers: disabled
> > > (XEN) Std. Loglevel: All
> > > (XEN) Guest Loglevel: All
> > > (XEN) **********************************************
> > > (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
> > > (XEN) ******* This option is intended to aid debugging of Xen by
> ensuring
> > > (XEN) ******* that all output is synchronously delivered on the serial
> line.
> > > (XEN) ******* However it can introduce SIGNIFICANT latencies and
> affect
> > > (XEN) ******* timekeeping. It is NOT recommended for production use!
> > > (XEN) **********************************************
> > > (XEN) 3... 2... 1...
> > >
> >
> >
> > Can you please paste the full boot messages before it locks up?
> >
> >
>
> Unfortunately no, because I am not getting any output (kernel messages) to
> the terminal on the other machine listening. I attached a photo of what I
> see on the screen when console=com1,vga.
>
So do you see the Xen hypervisor boot messages at least?
> > > After that I just get a blank screen with a blinking "_" prompt at the
> top
> > > left hand corner of the screen. I understand that this message should
> not
> > > alone cause the kernel to stop booting at the output was actually
> found on
> > > another thread at:
> > >
> [3]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00340.html
> > >
> > > Does any have a non-standard PCI serial port Xen serial console
> working
> > > with grub2? What does your /etc/default/grub file and menuentrys look
> > > like? What does your /etc/inittab look like?
> > >
> > > My motherboard does not have a serial port or even serial headers
> > > connectors on the board. Therefor I purchased an add-in serial card to
> > > obtain serial ports on the machine.
> > >
> > > Motherboard:
> > >
>
> [4]http://www.intel.com/products/desktop/motherboards/DP55WG/DP55WG-overview.htm
> > > [5]http://ark.intel.com/Product.aspx?id=40078
> > >
> > > Add-in serial card:
> > > "Cables Unlimited IOC-2200 2-Port DB9 Serial PCI I/O Card"
> > >
>
> [6](http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=1431863&CatId=1422)
> > >
> >
> > Does the serial console work with plain baremetal Linux? (without Xen).
> >
> >
>
> No it does not. I started a thread over on the Debian mailing-list for
> this though to see if anyone there had any ideas. I have got no replies as
> of yet.
>
> Mainly I was asking if one needed to build the mcs9865-serial.ko (kernel
> module) against the kernel source for the running kernel in order to log
> kernel message during boot time or does grub implement a generic driver to
> capture the kernel message?
>
Uhm.. are you saying this serial-card requires some non-standard driver?
Then it probably can't be used as a serial console.
The PCI serial-card needs to show up as a 'real' serial port, so that
Xen can output there boot time (before any drivers are loaded in dom0 kernel).
-- Pasi
> [1]http://lists.debian.org/debian-user/2010/04/msg00765.html
>
> >
> > > My GRUB2 configuration files are also attached from:
> > >
> > > /etc/default/grub
> > > /boot/grub/grub.cfg (trying to boot "Setting up Xen 4.0.0 / PVOPS
> > > 2.6.32-4-xen-amd64 with a serial console" entry)
> > >
> > > Lastly a snippet from lspci -vvv
> > >
> > > 05:01.0 Serial controller: NetMos Technology Device 9865 (prog-if 02
> > > [16550])
> > > Subsystem: Device a000:1000
> > > 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 22
> > > Region 0: I/O ports at 1008 [size=8]
> >
> >
> > So the first port has IO port 0x1008 and uses IRQ 22.
>
> Agreed. And I also physically connected my null modem cable to both (out
> of two) serial ports to eliminate the possibility that I was connected to
> the wrong port.
>
> >
> > -- Pasi
> >
> > > Region 1: Memory at f0007000 (32-bit, non-prefetchable) [size=4K]
> > > Region 4: Memory at f0006000 (32-bit, non-prefetchable) [size=4K]
> > > Capabilities: [48] Power Management version 2
> > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> > > PME(D0+,D1+,D2+,D3hot+,D3cold+)
> > > Status: D0 PME-Enable- DSel=0 DScale=1 PME-
> > >
> > > 05:01.1 Serial controller: NetMos Technology Device 9865 (prog-if 02
> > > [16550])
> > > Subsystem: Device a000:1000
> > > 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 B routed to IRQ 21
> > > Region 0: I/O ports at 1000 [size=8]
> > > Region 1: Memory at f0005000 (32-bit, non-prefetchable) [size=4K]
> > > Region 4: Memory at f0004000 (32-bit, non-prefetchable) [size=4K]
> > > Capabilities: [48] Power Management version 2
> > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> > > PME(D0+,D1+,D2+,D3hot+,D3cold+)
> > > Status: D0 PME-Enable- DSel=0 DScale=1 PME-
> > >
> > >
> > > Thanks for looking!
> > >
> > > -M
> > >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
> -M
>
> --------------------------------------------------------------------------
>
> Stay in touch. [2]Get Hotmail & Messenger on your phone.
>
> References
>
> Visible links
> 1. http://lists.debian.org/debian-user/2010/04/msg00765.html
> 2. http://go.microsoft.com/?linkid=9724458
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home