Hi,
which version of the 2.4.17 patch are you using (the -nf one or the older)?
That's not a dasd problem, but a problem in the common I/O layer with the
handling of paths (I thought I had that one fixed - at least in the -nf
patch...)
Is there something wrong with the paths leading to your dasds? (Check with
#cp q paths to <devno>) If so, you might try to vary the ailing path(s)
offline completely and try if the system will come up then.
Mit freundlichen Gr��en/Regards
Cornelia Huck
Linux for zSeries Development
IBM Deutschland Entwicklung GmbH
Email: [EMAIL PROTECTED]
Phone: ext. +49(0)7031/16-4837, int. *120-4837
|---------+---------------------------->
| | Pat Carroll |
| | <pcarroll@llbean.|
| | com> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 05/28/02 06:38 PM|
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| 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]
