Peter, 
Looking at these messages, and as you said earlier, the diag driver is
getting loaded well after dasd_generic_probe tries to online the device.
Interesting that I can't manually online the device after the diag
driver finally gets loaded...
Cheers...Pat 


Loading dasd_mod.ko module
Loading dasd_eckd_mod.ko module
dasd(eckd): 0.0.0800: 3390/0C(CU:3990/01) Cyl:10016 Head:15 Sec:224
Using cfq io scheduler
dasd(eckd): 0.0.0800: (4kB blks): 7211520kB at 48kB/trk compatible disk
layout
 dasda:VOL1/  0X0800: dasda1 dasda2
Loading dasd_fba_mod.ko module
dasd_generic couldn't online device 0.0.0801 - discipline DIAG not
available
dasd_generic_probe: could not initially online ccw-device 0.0.0801
dasd_generic couldn't online device 0.0.0900 - discipline DIAG not
available
dasd_generic_probe: could not initially online ccw-device 0.0.0900 
Loading jbd.ko module
Loading ext3.ko module
Loading dasd_diag_mod.ko module
<<<<<<<<<<<<<<---------------------------


Patrick Carroll  |  Enterprise Architect
L.L.Bean, Inc.(r) |  Double L St. |  Freeport ME 04033
http://www.llbean.com | [EMAIL PROTECTED] | 207.552.2426

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter 1 Oberparleiter
Sent: Monday, November 26, 2007 12:38 PM
To: [email protected]
Subject: Re: Missing DIAG discipline; was RE:

Linux on 390 Port <[email protected]> wrote on 26.11.2007
16:23:33:
> Linux on 390 Port <[email protected]> wrote on 26.11.2007
> > Has DIAG access to a DASD worked before on your system (i.e. not at 
> > reboot but by manual activation)?
> Yes...methinks that this started after a mkinitrd/zipl

Ok, did some tests and ran into the same issue.. on RHEL5. Apparently
there are two problems:

1) mkinitrd does not include support for dasd_diag_mod - I'm assuming
you specified the module using mkinitrd's --with= switch
2) a kernel bug prevents devices that failed to be activated during dasd
module load to be activated later on

Because of 1) and the fact that the --with switch adds modules too late
in the initialization sequence, you seem to be running into 2). As a
workaround, use the following method:

        mkinitrd initrd-<version> <version> --preload=dasd_mod
--preload=dasd_diag_mod


Regards,
  Peter

--
Peter Oberparleiter
Linux on System z Development
IBM Deutschland Entwicklung GmbH

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to