Bug 230869 – F7T2 libata null pointer kernel crash

Bug 230869 - F7T2 libata null pointer kernel crash

Summary:	F7T2 libata null pointer kernel crash

Status:	CLOSED DUPLICATE of bug 230318

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Kernel Maintainer List
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-03-03 19:50 EST by Andy Burns
Modified:	2007-11-30 17:11 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-03-07 14:33:50 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
screen photo (205.32 KB, image/jpeg) 2007-03-03 19:50 EST, Andy Burns	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andy Burns 2007-03-03 19:50:05 EST

Description of problem:

Booting from live CD, kernel crashes during libata device probing

Version-Release number of selected component (if applicable):

F7T2

How reproducible:

always

Steps to Reproduce:
1. boot from live CD
2.
3.
  
Actual results:

null pointer boom, see attached

Expected results:


Additional info:

machine is Dell D800 laptop, has run FC1/2/3/4/5/6 OK

disk devices present
PATA 2.5" hard drive
PATA DVD reader/CD rewriter
1GB lexar CF card in PCMCIA adapter

Comment 1 Andy Burns 2007-03-03 19:50:05 EST

Created attachment 149196 [details]
screen photo

Comment 2 Andy Burns 2007-03-03 20:16:39 EST

Turns out the offending drive is the CF in the PCMCIA adapter, removing that
allows booting, not yet tried hot-plugging it back in when F7 is running.

Comment 3 Alan Cox 2007-03-07 14:33:50 EST


*** This bug has been marked as a duplicate of 230318 ***

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