Bug 956

Summary:	Kernel hangs when using a primary and secondary IDE controller under software raid0
Product:	IO/Storage	Reporter:	SpamBox
Component:	IDE	Assignee:	Bugme Janitors Team (bugme-janitors)
Status:	REJECTED INSUFFICIENT_DATA
Severity:	blocking	CC:	bunk
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.4.20-18.9 and 2.6.0-mm1-ac2	Subsystem:
Regression:	---	Bisected commit-id:
Attachments:	.config and everything else I could think of that might be helpful

Description SpamBox 2003-07-18 00:11:37 UTC

Distribution:RedHat 9.0
Hardware Environment:K7V motherboard with onboard ATA66 controller. Secondary 
controller is Promise PCD20268 - ATA100
Software Environment: 2.4.20-18.9 and 2.6.0-mm1-ac2
Problem Description: I'm attempting to use 3 HDs under software raid0. My 
Maxtor 40GB HD is attached 
to the ATA66 onboard controller on my K7V motherboard, and my two 20GB IBM HDs 
are attached to the secondary Promise controller (PDC20268 - ATA100).

If I create a raid0 configuration consisting only of my two IBM HDs everything 
is fine. When using all 3 HDs the kernel locks up so tightly that even 
Alt+SysRq+T does not respond.

All three HDs can be used in Linux provided they are not used in raid.

Tests were run using ext3 and ext2.

I have researched the problem for a couple weeks and the only work-around I 
have found is using ide=nodma which is not a very desirable solution.

I will be glad to add additional info if it is needed. Just let me know.


Steps to reproduce:
1. The problem should be reproducable by using a primary and secondary IDE 
controller under software raid0.
2.Run bonnie++

Comment 1 SpamBox 2003-07-19 18:26:40 UTC

Created attachment 581 [details]
.config and everything else I could think of that might be helpful

Hopefully with this additional input a resolution/fix will be forthcoming soon.

Once again, if additional input is needed please let me know.

Comment 2 SpamBox 2003-08-08 12:42:11 UTC

Is there any additional info that I can provide that may help resolve this 
problem?

Comment 3 Adrian Bunk 2005-07-04 16:07:09 UTC

Is this problem still present in recent 2.6 kernels?

Comment 4 Adrian Bunk 2005-08-03 09:05:45 UTC

Please reopen this bug if you are still able to reproduce it in recent 2.6 kernels.