On Fri, Nov 10, 2017 at 10:29:59PM +0100, Thomas Gleixner wrote:
On Fri, 10 Nov 2017, Linus Torvalds wrote:
On Wed, Nov 8, 2017 at 9:19 PM, Fengguang Wu wrote:
>
> Yes it's accessing the list. Here is the faddr2line output.
Ok, so it's a corrupted timer list. Which is not a big surprise.
It'
On Fri, 10 Nov 2017, Linus Torvalds wrote:
> On Wed, Nov 8, 2017 at 9:19 PM, Fengguang Wu wrote:
> >
> > Yes it's accessing the list. Here is the faddr2line output.
>
> Ok, so it's a corrupted timer list. Which is not a big surprise.
>
> It's
>
> next->pprev = pprev;
>
> in __
On Wed, Nov 8, 2017 at 9:19 PM, Fengguang Wu wrote:
>
> Yes it's accessing the list. Here is the faddr2line output.
Ok, so it's a corrupted timer list. Which is not a big surprise.
It's
next->pprev = pprev;
in __hlist_del(), and the trapping instruction decodes as
mov
On Mon, Oct 30, 2017 at 12:29:47PM -0700, Linus Torvalds wrote:
On Sun, Oct 29, 2017 at 4:48 PM, Fengguang Wu wrote:
Here are 3 dmesgs related to wireless and 1 from ethernet.
Fengguang, these would be lovelier still _if_ you have DEBUG_INFO
enabled on the kernel, and your script were to fin
On Sun, Oct 29, 2017 at 4:48 PM, Fengguang Wu wrote:
>
> Here are 3 dmesgs related to wireless and 1 from ethernet.
Fengguang, these would be lovelier still _if_ you have DEBUG_INFO
enabled on the kernel, and your script were to find things like
"symbol+0xhex/0xhex", and run "./scripts/faddr2line
