Bug 660346 - cpqphp driver crashes on HP Proliant DL380
Summary: cpqphp driver crashes on HP Proliant DL380
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-06 15:50 UTC by William H. Haller
Modified: 2011-06-28 10:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 10:08:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/proc/cpuinfo (2.48 KB, text/plain)
2010-12-06 15:50 UTC, William H. Haller
no flags Details
lsmod output (1.49 KB, text/plain)
2010-12-06 15:51 UTC, William H. Haller
no flags Details
lspci output (11.87 KB, text/plain)
2010-12-06 15:51 UTC, William H. Haller
no flags Details
lsusb output (2.11 KB, text/plain)
2010-12-06 15:52 UTC, William H. Haller
no flags Details

Description William H. Haller 2010-12-06 15:50:42 UTC
Created attachment 465005 [details]
/proc/cpuinfo

Description of problem: Upgraded from working Fedora 12 system since it reached EOL against fully updated fedora repository via yum. Upon reboot, the system failed to start. Analysis of dmesg output in single user mode showed cpqphp failed to handle kernel NULL pointer at 00000050.


Version-Release number of selected component (if applicable): kernel-PAE-2.6.34.7-61.fc13.i686. The normal non PAE kernel also fails. The still installed kernel-PAE-2.6.32.26-175.fc12.i686 works fine.


How reproducible: Always. The system crashes when doing module probing after udev prompt.


Steps to Reproduce:
1. Boot system
2.
3.
  
Actual results: Modprobe fails and system hangs. You can Ctrl-Alt-Del it to get it to either reboot or continue on to single mode for dmesg, but is not functional.


Expected results: Upgrade from F12 to F13 should just work. Google searches seem to imply that this bug was found and fixed at some point around 2.6.33, and I'm not sure why 2.6.34 is failing again.


Additional info: See attachments. This is a production system so I'm not at liberty to experiment with test kernels. I will be happy to install released kernels and report back, or provide any other hardware details that I can.

Comment 1 William H. Haller 2010-12-06 15:51:33 UTC
Created attachment 465006 [details]
lsmod output

Comment 2 William H. Haller 2010-12-06 15:51:57 UTC
Created attachment 465007 [details]
lspci output

Comment 3 William H. Haller 2010-12-06 15:52:25 UTC
Created attachment 465008 [details]
lsusb output

Comment 4 William H. Haller 2010-12-06 15:53:47 UTC
blacklisting the cpqphp driver, along with hpwdt and hpilo for good measure, allows the system to boot and run properly.

Comment 5 Chuck Ebbert 2010-12-15 02:12:42 UTC
Can you upload the oops report?

Comment 6 William H. Haller 2011-02-01 20:01:51 UTC
Sorry for the delay. The e-mail got spam filtered for some reason. I find no kerneloops* directories where google seems to indicate one might be found. If you can indicate where to look, I'd be happy to do so.

Comment 7 Bug Zapper 2011-05-30 13:03:14 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Bug Zapper 2011-06-28 10:08:46 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.