search for: s1200btl

...XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffa00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000240000000 (usable) (XEN) ACPI: RSDP 000F0410, 0024 (r2 INTEL) (XEN) ACPI: XSDT BEFFDE18, 00AC (r1 INTEL S1200BTL 6222004 INTL 20090903) (XEN) ACPI: FACP BEFFCD98, 00F4 (r4 INTEL S1200BTL 6222004 INTL 20090903) (XEN) ACPI: DSDT BEFEE018, CE48 (r2 INTEL S1200BTL 0 INTL 20100331) (XEN) ACPI: FACS BEFFDD40, 0040 (XEN) ACPI: APIC BEFFB018, 0652 (r3 INTEL S1200BTL 6222004 INTL 20090903) (XEN) ACPI: SPM...

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

...00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000023fffffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] SMBIOS 2.6 present. [ 0.000000] DMI: Intel Corporation S1200BTL/S1200BTL, BIOS S1200BT.86B.02.00.0041.120520121743 12/05/2012 [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x240000 max_arch_pfn = 0x40...

...f] reserved [ 0.000000] Xen: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved [ 0.000000] Xen: [mem 0x0000000100000000-0x000000023fffffff] usable [ 0.000000] Notice: NX (Execute Disable) protection missing in CPU! [ 0.000000] SMBIOS 2.6 present. [ 0.000000] DMI: Intel Corporation S1200BTL/S1200BTL, BIOS S1200BT.86B.02.00.0041.120520121743 12/05/2012 [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x240000 max_arch_pfn = 0x40...

Attached are the most recent boot logs. All tests have been on the same system, an Intel S1200BTL motherboard. I did 2 boots, both with kernel 3.13. First one into xen 4.3 and the 2nd into xen 4.1. The keyboard works on xen 4.1, not on 4.3. Cheers, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel...

...+0400, rush wrote: > > Hi, > > > > There are several Not tainted lines in old messages file. There are all of them: > > > > Sep 10 22:35:33 xen-dom0 kernel: [24183.985513] Pid: 2605, comm: > > debootstrap Not tainted 3.0.0-1-amd64 #1 Intel Corporation > > S1200BTL/S1200BTL > > Sep 10 22:35:33 xen-dom0 kernel: [24183.985621] RIP: > > e030:[<ffffffff810106db>] [<ffffffff810106db>] > > __sanitize_i387_state+0x23/0xe1 > > Source/disassembly: > > void __sanitize_i387_state(struct task_struct *tsk) > { > u64 xsta...

On Fri, 2014-05-23 at 08:52 +0100, Jan Beulich wrote: > > I am a noob when working with source code. How do I bump my xen up to 4.3.3? > > I guess this > http://wiki.xenproject.org/wiki/Compiling_Xen_From_Source > should help you. Since this only needs a new hypervisor binary and not a full set of tools etc to reproduce I think it can be simplified to replacing the previous

>>> On 16.05.14 at 17:31, <ijc at hellion.org.uk> wrote: > On Fri, 2014-05-16 at 11:08 +0100, Jan Beulich wrote: >> And finally, looking at the IRQ usage, this >> >> [ 2.087722] xen: registering gsi 22 triggering 0 polarity 1 >> [ 2.087731] xen: --> pirq=22 -> irq=22 (gsi=22) >> [ 2.100161] xen: registering gsi 20 triggering 0

On Fri, 2014-05-16 at 11:08 +0100, Jan Beulich wrote: Thanks for taking a look. FYI Mike has since mentioned on the bug report that 4.1 worked. I've asked for logs of Xen 4.1 + Linux 3.13 and Xen 4.3 + Linux 3.13 for comparison. > >>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: > > So it seems like dom0 is unable to (correctly) bind to some hardware >

...eyboard this is (USB, PS2?) # #Also the precise version of the kernel might be useful. You say "3.13" #but do you mean Debian's 3.13? What is the actual version? # #You may find you have better luck with this question on the upstream #xen-users list. USB Keyboard plugged into a Intel S1200BTL Motherboard. After ssh'ing into the box. root at xen-3:~# uname -a Linux xen-3 3.13-1-amd64 #1 SMP Debian 3.13.10-1 (2014-04-15) x86_64 GNU/Linux root at xen-3:~# xl list Name ID Mem VCPUs State Time(s) Domain-0...

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum