Bug 769467

Summary: kernel crash at boot w/ 2.6.41 kernel, perhaps related to symbios scsi card with no bootable drives on it?
Product: [Fedora] Fedora Reporter: Steven Ellis <ellis>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-07 17:47:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
picture of crash screen none

Description Steven Ellis 2011-12-20 22:44:48 UTC 
Description of problem:
Kernel crashes immediately at boot, with these lines:

BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
IP: [<ffffffffa00c921b>] sym53c8xx_slave_destroy+0x63/0xfa [sym53c8xx]

(see attachment for a picture of the crash screen)

Version-Release number of selected component (if applicable):
Fedora 15 with any 2.6.41 kernel that I tried (the 2.6.40 kernel I have seems to be fine)

How reproducible:
I'm suspecting that the issue is that my symbios card has no bootable drives on it (in fact, it only hosts an LTO3 changer)

Steps to Reproduce:
1. boot a 2.6.41 kernel on Fedora 15
2. have a symbios card, probably with no hard drives attached (but probably needs something, as my symbios card has 2 scsi chains--only the second one with just the tape changer on it causes the problem.
3. profit!
  
Actual results:
Crash :-(

Expected results:
No Crash :-)

Additional info:
I can try to collect more data if necessary, I see that the I missed some of the stack trace from the crash in the attached photo.
Comment 1 Steven Ellis 2011-12-20 22:47:52 UTC 
Created attachment 548946 [details]
picture of crash screen
Comment 2 Steven Ellis 2011-12-20 23:00:58 UTC 
I just stumbled on this: http://permalink.gmane.org/gmane.linux.kernel/1224030
which suggests that this was a recent change--perhaps this has already been fixed upstream?
Comment 3 Josh Boyer 2012-06-07 15:18:21 UTC 
The patch you referenced went into the 3.3 kernel. Does 2.6.43/3.3 resolve this for you?
Comment 4 Steven Ellis 2012-06-07 16:26:43 UTC 
(In reply to comment #3)
> The patch you referenced went into the 3.3 kernel. Does 2.6.43/3.3 resolve
> this for you?

Yep--once I got a 2.6.43 kernel the issue went away.  I suppose I should have commented with an update to this issue, my apologies.
Comment 5 Josh Boyer 2012-06-07 17:47:26 UTC 
THanks.