umb0 ucom0 umodem0 detached

2019-05-03 Thread Malte Wedel 
Hello Misc,

I have OpenBSD running on a Thinkpad X1 Carbon, 3rd Gen, everything is
working great, except for the builtin 4G modem "umb0" which detaches and
disappears from time to time and needs a reboot to become available
again. I found this thread which seems to be exactly my issue:

http://openbsd-archive.7691.n7.nabble.com/Re-Current-197-Nov-5-umb0-ucom0-umodem0-detached-td330969.html

When the issue occurs, the following is written into /var/log/messages:

May  3 14:42:09 carbon /bsd: umb0 detached
May  3 14:42:09 carbon /bsd: ucom0 detached
May  3 14:42:09 carbon /bsd: umodem0 detached
May  3 14:42:26 carbon /bsd: uhub0: port 4, set config 0 at addr 2 failed
May  3 14:42:26 carbon /bsd: uhub0: device problem, disabling port 4

The issue also occurs with GENERIC.MP kernel. I guess you need the issue
reproduced with XHCI_DEBUG enabled? Is there any other way than
rebooting to enable port 4 on uhub0 again?

Regards,
Malte

OpenBSD 6.5 (CARBON) #4: Thu Apr 25 01:59:26 CEST 2019
    ma...@carbon.malte.de:/usr/src/sys/arch/amd64/compile/CARBON
real mem = 8446996480 (8055MB)
avail mem = 8189042688 (7809MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET32W (1.10 )" date 08/13/2015
bios0: LENOVO 20BTS33S01
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT
SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT TCPA SSDT UEFI MSDM BATB
FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2195.26 MHz, 06-3d-04
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2194.93 MHz, 06-3d-04
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2194.93 MHz, 06-3d-04
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2194.93 MHz, 06-3d-04
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 3 (EXP1)
acpiprt3 at acpi0: bus 4 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus -1 (EXP6)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@

Re: Filesystem corruption with ext4 and qcow2 in vmm

2019-04-18 Thread Malte Wedel 
Thanks, that did solve the problem. I guess I could have found this by
myself, I will try harder next time... it's the first time I have
installed OpenBSD and I am amazed how many things just work as expected.
While I miss some features like jails or linux compatibility, I am
impressed how usable the system is for desktop usage out of the box.

On 4/18/19 12:33 PM, Peter Hessler wrote:
> Please make sure you installed the errata for 6.4 (syspatch will do it
> for you, don't forget to reboot!).  There was a bug that was fixed in
> errata 008: "writing more than 4GB to a qcow2 volume corrupts the virtual 
> disk".
>
>
>
> On 2019 Apr 18 (Thu) at 10:06:59 +0200 (+0200), Malte Wedel wrote:
> :Hello OpenBSD,
> :
> :I was trying to run Linux inside vmm, by converting an existing
> :vmdk-image to qcow2 using qemu-img. While the configuration and setup
> :seems to be straightforward, I had filesystem corruption issues on the
> :ext4-fs inside the VM.
> :
> :This happened on two separate occasions - in the first try I was booting
> :from the cd iso-image and mounted the disk to enable serial console. As
> :soon as I changed files on the mounted disk I got errors, unmounting and
> :running fsck could not repair.
> :
> :The next try I booted the VM on a different machine, enabled serial
> :console there, and then converted to qcow2. This time the machine did
> :boot up once, but failed due to filesystem errors as soon processes
> :started to write to the filesystem. I was not able to boot it again.
> :
> :When converting the same vmdk image to raw instead of qcow2 the VM did
> :start up and run without issues.
> :
> :I am running OpenBSD 6.4. Are there known issues with qcow2 in vmm?
> :Anything I can do to help understand/analyze the issue?
> :
> :Regards,
> :Malte
> :
> :
>

Filesystem corruption with ext4 and qcow2 in vmm

2019-04-18 Thread Malte Wedel 
Hello OpenBSD,

I was trying to run Linux inside vmm, by converting an existing
vmdk-image to qcow2 using qemu-img. While the configuration and setup
seems to be straightforward, I had filesystem corruption issues on the
ext4-fs inside the VM.

This happened on two separate occasions - in the first try I was booting
from the cd iso-image and mounted the disk to enable serial console. As
soon as I changed files on the mounted disk I got errors, unmounting and
running fsck could not repair.

The next try I booted the VM on a different machine, enabled serial
console there, and then converted to qcow2. This time the machine did
boot up once, but failed due to filesystem errors as soon processes
started to write to the filesystem. I was not able to boot it again.

When converting the same vmdk image to raw instead of qcow2 the VM did
start up and run without issues.

I am running OpenBSD 6.4. Are there known issues with qcow2 in vmm?
Anything I can do to help understand/analyze the issue?

Regards,
Malte