Hi Mark I'm trying to force the use of the diag driver for vdisk swap devices. In particular, I want to set up device 801 as the default swap device for all servers, and have the ability to add additional swap devices at 900-90f, as required. Results are documented below. In my search I found hints that there may be an issue with diag250 in 64 bit mode with > 2GB of memory, hence the question.
Here's a snippet of the boot messages: Nov 20 13:25:18 vmlinux1 kernel: We are running under VM (64 bit mode) Nov 20 13:25:18 vmlinux1 kernel: Built 1 zonelists Nov 20 13:25:18 vmlinux1 kernel: Kernel command line: dasd=800,801(diag),802-83f,900-90f(diag) possible_cpus=2 root=LABEL=/ BOOT_IMAGE=0 <snip> Nov 20 13:25:19 vmlinux1 kernel: dasd(eckd): 0.0.0800: 3390/0C(CU:3990/01) Cyl:10016 Head:15 Sec:224 Nov 20 13:25:19 vmlinux1 kernel: Using cfq io scheduler Nov 20 13:25:19 vmlinux1 netfs: Mounting other filesystems: succeeded Nov 20 13:25:19 vmlinux1 kernel: dasd(eckd): 0.0.0800: (4kB blks): 7211520kB at 48kB/trk compatible disk layout Nov 20 13:25:19 vmlinux1 kernel: dasda:VOL1/ 0X0800: dasda1 dasda2 Nov 20 13:25:19 vmlinux1 kernel: dasd_generic couldn't online device 0.0.0801 - discipline DIAG not available Nov 20 13:25:19 vmlinux1 kernel: dasd_generic_probe: could not initially online cw-device 0.0.0801 <snip> Nov 20 13:25:19 vmlinux1 kernel: dasd_generic couldn't online device 0.0.0900 - discipline DIAG not available Nov 20 13:25:19 vmlinux1 kernel: dasd_generic_probe: could not initially online ccw-device 0.0.0900 After boot is complete, here's some status: bash-3.00# cat /sys/bus/ccw/devices/0.0.0801/online 0 bash-3.00# cat /sys/bus/ccw/devices/0.0.0900/online 0 bash-3.00# cat /sys/bus/ccw/devices/0.0.0801/use_diag 1 bash-3.00# cat /sys/bus/ccw/devices/0.0.0900/use_diag 1 Echoing a "1" to online does not change the status of etiher device. >From vmlinux1's PROFILE EXEC: /* Set up swap on vdisk */ 'EXEC SWAPGEN 801 819200 (DIAG' 'EXEC SWAPGEN 900 819200 (DIAG' Here's what CP says (after boot is complete): #CP Q V DASD <snip> DASD 0800 3390 VM6472 R/W 10016 CYL ON DASD 6472 SUBCHANNEL = 0007 DASD 0801 9336 (VDSK) R/W 819200 BLK ON DASD VDSK SUBCHANNEL = 0011 DASD 0900 9336 (VDSK) R/W 819200 BLK ON DASD VDSK SUBCHANNEL = 0012 Modprobe.conf and zipl.conf look correct (see the third boot message, above). The initrd image has dasd_diag_mod in it (I decomposed and verified). I'm running out of ideas...?? Thanks for your response. Cheers....Pat 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 Mark Post Sent: Tuesday, November 20, 2007 6:21 PM To: [email protected] Subject: >>> On Tue, Nov 20, 2007 at 5:39 PM, in message <[EMAIL PROTECTED]>, Pat Carroll <[EMAIL PROTECTED]> wrote: > Can someone please clear up some confusion... > Does the dasd diag driver (dasd_diag_mod) work in a 64 bit Red Hat > Linux server configured with > 2GB memory? > > RH4 U4 (2.6.9-55.0.2.EL) and z/VM 5.2 RSU 0602 (64 bit). It should. What problem(s) are you having with it? 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 ---------------------------------------------------------------------- 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
