Bug 443383 – Most Ralink chipsets make the kernel-2.6.24.4-64.fc8 to crash

Bug 443383 - Most Ralink chipsets make the kernel-2.6.24.4-64.fc8 to crash

Summary:	Most Ralink chipsets make the kernel-2.6.24.4-64.fc8 to crash

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	John W. Linville
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-04-21 05:46 EDT by Nicolas Chauvet (kwizart)
Modified:	2008-04-21 10:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:	2.6.24.4-69.fc8
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-04-21 10:38:00 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Nicolas Chauvet (kwizart) 2008-04-21 05:46:25 EDT

Description of problem: Many users are reporting crash on early boot when they
have a Ralink chipset configured on their system.


Version-Release number of selected component (if applicable): 
kernel-2.6.24.4-64.fc8


How reproducible: always


Steps to Reproduce:
1. Boot on kernel-2.6.24.4-64.fc8 with Ralink chipset configured.
2. 
3.
  
Actual results: Kernel crash
(I personnaly experienced this on rt61pci and rt2500pci kernel modules but
rt73usb seems also experiencing problem wich suggest all ralink chipset are
affected)


Expected results:


Additional info:
I'm suggesting to use http://koji.fedoraproject.org/koji/buildinfo?buildID=46626
But i cannot test myself directly for now.

Comment 1 John W. Linville 2008-04-21 10:38:00 EDT

Yes, any later F8 kernel should do (at least until we break it again...)

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