Pat, No, you don't have to reformat your DASD. This looks like some sort of kernel bug, but what it might be, I have no idea. I would recommend checking the "devfs" parameter in your kernel configuration, but those "not operational" messages are coming out way before that would be an issue.
Mark Post -----Original Message----- From: Pat Carroll [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 12:38 PM To: [EMAIL PROTECTED] Subject: kernel 2.4.17 DASD not op? After successfully building 2.4.17 from Developerworks (thanks Mark), I get the following at IPL time: (DASD was formatted in classic layout under kernel 2.4.7) ------------------------------------------------------- i 173f clear hwc low level driver: can write messages hwc low level driver: can not read state change notifications hwc low level driver: can read commands hwc low level driver: can read priority commands Linux version 2.4.17 (root@vmlinux0) (gcc version 2.95.3 20010315 (SuSE)) #1 SMP Thu May 23 08:37:51 EDT 2002 We are running under VM (31 bit mode) This machine has an IEEE fpu Kernel command line: dasd=173f,173e,173d,200,201 iucv=TCPIP ctc=noauto root=/dev/dasda1 noinitrd Highest subchannel number detected (hex) : 000C SPID - Device 173F on Subchannel 0004, lpm 10, became 'not operational' SPID - Device 173E on Subchannel 0005, lpm 10, became 'not operational' SPID - Device 173D on Subchannel 0006, lpm 10, became 'not operational' . . . dasd: No device registered as (94:1) VFS: Cannot open root device "dasda1" or 5e:01 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 5e:01 HCPGIR450W CP entered; disabled wait PSW 000A0000 804A868E -------------------------------------------------------------- Rebooting from my 2.4.7 kernel works fine. Is there a requirement to reformat DASD with the new layout? TIA Patrick A. Carroll Senior Systems Engineer L. L. Bean Casco St Freeport, ME 04033 (207) 552-2426 [EMAIL PROTECTED]
