Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Sep 2016 17:18:30 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-usb@FreeBSD.org
Subject:   [Bug 211895] Logitech K360 keyboard: `usbconfig` hangs after suspend/resume
Message-ID:  <bug-211895-17-xOKO5qzEsN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211895-17@https.bugs.freebsd.org/bugzilla/>
References:  <bug-211895-17@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211895

--- Comment #10 from Aleksander Alekseev <afiskon@devzen.ru> ---
Ok, here are a few updates on this issue.

1. I solved all issues regarding entering KDB and writing kernel core dumps.
Now I can provide really any debug information you might need. In case anyo=
ne
is interested the problem with KDB was that for some reason RC and RELEASE
builds of FreeBSD don't have DDB option in GENERIC kernel by default. To wr=
ite
kernel dumps one needs a swap partition and dumpdev value in /etc/rc.conf
pointing to this partition. A good explanation of how UFS partition could be
shrinked to create a swap partition:
https://www.reddit.com/r/freebsd/comments/4ph4xu/shrink_ufs_root_fs/

2. The problem _does_ exist in 12.0 as well (I tested on r305736). usbconfig
doesn't hang, but keyboard still doesn't work. Neither does any other USB
device (flash drives, etc). Here is how dmesg looks like:

http://afiskon.ru/s/67/ba7648265f_usb120.jpg

As you may see there is no more infinite loop that calls usb_alloc_device a=
nd
uhub_reattach_port - they are called only one. But no other USB device coul=
d be
connected afterwards (see "giving up" errors).

3. Here are core.txt.0 and vmcore.0 created manually after issue was
reproduced:

http://afiskon.ru/s/aa/0e02bb563b_core.txt.0.txt
http://afiskon.ru/s/7a/d529b2c2d7_vmcore.0.tgz

Is there anything else I can do to help?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211895-17-xOKO5qzEsN>