From: Sachin Sant <sachinp@in.ibm.com>
To: linux-next@vger.kernel.org
Cc: netdev <netdev@vger.kernel.org>, HERING2@de.ibm.com
Subject: [-next April 8] eHEA driver failure on powerpc
Date: Thu, 08 Apr 2010 17:25:51 +0530 [thread overview]
Message-ID: <4BBDC447.3040901@in.ibm.com> (raw)
In-Reply-To: <20100408155113.ef8df30c.sfr@canb.auug.org.au>
With today's next release, eHEA network interface on couple
of power6 boxes fails to initialize.
# modprobe ehea
IBM eHEA ethernet device driver (Release EHEA_0102)
alloc irq_desc for 256 on node 0
alloc kstat_irqs on node 0
irq: irq 590080 on host null mapped to virtual irq 256
ehea: Error in ehea_plpar_hcall_norets: opcode=26c ret=fffffffffffffffc arg1=8000000003000000 arg2=0 arg3=7000000000050400 arg4=fc9b0000 arg5=200 arg6=0 arg7=0
ehea: Error in ehea_reg_mr_section: register_rpage_mr failed
ehea: Error in ehea_reg_kernel_mr: registering mr failed
ehea: Error in ehea_setup_ports: creating MR failed
ehea 23c00200.lhea: setup_ports failed
ehea: probe of 23c00200.lhea failed with error -5
# lsmod
Module Size Used by
ehea 82002 0
ipv6 386130 24
fuse 89953 1
loop 20967 0
dm_mod 105104 0
sg 40193 0
sd_mod 46334 3
crc_t10dif 1619 1 sd_mod
ibmvscsic 36002 2
scsi_transport_srp 8024 1 ibmvscsic
scsi_tgt 17581 1 scsi_transport_srp
scsi_mod 218761 5 sg,sd_mod,ibmvscsic,scsi_transport_srp,scsi_tgt
# ifconfig eth0
eth0: error fetching interface information: Device not found
Yesterday's next worked fine.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2010-04-08 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 5:51 linux-next: Tree for April 8 Stephen Rothwell
2010-04-08 11:55 ` Sachin Sant [this message]
2010-04-09 17:48 ` [-next April 8] eHEA driver failure on powerpc Sachin Sant
2010-04-09 17:48 ` Sachin Sant
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=4BBDC447.3040901@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=HERING2@de.ibm.com \
--cc=linux-next@vger.kernel.org \
--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 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.