[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #34 from Konstantin Belousov --- (In reply to Hans Petter Selasky from comment #30) Minus one reads mean that there is no more a device to respond at the address read. I have no idea why, and there seems to be the mix of

[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #35 from Mike Karels --- This is not a laptop; it's a tower computer. Also, note that the messages start even before autoconfiguration is complete. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #38 from Hans Petter Selasky --- Adding John Baldwin aswell after searching for similar issues. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #37 from Hans Petter Selasky --- Hi, Can you attach output from: devinfo -r and acpidump -dt --HPS -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #40 from Mike Karels --- Created attachment 206443 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=206443=edit devinfo -r devinfo -r is attached; acpdidump -dt is ftp://ftp.karels.net/outgoing/acpidump-dt. -- You

[Bug 233884] Corsair CORSAIR K70 RGB MK.2 / K63 / K63 Wireless not working

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233884 --- Comment #15 from Hans Petter Selasky --- The BOOT protocol should only use 8-BYTE messages. The other format basically resembles a keyboard bitmap with all possible keys. Eventually we could add support for this format to the FreeBSD

[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #36 from Hans Petter Selasky --- @kib: What about these PCI errors? > pcib7: failed to allocate initial I/O port window: 0-0xfff > pcib7: failed to allocate initial memory window: 0-0xf > pcib7: failed to allocate initial

[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #39 from Konstantin Belousov --- (In reply to Hans Petter Selasky from comment #36) These 'failed to allocate' messages are the secondary effects of reading all ones. Values of the bridge' registers to specify io and memory

[Bug 233884] Corsair CORSAIR K70 RGB MK.2 / K63 / K63 Wireless not working

2019-08-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233884 --- Comment #16 from a...@mashtizadeh.com --- I can look at this after this week. Yes, it seems to only send in the bit vector format. I think I understand the decoding. The bit set is the usage ID in the keyboard page description in

Problem reports for u...@freebsd.org that need special attention

2019-08-11 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Re: Is it a good idea to use a usb-serial adapter for PPS input? Yes, it is.

2019-08-11 Thread O'Connor, Daniel
> On 6 Aug 2019, at 00:12, Ian Lepore wrote: > On Mon, 2019-08-05 at 15:28 +0930, O'Connor, Daniel wrote: >>> Most people are not worried about their kernel clock being 200 >>> microseconds off from UTC, even if they're using the PPS signal from a >>> GPS receiver. So I think most people