>>> On Mon, Nov 26, 2007 at 1:36 PM, in message <[EMAIL PROTECTED]>, Pat Carroll <[EMAIL PROTECTED]> wrote: > 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...
That would be the kernel bug Peter mentioned, I suppose. > 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 This definitely looks like the modules are not being loaded in the proper order. Tell you what... If you would, send me a copy of your initrd and mkinitrd script, off-list. I'll take a look at them. Mark Post ---------------------------------------------------------------------- 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
