Hi,
This sounds like the dasd driver bug which I found on my hercules s390
emulator in Aug. 2001 and posted in this mailing list.
Please change drivers/s390/block/dasd.c around line 3316 as follows.
rc = device->discipline->start_IO (device->init_cqr);
if ( rc ) {
s390irq_spin_unlock_irqrestore(device->devinfo.irq, flags);
goto out;
}
device->level = DASD_STATE_INIT;
s390irq_spin_unlock_irqrestore(device->devinfo.irq, flags);
That is, the device level must be set inside the spin lock.
Hope this helps.
> I have a problem booting Suse 7.2 2.4.7 under VM.
...
> Partition check:
> dasda:VOL1/ 0X0192: dasda dasda1
> ...
> Kernel panic: VFS: Unable to mount root fs on 5e:05
> HCPGIR450W CP entered; disabled wait PSW 000A0000 80298088
>
> dasdb dasdb1 is never found/detected correctly
>
> Unless the VM system is VERY busy I can not get Linux to boot.
>
> It would seem that the Linux dasd init routines are expecting responses
> in a specific order. Probably not a good assumption.
--
[EMAIL PROTECTED] Motohiro Kanda Hitachi Ltd.
