Ok. Thanks a lot for your help. Lets wait for snv_131.
> Thanks -
> Dana
>
> > -Original Message-
> > From: Dana H. Myers
> > Cc: opensolaris-discuss@opensolaris.org
> > Subject: Re: [osol-discuss] OpenSolaris snv_130
> panic.
> > Date: T
rrupt routing
(you'll lose some, but not all ACPI-based features).
Build 131 should correct this, though.
Thanks -
Dana
-Original Message-
From: Dana H. Myers
Cc: opensolaris-discuss@opensolaris.org
Subject: Re: [osol-discuss] OpenSolaris snv_130 panic.
Date: Thu, 14 Jan 2010 09:58
loaded .
installing isa, modules id 21
trap: Unknown trap type 8 in user mode
panic[cpu0]/thread (previously posted message)
-Original Message-
From: Dana H. Myers
Cc: opensolaris-discuss@opensolaris.org
Subject: Re: [osol-discuss] OpenSolaris snv_130 panic.
Date: Thu,
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.
use I'm not that experienced in kmdb.
-Original Message-
From: Brian Ruthven - Sun UK
To: Juris Krumins
Cc: opensolaris-discuss@opensolaris.org
Subject: Re: [osol-discuss] OpenSolaris snv_130 panic.
Date: Thu, 14 Jan 2010 11:12:53 +
Juris Krumins wrote:
panic[cpu0]/th
in kmdb.
-Original Message-
From: Brian Ruthven - Sun UK
To: Juris Krumins
Cc: opensolaris-discuss@opensolaris.org
Subject: Re: [osol-discuss] OpenSolaris snv_130 panic.
Date: Thu, 14 Jan 2010 11:12:53 +
Juris Krumins wrote:
> panic[cpu0]/thread = fbc2e3a0: mutex_ent
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
> > 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
> 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 boot_archive:
Bug ID
This is not about some specific process.
All this happens when I try to boot newly created boot environment (after pkg
image-update from snv_124 to snv_130 build)
So when I boot kernel with kmdb enabled (using -kd flags in grub and manually
run kernel) I get this.
Unfortunately users using this
>Experiencing very strange behaviour with upgraded OpenSolaris machine ( from
>snv_124 to snv_130 )
>
>Machine gets panic, with the following error:
>
>trap: Unknown trap type 8 in user mode.
>
>panic[cpu0]/thread = fbc2e3a0: mutex_enter: bad mutex, lp=20
>owner=f000e987f000fea0 thread
=
Experiencing very strange behaviour with upgraded OpenSolaris machine ( from
snv_124 to snv_130 )
Machine gets panic, with the following error:
trap: Unknown trap type 8 in user mode.
panic[cpu0]/thread = fbc2e3a0: mutex_enter: bad mutex, lp=20
owner=f000e987f000fea0 thread=fbc
12 matches
Mail list logo
