[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 Mark Linimon changed: What|Removed |Added Status|New |Open -- You are receiving this mai

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #12 from goriot --- No symptoms that I've ever seen, no issues with usb devices failing in any way. As I mentioned though, this is a relatively new occurence on my system - can't say exactly when it started but at most a couple

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #11 from Warner Losh --- OK. Sure looks like we're racing the driver loads and sometimes we can't get the list from the kernel. I suspect that if we retried after some fraction of a second it would be fine. I suspect they are ha

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-06-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #10 from goriot --- >>Same place every time? The messages occur at the same point on each boot. There are two such messages in the relevant segment of the console output: . . . Autoloading module: uhid Autoloading module: usb

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #9 from goriot --- >>Ah... so no other messages... ok.. Correct, no other messages. >>Same place every time? Unknown at this point. I'll update after the next reboot. This message is only occurring on one box, Another (older

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #8 from Warner Losh --- Same place every time? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #7 from Warner Losh --- Ah... so no other messages... ok.. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #6 from goriot --- The message is right in the center of the OP's screenshot. His/her screenshot demonstrates *when* this messages occurs within the context of the overall boot process. Seems to be after attempting initialize

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 --- Comment #5 from Warner Losh --- I don't see the devinfo message in the screen shot. It looks like all the EINVAL return values have some kind of printout for why... That's the next step in debugging. Might try to enable console.log in s

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 pere_gorio...@yahoo.com changed: What|Removed |Added CC||pere_gorio...@yahoo.com

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-01-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org --- Comment #3 from

[Bug 266747] devmatch: devinfo_init: Invaild arguement

2025-01-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266747 Mark Linimon changed: What|Removed |Added Component|standards |misc CC|