Gentle reminder, hoping that someone with the needed knowledge chime in.
On 1/19/19 4:05 PM, Alessandro DE LAURENZIS wrote:
Dear developers,
it has already been reported [1] that suspend to disk breaks OpenGL
acceleration for 2nd and 3rd gen "Intel HD Graphics"; I'm on a Thinkpad
T430,
On Tue, Jan 22, 2019 at 10:22:39AM -0200, Martin Pieuchot wrote:
> On 31/10/18(Wed) 02:55, Artturi Alm wrote:
> > Hi,
> >
> > spam in the subject does make ttyC0 unusable in practice with urndis(4).
> > I don't like repeating myself, so all i provide is the link where this
> > behaviour requiring
This is fun.
On 17/12/18(Mon) 22:30, Alexander Bluhm wrote:
> On Fri, Nov 02, 2018 at 10:19:15PM +0100, Mark Kettenis wrote:
> > I think Ted is pointing out a different issue here that doesn't really
> > have anything to do with SMT. The issue is that in some cases we end
> > up with CPUs
On 31/10/18(Wed) 02:55, Artturi Alm wrote:
> Hi,
>
> spam in the subject does make ttyC0 unusable in practice with urndis(4).
> I don't like repeating myself, so all i provide is the link where this
> behaviour requiring while (len > 1) is explained:
>
On 2019/01/22 09:53, Giovanni Bechis wrote:
> >>> Description:
> >>On Vsphere 6.0 an OpenBSD guest does recognizes the second cpu but it
> >> cannot put it online
> >> The host uses an AMD cpu
> >>> How-To-Repeat:
> >>Start a vm on Vsphere 6.0 with smt disabled
> >>> Fix:
> >>
On 1/22/19 9:37 AM, Stuart Henderson wrote:
> On 2019/01/21 21:27, giova...@paclan.it wrote:
>>
>> Architecture: OpenBSD.amd64
>> Machine : amd64
>>> Description:
>> On Vsphere 6.0 an OpenBSD guest does recognizes the second cpu but it
>> cannot put it online
>> The
On 2019/01/21 21:27, giova...@paclan.it wrote:
>
> Architecture: OpenBSD.amd64
> Machine : amd64
> >Description:
> On Vsphere 6.0 an OpenBSD guest does recognizes the second cpu but it
> cannot put it online
> The host uses an AMD cpu
> >How-To-Repeat:
> Start
On Wed, Oct 31, 2018 at 02:55:20AM +0200, Artturi Alm wrote:
> Hi,
>
> spam in the subject does make ttyC0 unusable in practice with urndis(4).
> I don't like repeating myself, so all i provide is the link where this
> behaviour requiring while (len > 1) is explained:
>
