Red Hat Bugzilla – Bug 105023
dasd_diag_mod.o not found.
Last modified: 2007-11-30 17:06:58 EST
2.4.21-1.1931.2.399.ent #1 SMP Wed Aug 20 15:23:46 EDT 2003 s390x s390x s390x
2.4.21-3.EL #1 SMP Fri Sep 19 13:58:05 EDT 2003 s390x s390x s390x GNU/Linux
and attempting to load the dasd_diag module for VM reserved minidisk.
Found that the dasd_diag_mod.o is not present in
Please contact me for any further information
The diag access is not enabled in Taroon. It was present in Mach1,
although it never was supported officially (neither was FBA).
Is it good for anything at all? I thought that ECKD method
covered all possible dasds, and that VM diagnostics only
allowed access to something which Linux cannot use anyway.
The xpram is driven by FBA module. The Open System SCSI is
driven by zfcp.
I'll ask Florian to clarify.
This module is used for VM minidisks and if this item has fallen through for GA,
we should add this item to the IBM <-> Red Hat discussions and check if this
should be changed for U1.
Pete, can you comment on why it is left out? The config file looks like this is
marked as a module we wanted to include for GA, so there must be some problem
in the s390 code the prevent it from proper building?
Florian La Roche
I've just gone back and checked our kernel again, since I was sure I have used
this module a few weeks ago. Seems it is properly included in the s390(31bit)
version, but not in the s390x(64bit) release. Config files are identical, so
there must be some s390 <-> s390x bug in the configuration or Pete is right and
this module might not make that much sense on newer setups?
Florian La Roche
Hi Pete, the guy that was trying to load dasd diag was trying to run a test
scenario for reserved VM minidisk. I was reading the change log for
kernel-unsupported yesterday and it looks like you added some support for
reserved minidisk in there. We will test this with RC 1 and see what happens.
Florian is right. The configuration file drivers/s390/Config.in says
if [ "$CONFIG_ARCH_S390X" != "y" ]; then
dep_tristate ' Support for DIAG access to CMS reserved Disks'
This is identical to what 2.4.9 based kernels were, and
what is in Marcelo tree. So, this is not a regression.
I think only experts in Boeblingen can tell why the diag
access is only used in 31 bit more.
*** Bug 106602 has been marked as a duplicate of this bug. ***
Here are some comments from one of the IBM Linux Developers:
I woould make the below update to the bugzilla, but I have no write access........
We disabled the DIAG module fo 64 bit simply because the z/VM DIAG250 access method
used in this module is NOT 64 bit ready. This means that as soon as the machine
is using more than 2G memory we might get unpredictable results if using the module.
Therefore we disabled the module for 64bit and I think we should not enable
again until z/VM DIAG supports 64bit addresses.
The ECKD module is able to access this kind of devices using CCWs without any
restrictions. In fact there is NO NEED for the DIAG access method.
Hope this helps....
Mit freundlichen Gruessen / Best regards
Linux for eServer Development (D/3303)
Schoenaicher Str. 220, 71032 Boeblingen, Germany