From: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"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 12:17:10 +0000 [thread overview]
Message-ID: <d7c17267f87c4e64a1559fa706cf1ead@FE-MBX1012.de.bosch.com> (raw)
In-Reply-To: <CAPDOMVgFA-jTL=iDD2vLzPHrsO_=qsupAebTSUm0k0VmmHvX6A@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 590 bytes --]
> Mathias ,
> After tracing this it seems to be either one of two things based on
> the warn on messages in
> __queue_work. Normally it would be because of this line.
> WARN_ON_ONCE(!irqs_disabled());.
> However it would also be the second warn on, If you want I can send a
> simple patch with
> a printk statement to see which one it is.
> Regards Nick
That would be helpful. I can try to see what's happening.
Regards
Mathias
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-08-06 12:17 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)
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) [this message]
[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=d7c17267f87c4e64a1559fa706cf1ead@FE-MBX1012.de.bosch.com \
--to=mathias.koehrer@etas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xerofoify@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
all inboxes | Powered by JetHome®