Re: [Xen-devel] xen 4 only seeing one keyboard and mouse

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Thu, Jul 22, 2010 at 07:54:17PM +0100, M A Young wrote:
> On Thu, 22 Jul 2010, Konrad Rzeszutek Wilk wrote:
> 
> >Looking briefly at the code, it looks to be sending two bytes down the
> >port. What does 'dmesg | grep serio' show? Something like this:
> >
> >serio: i8042 KBD port at 0x60,0x64 irq 1
> >serio: i8042 AUX port at 0x60,0x64 irq 12
> >input: AT Translated Set 2 keyboard as
> >/devices/platform/i8042/serio0/input/input4
> >
> >
> >Do you see both ports in /proc/ioports and the IRQ utilized in
> >/proc/interrupts? Are there an interrupts being sent when you type on
> >the keyboard?
> 
> For a baremetal boot
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX0 port at 0x60,0x64 irq 12
> serio: i8042 AUX1 port at 0x60,0x64 irq 12
> serio: i8042 AUX2 port at 0x60,0x64 irq 12
> serio: i8042 AUX3 port at 0x60,0x64 irq 12
> input: AT Translated Set 2 keyboard as
> /devices/platform/i8042/serio0/input/input4
> input: PS/2 Mouse as /devices/platform/i8042/serio2/input/input5
> input: AlpsPS/2 ALPS GlidePoint as
> /devices/platform/i8042/serio2/input/input6
> 
> for the xen boot
> 
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX0 port at 0x60,0x64 irq 12
> serio: i8042 AUX1 port at 0x60,0x64 irq 12
> serio: i8042 AUX2 port at 0x60,0x64 irq 12
> serio: i8042 AUX3 port at 0x60,0x64 irq 12
> input: AT Translated Set 2 keyboard as
> /devices/platform/i8042/serio0/input/input4
> input: PS/2 Generic Mouse as /devices/platform/i8042/serio2/input/input9
> psmouse.c: Failed to enable mouse on isa0060/serio2
> 
> /proc/ioports is the same for xen and baremetal. /proc/interrupts says
>   1:        120         38   IO-APIC-edge      i8042
>  12:        609        115   IO-APIC-edge      i8042
> for baremetal, and for xen
>   1:          8          0  xen-pirq-ioapic-edge  i8042
>  12:          3          0  xen-pirq-ioapic-edge  i8042
> but for xen the counts don't change.

OK. So we need to dig in this a bit further. Can you enable all of the
debugging options on Xen and Linux and send the serial log? And also
run 'apic=debug' on Xen command line. Pasi's PV-OPS Wiki page has a
whole section on what to set for a full debug enabled boot.

Another thing that might be worth checking is to boot the PV-OPS kernel
with a 3.4-testing Xen hypervisor (it actually does boot at least on my
SuperMicro X8DBN+- but don't try to use the 4.x-unstable tool stack with
it :-)).

That would eliminate the problem being in the Linux kernel.

FYI, I don't have a PS/2 mouse, but I do have a PS/2 keyboard that works
OK.

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