Bug 1001632 - Suspend/Resume doesn't work for Areca RAID controller [NEEDINFO]
Summary: Suspend/Resume doesn't work for Areca RAID controller
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-27 12:33 UTC by Ferry Huberts
Modified: 2014-03-10 14:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 14:44:26 UTC
Type: Bug
jforbes: needinfo?

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

Description Ferry Huberts 2013-08-27 12:33:37 UTC 
Description of problem:
I have several systems with Areca RAID controllers.
For all of these systems suspend/resume doesn't work.



Version-Release number of selected component (if applicable):
kernel 3.10.9-200.fc19.x86_64

How reproducible:
always


Additional info:

Areca ARC-1210
Areca ARC-1261
Areca ARC-1882I
Comment 1 Josh Boyer 2013-09-18 20:37:32 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.
Comment 2 Josh Boyer 2013-10-08 16:09:23 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Comment 3 Ferry Huberts 2013-10-08 16:25:55 UTC 
still an issue on latest kernel: 3.11.3-201.fc19.x86_64
Comment 4 Justin M. Forbes 2014-01-03 22:11:28 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.
Comment 5 Justin M. Forbes 2014-03-10 14:44:26 UTC 
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.
Note You need to log in before you can comment on or make changes to this bug.