Re: Re: fr1-2.16 patch for 2.6.10 kernel

> 
> Looks like rdev is fine. Or at least not equal to zero. Just print
> rdev.
> 
>   	printk(KERN_INFO "md: *****test***rdev=%p***!!!\n", rdev);
> 
> Same for mddev.
> 
added	

		ITERATE_RDEV(mddev,rdev,rtmp) {
				if (!mddev) {
					printk(KERN_INFO "md: *****BUG***mddev***********!!!\n");
					break;
				}
				printk(KERN_INFO "md: *****mddev=%p rdev=%p *************!!!\n", mddev, rdev);
				if (!rdev) {
					printk(KERN_INFO "md: *****BUG**rdev*************!!!\n");
					break;
				}

and got this  :


first hotadd (no crash)

Mar 22 09:10:11 ldap-fixe kernel:  disk 1, wo:0, o:1, dev:sda2
Mar 22 09:10:11 ldap-fixe kernel: md: 3846
Mar 22 09:10:11 ldap-fixe kernel: md: *****mddev=f7fc8480 rdev=f7ff7bc0 *************!!!
Mar 22 09:10:11 ldap-fixe kernel: md: *****test2************!!!
Mar 22 09:10:11 ldap-fixe kernel: md: *****mddev=f7fc8480 rdev=f7ff7c40 *************!!!
Mar 22 09:10:11 ldap-fixe kernel: md: *****test2************!!!

hotremove :

Mar 22 09:12:09 ldap-fixe kernel: raid1: Disk failure on sda1, disabling device.
Mar 22 09:12:09 ldap-fixe kernel: ^IOperation continuing on 1 devices
Mar 22 09:12:09 ldap-fixe kernel: raid1: bitmap f7cbb740 already active!


second one (crash)

Mar 22 09:13:18 ldap-fixe kernel: md0: md_check_recovery 2: cleared recovery bits on sb f7fc8480
Mar 22 09:13:18 ldap-fixe kernel: md0: md_check_recovery 2: restored repair bit on sb f7fc8480
Mar 22 09:13:18 ldap-fixe kernel: md: 3830
Mar 22 09:13:18 ldap-fixe kernel: md: 3838
Mar 22 09:13:18 ldap-fixe kernel: md: 3846
Mar 22 09:13:18 ldap-fixe kernel: md: 3838
Mar 22 09:13:18 ldap-fixe kernel: md: 3846
Mar 22 09:13:18 ldap-fixe kernel: md: *****mddev=f7fc8480 rdev=f7188b40 *************!!!
Mar 22 09:13:18 ldap-fixe kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
Mar 22 09:13:18 ldap-fixe kernel:  printing eip:
Mar 22 09:13:18 ldap-fixe kernel: f88a53d7
Mar 22 09:13:18 ldap-fixe kernel: *pde = 00000000
Mar 22 09:13:18 ldap-fixe kernel: Oops: 0000 [#1]
Mar 22 09:13:18 ldap-fixe kernel: PREEMPT
Mar 22 09:13:18 ldap-fixe kernel: Modules linked in: raid1 bitmap md epic100 usbkbd parport_pc lp parport
Mar 22 09:13:18 ldap-fixe kernel: CPU:    0
Mar 22 09:13:18 ldap-fixe kernel: EIP:    0060:[__crc_proc_dointvec_minmax+1718380/2155284]    Not tainted
Mar 22 09:13:18 ldap-fixe kernel: EFLAGS: 00010083   (2.6.8-enbd-fr1-debug1)
Mar 22 09:13:18 ldap-fixe kernel: EIP is at raid1_add_disk+0x4f/0xf8 [raid1]
Mar 22 09:13:18 ldap-fixe kernel: eax: 00000000   ebx: f798abe0   ecx: c0431cdc   edx: f7fc8280
Mar 22 09:13:18 ldap-fixe kernel: esi: f7188b40   edi: 00000000   ebp: f7fc8480   esp: f7787f30
Mar 22 09:13:18 ldap-fixe kernel: ds: 007b   es: 007b   ss: 0068
Mar 22 09:13:18 ldap-fixe kernel: Process md0_raid1 (pid: 610, threadinfo=f7786000 task=f76fe7d0)
Mar 22 09:13:18 ldap-fixe kernel: Stack: f7188b40 f7fc8480 f7ff7bc0 f7fc8490 00000000 f7fc8280 f88b9cdd f7fc8480
Mar 22 09:13:18 ldap-fixe kernel:        f7188b40 f7cbb700 f7786000 f7787fdc f7786000 f7fc850c 00000000 f88a59f5
Mar 22 09:13:18 ldap-fixe kernel:        f7fc8480 f7cbb700 f7786000 f7787fdc f7786000 00000000 f76fe7d0 00000000

mddev seems correct.