Bug 921588

Summary:

ipr driver unable to load, probe failed with error -5

Product:

[Fedora] Fedora

Reporter:

Ingvar Hagelund <ingvar>

Component:

kernel

Assignee:

Kernel Maintainer List <kernel-maint>

Status:

CLOSED INSUFFICIENT_DATA

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

CC:

gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda

Target Milestone:

---

Target Release:

---

Hardware:

ppc64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2013-10-08 17:31:26 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Output of lspci -xx	none

Description Ingvar Hagelund 2013-03-14 13:35:33 UTC

Description of problem:
At boot time, ipr module reports 
ipr: probe of 0001:d0:01.0 failed with error -5

No disk is found, so Fedora won't boot

Hardware: IBM 720 OpenPower.

Version-Release number of selected component (if applicable):
3.6.10-4.fc18.ppc64 (fedup boot image)

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora 17 with all errata

2. Boot fedup updater with 3.6.10-4.fc18.ppc64 (That is the image found when feora repo baseurl is set to http://secondary.fedoraproject.org/pub/fedora-secondary/releases/$releasever/Fedora/$basearch/os/ )

Actual results:
At reboot, ipr loads, but says

[  287.805063] ipr: IBM Power RAID SCSI Device Driver version: 2.5.3 (March 10, 2012)
[  287.805307] ipr 0001:d0:01.0: Found IOA with IRQ: 151
[  287.805657] ipr 0001:d0:01.0: Write of cache line size failed
[  287.805933] ipr: probe of 0001:d0:01.0 failed with error -5

And then it just drops to the dracut shell.


Expected results:
Works fine in f17, so it should work fine in f18 too

Additional info:

lspci reports the scsi device used like this:

0001:d0:01.0 SCSI storage controller: Mylex Corporation AcceleRAID 600/500/400/Sapphire support Device (rev 04)
	Subsystem: IBM Dual Channel PCI-X U320 SCSI Adapter
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 144, Cache Line Size: 128 bytes
	Interrupt: pin A routed to IRQ 151
	BIST result: 00
	Region 0: Memory at 401f0900000 (64-bit, non-prefetchable) [size=256K]
	Region 2: Memory at 401f0000000 (64-bit, prefetchable) [size=8M]
	Expansion ROM at 401f0800000 [disabled] [size=1M]
	Capabilities: [40] PCI-X non-bridge device
		Command: DPERE+ ERO+ RBC=4096 OST=2
		Status: Dev=d0:01.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=4096 DMOST=8 DMCRS=64 RSCEM- 266MHz- 533MHz-
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: ipr

Comment 1 Ingvar Hagelund 2013-03-14 13:50:50 UTC

Exactly same results with kernel 3.7.9-201.fc18.ppc64

Comment 2 Ingvar Hagelund 2013-03-14 14:25:02 UTC

I guess this is caused by the update of the ipr driver. The kernels I have tested above have versions 2.5.3 and 2.5.4.

The latest version that works on my 720 is 2.5.2.

Comment 3 Ingvar Hagelund 2013-03-14 14:35:24 UTC

Created attachment 710046 [details]
Output of lspci -xx

This was fetched running 3.3.4-5.fc17.ppc64

Comment 4 Ingvar Hagelund 2013-03-20 14:11:56 UTC

Compiled the latest¹ kernel.org ipr driver, version 2.6.0 against kernel 3.7.9-201.fc18.ppc64. Same results.

Ingvar



1) https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/?id=a937536b868b8369b98967929045f1df54234323

Comment 5 Josh Boyer 2013-07-02 19:23:09 UTC

Does this still happen with the F19 images?  If so, you probably want to ask Brian King and/or Wen Xiong about it on the linuxppc-dev list.

Comment 6 Josh Boyer 2013-09-18 20:44:41 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 7 Josh Boyer 2013-10-08 17:31:26 UTC

This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.