From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 71781] New: Kernel panic - not syncing: Fatal exception in interrupt
Date: Mon, 10 Mar 2014 09:12:08 -0700 [thread overview]
Message-ID: <20140310091208.65c31c75@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Mon, 10 Mar 2014 05:51:48 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 71781] New: Kernel panic - not syncing: Fatal exception in interrupt
https://bugzilla.kernel.org/show_bug.cgi?id=71781
Bug ID: 71781
Summary: Kernel panic - not syncing: Fatal exception in
interrupt
Product: Networking
Version: 2.5
Kernel Version: 3.10.32
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: asilva@wirelessmundi.com
Regression: No
Created attachment 128811
--> https://bugzilla.kernel.org/attachment.cgi?id=128811&action=edit
full boot sequence log
The servers just panic on boot time:
[ 18.647435] BUG: unable to handle kernel NULL pointer dereference at
0000000000000080
[ 18.656468] IP: [<ffffffff810f4c8d>] ____cache_alloc+0x1f/0x290
[ 18.663269] PGD 0
[ 18.665581] Oops: 0000 [#1] SMP
.... (see attach log for the full message)
[ 19.200202] ---[ end trace 85fce9ca9a98a944 ]---
[ 19.207209] Kernel panic - not syncing: Fatal exception in interrupt
[ 19.216142] Rebooting in 1 seconds..
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-03-10 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 16:12 Stephen Hemminger [this message]
2014-03-11 5:30 ` Fw: [Bug 71781] New: Kernel panic - not syncing: Fatal exception in interrupt Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140310091208.65c31c75@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).