On Mon, May 07, 2018 at 05:44:59PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, May 07, 2018 at 04:06:38PM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Since commit 1455cf8dbfd0 ("driver core: emit uevents when
> > device is bound to a driver") the kernel started emitting
>
From: Ville Syrjälä
Since commit 1455cf8dbfd0 ("driver core: emit uevents when
device is bound to a driver") the kernel started emitting
"bind" and "unbind" uevents which confuse the hid2hci
udev rules.
The symptoms on an affected machine (Dell E5400 in my case)
include bluetooth devices not app
On 06/20/2018 06:33 AM, Lennart Poettering wrote:
On Di, 19.06.18 17:21, Christopher Cox ([email protected]) wrote:
Not sure what happened, but on one of our CentOS 7 host we had like 64
socket connects owned by pid 1 (systemd) in CLOSE-WAIT state. And systemctl
-a shows a bunch of lines lik
On Di, 19.06.18 17:21, Christopher Cox ([email protected]) wrote:
> Not sure what happened, but on one of our CentOS 7 host we had like 64
> socket connects owned by pid 1 (systemd) in CLOSE-WAIT state. And systemctl
> -a shows a bunch of lines like:
>
> [email protected]:6556-10.32.3
On Mi, 20.06.18 10:45, [email protected] ([email protected]) wrote:
> Hey,
> On Tue, Jun 19, 2018 at 15:30, Simon McVittie wrote:
> On Tue, 19 Jun 2018 at 12:32:19 +, [email protected]
> (mailto:[email protected]) wrote:
> The system is on a quite old kernel (3.18.44)
> ...
> At this point,
Hey,
On Tue, Jun 19, 2018 at 15:30, Simon McVittie wrote:
On Tue, 19 Jun 2018 at 12:32:19 +, [email protected]
(mailto:[email protected]) wrote:
The system is on a quite old kernel (3.18.44)
...
At this point, things go wrong when
recvmsg() is called on bus->input_fd with flags MSG_DONTWAIT|M
