From: Stephen Hemminger <stephen@networkplumber.org>
To: "Nimrod Andy" <B38611@freescale.com>,
"Lothar Waßmann" <LW@KARO-electronics.de>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Fabio Estevam" <fabio.estevam@freescale.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Philippe Reynes" <tremyfr@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 106171] New: Regression causes "ip" command to crash, leaving the user without any networking
Date: Sun, 18 Oct 2015 21:28:38 -0700 [thread overview]
Message-ID: <20151018212838.552beb1d@xeon-e3> (raw)
Freescale driver bug.
Begin forwarded message:
Date: Mon, 19 Oct 2015 02:14:45 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 106171] New: Regression causes "ip" command to crash, leaving the user without any networking
https://bugzilla.kernel.org/show_bug.cgi?id=106171
Bug ID: 106171
Summary: Regression causes "ip" command to crash, leaving the
user without any networking
Product: Networking
Version: 2.5
Kernel Version: 4.2.0
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: justincase@yopmail.com
Regression: No
Created attachment 190481
--> https://bugzilla.kernel.org/attachment.cgi?id=190481&action=edit
Process ip (pid: 252, stack limit = 0xed7a4220) Stack: (0xed7a5a58 to
0xed7a6000)
Between kernel version 4.1.7 and 4.2.0 something caused networking to be left
non-functioning. I can confirm the bug is still in mainline 4.2.3.
Attached is the stack trace showing up during boot of the device with 4.2.3
kernel. I have since regressed to 4.1.x and networking works fine again.
I had one other user confirm this bug via Freenode IRC.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-10-19 4:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151018212838.552beb1d@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=B38611@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=andrew@lunn.ch \
--cc=fabio.estevam@freescale.com \
--cc=l.stach@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=tremyfr@gmail.com \
/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).