Displaying 20 results from an estimated 5000 matches similar to: "ehci dbgp reset during boot?"
2012 Sep 18
4
[PATCH] EHCI/Xen: propagate controller reset information to hypervisor
Just like for the in-tree early console debug port driver, the
hypervisor - when using a debug port based console - also needs to be
told about controller resets, so it can suppress using and then
re-initialize the debug port accordingly.
Other than the in-tree driver, the hypervisor driver actually cares
about doing this only for the device where the debug is port actually
in use, i.e. it needs
2013 Jul 09
6
4.3 regression in booting on a particular platform
Jan,
I was given a machine to diagnose a boot problem on xen 4.3, that used
to work on 4.2, and have bisected to the following changeset:
commit d0d4635d034f202bb401a6efa3ba61530f3854ab
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Nov 22 10:47:58 2012 +0100
implement vmap()
... and use it as basis for a proper ioremap() on x86.
Signed-off-by: Jan Beulich
2013 Mar 05
8
eDP screen corruption using linux 3.8 & xen 4.2
Konrad, et al,
I am seeing visual corruption (almost like an interlacing problem) with
i915 under Xen on some platforms using linux-3.8.
See attached file for an example of the visual corruption.
This particular platform is an HP Elitebook 2540p
The same kernel and ramdisk, when booted as native linux does not show this
corruption.
dmesg is attached, as well (out.txt) - but I did not see
2006 Jun 24
3
Installing TOO USB Drive
Greetings CentOS Fans.
I'm working on an Inspiron 9400 Laptop. It supports booting from USB
devices, so I'd like to install CentOS on a USB hard drive as an
alternative to XP.
I tried booting to the 4.3 (disk 1) CD, but it doesn't see the USB Drive
when it gets to the stage of partitioning... any idea what's involved in
getting the USB drive recognized so I can install
2012 Aug 17
4
[ANNOUNCE] Git mirror of Xen repositories available
Hi everyone,
I''m pleased to announce that a Git mirror repository is now available
(and up-to-date). This one contains several branches:
* master --> xen-unstable.hg
* staging --> staging/xen-unstable.hg
* stable-4.0 --> xen-4.0-testing.hg
* stable-4.1 --> xen-4.1-testing.hg
http://xenbits.xen.org/gitweb/?p=xen.git
git://xenbits.xen.org/xen.git
Regards,
--
2012 Jun 07
7
[PATCH] xen/hvc: Fix polling mode to work with kdb/kgdb
Fix the polling section of the hvc driver to use the global "last_hvc"
variable, rather than the ttys.
With this change debugging a xen dom0 kernel is possible via the
following kernel parameter:
kgdboc=hvc0
Signed-off-by: Ben Guthro <Benjamin.Guthro@citrix.com>
diff --git a/drivers/tty/hvc/hvc_console.c b/drivers/tty/hvc/hvc_console.c
index 2d691eb..3750e74 100644
---
2008 Jun 05
2
[PATCH 1/2] Migrate tsc values during migration
Migrate the last TSC values for more accurate timekeeping during live
migration
Signed-off-by: Dave Winchell <dwinchell@virtualiron.com>
Signed-off-by: Ben Guthro <bguthro@virtualiron.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2008 Jun 17
8
VCPU cores & sockets
Before I get to entrenched in the ACPI code - I thought I''d ping the
community to make sure nobody else has investigated this already -
Can we present cores vs sockets for guest VCPUs?
Right now, the number of total processors can be specified, but can we
specify cores per socket?
I see this potentially being an hvmloader function, as part of its acpi
build code.
Could this be
2012 Nov 02
5
[PATCH, v3] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled
Since there''s no possible caller of dbgp_external_startup() and
dbgp_reset_prep() when !USB, there''s no point in building and exporting
these functions in that case. This eliminates a build error under the
conditions listed in the subject, introduced with the merge
f1c6872e4980bc4078cfaead05f892b3d78dea64.
Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Jan
2007 Aug 27
3
[PATCH] Limit MCG Cap
Intercept guest reads of MSR_IA32_MCG_CAP and limit the number of memory banks reported to one.
This prevents us from trying to read status of non-existent banks when migrated to a machine
with fewer banks.
Signed-off-by: Ben Guthro
Signed-off-by: David Lively <dlively@virtualiron.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
2013 Sep 12
23
More Coverity-reported issues.
Another bundle of issues from Coverity triage.
The first one is in x86/mm, and looks scarier than it is. The others
are all in xen/drivers and AFAICT are pretty minor.
Cheers,
Tim.
2002 Jan 23
3
Troubles with my HDD
Hello all,
I am new to this list and hope that my mail is not OFF TOPIC. After
looking around for 2 months now, to find a solution, I will try it here now.
Now the scenario: I bought a new cool dell laptop:
INSPIRON 8100, 512MB RAM, NVIDEA GeForce2Go 32MB, 30GB Hitachi hard disk
and a DVD. I bought it with WinME preinstalled, because it wasn't
possible to get it with linux nor without an
2013 Nov 24
9
[Bug 71967] New: error message during boot
https://bugs.freedesktop.org/show_bug.cgi?id=71967
Priority: medium
Bug ID: 71967
Assignee: nouveau at lists.freedesktop.org
Summary: error message during boot
QA Contact: xorg-team at lists.x.org
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: adham3322 at gmail.com
2013 Mar 27
2
[PATCH] x86/S3: Restore broken vcpu affinity on resume (v3)
When in SYS_STATE_suspend, and going through the cpu_disable_scheduler
path, save a copy of the current cpu affinity, and mark a flag to
restore it later.
Later, in the resume process, when enabling nonboot cpus restore these
affinities.
v2:
Fix formatting problems.
remove early return in cpu_disable_scheduler() path.
v3:
Fix remaining errant tab
Move restore_vcpu_affinity() to thaw_domains(),
2014 May 16
0
Bug#748052: [Xen-devel] dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110"
>>> 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
2005 May 21
1
EHCI device
I have a motherboard here that reports USB controllers thusly in dmesg
(5.4-stable):
usb0: OHCI version 1.0, legacy support
usb0: <SiS 5571 USB controller> on ohci0
usb0: USB revision 1.0
uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ohci1: <SiS 5571 USB controller> mem 0xf7002000-0xf7002fff irq 5 at
device 3.1 on pci0
usb1:
2014 May 16
0
Bug#748052: [Xen-devel] dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110"
>>> 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
2014 May 16
0
Bug#748052: [Xen-devel] dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110"
On 16/05/14 11:08, Jan Beulich wrote:
>>>> 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
>> interrupts. I wonder if these messages from Xen's dmesg are relevant.
>> (XEN) Not enabling x2APIC: depends on iommu_supports_eim.
>> (XEN) I/O virtualisation disabled
>> (XEN)
2014 May 16
1
Bug#748052: [Xen-devel] dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile
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:
2014 May 19
0
Bug#748052: [Xen-devel] dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 faile
On Fri, 2014-05-16 at 10:05 -0700, Mike Egglestone wrote:
> Here's some more info:
>
> I went into the BIOS, Advanced Tab-->USB Configuration
> and set the following:
>
> USB Controller [Enabled]
> Legacy USB Support [Disabled]
> Port 60/64 Emulation [Disabled]
>
> Make USB Devices Non-Bootable