Hi Mischa,
On Thu, Sep 24, 2020 at 08:52:55AM +0200, Mischa wrote:
> Hi All,
>
> With the last couple of -current updates I noticed a VM doesn’t come back
> after running sysupgrade, which it used to do.
it's very unlikely that this is a sysupgrade problem.
More likely something in the kernel c
> On 24 Sep 2020, at 09:15, Florian Obser wrote:
>
> Hi Mischa,
>
> On Thu, Sep 24, 2020 at 08:52:55AM +0200, Mischa wrote:
>> Hi All,
>>
>> With the last couple of -current updates I noticed a VM doesn’t come back
>> after running sysupgrade, which it used to do.
>
> it's very unlikely th
> On 24 Sep 2020, at 09:15, Florian Obser wrote:
>
> Hi Mischa,
>
> On Thu, Sep 24, 2020 at 08:52:55AM +0200, Mischa wrote:
>> Hi All,
>>
>> With the last couple of -current updates I noticed a VM doesn’t come back
>> after running sysupgrade, which it used to do.
>
> it's very unlikely th
On Thu, Sep 24, 2020 at 12:13:31PM +0200, Mischa wrote:
>
>
> > On 24 Sep 2020, at 09:15, Florian Obser wrote:
> > 3a) does it also shutdown: bisect the hypervisor (tbh I expect the problem
> > here).
>
> 6.8 bsd.rd shuts down
> 6.7 bsd.rd reboots
>
> Both VMs are running on the same host whi
> On 24 Sep 2020, at 12:23, Florian Obser wrote:
>
> On Thu, Sep 24, 2020 at 12:13:31PM +0200, Mischa wrote:
>>
>>
>>> On 24 Sep 2020, at 09:15, Florian Obser wrote:
>>> 3a) does it also shutdown: bisect the hypervisor (tbh I expect the problem
>>> here).
>>
>> 6.8 bsd.rd shuts down
>> 6.
On Thu, Sep 24, 2020 at 09:15:20AM +0200, Florian Obser wrote:
> Hi Mischa,
>
> On Thu, Sep 24, 2020 at 08:52:55AM +0200, Mischa wrote:
> > Hi All,
> >
> > With the last couple of -current updates I noticed a VM doesn’t come back
> > after running sysupgrade, which it used to do.
>
> it's very
I can confirm what Theo is seeing. On my workstation with a test VM
running the latest snapshot I get:
Welcome to the OpenBSD/amd64 6.8 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
# reboot
syncing disks... done
vmmci0: powerdown
rebooting...
Using drive 0, partition 3.
On Thu, Sep 24, 2020 at 12:47:30PM +0200, Mischa wrote:
> >
> > One quirk of the archive: It just creates a directory every night, no
> > matter if a snap was built or not, you can check with what(1) if you
> > actually have a different kernel to the one you already tested.
>
> for i in $(jot -w
> On 24 Sep 2020, at 13:52, Sebastien Marie wrote:
>
> On Thu, Sep 24, 2020 at 12:47:30PM +0200, Mischa wrote:
>>>
>>> One quirk of the archive: It just creates a directory every night, no
>>> matter if a snap was built or not, you can check with what(1) if you
>>> actually have a different kern
On 2020-09-17 23:42, Jonathan Gray wrote:
The big difference between July and now is the Mesa 20.1 update which
occurred at the end of August.
It seems to point to memory being incorrectly handled in the kernel.
There never seems to be a simple test case to reproduce problems.
Problems only see
Hello to all
I just downloaded and installed OpenBSD 6.8 (snapshot: 23-Sep-2020)
After a while, the mouse pointer stops moving and everything freezes. Only
hard reset is possible.
In OpenBSD Current (snapshot: 23 Sep 2020)
the amdgpu driver (for my system which is a AMD Ryzen, Vega 10, codename
Picasso) there is a screen tearing. I did not managed to fix it using a
xorg.conf file.
12 matches
Mail list logo