linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: suggest <harshalshete@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: suspecting ibm_newemac driver problem.
Date: Mon, 7 Nov 2011 02:33:17 -0800 (PST)	[thread overview]
Message-ID: <32788715.post@talk.nabble.com> (raw)


Hello All,

I am using ppc460ex based custom board.
using linux 2.6.30.2 kernel on this board it has ibm_newemac driver in it.

I am using this board as a iSCSI target which has RAID system behind it.

                                               ||
                                               ||                    ||                      
||
      n/w driver (ibm_newemac)    ||    n/w layer   ||    iSCSI Target  ||  
RAID
                                               ||                    ||                      
||

The problem i am facing is when i start iometer based i/o.
I am doing i/o with following specifications.

Workload type : All in one.
no of outstanding i/o : 32.
no of worker threads : 8.

With this kind of workload n/w stucks in between. and board becomes
unresponsive.
If i try to ping to the board then ping fails with 100% packet loss.

While debugging the issue i found out that
sock->sk_state_change callback is called from the TCP layer and state of the
socket is not TCP_ESTABLISHED in the iSCSI target driver.

So i am assuming that this is a problem related to n/w driver.

Did anyone faced similar kind of issue before? Please point me in right
direction.


Thanks and Regards,
Harshal Shete.
-- 
View this message in context: http://old.nabble.com/suspecting-ibm_newemac-driver-problem.-tp32788715p32788715.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

                 reply	other threads:[~2011-11-07 10:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=32788715.post@talk.nabble.com \
    --to=harshalshete@gmail.com \
    --cc=linuxppc-dev@ozlabs.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).