[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140528140147.7eaa538e@nehalam.linuxnetplumber.net>
Date: Wed, 28 May 2014 14:01:47 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Fw: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173,
fatal exception in interrupt
Begin forwarded message:
Date: Fri, 23 May 2014 00:07:48 -0700
From: "bugzilla-daemon@...zilla.kernel.org" <bugzilla-daemon@...zilla.kernel.org>
To: "stephen@...workplumber.org" <stephen@...workplumber.org>
Subject: [Bug 76781] New: unable to handle NULL in xfrm_input+0x173, fatal exception in interrupt
https://bugzilla.kernel.org/show_bug.cgi?id=76781
Bug ID: 76781
Summary: unable to handle NULL in xfrm_input+0x173, fatal
exception in interrupt
Product: Networking
Version: 2.5
Kernel Version: 3.15.0-rc6
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@...ux-foundation.org
Reporter: cate@...eee.net
Regression: No
See also the fatal oops in:
http://cateee.net/kernel/IMG_20140522_225238.jpg
http://cateee.net/kernel/IMG_20140523_082629.jpg
It seems it happens "often": twice in last few hours I used the new kernels.
(the first oops was with 3.15.0-rc5-00270-gfba69f0)
I had also usual debian unstable updates, and I just finished to instal aiccu
(a sixxs program for dynamic ip6to4, so I'm not sure it is a recent bug or just
I forced it to appear in very last HEAD.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists