Hi Juergen,
I tried it out and yes both the fields are
filled with valid values (ufs for fs-type ,and bo_name
has the valid dev name)
Thanks
Som
--- Juergen Keil [EMAIL PROTECTED] wrote:
Hi Som,
I have a strange issue with the iscsi
boot,whenever i do a 'reboot'
Juergen,
Yes i did because except for the address,
everything else was identical.
There was NO name following the msg path.Infact there
is a blank line ,but when i did step through the code
,even after the panic happened and i did a
rootfs::print ,the correct value for bo_name showed
Hi Som,
I have met similar problem before. The root cause of my problem is the
root disk not being configured correctly.
Are you sure your boot disk(iSCSI target) was enumerated by your iscsi
initiator driver correctly and attached already?
You can use -k option to boot your system and when
Wesley Shao wrote:
I would prefer this information be presented in an architected manner
so it would work for both SPARC and x86 platforms and move the
package/core/thread determination out of the driver and into kernel,
wouldn't you agree?
Yes. Essentially the only information I care
FYI.
- Forwarded message from Garrett D'Amore - sun microsystems [EMAIL
PROTECTED] -
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
From: Garrett D'Amore - sun microsystems [EMAIL PROTECTED]
Date: Wed, 05 Mar 2008 00:01:27 -0800 (PST)
Subject: Brussels framework
FYI.
- Forwarded message from Garrett D'Amore - sun microsystems [EMAIL
PROTECTED] -
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
From: Garrett D'Amore - sun microsystems [EMAIL PROTECTED]
Date: Tue, 04 Mar 2008 21:24:01 -0800 (PST)
Subject: Brussels: NDD compatiblity support
Javen,
Thank you once again, but one thing i do not
understand is if that is the case,then why does it
boot fine after the reboot ,i mean everytime there is
a panic ..the subsequent reboot that is initiated by
it always leads to a succesful boot ..(reboot from
this stage again leads to a
