Re: 3.2-rc6+: Reported regressions from 3.0 and 3.1

From: Markus Trippelsdorf
Date: Wed Dec 21 2011 - 01:45:44 EST


On 2011.12.21 at 00:54 +0100, Rafael J. Wysocki wrote:
> Subject : WARNING: at fs/sysfs/sysfs.h:195 (during boot)
> Submitter : Markus Trippelsdorf <markus-xp2qqqlHh3xzoYq+O6RWwA@xxxxxxxxxxxxxxxx>
> Date : 2011-11-13 19:24
> Message-ID : 20111113192417.GA1659-tLCgZGx+iJ+kxVt8IV0GqQ@xxxxxxxxxxxxxxxx
> References : http://marc.info/?l=linux-kernel&m=132121231921932&w=2
>
> Subject : WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413
> Submitter : Markus Trippelsdorf <markus-xp2qqqlHh3xzoYq+O6RWwA@xxxxxxxxxxxxxxxx>
> Date : 2011-11-18 7:25
> Message-ID : 20111118072519.GA1615-tLCgZGx+iJ+kxVt8IV0GqQ@xxxxxxxxxxxxxxxx
> References : http://marc.info/?l=linux-kernel&m=132160119031794&w=2

Both entries were caused by the same Radeon kexec writeback bug. This issue
will hopefully be fixed in the next release.

> Subject : Impossible high cpu-time values for migration threads
> Submitter : Markus Trippelsdorf <markus-xp2qqqlHh3xzoYq+O6RWwA@xxxxxxxxxxxxxxxx>
> Date : 2011-11-17 22:17
> Message-ID : 20111117221731.GA9229-tLCgZGx+iJ+kxVt8IV0GqQ@xxxxxxxxxxxxxxxx
> References : http://marc.info/?l=linux-kernel&m=132156832124314&w=2

This is a cosmetic issue, but I'm still seeing this after bursts of high
CPU usage:

% ps afx -F
UID PID PPID C SZ RSS PSR STIME TTY STAT TIME CMD
root 2 0 0 0 0 1 Dec20 ? S 0:00 [kthreadd]
root 3 2 0 0 0 0 Dec20 ? S 0:01 \_ [ksoftirqd/0]
root 6 2 0 0 0 0 Dec20 ? S 0:00 \_ [migration/0]
root 7 2 0 0 0 1 Dec20 ? S 0:00 \_ [migration/1]
root 8 2 0 0 0 1 Dec20 ? S 0:05 \_ [kworker/1:0]
root 9 2 0 0 0 1 Dec20 ? S 0:01 \_ [ksoftirqd/1]
root 11 2 0 0 0 2 Dec20 ? S 0:00 \_ [migration/2]
root 13 2 0 0 0 2 Dec20 ? S 0:01 \_ [ksoftirqd/2]
root 14 2 22 0 0 3 Dec20 ? S 192:21 \_ [migration/3]
root 16 2 0 0 0 3 Dec20 ? S 0:01 \_ [ksoftirqd/3]
root 17 2 0 0 0 2 Dec20 ? S< 0:00 \_ [khelper]
...

--
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/