From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
linux-net maillist <linux-net@vger.kernel.org>,
e1000-devel list <e1000-devel@lists.sourceforge.net>,
"nikola.ciprich@linuxbox.cz" <nikola.ciprich@linuxbox.cz>
Subject: Re: [E1000-devel] 2.6.36-rc7-git2 - panic/GPF: e1000e/vlans?
Date: Wed, 20 Oct 2010 16:46:40 +0200 [thread overview]
Message-ID: <20101020144640.GA3009@pcnci.linuxbox.cz> (raw)
In-Reply-To: <EA929A9653AAE14F841771FB1DE5A1366027CEFF1C@rrsmsx501.amr.corp.intel.com>
Hello Emil,
I tried it now, I can still 100% reproduce with 2.6.36-rc7-git2, but
with 2.6.36-rc8-git5 it works OK. So it certainly got fixed in the meantime!
I'll therefore close the bug in BZ.
have a nice day!
best regards
nik
On Fri, Oct 15, 2010 at 10:58:15AM -0600, Tantilov, Emil S wrote:
> >-----Original Message-----
> >From: Nikola Ciprich [mailto:extmaillist@linuxbox.cz]
> >Sent: Wednesday, October 13, 2010 10:23 PM
> >To: Linux kernel list; linux-net maillist; e1000-devel list
> >Cc: nikola.ciprich@linuxbox.cz
> >Subject: [E1000-devel] 2.6.36-rc7-git2 - panic/GPF: e1000e/vlans?
> >
> >Hi,
> >when I try to boot 2.6.36-rc7-git2 on one of my machines, it crashes while
> >setting up the network.
>
> Thanks for letting us know!
>
> >The setup is quite complex, with bonding, lots of vlans and 3 intel
> >adapters (system is quad x86_64)
>
> Could you provide more details about the exact setup and the sequence of
> commands that lead to the crash? If you can narrow it down to the actual
> command that caused the crash that would be very helpful.
>
> Also - are you testing from Linus or net-next tree? If you are not using
> net-next, could you give it a try and see if you can reproduce it there?
>
> >
> >snip of lspci:
> >06:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet
> >Controller (Copper) (rev 01)
> >06:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet
> >Controller (Copper) (rev 01)
> >09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> >Connection
>
> Could you provide the output of lspci -vvv and a kernel config?
>
> Thanks,
> Emil
> --
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2010-10-20 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101014052242.GA8998@pcnci.linuxbox.cz>
2010-10-15 16:58 ` [E1000-devel] 2.6.36-rc7-git2 - panic/GPF: e1000e/vlans? Tantilov, Emil S
2010-10-18 6:12 ` Nikola Ciprich
2010-10-20 14:46 ` Nikola Ciprich [this message]
2010-10-20 16:36 ` Nikola Ciprich
2010-10-21 19:02 ` Nikola Ciprich
2010-10-21 19:09 ` Brandeburg, Jesse
2010-10-21 19:09 ` Brandeburg, Jesse
2010-10-22 11:01 ` [E1000-devel] " Jussi Kivilinna
2010-10-22 18:15 ` Ben Greear
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=20101020144640.GA3009@pcnci.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=e1000-devel@lists.sourceforge.net \
--cc=emil.s.tantilov@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.