From: Iain Paton <selsinork@gmail.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Michael Chan <mchan@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.37 vlans on bnx2 not functional, panic with tcpdump
Date: Sun, 09 Jan 2011 11:22:39 +0000 [thread overview]
Message-ID: <4D299A7F.40604@gmail.com> (raw)
In-Reply-To: <4D28AFD1.3020808@gmail.com>
Jarek Poplawski wrote:
> Iain Paton wrote:
> ...
>> So you can consider any bnx2 cause for this closed. I'll get back to the
>> list if I can come up with any more useful info.
>
> Hi Iain,
> If it's not a problem, please try if the attached debugging patch
> (not tested) can change anything.
No problem testing with the patch installed, however I'm now unable to duplicate the problem with a rebuilt kernel, with or without
the patch.
The original kernel build I did still fails repeatably, but something as simple as erasing the directory, unpacking the same source
tarball and re-compiling using the same config file gets me a working kernel.
This is somewhat troubling as there must have been some initial cause, but I'm unable to pin it down. Have spent the last day or so
checking toolchain versions, running hardware tests on the physical build server and have come up completely empty.
I think we can safely ignore this now as it appears to be a one-off bad compile, for reasons unknown, but totally unrepeatable.
Thanks to all for your help, and apologies for the noise.
Iain
prev parent reply other threads:[~2011-01-09 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 21:32 2.6.37 vlans on bnx2 not functional, panic with tcpdump Iain Paton
2011-01-06 23:52 ` Michael Chan
2011-01-07 0:46 ` Michael Chan
2011-01-07 9:03 ` selsinork
[not found] ` <AANLkTi=PGPVRbS3XViskpZ0GSS8ouBcgVZYYG9EoM-Nz@mail.gmail.com>
2011-01-07 17:50 ` Michael Chan
2011-01-07 18:01 ` Iain Paton
2011-01-08 18:41 ` Jarek Poplawski
2011-01-09 11:22 ` Iain Paton [this message]
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=4D299A7F.40604@gmail.com \
--to=selsinork@gmail.com \
--cc=jarkao2@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--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;
as well as URLs for NNTP newsgroup(s).