[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150816113342.GB7004@linutronix.de>
Date: Sun, 16 Aug 2015 13:33:42 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Clark Williams <williams@...hat.com>
Cc: RT <linux-rt-users@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RT] oops in 4.1.3-rt3
* Clark Williams | 2015-08-03 14:27:00 [-0500]:
>Sebastian,
Hi Clark,
>Below is a traceback I hit while running 4.1.3-rt3 on my Lenovo T530.
>
>I was doing my normal, play music, copy files over the lan, do compiles,
>do email, etc., so I I can't really point you at a reproducer. The graphics
>system stayed up somewhat but the actual trace I hit scrolled off. This was
>extracted from the syslog with 'journalctl'.
>
>If I encounter it again, I'll see if I can force a kdump.
So it did not happen again? Is it possible to get addr2line from this
kernel (from $eip)? sock_prot_inuse_add() does "just" __this_cpu_add().
>Clark
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists