netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [-next April 8] eHEA driver failure on powerpc
       [not found] <20100408155113.ef8df30c.sfr@canb.auug.org.au>
@ 2010-04-08 11:55 ` Sachin Sant
  2010-04-09 17:48   ` Sachin Sant
  0 siblings, 1 reply; 2+ messages in thread
From: Sachin Sant @ 2010-04-08 11:55 UTC (permalink / raw)
  To: linux-next; +Cc: netdev, HERING2

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
---------------------------------

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [-next April 8] eHEA driver failure on powerpc
  2010-04-08 11:55 ` [-next April 8] eHEA driver failure on powerpc Sachin Sant
@ 2010-04-09 17:48   ` Sachin Sant
  0 siblings, 0 replies; 2+ messages in thread
From: Sachin Sant @ 2010-04-09 17:48 UTC (permalink / raw)
  To: Linux/PPC Development
  Cc: linux-next, netdev, HERING2, Anton Blanchard,
	Benjamin Herrenschmidt

Sachin Sant wrote:
> 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
I tracked this problem to the following commit.

commit 7545ba6f82924d4523f8f8a2baf2e517a750265d
powerpc/mm: Bump SECTION_SIZE_BITS from 16MB to 256MB

If i revert this commit, the network interface is initialized
properly. Verified this on two different power6 boxes.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-04-09 17:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20100408155113.ef8df30c.sfr@canb.auug.org.au>
2010-04-08 11:55 ` [-next April 8] eHEA driver failure on powerpc Sachin Sant
2010-04-09 17:48   ` Sachin Sant

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).