On Fri, Jan 29, 2021 at 12:26 AM Jürgen Groß wrote:
>
> On 29.01.21 01:51, Marek Marczykowski-Górecki wrote:
> > On Thu, Jan 28, 2021 at 07:03:00PM -0500, Boris Ostrovsky wrote:
> >>
> >> On 1/28/21 6:52 PM, Michael D Labriola wrote:
> >>> Hey, everyone. I've run into problems starting up my Xen
On Thu, Jan 28, 2021 at 7:03 PM Boris Ostrovsky
wrote:
>
>
> On 1/28/21 6:52 PM, Michael D Labriola wrote:
> > Hey, everyone. I've run into problems starting up my Xen domUs as of
> > the latest batch of stable updates. Whenever I try to create one, I
> > get a bunch of block device errors like
On Sat, Feb 16, 2019 at 2:00 PM Koenig, Christian
wrote:
>
> Am 15.02.19 um 22:29 schrieb Michael D Labriola:
> > This commit fixes DRM failures on Xen PV systems that were introduced in
> > v4.17 by the following commits:
> >
> > 82626363 drm: add func to get max iomem address v2
> > fd5fd480
On Fri, Feb 15, 2019 at 12:57 AM Juergen Gross wrote:
>
> On 14/02/2019 18:57, Christoph Hellwig wrote:
> > On Thu, Feb 14, 2019 at 07:03:38AM +0100, Juergen Gross wrote:
> >>> The thing which is different between Xen PV guests and most others (all
> >>> others(?), now that Lguest and UML have
On Wed, Feb 13, 2019 at 3:21 PM Andrew Cooper wrote:
>
> On 13/02/2019 20:15, Michael Labriola wrote:
> > On Wed, Feb 13, 2019 at 2:16 PM Konrad Rzeszutek Wilk
> > wrote:
> >> On Wed, Feb 13, 2019 at 01:38:21PM -0500, Michael Labriola wrote:
> >>> On Wed, F
On Wed, Feb 13, 2019 at 2:16 PM Konrad Rzeszutek Wilk
wrote:
>
> On Wed, Feb 13, 2019 at 01:38:21PM -0500, Michael Labriola wrote:
> > On Wed, Feb 13, 2019 at 1:16 PM Michael Labriola
> > wrote:
> > >
> > > On Wed, Feb 13, 2019 at 11:57 A
On Wed, Feb 13, 2019 at 1:16 PM Michael Labriola
wrote:
>
> On Wed, Feb 13, 2019 at 11:57 AM Konrad Rzeszutek Wilk
> wrote:
> >
> > On Wed, Feb 13, 2019 at 09:09:32AM -0700, Jan Beulich wrote:
> > > >>> On 13.02.19 at 17:00, wrote:
> > > >
On Wed, Feb 13, 2019 at 11:57 AM Konrad Rzeszutek Wilk
wrote:
>
> On Wed, Feb 13, 2019 at 09:09:32AM -0700, Jan Beulich wrote:
> > >>> On 13.02.19 at 17:00, wrote:
> > > On Wed, Feb 13, 2019 at 9:28 AM Jan Beulich wrote:
> > >> >>> On 13.02.19 at 15:10, wrote:
> > >> > Ah, so this isn't
On Wed, Feb 13, 2019 at 11:09 AM Jan Beulich wrote:
>
> >>> On 13.02.19 at 17:00, wrote:
> > On Wed, Feb 13, 2019 at 9:28 AM Jan Beulich wrote:
> >> >>> On 13.02.19 at 15:10, wrote:
> >> > Ah, so this isn't necessarily Xen-specific but rather any paravirtual
> >> > guest? That hadn't crossed
On Wed, Feb 13, 2019 at 9:28 AM Jan Beulich wrote:
>
> >>> On 13.02.19 at 15:10, wrote:
> > On Wed, Feb 13, 2019 at 5:34 AM Jan Beulich wrote:
> >>
> >> >>> On 12.02.19 at 19:46, wrote:
> >> > Konrad,
> >> >
> >> > Starting w/ v4.17, I cannot log in to GNOME w/out getting the
> >> > following
On Wed, Feb 13, 2019 at 5:34 AM Jan Beulich wrote:
>
> >>> On 12.02.19 at 19:46, wrote:
> > Konrad,
> >
> > Starting w/ v4.17, I cannot log in to GNOME w/out getting the
> > following mess in dmesg and ending up back at the GDM login screen.
> >
> > [ 28.554259] radeon_dp_aux_transfer_native:
Konrad,
Starting w/ v4.17, I cannot log in to GNOME w/out getting the
following mess in dmesg and ending up back at the GDM login screen.
[ 28.554259] radeon_dp_aux_transfer_native: 200 callbacks suppressed
[ 31.219821] radeon :01:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[
12 matches
Mail list logo
