Bug 691585 - pagefault (oops) from iwl_queue_space
Summary: pagefault (oops) from iwl_queue_space
Keywords:
Status: CLOSED DUPLICATE of bug 688252
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-28 21:48 UTC by Bastiaan Jacques
Modified: 2011-04-22 12:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-22 12:13:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
photo of screen showing oops (981.88 KB, image/jpeg)
2011-03-28 21:48 UTC, Bastiaan Jacques
no flags Details

Description Bastiaan Jacques 2011-03-28 21:48:51 UTC
Created attachment 488281 [details]
photo of screen showing oops

Description of problem:
Oops that seems to originate in iwl_queue_space().

Version-Release number of selected component (if applicable):
kernel-2.6.38-1.fc15.i686

How reproducible:
Occasionally

Steps to Reproduce:
1. Connect to wireless internet (iwl3945)
2. leave the computer alone for a few hours
3.
  
Actual results:
Fedora switched from X to console and showed oops message.

Expected results:
Continue functioning as normal.

Additional info:
I took a photo of the screen, which is attached.

Comment 1 Stanislaw Gruszka 2011-03-31 07:59:03 UTC
Looks like duplicate of 688252
disable_hw_scan=1 should help
https://bugzilla.redhat.com/show_bug.cgi?id=688252#c6

Comment 2 Bastiaan Jacques 2011-04-14 17:13:13 UTC
(In reply to comment #1)
> Looks like duplicate of 688252
> disable_hw_scan=1 should help
> https://bugzilla.redhat.com/show_bug.cgi?id=688252#c6

Because the oops happened so infrequently it took a while to confirm that in fact disable_hw_scan=1 prevents it from happening.

Comment 3 Stanislaw Gruszka 2011-04-22 12:13:41 UTC

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


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