From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 84051] New: Panic while transferring bigger amount of data with device driver "forcedeth"
Date: Mon, 8 Sep 2014 17:28:04 -0700 [thread overview]
Message-ID: <20140908172804.6d5f19ed@uryu.home.lan> (raw)
Begin forwarded message:
Date: Sun, 7 Sep 2014 23:43:26 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 84051] New: Panic while transferring bigger amount of data with device driver "forcedeth"
https://bugzilla.kernel.org/show_bug.cgi?id=84051
Bug ID: 84051
Summary: Panic while transferring bigger amount of data with
device driver "forcedeth"
Product: Networking
Version: 2.5
Kernel Version: 3.14.4
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
Assignee: shemminger@linux-foundation.org
Reporter: mapo2364@gmail.com
Regression: No
Created attachment 149391
--> https://bugzilla.kernel.org/attachment.cgi?id=149391&action=edit
/var/log/messages with kernel panic
Overview:
While transferring about 20GB (~40MB/s) over SSH the kernel is going to panic.
After about a minute.
Steps to Reproduce:
1) git clone of a big repo
2) wait
Actual Results:
Kernel Panic: see attached log
Build Date & Hardware:
Linux client-01 3.14.4-aufs-x86_64-mynet-latest-unstable #1 SMP Sat Jul 5
13:06:29 CEST 2014 x86_64 AMD Phenom(tm) II X4 955 Processor AuthenticAMD
GNU/Linux
aufs-sources from gentoo portage
PS: This is my first bug report. Please feel free to ask for further
information, if needed.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2014-09-09 0: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=20140908172804.6d5f19ed@uryu.home.lan \
--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