Re: macbook - uvideo0: can't find video interface

2020-05-31 Thread Jan Stary
On May 31 13:24:20, h...@stare.cz wrote:
> On May 31 12:16:58, h...@stare.cz wrote:
> > Hi,
> > 
> > On May 26 22:15:28, feine...@logic.at wrote:
> > > I think that my fix for video(1) posted at
> > > https://marc.info/?l=openbsd-tech=159048565528060=2 could also
> > > remedy your problem of video(1) crashing reported at
> > > https://marc.info/?l=openbsd-misc=158800058009113=2 .
> > 
> > On May 30 23:52:43, patr...@blueri.se wrote:
> > > On Sat, May 30, 2020 at 07:47:17PM +0200, Jan Stary wrote:
> > > > On May 30 18:50:12, h...@stare.cz wrote:
> > > > > This is current/amd64 on a MacBook2,1 (dmesg below)
> > > > > With the latest upgrade, it has lost video0:
> > > > > 
> > > > > uvideo0 at uhub0 port 4 configuration 1 interface 0 "Micron Built-in 
> > > > > iSight" rev 2.00/1.84 addr 2
> > > > > uvideo0: can't find interface assoc descriptor
> > > > 
> > > > Similar thing happens with current/i386 on a MacBook1,1 (dmesg below):
> > > > uvideo0: can't find video interface
> > > > 
> > > > Jan
> > > 
> > > Yeah, this is due to the change to support multiple cameras in one
> > > device.  You can try this diff, let me know if this works on both
> > > of your machines.
> > 
> > With Patrick's diff, my amd64 Macbook2,1 has video0 at uvideo0 again.
> > I compiled the patched kernel with UVIDEO_DEBUG, dmesg below. Thanks!
> 
> On the i386 macbook, the UVIDEO_DEBUG messages spam the dmesg so much
> that I only have the uvideo tail in dmesg.boot (see below).
> I will recompile without UVIDEO_DEBUG.

dmesg below

Notice how uvideo0 frst ataches as "Apple Computer Bluetooth",
detaches, and ataches again as "Micron Built-in iSight"

Jan


OpenBSD 6.7-current (GENERIC.MP) #0: Sun May 31 13:44:04 CEST 2020
h...@mb32.stare.cz:/usr/src/sys/arch/i386/compile/GENERIC.MP
real mem  = 2113323008 (2015MB)
avail mem = 2059010048 (1963MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 07/29/05, SMBIOS rev. 2.4 @ 0xe7490 (36 entries)
bios0: vendor Apple Computer, Inc. version "MB11.88Z.0061.B03.0610121324" date 
10/12/06
bios0: Apple Computer, Inc. MacBook1,1
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) USB7(S3) EC__(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Genuine Intel(R) CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz, 
06-0e-08
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,NXE,PERF,SENSOR,MELTDOWN
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Genuine Intel(R) CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz, 
06-0e-08
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,NXE,PERF,SENSOR,MELTDOWN
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
gcpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: !C4(100@55 mwait@0x31), !C3(500@1 mwait@0x20), !C2(500@1 
mwait@0x10), C1(1000@1 mwait), PSS
acpicpu1 at acpi0: !C4(100@55 mwait@0x31), !C3(500@1 mwait@0x20), !C2(500@1 
mwait@0x10), C1(1000@1 mwait), PSS
acpisbs0 at acpi0: SBS0 model "ASMB016" serial 35580 type LION oem "DP"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
"APP0002" at acpi0 not configured
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
"PNP0A08" at acpi0 not configured
"APP0001" at acpi0 not configured
"APP0003" at acpi0 not configured
"ACPI0001" at acpi0 not configured
"IFX0101" at acpi0 not configured
acpicmos0 at acpi0
acpivideo0 at acpi0: GFX0
bios0: ROM list: 0xc/0xe600!
cpu0: Enhanced SpeedStep 1998 MHz: speeds: 2000, 1833, 1667, 1500, 1333, 1000 
MHz
memory map conflict 0xe00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xfffb/0x3
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0x8000, size 0x1000
inteldrm0: apic 1 int 16, I945GM, gen 3
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and Frequency, 
rev 0x03) at pci0 dev 7 function 0 not configured
azalia0 at pci0 dev 27 function 

Re: macbook - uvideo0: can't find video interface

2020-05-31 Thread Jan Stary
On May 31 12:16:58, h...@stare.cz wrote:
> Hi,
> 
> On May 26 22:15:28, feine...@logic.at wrote:
> > I think that my fix for video(1) posted at
> > https://marc.info/?l=openbsd-tech=159048565528060=2 could also
> > remedy your problem of video(1) crashing reported at
> > https://marc.info/?l=openbsd-misc=158800058009113=2 .
> 
> On May 30 23:52:43, patr...@blueri.se wrote:
> > On Sat, May 30, 2020 at 07:47:17PM +0200, Jan Stary wrote:
> > > On May 30 18:50:12, h...@stare.cz wrote:
> > > > This is current/amd64 on a MacBook2,1 (dmesg below)
> > > > With the latest upgrade, it has lost video0:
> > > > 
> > > > uvideo0 at uhub0 port 4 configuration 1 interface 0 "Micron Built-in 
> > > > iSight" rev 2.00/1.84 addr 2
> > > > uvideo0: can't find interface assoc descriptor
> > > 
> > > Similar thing happens with current/i386 on a MacBook1,1 (dmesg below):
> > > uvideo0: can't find video interface
> > > 
> > >   Jan
> > 
> > Yeah, this is due to the change to support multiple cameras in one
> > device.  You can try this diff, let me know if this works on both
> > of your machines.
> 
> With Patrick's diff, my amd64 Macbook2,1 has video0 at uvideo0 again.
> I compiled the patched kernel with UVIDEO_DEBUG, dmesg below. Thanks!

On the i386 macbook, the UVIDEO_DEBUG messages spam the dmesg so much
that I only have the uvideo tail in dmesg.boot (see below).
I will recompile without UVIDEO_DEBUG.

At any rate, video0 at uvideo0 exists now - thanks.

Jan


uvideo0: send 3 bytes data to offset 0x1b
uvideo0: ucode data len=3, request=0x33
uvideo0: send 3 bytes data to offset 0x33
uvideo0: ucode data len=3, request=0x43
uvideo0: send 3 bytes data to offset 0x43
uvideo0: ucode data len=3, request=0x4b
uvideo0: send 3 bytes data to offset 0x4b
uvideo0: ucode data len=3, request=0x53
uvideo0: send 3 bytes data to offset 0x53
uvideo0: ucode data len=1023, request=0x100
uvideo0: send 50 bytes data to offset 0x100
uvideo0: send 50 bytes data to offset 0x132
uvideo0: send 50 bytes data to offset 0x164
uvideo0: send 50 bytes data to offset 0x196
uvideo0: send 50 bytes data to offset 0x1c8
uvideo0: send 50 bytes data to offset 0x1fa
uvideo0: send 50 bytes data to offset 0x22c
uvideo0: send 50 bytes data to offset 0x25e
uvideo0: send 50 bytes data to offset 0x290
uvideo0: send 50 bytes data to offset 0x2c2
uvideo0: send 50 bytes data to offset 0x2f4
uvideo0: send 50 bytes data to offset 0x326
uvideo0: send 50 bytes data to offset 0x358
uvideo0: send 50 bytes data to offset 0x38a
uvideo0: send 50 bytes data to offset 0x3bc
uvideo0: send 50 bytes data to offset 0x3ee
uvideo0: send 50 bytes data to offset 0x420
uvideo0: send 50 bytes data to offset 0x452
uvideo0: send 50 bytes data to offset 0x484
uvideo0: send 50 bytes data to offset 0x4b6
uvideo0: send 23 bytes data to offset 0x4e8
uvideo0: ucode data len=1023, request=0x4ff
uvideo0: send 50 bytes data to offset 0x4ff
uvideo0: send 50 bytes data to offset 0x531
uvideo0: send 50 bytes data to offset 0x563
uvideo0: send 50 bytes data to offset 0x595
uvideo0: send 50 bytes data to offset 0x5c7
uvideo0: send 50 bytes data to offset 0x5f9
uvideo0: send 50 bytes data to offset 0x62b
uvideo0: send 50 bytes data to offset 0x65d
uvideo0: send 50 bytes data to offset 0x68f
uvideo0: send 50 bytes data to offset 0x6c1
uvideo0: send 50 bytes data to offset 0x6f3
uvideo0: send 50 bytes data to offset 0x725
uvideo0: send 50 bytes data to offset 0x757
uvideo0: send 50 bytes data to offset 0x789
uvideo0: send 50 bytes data to offset 0x7bb
uvideo0: send 50 bytes data to offset 0x7ed
uvideo0: send 50 bytes data to offset 0x81f
uvideo0: send 50 bytes data to offset 0x851
uvideo0: send 50 bytes data to offset 0x883
uvideo0: send 50 bytes data to offset 0x8b5
uvideo0: send 23 bytes data to offset 0x8e7
uvideo0: ucode data len=1023, request=0x8fe
uvideo0: send 50 bytes data to offset 0x8fe
uvideo0: send 50 bytes data to offset 0x930
uvideo0: send 50 bytes data to offset 0x962
uvideo0: send 50 bytes data to offset 0x994
uvideo0: send 50 bytes data to offset 0x9c6
uvideo0: send 50 bytes data to offset 0x9f8
uvideo0: send 50 bytes data to offset 0xa2a
uvideo0: send 50 bytes data to offset 0xa5c
uvideo0: send 50 bytes data to offset 0xa8e
uvideo0: send 50 bytes data to offset 0xac0
uvideo0: send 50 bytes data to offset 0xaf2
uvideo0: send 50 bytes data to offset 0xb24
uvideo0: send 50 bytes data to offset 0xb56
uvideo0: send 50 bytes data to offset 0xb88
uvideo0: send 50 bytes data to offset 0xbba
uvideo0: send 50 bytes data to offset 0xbec
uvideo0: send 50 bytes data to offset 0xc1e
uvideo0: send 50 bytes data to offset 0xc50
uvideo0: send 50 bytes data to offset 0xc82
uvideo0: send 50 bytes data to offset 0xcb4
uvideo0: send 23 bytes data to offset 0xce6
uvideo0: ucode data len=1023, request=0xcfd
uvideo0: send 50 bytes data to offset 0xcfd
uvideo0: send 50 bytes data to offset 0xd2f
uvideo0: send 50 bytes data to offset 0xd61
uvideo0: send 50 bytes data to offset 0xd93
uvideo0: send 50 bytes data 

Re: macbook - uvideo0: can't find video interface

2020-05-31 Thread Jan Stary
Hi,

On May 26 22:15:28, feine...@logic.at wrote:
> I think that my fix for video(1) posted at
> https://marc.info/?l=openbsd-tech=159048565528060=2 could also
> remedy your problem of video(1) crashing reported at
> https://marc.info/?l=openbsd-misc=158800058009113=2 .

On May 30 23:52:43, patr...@blueri.se wrote:
> On Sat, May 30, 2020 at 07:47:17PM +0200, Jan Stary wrote:
> > On May 30 18:50:12, h...@stare.cz wrote:
> > > This is current/amd64 on a MacBook2,1 (dmesg below)
> > > With the latest upgrade, it has lost video0:
> > > 
> > > uvideo0 at uhub0 port 4 configuration 1 interface 0 "Micron Built-in 
> > > iSight" rev 2.00/1.84 addr 2
> > > uvideo0: can't find interface assoc descriptor
> > 
> > Similar thing happens with current/i386 on a MacBook1,1 (dmesg below):
> > uvideo0: can't find video interface
> > 
> > Jan
> 
> Yeah, this is due to the change to support multiple cameras in one
> device.  You can try this diff, let me know if this works on both
> of your machines.

With Patrick's diff, my amd64 Macbook2,1 has video0 at uvideo0 again.
I compiled the patched kernel with UVIDEO_DEBUG, dmesg below. Thanks!

video(1) still doesn't work though: running 'video -v'
opens a black window of nothing, saying

hans@mb64:~$ video -v
video device /dev/video:
  encodings: uyvy
  frame sizes (width x height, in pixels) and rates (in frames per second):
320x240: 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 
30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30
352x288: 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 
30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30
640x480: 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 
30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30, 30
  controls: brightness, saturation, gamma, sharpness
Xv adaptor 0, Intel(R) Textured Video:
  encodings: yuy2, uyvy, yv12
  max size: 1280x800
using uyvy encoding
using frame size 640x480 (614400 bytes)
using default frame rate
video: ioctl VIDIOC_DQBUF: Invalid argument

The ioctl error message is after I pressed 'q' to quit.

These are the UVIDEO_DEBUG messages when running that:


uvideo0: uvideo_open: sc=0x8011d000
uvideo0: uvideo_find_ctrl: control not supported by device!
uvideo0: uvideo_find_ctrl: control not supported by device!
uvideo0: uvideo_find_ctrl: control not supported by device!
uvideo0: uvideo_s_fmt: requested width=640, height=480
uvideo0: uvideo_find_res: frame index 0: width=640, height=480
uvideo0: uvideo_find_res: frame index 1: width=352, height=288
uvideo0: uvideo_find_res: frame index 2: width=320, height=240
uvideo0: SET probe request successfully
bmHint=0x01
bFormatIndex=0x01
bFrameIndex=0x01
dwFrameInterval=33 (100ns units)
wKeyFrameRate=0
wPFrameRate=0
wCompQuality=0
wCompWindowSize=0
wDelay=0 (ms)
dwMaxVideoFrameSize=0 (bytes)
dwMaxPayloadTransferSize=0 (bytes)
uvideo0: GET probe request successfully
bmHint=0x00
bFormatIndex=0x01
bFrameIndex=0x01
dwFrameInterval=33 (100ns units)
wKeyFrameRate=0
wPFrameRate=0
wCompQuality=0
wCompWindowSize=0
wDelay=33 (ms)
dwMaxVideoFrameSize=614400 (bytes)
dwMaxPayloadTransferSize=3072 (bytes)
fixed dwMaxVideoFrameSize=614400, width=640 height=480 bpp=16
uvideo0: SET commit request successfully
uvideo0: uvideo_s_fmt: offered width=640, height=480
uvideo0: SET probe request successfully
bmHint=0x01
bFormatIndex=0x01
bFrameIndex=0x01
dwFrameInterval=33 (100ns units)
wKeyFrameRate=0
wPFrameRate=0
wCompQuality=0
wCompWindowSize=0
wDelay=0 (ms)
dwMaxVideoFrameSize=0 (bytes)
dwMaxPayloadTransferSize=0 (bytes)
uvideo0: GET probe request successfully
bmHint=0x00
bFormatIndex=0x01
bFrameIndex=0x01
dwFrameInterval=33 (100ns units)
wKeyFrameRate=0
wPFrameRate=0
wCompQuality=0
wCompWindowSize=0
wDelay=33 (ms)
dwMaxVideoFrameSize=614400 (bytes)
dwMaxPayloadTransferSize=3072 (bytes)
fixed dwMaxVideoFrameSize=614400, width=640 height=480 bpp=16
uvideo0: SET commit request successfully
uvideo0: uvideo_reqbufs: count=4
uvideo0: allocated 2457600 bytes mmap buffer
uvideo0: uvideo_reqbufs: index=0, offset=0, length=614400
uvideo0: uvideo_reqbufs: index=1, offset=614400, length=614400
uvideo0: uvideo_reqbufs: index=2, offset=1228800, length=614400
uvideo0: uvideo_reqbufs: index=3, offset=1843200, length=614400
uvideo0: uvideo_querybuf: index=0, offset=0, length=614400
uvideo0: uvideo_querybuf: index=1, offset=614400, length=614400
uvideo0: uvideo_querybuf: index=2, offset=1228800, length=614400
uvideo0: uvideo_querybuf: index=3, offset=1843200, length=614400
uvideo0: uvideo_vs_open
uvideo0: set alternate iface to bAlternateSetting=0x01 psize=3072 
max_packet_size=3072
uvideo0: open pipe for bEndpointAddress=0x82
uvideo0: nframes=40
uvideo0: uvideo_vs_alloc_isoc
uvideo0: allocated 122880 bytes isoc VS xfer buffer
uvideo0: allocated 122880 bytes isoc VS xfer buffer
uvideo0: allocated 122880 bytes isoc VS xfer buffer
uvideo0: uvideo_vs_alloc_frame: allocated 

Re: macbook - uvideo0: can't find video interface

2020-04-28 Thread Jan Stary
On Apr 28 07:52:59, rgci...@disroot.org wrote:
> On Mon, Apr 27, 2020 at 05:12:59PM +0200, Jan Stary wrote:
> > Thanks for the clue, video0 at uvideo0 is detected again
> > (dmesg below; NB: a different macbook with the same symptom).
> > 
> 
> note
> you're now showing an amd64 kernel log
> your first post all the logs were i386

Yes, that's what I mean by

NB: a different macbook with the same symptom

> so your analysis (one machine crashing, one machine just hangs)

No.

'video' crashes with the ioctl error,
'video -g' runs without output;
on both machines.

For completeness, both dmesgs below (macbook2,1 and macbook1,1)
with uvideo.c that has the -r1.202 -r1.203 diff reverted.

Jan


OpenBSD 6.7-beta (GENERIC.MP) #0: Mon Apr 27 14:24:47 CEST 2020
h...@mb64.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3171909632 (3024MB)
avail mem = 3063234560 (2921MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (37 entries)
bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date 06/27/07
bios0: Apple Inc. MacBook2,1
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) USB7(S3) EC__(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.65 MHz, 06-0f-06
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.25 MHz, 06-0f-06
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: !C3(100@55 mwait@0x31), !C2(500@1 mwait@0x10), C1(1000@1 
mwait), PSS
acpicpu1 at acpi0: !C3(100@55 mwait@0x31), !C2(500@1 mwait@0x10), C1(1000@1 
mwait), PSS
acpisbs0 at acpi0: SBS0 model "ASMB016" serial 19351 type LION oem "DP"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
"APP0002" at acpi0 not configured
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x
"APP0001" at acpi0 not configured
"APP0003" at acpi0 not configured
"ACPI0001" at acpi0 not configured
acpicmos0 at acpi0
acpivideo0 at acpi0: GFX0
cpu0: Enhanced SpeedStep 2161 MHz: speeds: 2167, 2000, 1833, 1667, 1500, 1333, 
1000 MHz
memory map conflict 0xbef0/0x10
memory map conflict 0xbf00/0x100
memory map conflict 0xf00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xfffb/0x3
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xc000, size 0x1000
inteldrm0: apic 1 int 16, I945GM, gen 3
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and Frequency, 
rev 0x03) at pci0 dev 7 function 0 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Sigmatel STAC9220/1
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22, Yukon-2 EC 
rev. A3 (0x2): apic 1 int 16
msk0 at mskc0 port A: address 00:1b:63:36:2b:5d
eephy0 at msk0 phy 0: 88E Gigabit PHY, rev. 2
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
athn0 at pci2 dev 0 function 0 "Atheros AR5418" rev 0x01: apic 1 int 17
athn0: MAC AR5418 rev 2, RF AR5133 (2T3R), ROM rev 4, address 00:1c:b3:c4:b2:ae
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 1 int 21
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 1 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 1 int 18
uhci3 at pci0 dev 29 

Re: macbook - uvideo0: can't find video interface

2020-04-27 Thread rgc
On Mon, Apr 27, 2020 at 05:12:59PM +0200, Jan Stary wrote:
> Thanks for the clue, video0 at uvideo0 is detected again
> (dmesg below; NB: a different macbook with the same symptom).
> 

note
you're now showing an amd64 kernel log
your first post all the logs were i386

so your analysis (one machine crashing, one machine just hangs)
might be off a bit

~ rgc



Re: macbook - uvideo0: can't find video interface

2020-04-27 Thread Jan Stary
On Apr 27 10:55:15, sema...@online.fr wrote:
> On Mon, Apr 27, 2020 at 10:26:23AM +0200, Jan Stary wrote:
> > This is current/i386 on an old macbook (dmesgs below).
> > It runs fine except it no longer recognizes the video0 camera
> > ist used to. I am seeing the same on another macbook (amd64).
> > 
> > [...]
> >
> > Looking at uvideo.c history, I naively spot
> > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uvideo.c.diff?r1=1.202=1.203=h
> > - the commit message says
> > 
> > Add support for integrated USB cameras with two functions, as
> > seen on a Lenovo X395 which combines normal webcam functionality
> > with another IR camera, by parsing the USB interface association
> > descriptors.  This fixes the symptom of uvideo(4) complaining
> > about too many headers and not providing any functionality at all.
> > 
> > My camera definitely is an "integrated USB camera",
> > the diff introduces the "can't find video interface" error message,
> > and the change fits into my very sparse timeline of works/breaks.
> > 
> > How can I help debug this?
> > 
> > Jan
> 
> you could try to build a kernel with this specific commit reverted, and try to
> see if your webcam works.
> 
> the commit seems relatively self contained (do not introduce too much 
> changes),
> and posterious commits seems to not rely on it, so I assume just reverting it
> should works.
> 
> this way it would be know that it is this commit which introduces a 
> regression,
> and someone might figure why.


Thanks for the clue, video0 at uvideo0 is detected again
(dmesg below; NB: a different macbook with the same symptom).

video(1) crashes though, after a few seconds of a black window:
video: ioctl VIDIOC_DQBUF: Invalid argument.
Looking at ktrace, I just spot

 27453 videoCALL  ioctl(4,VIDIOC_DQBUF,0x7f7d96b8)
 27453 videoRET   ioctl -1 errno 22 Invalid argument

(I can send the whole trace if someone cares.)

'video -g -o video.out' does not crash,
but just sits there, producing empty output,
and does not exit on `q', needs to be killed.

I have no idea why one crashes with VIDIOC_DQBUF
and the other doesn't. Nothing in the postsequent commits
(i.e. after the 1.203 which I reversed) seems to touch that.

What else should I test?

Jan


OpenBSD 6.7-beta (GENERIC.MP) #0: Mon Apr 27 14:24:47 CEST 2020
h...@mb64.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3171909632 (3024MB)
avail mem = 3063234560 (2921MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (37 entries)
bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date 06/27/07
bios0: Apple Inc. MacBook2,1
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) USB7(S3) EC__(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.65 MHz, 06-0f-06
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.25 MHz, 06-0f-06
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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR,MELTDOWN
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: !C3(100@55 mwait@0x31), !C2(500@1 mwait@0x10), C1(1000@1 
mwait), PSS
acpicpu1 at acpi0: !C3(100@55 mwait@0x31), !C2(500@1 mwait@0x10), C1(1000@1 
mwait), PSS
acpisbs0 at acpi0: SBS0 model "ASMB016" serial 19351 type LION oem "DP"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
"APP0002" at acpi0 not configured
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x
"APP0001" at acpi0 not configured
"APP0003" at acpi0 not configured
"ACPI0001" at acpi0 not configured
acpicmos0 at acpi0
acpivideo0 at acpi0: GFX0
cpu0: Enhanced SpeedStep 2161 MHz: speeds: 2167, 2000, 1833, 1667, 1500, 1333, 
1000 MHz
memory map 

Re: macbook - uvideo0: can't find video interface

2020-04-27 Thread Sebastien Marie
On Mon, Apr 27, 2020 at 10:26:23AM +0200, Jan Stary wrote:
> This is current/i386 on an old macbook (dmesgs below).
> It runs fine except it no longer recognizes the video0 camera
> ist used to. I am seeing the same on another macbook (amd64).
> 
> [...]
>
> Looking at uvideo.c history, I naively spot
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uvideo.c.diff?r1=1.202=1.203=h
> - the commit message says
> 
>   Add support for integrated USB cameras with two functions, as
>   seen on a Lenovo X395 which combines normal webcam functionality
>   with another IR camera, by parsing the USB interface association
>   descriptors.  This fixes the symptom of uvideo(4) complaining
>   about too many headers and not providing any functionality at all.
> 
> My camera definitely is an "integrated USB camera",
> the diff introduces the "can't find video interface" error message,
> and the change fits into my very sparse timeline of works/breaks.
> 
> How can I help debug this?
> 
>   Jan

you could try to build a kernel with this specific commit reverted, and try to
see if your webcam works.

the commit seems relatively self contained (do not introduce too much changes),
and posterious commits seems to not rely on it, so I assume just reverting it
should works.

this way it would be know that it is this commit which introduces a regression,
and someone might figure why.

thanks.
-- 
Sebastien Marie



macbook - uvideo0: can't find video interface

2020-04-27 Thread Jan Stary
This is current/i386 on an old macbook (dmesgs below).
It runs fine except it no longer recognizes the video0 camera
ist used to. I am seeing the same on another macbook (amd64).

uvideo-firmware-1.2.p3 is installed; in short, what is now

acpivideo0 at acpi0: GFX0
uvideo0 at uhub0 port 4 configuration 1 interface 0 "Apple Computer Bluetooth" 
rev 2.00/0.0c addr 2
uvideo0: can't find video interface

used to be

acpivideo0 at acpi0: GFX0
uvideo0 at uhub0 port 4 configuration 1 interface 0 "Apple Computer Bluetooth" 
rev 2.00/0.0c addr 2
uvideo0 detached
uvideo0 at uhub0 port 4 configuration 1 interface 0 "Micron Built-in iSight" 
rev 2.00/1.84 addr 2
video0 at uvideo0

I don't usually use the camera on this machine (except now we need to run
twice as many laptops to get at the school's damned MS Teams of course)
- the regression is probably older. Below, please find three dmesgs:

  * the last one where video0 at uvideo0 worked (2018)
  * the first I have that shows the error (2019, only noticed now)
  * current

Edited highlights of the diffs
(other dmesgs available at https://github.com/janstary/dmesg):

(2018 to 2019)
-inteldrm0: 848x480, 32bpp
-uvideo0 detached
-uvideo0 at uhub0 port 4 configuration 1 interface 0 "Micron Built-in iSight" 
rev 2.00/1.84 addr 2
-video0 at uvideo0
+uvideo0: can't find video interface
+inteldrm0: 1280x800, 32bpp

(2019 to 2020)
-inteldrm0: apic 1 int 16
+inteldrm0: apic 1 int 16, I945GM, gen 3

Looking at uvideo.c history, I naively spot
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/uvideo.c.diff?r1=1.202=1.203=h
- the commit message says

Add support for integrated USB cameras with two functions, as
seen on a Lenovo X395 which combines normal webcam functionality
with another IR camera, by parsing the USB interface association
descriptors.  This fixes the symptom of uvideo(4) complaining
about too many headers and not providing any functionality at all.

My camera definitely is an "integrated USB camera",
the diff introduces the "can't find video interface" error message,
and the change fits into my very sparse timeline of works/breaks.

How can I help debug this?

Jan


OpenBSD 6.2-current (GENERIC.MP) #0: Sat Jan 13 14:30:23 CET 2018
h...@mb.stare.cz:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Genuine Intel(R) CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF,SENSOR
real mem  = 2114273280 (2016MB)
avail mem = 2061774848 (1966MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 07/29/05, SMBIOS rev. 2.4 @ 0xe7490 (36 entries)
bios0: vendor Apple Computer, Inc. version "MB11.88Z.0061.B03.0610121324" date 
10/12/06
bios0: Apple Computer, Inc. MacBook1,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) USB7(S3) EC__(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Genuine Intel(R) CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF,SENSOR
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: !C4(100@55 mwait@0x31), !C3(500@1 mwait@0x20), !C2(500@1 
mwait@0x10), C1(1000@1 mwait), PSS
acpicpu1 at acpi0: !C4(100@55 mwait@0x31), !C3(500@1 mwait@0x20), !C2(500@1 
mwait@0x10), C1(1000@1 mwait), PSS
acpisbs0 at acpi0: SBS0 model "ASMB016" serial 35580 type LION oem "DP"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID0
"APP0002" at acpi0 not configured
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
"APP0001" at acpi0 not configured
"APP0003" at acpi0 not configured
"ACPI0001" at acpi0 not configured
"IFX0101" at acpi0 not configured
acpivideo0 at acpi0: GFX0
bios0: ROM list: 0xc/0xe600!
cpu0: Enhanced SpeedStep 1998 MHz: speeds: 2000, 1833, 1667, 1500, 1333, 1000 
MHz
memory map conflict 0xe00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xfffb/0x3
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0