https://bugzilla.suse.com/show_bug.cgi?id=1174737https://bugzilla.suse.com/show_bug.cgi?id=1174737#c6
--- Comment #6 from Markus Kolb <novell(a)tower-net.de> ---
(In reply to Takashi Iwai from comment #4)
> Also, you can try the kernel in OBS Kernel:openSUSE-15.2 repo (unless you're
> booting with Secure Boot), just to check whether the issue has been already
> addressed. The kernel found there as of now is a bit behind the latest git,
> but contains more patches than the last update release.
I'll try this one and write tomorrow.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174737https://bugzilla.suse.com/show_bug.cgi?id=1174737#c5
--- Comment #5 from Markus Kolb <novell(a)tower-net.de> ---
(In reply to Takashi Iwai from comment #3)
> Hrm, it's pretty hard to guess what's wrong without log, as you guessed.
>
> Is it a hard hang, i.e. no network ping or such? Magic sysrq also doesn't
> work?
Magic SysRq isn't reacting.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174625
Bug ID: 1174625
Summary: uvcvideo module doesn't create /dev/video devices
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: david(a)gloveraoki.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Somewhere between kernel 5.7.7 and 5.7.9, uvcvideo stopped working.
dmesg for 5.7.7:
[ 69.528291] usb 1-14: new high-speed USB device number 4 using xhci_hcd
[ 69.679365] usb 1-14: New USB device found, idVendor=534d, idProduct=2109,
bcdDevice=21.00
[ 69.679370] usb 1-14: New USB device strings: Mfr=1, Product=0,
SerialNumber=0
[ 69.679373] usb 1-14: Manufacturer: MACROSILICON
[ 69.681595] hid-generic 0003:534D:2109.0005: hiddev97,hidraw4: USB HID v1.10
Device [MACROSILICON] on usb-0000:00:14.0-14/input4
[ 69.698468] mc: Linux media interface: v0.10
[ 69.714359] videodev: Linux video capture interface: v2.00
[ 69.722387] usbcore: registered new interface driver snd-usb-audio
[ 69.730136] uvcvideo: Found UVC 1.00 device <unnamed> (534d:2109)
[ 69.730785] uvcvideo 1-14:1.0: Entity type for entity Processing 2 was not
initialized!
[ 69.730786] uvcvideo 1-14:1.0: Entity type for entity Camera 1 was not
initialized!
[ 69.730831] usbcore: registered new interface driver uvcvideo
[ 69.730831] USB Video Class driver (1.1.1)
dmesg for 5.7.9:
[ 57.374607] usb 1-14: new high-speed USB device number 4 using xhci_hcd
[ 57.525662] usb 1-14: New USB device found, idVendor=534d, idProduct=2109,
bcdDevice=21.00
[ 57.525667] usb 1-14: New USB device strings: Mfr=1, Product=0,
SerialNumber=0
[ 57.525670] usb 1-14: Manufacturer: MACROSILICON
[ 57.527975] hid-generic 0003:534D:2109.0005: hiddev97,hidraw4: USB HID v1.10
Device [MACROSILICON] on usb-0000:00:14.0-14/input4
[ 57.543400] mc: Linux media interface: v0.10
[ 57.563578] videodev: Linux video capture interface: v2.00
[ 57.565995] usbcore: registered new interface driver snd-usb-audio
[ 57.581779] usbcore: registered new interface driver uvcvideo
[ 57.581780] USB Video Class driver (1.1.1)
Under 5.7.9, the /dev/video devices are not created.
Booting from the earlier kernel, but changing nothing else, fixes the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174737https://bugzilla.suse.com/show_bug.cgi?id=1174737#c4
--- Comment #4 from Takashi Iwai <tiwai(a)suse.com> ---
Also, you can try the kernel in OBS Kernel:openSUSE-15.2 repo (unless you're
booting with Secure Boot), just to check whether the issue has been already
addressed. The kernel found there as of now is a bit behind the latest git,
but contains more patches than the last update release.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174737https://bugzilla.suse.com/show_bug.cgi?id=1174737#c3
Takashi Iwai <tiwai(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tiwai(a)suse.com
--- Comment #3 from Takashi Iwai <tiwai(a)suse.com> ---
Hrm, it's pretty hard to guess what's wrong without log, as you guessed.
Is it a hard hang, i.e. no network ping or such? Magic sysrq also doesn't
work?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1168873https://bugzilla.suse.com/show_bug.cgi?id=1168873#c2
--- Comment #2 from Thomas Rother <t.rother(a)netzwissen.de> ---
I have the same errors in the boot log with kernel 5.7.9-1-default
Jul 30 07:02:54 locutus kernel: FS-Cache: Netfs 'cifs' registered for caching
Jul 30 07:02:58 locutus kernel: FS-Cache: Duplicate cookie detected
Jul 30 07:02:58 locutus kernel: FS-Cache: O-cookie c=000000006e3a0472
[p=000000003e41e630 fl=222 nc=0 na=1]
Jul 30 07:02:58 locutus kernel: FS-Cache: O-cookie d=000000006c3ea506
n=00000000e04cf4ce
Jul 30 07:02:58 locutus kernel: FS-Cache: O-key=[8] '0200008bc0a84803'
Jul 30 07:02:58 locutus kernel: FS-Cache: N-cookie c=00000000ca118bc4
[p=000000003e41e630 fl=2 nc=0 na=1]
Jul 30 07:02:58 locutus kernel: FS-Cache: N-cookie d=000000006c3ea506
n=00000000f80486d7
Jul 30 07:02:58 locutus kernel: FS-Cache: N-key=[8] '0200008bc0a84803'
And the same behaviour: mounting during bootup fails but mounting after full
boot with "mount -a" is successful.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1159767https://bugzilla.suse.com/show_bug.cgi?id=1159767#c12
--- Comment #12 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> ---
So far I haven't visited my far away relatives. They're not computer savvy, the
laptop is just a "black box" for them. I can't expect them to do a lot of
rebooting and debugging via a phone call. I can log into their machine, but
then there's the Bluetooth headphone ... too many variables. Of course it
doesn't have ILO / IPMI either. This is an on-site job.
There are 2 BIOS updates pending. Unfortunately Lenovo requires Windows for
BIOS updates in their consumer grade laptops. Maybe W10-to-go on a USB-stick
will help there ... I'll find out.
I will report back after I've made the trip and hopefully made all of the
updates happen. Sorry for the delay.
--
You are receiving this mail because:
You are the assignee for the bug.