Hello Andrew,
There are changes to both sata_nv and to md in 2.6.13-mm2. To isolate them
it would be great of you could apply
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/broken-out/linus.patch
I applied and tested it with 2.6.13 vanilla kernel + linux.patch as suggested, but so far no problem as with 2.6.13-mm2.
I also played with the git-snapshots 2.6.13-git[1-9] no problem here. I think the problem is
somewhere else we have to pay attention, too. MD Raidlevels [0,1] failed to start with 2.6.13-mm2.
Raid0 config:
2x 20GB Partitiontype 0xFD "Linux Raid autodetect"
64k Chunksize, persistent superblock.
little output from mdadm
/dev/md2:
Version : 00.90.02
Creation Time : Sun Jun 26 19:14:45 2005
Raid Level : raid0
Array Size : 40001536 (38.15 GiB 40.96 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Sun Jun 26 19:14:45 2005
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 64K
UUID : c53fa0d8:9d85875b:efb82dde:11c6617c
Events : 0.1
Number Major Minor RaidDevice State
0 8 23 0 active sync /dev/sdb7
1 8 6 1 active sync /dev/sda6
Raid1 config.
2x 15GB Partitiontype 0xFD "Linux Raid autodetect"
chunksize 128k.
I have no idea where I should look, to resolve this behavior.
to 2.6.13 and see if the problem still happens. That will separate out the
md changes which are still in -mm.
Thanks.
As for all the time, I'm willing to test to glue the problem out.
Thanks
Best regards
--
Michael Thonke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |