Recent kernel anomalies

[Antonio Huete Jiménez]

Hi Daniel,

Would you mind pin pointing the commit that may be causing the problems?
You can use 'git bisect' for it.

Regards,
Antonio Huete

Daniel Bilik <ddb at neosystem.org> escribió:

> Hi.
>
> After updating to current 5.3-DEVELOPMENT (21b2a00+), chromium started to
> fall on me. Well, not really chromium itself, but "just" extensions are
> crashing during browser activity, taking down chromium child processes,
> with kernel reporting something like this:
>
> pid 1123 (chrome), uid 1001: exited on signal 10
> pid 1717 (chrome), uid 1001: exited on signal 4
> pid 1512 (chrome), uid 1002: exited on signal 4
> pid 1146 (chrome), uid 1001: exited on signal 6
> pid 1149 (chrome), uid 1001: exited on signal 10
> pid 1811 (chrome), uid 1001: exited on signal 11
> pid 1724 (chrome), uid 1001: exited on signal 4
> pid 1806 (chrome), uid 1002: exited on signal 11
> pid 1310 (chrome), uid 1001: exited on signal 10
> pid 1343 (chrome), uid 1002: exited on signal 10
> pid 1021 (chrome), uid 1001: exited on signal 11
>
> I've also noticed another anomalous behaviour with this kernel...
>
> On reboot, ssh-agent(1) leaves its socket laying on the filesystem, which
> prevents it from starting after next system boot. And, for one time,
> Windowmaker state file was sort-of reset on reboot, and I had to recover
> it from a snapshot.
>
> Other applications did not seem to have problems, or at least I did not
> hit any more.
>
> Using kernel.old (5af112a+ from Oct 31) - just kernel, userland remains
> current (21b2a00+) - everything is back to normal, ie. chromium processes
> are not crashing and ssh-agent cleans its socket on reboot.
>
> From Oct 31 to now, there have been some modifications to kernel, and also
> some vfs related ones. But looking at particular commits, I'm not sure
> what to try to revert. Any hints?
>
> Thanks.
>
> --
> 						Daniel