From: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>
To: Heinz Diehl <htd@fancy-poultry.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: PROBLEM: [x86] Running ptpd2 using an Intel 82572EI (e1000e) leads to a kernel oops (3.12.26)
Date: Wed, 6 Aug 2014 10:52:12 +0000 [thread overview]
Message-ID: <6360ed72fccb44b2907bfaddef31cbbe@FE-MBX1012.de.bosch.com> (raw)
In-Reply-To: <20140806083315.GA3102@fancy-poultry.org>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org] On
> Behalf Of Heinz Diehl
> Sent: Wednesday, August 06, 2014 10:33 AM
> To: linux-kernel@vger.kernel.org
> Cc: Koehrer Mathias (ETAS/ESW5); netdev@vger.kernel.org
> Subject: Re: PROBLEM: [x86] Running ptpd2 using an Intel 82572EI (e1000e) leads
> to a kernel oops (3.12.26)
>
> On 06.08.2014, Nick Krause wrote:
>
> > I am going to have to ask a few questions first, what distribution is
> > and is this a vanilla kernel?
>
> Read his mail. He's on Debian, and it's a Debian kernel.
I am on Debian. But it is a vanilla kernel from kernel.org without any additional patches.
>
> > If it's not just send the report to the distribution developers.
>
> His mail is quite sure a copy from the data entered into the Debian
> bugtracker.
No. I've never entered this into the Debian bugtracker.
Mathias
next prev parent reply other threads:[~2014-08-06 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 12:26 Koehrer Mathias (ETAS/ESW5)
2014-08-06 0:35 ` Nick Krause
2014-08-06 8:33 ` Heinz Diehl
2014-08-06 10:52 ` Koehrer Mathias (ETAS/ESW5) [this message]
2014-08-06 10:15 ` Koehrer Mathias (ETAS/ESW5)
[not found] ` <CAPDOMVgFA-jTL=iDD2vLzPHrsO_=qsupAebTSUm0k0VmmHvX6A@mail.gmail.com>
2014-08-06 12:17 ` Koehrer Mathias (ETAS/ESW5)
[not found] ` <CAPDOMVjWO9rfZjnHOgK+yB-3MVkmVz_00piBgnDFdf6j=56+GA@mail.gmail.com>
2014-08-06 13:25 ` Koehrer Mathias (ETAS/ESW5)
2014-08-06 9:29 ` Hannes Frederic Sowa
2014-08-06 15:38 ` [E1000-devel] " Fujinaka, Todd
2014-08-06 22:32 ` Keller, Jacob E
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=6360ed72fccb44b2907bfaddef31cbbe@FE-MBX1012.de.bosch.com \
--to=mathias.koehrer@etas.com \
--cc=htd@fancy-poultry.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome