>> > Maybe your patch will be acceptable, though. We'll have to hear from
>> > Markus and Matt.
>>
>> We'll probably have to take this to fsdevel as well ... they might have
>> opinions about whether the FS wants to be informed about flush failure.
So, it is okay to wait for the end of that discu
> Please test it now. I'd like to know if it fixes your problem,
> regardless of how the discussion goes.
Seems to be working, I also attached the kernel log.
The "flush failed" will grow with disc activity (but that was to be expected).
Jun 22 23:24:50 m3800 kernel: usb 1-3: new high-speed USB
Hello!
Do you remember?
I get it again, is there something I could do?
I attached a file that contains the "udevadm monitor" log.
I am using a v3.5.0 linux kernel (containing some gentoo patches).
Should I test it with a vanilla one?
Here the versions of some packages (kernel, udev, systemd):
s
> I have 3.5 here and see the loop too, but it stops after a couple of seconds:
>
> first: KERNEL[15636.368034]
> last: KERNEL[15638.879796]
Ah, sorry then.
The udev messages reported by the udev monitor reported up to 20
seconds of udev (userspace) events. I did not filter kernel reported
message
4 matches
Mail list logo