From: Taku Izumi <izumi.taku@jp.fujitsu.com>
To: netdev@vger.kernel.org, Bruce Allan <bruce.w.allan@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
John Ronciak <john.ronciak@intel
Cc: Koki Sanagi <sanagi.koki@jp.fujitsu.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Subject: [PATCH 0/3] e1000e,igb,ixgbe: add registers etc. printout code just before resetting adapters
Date: Thu, 07 Jan 2010 19:47:01 +0900 [thread overview]
Message-ID: <4B45BBA5.8010407@jp.fujitsu.com> (raw)
This patchset adds registers etc. printout code just before resetting adapters
to e1000e, igb, ixgbe modules. The registers, tx/rx rings status, descriptors,
and buffer info will be helpful for detecting the root cause of adapters reset.
This patchset is based on the following Jesse's debug patch of e1000e module.
http://marc.info/?l=linux-netdev&m=121446492912285&w=2
I think that code is very useful, and should be comitted to upstream.
The main difference between Jesse's patch and mine is as follows:
- the function which invokes xxx_dump function. (xxx_clean_tx_irq -> xxx_reset_task)
- add the "dump_flag" module option to select category of printout
The default output is netdevice status (transstart, last_rx), registers,
and tx/rx rings' simple information. TX/RX descriptors information and
buffer_info can be output by changing the dump_flag module option, but,
of course, the amount of output becomes quite large.
*[PATCH 1/3] e1000e: add registers etc. printout code just before resetting adapters
*[PATCH 2/3] igb: add registers etc. printout code just before resetting adapters
*[PATCH 3/3] ixgbe: add registers etc. printout code just before resetting adapters
Best regards,
Taku Izumi <izumi.taku@jp.fujitsu.com>
next reply other threads:[~2010-01-07 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 10:47 Taku Izumi [this message]
2010-01-07 11:01 ` [PATCH 1/3] e1000e: add registers etc. printout code just before resetting adapters Taku Izumi
2010-01-07 19:00 ` Laurent Chavey
2010-01-07 11:01 ` [PATCH 2/3] igb: " Taku Izumi
2010-01-07 19:16 ` Laurent Chavey
2010-01-08 10:33 ` Taku Izumi
2010-01-07 11:02 ` [PATCH 3/3] ixgbe: " Taku Izumi
2010-01-11 21:28 ` Jesse Brandeburg
2010-01-11 21:52 ` [PATCH 0/3] e1000e,igb,ixgbe: " Jeff Kirsher
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=4B45BBA5.8010407@jp.fujitsu.com \
--to=izumi.taku@jp.fujitsu.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=sanagi.koki@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).