Re: [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Yep
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Tim Sander <tim.sander@xxxxxxx>
- Subject: Re: [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Yep
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Date: Wed, 01 Feb 2012 15:27:43 -0500
- Cc: RT <linux-rt-users@xxxxxxxxxxxxxxx>, Mike Galbraith <efault@xxxxxx>, Tim Sander <tstone@xxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Clark Williams <williams@xxxxxxxxxx>, John Kacur <jkacur@xxxxxxxxxx>, Gerlando Falauto <gerlando.falauto@xxxxxxxxxxx>, Micha Nelissen <micha@xxxxxxxxxxxxxx>, Holger Brunck <holger.brunck@xxxxxxxxxxx>
- In-reply-to: <201201251031.48983.tim.sander@hbm.com>
- References: <1324525237.5916.114.camel@gandalf.stny.rr.com> <201201181211.45011.tim.sander@hbm.com> <201201241152.21472.tim.sander@hbm.com> <201201251031.48983.tim.sander@hbm.com>
On Wed, 2012-01-25 at 10:31 +0100, Tim Sander wrote:
> Bad news, the ksoftirq(sirq-net-tx) error seems to happen not so often any
> more but it still happens :-(.
Tim,
Is the system still usable when this happens? If so, can you configure
in ftrace, and run a trace on what ksoftirq is doing:
mkdir /debug
mount -t debugfs nodev /debug
cd /debug/tracing
echo <pid-of-ksoftirq> > set_ftrace_pid
echo function > current_tracer
cat trace
Thanks!
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[RT Stable]
[Kernel Newbies]
[Share Photos]
[IDE]
[Security]
[Git]
[Netfilter]
[Bugtraq]
[Photo]
[Yosemite]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Linux ATA RAID]
[Samba]
[Video 4 Linux]
[Device Mapper]
[Linux Resources]