Bug 520233 - [MCP55] Nvidia SATA kernel module causing all kinds of problems
Summary: [MCP55] Nvidia SATA kernel module causing all kinds of problems
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-29 12:40 UTC by Dennis de Vaal
Modified: 2010-06-28 14:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 14:22:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (10.98 KB, text/plain)
2009-08-29 12:40 UTC, Dennis de Vaal
no flags Details
lspci (11.55 KB, application/octet-stream)
2009-08-29 12:41 UTC, Dennis de Vaal
no flags Details
fdisk -l (2.35 KB, application/octet-stream)
2009-08-29 12:43 UTC, Dennis de Vaal
no flags Details
complete dmesg log (74.52 KB, text/plain)
2009-08-29 12:44 UTC, Dennis de Vaal
no flags Details

Description Dennis de Vaal 2009-08-29 12:40:49 UTC
Created attachment 359150 [details]
dmesg

Description of problem:

The kernel is mounting my volumes read only when doing normal or intensive I/O operations. I have checked the drives and replaced cabling. See attached dmesg log.

Fedora 11 fully updated.

How reproducible:

Copying some small or large files from drive to drive.

Steps to Reproduce:
See above
  
Actual results:
See dmesg log

Expected results:
Additional info:

Comment 1 Dennis de Vaal 2009-08-29 12:41:09 UTC
Created attachment 359151 [details]
lspci

Comment 2 Dennis de Vaal 2009-08-29 12:43:43 UTC
Created attachment 359152 [details]
fdisk -l

incomplete fdisk -l output

Comment 3 Dennis de Vaal 2009-08-29 12:44:40 UTC
Created attachment 359153 [details]
complete dmesg log

Comment 4 Dennis de Vaal 2009-08-29 12:46:42 UTC
These problems are not ocurring on my first SATA drive. When I reboot everything seems to be running normal. Except when I am performing the above. Copying files, doing other I/O operations.

Comment 5 Aioanei Rares 2009-10-07 10:54:46 UTC
Do your harddisks support NCQ?

Comment 6 Bug Zapper 2010-04-28 10:03:43 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 7 Bug Zapper 2010-06-28 14:22:34 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.