> NOTICE: cmi_hdl_create: chipid 15 coreid 0 strandid 0
handle already allocated!
I do not get that message at all. I am using ESX4i Update 1 (build
208167) on two Xeon W3520s with virtualization enabled.
Indeed, the update to ESXi 4 (build 219382) eliminates this message.
However, it sti
Hi Dana.
Looks like you are right. I can boot with acpi-user-options=2 option.
I've also done what's Brian suggested and got some output before "trap
type 8 ...":
load 'misc/acpidev' id 20 loaded
installing acpidev, module id 20
load 'drv/isa' id 21 loaded .
installing isa, modules id 21
You didn't read install document so you made wrong install. With ZFS you must
forgot your old behavior with disks/partitions/filesystems. You can get max
from ZFS when you use it for whole disk. Then you can divide your disk to
datasets as you want.
PS: Maybe you have a chance to add your "forg
Hello Juris,
You're running on an IBM xSeries machine: IBM xSeries 3650 64 bit,
which makes me certain this is reported as CR 6916573. Investigation
strongly suggests this is a duplicate of CR 6905550, regression induced
in build 129 and fixed in build 131. My apologies for the inconvenience.
sorry - 0xc000 is a bit over-zealous (it's what I had to use for a
different problem).
Try 0x8000 instead. I'm just curious what the last module loaded
was. I expected the majority of the output to scroll off the top of the
screen - it's only the last few lines I was hoping to catch
> Note that I have no special mind-reading abilities here, nor do I speak
> for Sun as an organization. Rather, this is my reading of the tea leaves.
Same here.
I am entirely too busy with other things to get caught up in discussions
about what can be, may be, should be. I am quite happy with So
I just installed OpenSolaris on a IBM desktop with an 80Gb hard drive. I
assigned the root partition 30gb to install off of the live cd. When I run a
format command after successful installation I am unable to see or partition
the remaining 50Gb. Typically I would expect format to reveal a parti
Dennis Clarke wrote:
Dennis Clarke wrote:
My impression is that Sun is currently leaving the server market ...
Jörg
Do you really think that Oracle will be running on anything less than a
multi-core and multi-socket Sparc server? I am certain that Solaris, as
a
server O
> Dennis Clarke wrote:
>
>>
>> > My impression is that Sun is currently leaving the server market ...
>> > Jörg
>>
>> Do you really think that Oracle will be running on anything less than a
>> multi-core and multi-socket Sparc server? I am certain that Solaris, as
>> a
>> server OS, will be arou
Joerg Schilling wrote:
> Dennis Clarke wrote:
>
>>
>>> My impression is that Sun is currently leaving the server market ...
>>> Jörg
>> Do you really think that Oracle will be running on anything less than a
>> multi-core and multi-socket Sparc server? I am certain that Solaris, as a
>> server O
I've tried.
But strings are scrolling too fast (is it possible to do some kind of
paging), and the only thing I can see before "trap type 8 ..." is
kobj_read_file: size
kobj_close: 0x82
after that I have "trap type 8 ..." and
panic: entering debugger
Loaded modules: [ mac specfs ]
k
Dennis Clarke wrote:
>
> > My impression is that Sun is currently leaving the server market ...
> > Jörg
>
> Do you really think that Oracle will be running on anything less than a
> multi-core and multi-socket Sparc server? I am certain that Solaris, as a
> server OS, will be around for a nice
> My impression is that Sun is currently leaving the server market ...
> Jörg
Do you really think that Oracle will be running on anything less than a
multi-core and multi-socket Sparc server? I am certain that Solaris, as a
server OS, will be around for a nice long time. Certainly Fujitsu would
Joerg Schilling wrote:
> My impression is that Sun is currently leaving the server market by ceasing
> the
> distribution of Solaris Express while the supposed successor (Indiana) is not
> ready for either he server market or the desktop.
That would be incorrect, since Solaris 10 has been and con
Juris Krumins wrote:
panic[cpu0]/thread = fbc2e3a0: mutex_enter: bad mutex, lp=20
owner=f000e987f000fea0 thread=fbc2e3a0
unix: mutex_panic + 73 ()
unix: mutex_vector_enter +446()
genunix: zone_getspecific+2b ()
genunix: core+5f ()
unix: kern_gpfault+18e ()
unix: trap+41e ()
un
Anon Y Mous wrote:
> No, this is very much incorrect. Joyent does not run "OpenSolaris Indiana" in
> production, they run "Solaris Express" in production. There is a big
> difference! Go to the link below for Ben Rockwood's opinion on OpenSolaris
> Indiana:
>
> http://www.cuddletech.com/blog
> > Experiencing very strange behaviour with upgraded
> > OpenSolaris machine ( from snv_124 to snv_130 )
> >
> > Machine gets panic, with the following error:
>
> Just a wild guess...
>
> An opensolaris upgrade currently has a nasty bug
> that
> results in old kernel modules ending in the
> boo
17 matches
Mail list logo
